HighCVE-2026-119197

    pyasn1: Quadratic-complexity denial of service in binary REAL decoding (CVE-2026-119197)

    Published Last modified Sources: Msrc Update Guide, EUVD, OSV, Hersteller, CVE.org, Ubuntu

    Share

    What is affected, what to do

    Update Pyasn1 to version 0.6.5.

    Affected
    • Pyasn1 lt *..0.6.5
    Fixed in
    • Pyasn1 0.6.5

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.5

    XIEM Effective CVSS

    Highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    7.5

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: Msrc Update Guide, EUVD, OSV, Hersteller, CVE.org, Ubuntu

    0.4 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 37.4

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    108.66 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.5 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.5
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.4 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    37.4
    High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 30 October 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-407

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    Summary

    In pyasn1 0.6.4 and earlier, decoding a binary-encoded ASN.1 REAL with a large mantissa can consume CPU time quadratic in the mantissa length. The BER, CER, and DER decoders all use the affected RealPayloadDecoder. An application is exposed when it passes attacker-controlled ASN.1 containing a REAL value to one of these decoders, either without an asn1Spec or with a schema that includes REAL. The work occurs inside decode(); the application does not need to convert, print, or otherwise use the resulting REAL object.

    This is distinct from CVE-2026-59886, which concerns converting an already-decoded REAL to a Python float. That issue was fixed in 0.6.4 and its advisory states that decoding alone does not trigger it.

    Root cause and affected components

    For binary REAL values, RealPayloadDecoder.valueDecoder in v0.6.4 builds the mantissa one octet at a time:

    p = 0
    while chunk:
        p <<= 8
        p |= chunk[0]
        chunk = chunk[1:]
    

    Each shift processes an integer that grows with the mantissa; with byte strings, each slice also copies the remaining suffix. Repeating both operations for every octet makes decoding quadratic in mantissa size. The decoder's eight-octet length-field limit does not impose a practical mantissa-size limit for the inputs demonstrated below. CER and DER reuse the BER REAL payload decoder, so all three paths reach this loop.

    The vulnerable loop is present in every available repository release tag inspected, from v0.2.1 through v0.6.4. Runtime measurements below were made on v0.6.4; older releases were checked for the loop, not benchmarked individually.

    Impact

    A comparatively small REAL value can hold a decoder worker on one CPU core for seconds or longer. The attacker must be able to supply data that the application sends to an affected decoder, and application-level input limits may reduce exposure. The demonstrated effect is CPU exhaustion during decoding; this advisory does not assert a network endpoint, unauthenticated access, or an affected downstream application by itself.

    Reproduction and evidence

    The following example uses pyasn1 0.6.4. The 0x09 tag identifies REAL; 0x80 0x00 selects a positive, base-2 binary value with a one-octet zero exponent, followed by a large mantissa. It exercises decode() only.

    import time
    
    from pyasn1.codec.ber import decoder as ber
    from pyasn1.codec.cer import decoder as cer
    from pyasn1.codec.der import decoder as der
    
    
    def real_value(mantissa_octets):
        content = b"\x80\x00" + b"\xff" * mantissa_octets
        length = len(content).to_bytes(3, "big")
        return b"\x09\x83" + length + content
    
    
    for codec in (ber, cer, der):
        for size in (50_000, 100_000, 200_000):
            substrate = real_value(size)
            started = time.process_time()
            value, rest = codec.decode(substrate)
            print(codec.__name__, size, time.process_time() - started)
            assert not rest
            assert tuple(value)[1:] == (2, 0)
    

    The original report measured the following BER CPU times on repository commit aa05757. That commit is later than the official v0.6.4 tag; the vulnerable loop is identical in the tagged release.

    Mantissa sizeReporter's BER CPU time
    50,000 octets0.328 s
    100,000 octets1.299 s
    200,000 octets6.043 s
    400,000 octets24.095 s

    The same report measured 5.645 s for a 200,000-octet mantissa through DER.

    A separate local reproduction on the official v0.6.4 tag (d43496f, CPython 3.14.8, macOS arm64) measured BER at 0.209 s, 0.884 s, and 3.451 s for 50,000, 100,000, and 200,000 mantissa octets respectively. CER and DER each took about 0.89 s at 100,000 octets. These are machine-specific measurements; the repeated near-fourfold cost for doubled input is the relevant result. Neither reproduction calls float(), str(), or prettyPrint().

    Fix

    pyasn1 0.6.5 replaces the per-octet shift and slice loop with one int.from_bytes(bytes(chunk), "big") conversion. Sign, scale, exponent, and the decoded REAL tuple are preserved. The fix is in the shared BER payload decoder and therefore covers BER, CER, and DER. A local check of the 0.6.5 candidate decoded a 200,000-octet mantissa correctly through all three codecs; the check does not establish behavior for every application using REAL.

    Workarounds

    Upgrade to pyasn1 0.6.5. Until then, reject or strictly limit attacker-controlled ASN.1 input that may contain REAL values before passing it to pyasn1. The appropriate size limit depends on the application's available CPU time and request volume.

    Source: Microsoft Security Update Guide, ENISA EUVD, OSV (Open Source Vulnerabilities), GitHub Security Advisories, cvelistv5, NVD (NIST), Ubuntu Security Notices

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    pyasn1pyasn1
    • < 0.6.5
    • 0.6.5
    pippyasn1
    • <= 0.6.4
    • 0.6.5
    pypipyasn1
    • 0.0.12a
    • 0.3.1
    • 0.6.0
    • 0.0.11a
    • 0.1.1
    • —
    • 0.3.7
    • 0.0.13b
    • 0.1.4
    • 0.4.2
    • 0.1.2
    • 0.4.8
    • 0.4.6
    • 0.3.4
    • 0.5.0
    • 0.3.3
    • 0.5.1
    • 0.6.3
    • 0.2.3
    • 0.1.5
    • 0.0.9a
    • 0.6.4
    • 0.0.13a
    • 0.2.2
    • 0.2.1
    • 0.4.7
    • 0.4.3
    • 0.4.4
    • 0.1.7
    • 0.0.13
    • 0.1.3
    • 0.3.2
    • 0.0.6a
    • 0.3.6
    • 0.0.10a
    • 0.4.5
    • 0.1.9
    • 0.6.1
    • 0.1.6
    • 0.6.2
    • 0.4.1
    • 0.3.5
    • 0.1.8
    • —
    • —
    • —
    • —
    • —
    • 0.6.5
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —

    Fixed in hardened container images

    Vendors of hardened images ship their own builds with a fix, often ahead of the distribution. This only concerns you if you use these images.

    Show all 102 entries
    Fixed in hardened container images
    Fixed in
    ChainguardChainguardaws-cli-1
    • 1.46.2-r1
    ChainguardChainguardaws-cli-1
    • 1.46.2-r1
    ChainguardChainguardbarman
    • 3.20.1-r3
    ChainguardChainguardbarman
    • 3.20.1-r3
    ChainguardChainguarddbt-bigquery
    • 1.10.3-r13
    ChainguardChainguarddbt-bigquery
    • 1.10.3-r13
    ChainguardChainguardelastic-connectors-8.19
    • 8.19.23-r8
    ChainguardChainguardelastic-connectors-8.19
    • 8.19.23-r8
    ChainguardChainguardelastic-connectors-9.5
    • 9.5.4-r7
    ChainguardChainguardelastic-connectors-9.5
    • 9.5.4-r7
    ChainguardChainguardelastic-connectors-fips-8.19
    • 8.19.23-r7
    ChainguardChainguardelastic-connectors-fips-8.19
    • 8.19.23-r7
    ChainguardChainguardelastic-connectors-fips-9.5
    • 9.5.6-r1
    ChainguardChainguardelastic-connectors-fips-9.5
    • 9.5.6-r1
    ChainguardChainguardkserve-huggingfaceserver-cuda-13.3
    • 0.21.0-r14
    ChainguardChainguardkubeflow-pipelines-apiserver
    • 2.18.0-r1
    ChainguardChainguardkubeflow-pipelines-apiserver
    • 2.18.0-r1
    ChainguardChainguardkubeflow-pipelines-apiserver-fips
    • 2.18.0-r2
    ChainguardChainguardkubeflow-pipelines-apiserver-fips
    • 2.18.0-r2
    ChainguardChainguardkubeflow-pipelines-visualization-server
    • 2.18.0-r2
    ChainguardChainguardlitellm
    • 1.106.6-r2
    ChainguardChainguardlitellm
    • 1.106.6-r2
    ChainguardChainguardlitellm-fips
    • 1.106.6-r3
    ChainguardChainguardlitellm-fips
    • 1.106.6-r3
    ChainguardChainguardlocalstack
    • 4.14.0-r37
    ChainguardChainguardlocalstack
    • 4.14.0-r37
    ChainguardChainguardmetaflow-service-fips
    • 2.6.1-r5
    ChainguardChainguardmetaflow-service-fips
    • 2.6.1-r5
    ChainguardChainguardmlflow
    • 3.17.2-r5
    ChainguardChainguardmlflow
    • 3.17.2-r5
    ChainguardChainguardmlflow-iamguarded-compat
    • 3.17.2-r5
    ChainguardChainguardmlflow-iamguarded-compat
    • 3.17.2-r5
    ChainguardChainguardnemo-gym
    • 0.5.0_rc0_git20260729-r14
    ChainguardChainguardnemo-rl-cuda-13.0
    • 0.7.0-r19
    ChainguardChainguardnemo-rl-cuda-13.0-automodel
    • 0.7.0-r19
    ChainguardChainguardnemo-rl-cuda-13.0-mcore
    • 0.7.0-r19
    ChainguardChainguardnemo-rl-cuda-13.0-sglang
    • 0.7.0-r19
    ChainguardChainguardnemo-rl-cuda-13.0-vllm
    • 0.7.0-r19
    ChainguardChainguardnemo-skills
    • 0.7.0_git20260911-r12
    ChainguardChainguardopenstack-cinder-2026.1
    • 28.1.0_git20261109-r0
    ChainguardChainguardopenstack-cinder-2026.1
    • 28.1.0_git20261109-r0
    ChainguardChainguardopenstack-cinder-2026.2
    • 29.0.1_git20261021-r4
    ChainguardChainguardopenstack-cinder-2026.2
    • 29.0.1_git20261021-r4
    ChainguardChainguardopenstack-ironic-2025.2
    • 32.1.0_git20261030-r1
    ChainguardChainguardopenstack-ironic-2025.2
    • 32.1.0_git20261030-r1
    ChainguardChainguardopenstack-ironic-2026.1
    • 35.1.0_git20261028-r4
    ChainguardChainguardopenstack-ironic-2026.1
    • 35.1.0_git20261028-r4
    ChainguardChainguardopenstack-keystone-2026.1
    • 29.0.1_git20261017-r5
    ChainguardChainguardopenstack-keystone-2026.1
    • 29.0.1_git20261017-r5
    ChainguardChainguardopenstack-keystone-2026.1-fips
    • 29.0.1_git20261017-r5
    ChainguardChainguardopenstack-keystone-2026.1-fips
    • 29.0.1_git20261017-r5
    ChainguardChainguardopenstack-keystone-2026.2
    • 30.0.1_git20261017-r5
    ChainguardChainguardopenstack-keystone-2026.2-fips
    • 30.0.1_git20261017-r5
    ChainguardChainguardopenstack-keystone-2026.2-fips
    • 30.0.1_git20261017-r5
    ChainguardChainguardopenstack-manila-2026.1
    • 22.0.1_git20261027-r4
    ChainguardChainguardopenstack-manila-2026.1
    • 22.0.1_git20261027-r4
    ChainguardChainguardopenstack-octavia-2025.2
    • 17.0.1_git20261027-r4
    ChainguardChainguardopenstack-octavia-2025.2
    • 17.0.1_git20261027-r4
    ChainguardChainguardopenstack-octavia-2026.1
    • 18.0.1_git20261028-r4
    ChainguardChainguardopenstack-octavia-2026.1
    • 18.0.1_git20261028-r4
    ChainguardChainguardopenstack-octavia-2026.2
    • 19.0.1_git20261027-r4
    ChainguardChainguardopenstack-octavia-2026.2
    • 19.0.1_git20261027-r4
    ChainguardChainguardopenstack-rally-2025.2
    • 4.1.0-r10
    ChainguardChainguardopenstack-rally-2025.2
    • 4.1.0-r10
    ChainguardChainguardpy3.12-airflow-3
    • 3.3.2-r15
    ChainguardChainguardpy3.12-airflow-3
    • 3.3.2-r15
    ChainguardChainguardpy3.13-airflow-3
    • 3.3.2-r15
    ChainguardChainguardpy3.13-airflow-3
    • 3.3.2-r15
    ChainguardChainguardpy3.14-airflow-3
    • 3.3.2-r15
    ChainguardChainguardpy3.14-airflow-3
    • 3.3.2-r15
    ChainguardChainguardsentry
    • 26.10.1-r4
    ChainguardChainguardsentry
    • 26.10.1-r4
    ChainguardChainguardsentry-fips
    • 26.10.1-r3
    ChainguardChainguardsentry-fips
    • 26.10.1-r3
    ChainguardChainguardsnuba
    • 26.10.1-r2
    ChainguardChainguardsnuba
    • 26.10.1-r2
    ChainguardChainguardsnuba-fips
    • 26.10.1-r3
    ChainguardChainguardsnuba-fips
    • 26.10.1-r3
    ChainguardChainguardsuperset-5.0
    • 5.0.0-r52
    ChainguardChainguardsuperset-5.0
    • 5.0.0-r52
    ChainguardChainguardsuperset-6.1
    • 6.1.0-r24
    ChainguardChainguardsuperset-6.1
    • 6.1.0-r24
    ChainguardChainguardsuperset-fips-6.1
    • 6.1.0-r19
    ChainguardChainguardsuperset-fips-6.1
    • 6.1.0-r19
    ChainguardChainguardvllm-openai-cuda-12.9
    • 0.31.0-r3
    ChainguardChainguardvllm-openai-cuda-12.9
    • 0.31.0-r3
    ChainguardChainguardvllm-openai-cuda-13.0
    • 0.32.0-r3
    ChainguardChainguardvllm-openai-cuda-13.0
    • 0.32.0-r3
    ChainguardChainguardwazuh-manager-framework
    • 4.14.9-r6
    ChainguardChainguardwazuh-manager-framework
    • 4.14.9-r6
    ChainguardChainguardwazuh-manager-framework-fips
    • 4.14.9-r7
    ChainguardChainguardwazuh-manager-framework-fips
    • 4.14.9-r7
    ChainguardWolfikubeflow-pipelines-apiserver
    • 2.18.0-r1
    ChainguardWolfikubeflow-pipelines-apiserver
    • 2.18.0-r1
    ChainguardWolfikubeflow-pipelines-visualization-server
    • 2.18.0-r2
    ChainguardWolfisuperset-6.1
    • 6.1.0-r24
    ChainguardWolfisuperset-6.1
    • 6.1.0-r24
    CleanStartCleanStartapache-superset
    • 6.1.0-r8
    CleanStartCleanStartlitellm-database
    • 1.97.1-r1
    EchoEchopyasn1
    • 0.6.1-1+deb13u3+e2
    EchoEcho:PyPIpyasn1
    • 0.6.3+echo.1
    Root.ioPyPIpyasn1
    • 0.5.1+aikido.5
    • 0.6.1+aikido.9
    • 0.6.2+aikido.7
    • 0.6.4+aikido.2
    • 0.6.4+aikido.3

    Source: OSV.dev, licensed CC BY 4.0.

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxubuntupyasn1bionic
    Linuxubuntupyasn1focal
    Linuxubuntupyasn1jammy
    Linuxubuntupyasn1noble
    Linuxubuntupyasn1resolute
    Linuxubuntupyasn1stonking
    Linuxubuntupyasn1trusty
    Linuxubuntupyasn1xenial

    Weakness classes (CWE)

    • CWE-407Inefficient Algorithmic Complexity

      Class

      An algorithm in a product has an inefficient worst-case computational complexity that may be detrimental to system performance and can be triggered by an attacker, typically using crafted manipulations that ensure that the worst case is being reached.

      Entry at MITRE CWE-407

    References & sources

    • github.compyasn1/pyasn1/commit/ce3ec3390784780a530047e0e77be5ff457636a4x_refsource_MISC, web, euvd
    • github.compyasn1/pyasn1/pull/132x_refsource_MISC, web, euvd
    • github.compyasn1/pyasn1/releases/tag/v0.6.5x_refsource_MISC, web, euvd
    • github.compyasn1/pyasn1/security/advisories/GHSA-mm57-4v3p-rchxx_refsource_CONFIRM, web, euvd
    • NVD (NIST)vuln/detail/CVE-2026-119197advisory
    • github.compyasn1/pyasn1package

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: none known, automatable: yes

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentadded
      —
      {"id":"CVE-2026-119197","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-10-30T15:47:11.257992Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. ReceivedGitHub

      Show 8 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      pyasn1 is a generic ASN.1 library for Python. Prior to 0.6.5, binary REAL decoding builds a large mantissa one octet at a time by shifting a growing integer and slicing the remaining byte string. Attacker-controlled ASN.1 includes a binary-encoded REAL with a large mantissa and reaches BER, CER, or DER decode(), with or without a schema containing REAL. RealPayloadDecoder.valueDecoder repeatedly performs a left shift, OR, and suffix copy for every mantissa octet, making decode time quadratic in mantissa length. A comparatively small REAL value can hold a decoding worker on one CPU core for seconds or longer and cause availability loss. This issue is fixed in version 0.6.5.
      CVSSadded
      —
      AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
      Weakness type (CWE)added
      —
      CWE-407
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/119xxx/CVE-2026-119197.json">CVE-2026-119197</a>
      Referenceadded
      —
      https://github.com/pyasn1/pyasn1/commit/ce3ec3390784780a530047e0e77be5ff457636a4
      Referenceadded
      —
      https://github.com/pyasn1/pyasn1/pull/132
      Referenceadded
      —
      https://github.com/pyasn1/pyasn1/releases/tag/v0.6.5
      Referenceadded
      —
      https://github.com/pyasn1/pyasn1/security/advisories/GHSA-mm57-4v3p-rchx

      Source identifier: security-advisories@github.com

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-119197
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-119197"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-119197.svg?lang=en" alt="CVE-2026-119197 – NEOSEC Intel" height="20"></a>