CVE-2026-59884

Public on

Last Modified: UTC

Moderate Moderate severity What does this mean?
5.9 CVSS v3 Score Breakdown

Description

A flaw was found in pyasn1, a generic ASN.1 library for Python. The Basic Encoding Rules (BER) decoder, used by CER and DER codecs, processes long-form tags by accumulating continuation octets without an upper bound. A remote attacker can exploit this by providing a specially crafted input, leading to the construction of an arbitrarily large integer. This can cause the CPU cost to grow quadratically, resulting in a Denial of Service (DoS) for any application decoding untrusted BER, CER, or DER input.

Statement

A flaw was found in pyasn1's BER decoder. The decoder parses long-form tags by accumulating continuation octets without an upper bound, allowing crafted input to force construction of an arbitrarily large integer with quadratic CPU cost. On Python 3.11+, this can also trigger unhandled ValueError exceptions. Exploitation requires that an application passes untrusted BER, CER, or DER input directly to the pyasn1 decoder — pyasn1 is a library and does not independently accept network input. Many common uses of pyasn1 involve parsing trusted certificates or local configuration and are not exposed to this flaw. The realistic impact is a denial-of-service of the consuming Python process, with automatic recovery in typical service deployments.

Mitigation

Update to pyasn1 version 0.6.4 or later when available for your product stream. The impact is limited to availability (denial of service) — an attacker cannot access or modify data. Applications that do not process untrusted ASN.1/BER input are at reduced risk.

Additional information

External References

Affected Packages and Issued Red Hat Security Errata

Unless explicitly stated as not affected, all previous versions of packages in any minor update stream of a product listed here should be assumed vulnerable, although may not have been subject to full analysis.

Products / Services Components State Errata
Red Hat AI Inference Server 3.3 rhaiis/model-opt-cuda-rhel9 Fixed RHSA-2026:59518
Red Hat Enterprise Linux AI 3.3 rhelai3/disk-image-cuda-rhel9 Fixed This content is not included.RHSA-2026:62335
Red Hat Enterprise Linux AI 3.3 rhelai3/bootc-aws-cuda-rhel9 Fixed This content is not included.RHSA-2026:62336
Red Hat Enterprise Linux AI 3.3 rhelai3/bootc-azure-cuda-rhel9 Fixed This content is not included.RHSA-2026:62336
Red Hat Enterprise Linux AI 3.3 rhelai3/bootc-cuda-rhel9 Fixed This content is not included.RHSA-2026:62336
Red Hat Enterprise Linux AI 3.3 rhelai3/bootc-gcp-cuda-rhel9 Fixed This content is not included.RHSA-2026:62336
Red Hat Hardened Images jaeger-main Fixed RHSA-2026:40236
Red Hat OpenShift AI 3.4 rhoai/odh-mlflow-rhel9 Fixed This content is not included.RHSA-2026:60520
Red Hat OpenShift AI 3.4 rhoai/odh-model-registry-job-async-upload-rhel9 Fixed This content is not included.RHSA-2026:60520
Red Hat OpenShift AI 3.4 rhoai/odh-pipeline-runtime-datascience-cpu-py312-rhel9 Fixed This content is not included.RHSA-2026:60520

Common Vulnerability Scoring System (CVSS) Score Details

Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authorities (CNA) source for its products and services (see Red Hat classifications ).

CVSS v3 Score Breakdown

Red Hat NVD cve.org
CVSS v3 Base Score 5.9 N/A 7.5
Attack Vector Network N/A Network
Attack Complexity High N/A Low
Privileges Required None N/A None
User Interaction None N/A None
Scope Unchanged N/A Unchanged
Confidentiality Impact None N/A None
Integrity Impact None N/A None
Availability Impact High N/A High

CVSS v3 Vector

Red Hat CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

cve.org CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Red Hat CVSS v3 Score Explanation

Adjusted from upstream AC:L (7.5) to AC:H (5.9). pyasn1 is a library, not a network service. Exploitation requires that the consuming application passes untrusted BER/CER/DER input to the pyasn1 decoder, which is not universally the case — many uses involve parsing trusted certificates or local configuration.

Frequently Asked Questions

Why is Red Hat's CVSS v3 score or Impact different from other vendors?

 For open source software shipped by multiple vendors, the CVSS base scores may vary for each vendor's version depending on the version they ship, how they ship it, the platform, and even how the software is compiled. This makes scoring of vulnerabilities difficult for third-party vulnerability databases such as NVD that only provide a single CVSS base score for each vulnerability. Red Hat scores reflect how a vulnerability affects our products specifically.

For more information, see https://access.redhat.com/solutions/762393.

My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
  • "Under investigation" doesn't necessarily mean that the product is affected by this vulnerability. It only means that our Analysis Team is still working on determining whether the product is affected and how it is affected.
  • "Affected" means that our Analysis Team has determined that this product is affected by this vulnerability and might release a fix to address this in the near future.

What can I do if my product is listed as "Will not fix"?

 A "will not fix" status means that a fix for an affected product version is not planned or not possible due to complexity, which may create additional risk.

Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
  • Upgrade to a supported product version that includes a fix for this vulnerability (recommended).
  • Apply a mitigation (if one exists).
  • Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.

What can I do if my product is listed as "Fix deferred"?

 A deferred status means that a fix for an affected product version is not guaranteed due to higher-priority development work.

Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
  • Apply a mitigation (if one exists).
  • Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
  • Red Hat Engineering focuses on addressing high-priority issues based on their complexity or limited lifecycle support. Therefore, lower-priority issues will not receive immediate fixes.

What is a mitigation?

 A mitigation is an action that can be taken to reduce the impact of a security vulnerability, without deploying any fixes.

I have a Red Hat product but it is not in the above list, is it affected?

 The listed products were found to include one or more of the components that this vulnerability affects. These products underwent a thorough evaluation to determine their affectedness by this vulnerability. Note that layered products (such as container-based offerings) that consume affected components from any of the products listed in this table may be affected and are not represented.

Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?

 In order to maintain code stability and compatibility, Red Hat usually does not rebase packages to entirely new versions. Instead, we backport fixes and new features to an older version of the package we distribute. This can result in some security scanners that only consider the package version to report the package as vulnerable. To avoid this, we suggest that you use an approved vulnerability scanner from our This content is not included.Red Hat Vulnerability Scanner Certification program.

My product is listed as "Out of Support Scope". What does this mean?

 When a product is listed as "Out of Support Scope", it means a vulnerability with the impact level assigned to this CVE is no longer covered by its current support lifecycle phase. The product has been identified to contain the impacted component, but analysis to determine whether it is affected or not by this vulnerability was not performed. The product should be assumed to be affected. Customers are advised to apply any mitigation options documented on this page, consider removing or disabling the impacted component, or upgrade to a supported version of the product that has an update available.