{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-119196 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-119196 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-119196 is a high-severity vulnerability in pyasn1, published on 29 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-119196 and fix it if it is affected.\n\nWhat it is: CVE-2026-119196 is a high-severity vulnerability in pyasn1, published on 29 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-119196 in the wild and no public exploit code.\n\nAffected product: pyasn1. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-119196/ (Markdown: https://insights.sbomify.com/CVE-2026-119196/index.md)","id":"CVE-2026-119196","markdown":"https://insights.sbomify.com/CVE-2026-119196/index.md","name":"CVE-2026-119196","record":{"aliases":[],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-407","name":"Inefficient Algorithmic Complexity"}],"description":"pyasn1 is a generic ASN.1 library for Python. Prior to 0.6.5, constructed BIT STRING decoding repeatedly shifts and copies the complete bit value accumulated from earlier fragments. Attacker-controlled BER or CER input contains many constructed BIT STRING fragments; schema-driven DER also accepts a definite-length constructed BIT STRING. BitStringPayloadDecoder repeatedly calls BitString.fromOctetString with the prior bitString as prepend, shifting an ever-growing SizedInteger for each fragment and causing quadratic work. Large fragmented values can exhaust CPU during decode() without requiring later conversion or formatting. This issue is fixed in version 0.6.5.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"pyasn1: Quadratic CPU consumption in constructed BIT STRING decoding","id":"CVE-2026-119196","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"pyasn1: Quadratic-complexity denial of service in binary REAL decoding","id":"CVE-2026-119197"},"packages":[],"prev":{"headline":"pyasn1: Quadratic-time denial of service in constructed string and indefinite-length ANY decoding","id":"CVE-2026-119195"},"products":["pyasn1"],"published":"2026-10-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-29","vendors":["pyasn1"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-119196/"}