CVE-2026-119194

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-10-30. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-113350 (ENISA EUVD) · GHSA-fm9c-5rcf-2q5p (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

pyasn1 is a generic ASN.1 library for Python. From 0.3.3 until 0.6.5, schemaless container decoding stores every decoded component's TagSet in a growing set even though only one-versus-multiple tag types must be distinguished. Attacker-controlled BER, CER, or DER input contains many distinct long tag IDs whose TagSet hashes collide. Each later set insertion compares against an increasing number of earlier colliding tags in ConstructedPayloadDecoderBase._decodeComponentsSchemaless, producing quadratic CPU work while decoded values and order remain valid. Repeated inputs can exhaust decoder CPU and reduce service availability. This issue is fixed in version 0.6.5.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
37th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-09). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 29, 2026

Last Modified

November 3, 2026

Advisory Details (4)

Auto-updated Oct 29, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github_commit, github_release, github.
GitHub release Patch Available

Release 0.6.5

Patch available: pyasn1/pyasn1 v0.6.5

https://github.com/pyasn1/pyasn1/releases/tag/v0.6.5
GitHub commit Patch Available

commit a36e3a3d0671 (pyasn1/pyasn1)

Patch available: pyasn1/pyasn1 v0.6.5 (contains commit a36e3a3d0671)

https://github.com/pyasn1/pyasn1/commit/a36e3a3d067148d26197a6b7221fd0e2cde9cc86
GitHub pull request Patch Available

Prepare release 0.6.5

Patch available: pyasn1/pyasn1 v0.6.5 (PR #132 merged 2026-10-27)

https://github.com/pyasn1/pyasn1/pull/132
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Quadratic CPU use in schemaless BER/CER/DER container decoding · Advisory · pyasn1/pyasn1 · GitHub

https://github.com/pyasn1/pyasn1/security/advisories/GHSA-fm9c-5rcf-2q5p

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhtas/model-transparency-rhel9:17936965782026-11-04redhat
pippyasn1 @ 0.6.5 (fixes >= 0.3.3, < 0.6.5)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
pyasn10.4.8-3 ... 0.6.5-1 (14 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
pyasn10.6.1-1 ... 0.6.5-1 (10 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
pyasn10.6.1-1 ... 0.6.4-1~bpo13+1 (6 versions)
  • every version up to 0.6.5-1: fixed in 0.6.5-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
pyasn10.3.3 ... 0.6.4 (20 versions)
  • 0.3.3 up to 0.6.5: fixed in 0.6.5
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 25× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  2. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  3. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  4. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  5. 2026-11-10 08:29 UTCEchelonGraph re-scored
  6. 2026-11-10 08:29 UTCVendor advisory
  7. 2026-11-10 08:29 UTCGHSA enrichmentGHSA-fm9c-5rcf-2q5p · GitHub severity HIGH · GitHub CVSS 7.5
  8. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  9. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  10. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  11. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  12. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  13. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  14. 2026-11-03 17:28 UTCEchelonGraph re-scored
  15. 2026-11-03 17:28 UTCVendor advisory
  16. 2026-11-03 17:28 UTCGHSA enrichmentGHSA-fm9c-5rcf-2q5p · GitHub severity HIGH · GitHub CVSS 7.5
  17. 2026-11-03 17:26 UTCEchelonGraph re-scored
  18. 2026-11-03 17:26 UTCVendor advisory
  19. 2026-11-03 17:26 UTCGHSA enrichmentGHSA-fm9c-5rcf-2q5p · GitHub severity HIGH · GitHub CVSS 7.5
  20. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  21. 2026-11-03 16:28 UTCEchelonGraph re-scored
  22. 2026-11-03 16:28 UTCVendor advisory
  23. 2026-11-03 16:28 UTCGHSA enrichmentGHSA-fm9c-5rcf-2q5p · GitHub severity HIGH · GitHub CVSS 7.5
  24. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  25. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
Show 7 more
  1. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  2. 2026-10-30 17:26 UTCEchelonGraph re-scored
  3. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  4. 2026-10-29 20:26 UTCEchelonGraph re-scored
  5. 2026-10-29 20:02 UTCENISA EUVD ID recordedEUVD-2026-113350 · Source: ENISA EUVD
  6. 2026-10-29 19:42 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
  7. 2026-10-29 19:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-119194?
CVE-2026-119194 is a high-severity vulnerability; its CVE record was published on October 29, 2026. pyasn1 is a generic ASN.1 library for Python. From 0.3.3 until 0.6.5, schemaless container decoding stores every decoded component's TagSet in a growing set even though only one-versus-multiple tag types must be distinguished. Attacker-controlled BER, CER, or DER input contains many distinct long…
When was the CVE record for CVE-2026-119194 published?
The CVE record for CVE-2026-119194 was published on October 29, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 3, 2026; the record at its source may have been updated since.
Is CVE-2026-119194 actively exploited?
CVE-2026-119194 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-119194?
CVE-2026-119194 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-119194?
A fix for CVE-2026-119194 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-119194 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-119194

Explore →

Is Your Infrastructure Affected by CVE-2026-119194?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.