VulnerabilityPublished 11 Nov 2026

CVE-2026-119194: python-pyasn1 security update

Affects python-pyasn1Source GCVE Database

Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-119194· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 0.5.1-5.oe2403sp3 soon.

Data as of 11 Nov 2026, 14:49 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	7.5

Patch: Available – fixed in 0.5.1-5.oe2403sp3

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade python-pyasn1 to 0.5.1-5.oe2403sp3.

Affected software

Product	Affected	Fixed in
openEuler 24.03-LTS-SP3python-pyasn1`pkg:rpm/openEuler/python-pyasn1&distro=openEuler-24.03-LTS-SP3`Other threats	Affected <0.5.1-5.oe2403sp3	Fixed in 0.5.1-5.oe2403sp3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade python-pyasn1 to version 0.6.5 or later, where these denial-of-service vulnerabilities have been fixed. No other mitigations are required as the issues are resolved in the fixed version.

Description

Multiple denial-of-service vulnerabilities exist in the python-pyasn1 library prior to version 0.6.5. These flaws involve quadratic CPU time complexity during decoding of specially crafted ASN.1 data with long tag IDs, fragmented constructed strings, BIT STRINGs, and binary REAL values. An attacker can exploit these issues by sending malicious BER, CER, or DER encoded inputs to exhaust CPU resources and reduce service availability. No confidentiality or integrity impacts are reported. The issues are fixed in version 0.6.5.

Impact

An attacker can cause denial of service by sending specially crafted ASN.1 BER, CER, or DER encoded data that triggers quadratic CPU consumption during decoding. This can exhaust CPU resources on the decoding system, reducing service availability. There is no impact on confidentiality or integrity of data. The vulnerabilities affect availability only.

Summary

The python-pyasn1 library versions before 0.6.5 contain several denial-of-service vulnerabilities caused by inefficient decoding algorithms that exhibit quadratic time complexity when processing attacker-controlled ASN.1 encoded data. Specifically, schemaless container decoding stores every decoded component's TagSet in a growing set, causing quadratic CPU work when many distinct long tag IDs with colliding hashes are present (CVE-2026-119194). Constructed string and indefinite-length ANY decoding repeatedly concatenates fragments, causing quadratic copying work (CVE-2026-119195). Constructed BIT STRING decoding repeatedly shifts and copies an ever-growing bit value, leading to quadratic CPU usage (CVE-2026-119196). Binary REAL decoding builds a large mantissa octet-by-octet with repeated shifts and copies, resulting in quadratic decode time (CVE-2026-119197). These issues can exhaust CPU resources during decoding, causing denial of service without affecting confidentiality or integrity. All these vulnerabilities are fixed in pyasn1 version 0.6.5.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Nov 2026, 14:49 UTC

Technical details

References

Community reviews

Related threats