CVE-2026-30922

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-03-17. The CNA's CVSS baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Elevated

Also known asEUVD-2026-12747 (ENISA EUVD) · GHSA-jr27-m4p2-rc6r (GitHub Security Advisories) · PYSEC-2026-2263 (OSV.dev)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.8%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. Prior to 0.6.3, the pyasn1 library is vulnerable to a Denial of Service (DoS) attack caused by uncontrolled recursion when decoding ASN.1 data with deeply nested structures. An attacker can supply a crafted payload containing thousands of nested SEQUENCE (0x30) or SET (0x31) tags with "Indefinite Length" (0x80) markers. This forces the decoder to recursively call itself until the Python interpreter crashes with a RecursionError or consumes all available memory (OOM), crashing the host application. This is a distinct vulnerability from CVE-2026-23490 (which addressed integer overflows in OID decoding). The fix for CVE-2026-23490 (MAX_OID_ARC_CONTINUATION_OCTETS) does not mitigate this recursion issue. Version 0.6.3 fixes this specific issue.

CVSS v3
7.5
EG Score
7.5HIGHmedium 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.8%
EPSS %ILE
58th
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.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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

March 18, 2026

Last Modified

September 17, 2026

Advisory Details (4)

Auto-updated May 1, 2026
Patch available. Sources: github.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4557-1] pyasn1 security update

https://lists.debian.org/debian-lts-announce/2026/05/msg00001.html
Web page

oss-security - [CVE-2026-30922] Denial of Service in pyasn1 via Unbounded Recursion

http://www.openwall.com/lists/oss-security/2026/03/20/4
GitHub advisoryMentions a patch (unverified)

Denial of Service in pyasn1 via Unbounded Recursion · Advisory · pyasn1/pyasn1 · GitHub

https://github.com/pyasn1/pyasn1/security/advisories/GHSA-jr27-m4p2-rc6r
Web page

Merge commit from fork · pyasn1/pyasn1@25ad481 · GitHub

https://github.com/pyasn1/pyasn1/commit/25ad481c19fdb006e20485ef3fc2e5b3eff30ef0

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17881858992026-09-08redhat
redhatrhmtc/openshift-migration-hook-runner-rhel8:17839317222026-07-20redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17824716972026-07-09redhat
redhatautomation-controller-0:4.7.12-1.el9ap2026-06-09redhat
redhatautomation-controller-0:4.6.29-2.el9ap2026-06-09redhat
redhatfence-agents-0:4.10.0-86.el9_6.172026-06-04redhat
redhatfence-agents-0:4.10.0-62.el9_4.252026-06-03redhat
redhatfence-agents-0:4.10.0-43.el9_2.222026-06-03redhat
redhatresource-agents-0:4.9.0-16.el8_6.222026-06-01redhat
redhatresource-agents-0:4.1.1-90.el8_4.252026-06-01redhat
redhatresource-agents-0:4.9.0-40.el8_8.192026-06-01redhat
redhatfence-agents-0:4.2.1-89.el8_6.222026-06-01redhat
redhatfence-agents-0:4.2.1-65.el8_4.282026-06-01redhat
redhatfence-agents-0:4.2.1-112.el8_8.172026-05-26redhat
redhatrhoai/odh-kserve-storage-initializer-rhel9:17782634072026-05-20redhat
redhatquay/quay-rhel9:17792040862026-05-19redhat
redhatfence-agents-0:4.16.0-21.el10_2.12026-05-19redhat
redhatfence-agents-0:4.10.0-110.el9_8.22026-05-19redhat
redhatrhelai3/bootc-rocm-rhel9:17786661242026-05-14redhat
redhatfence-agents-0:4.16.0-5.el10_0.92026-05-13redhat
redhatrhaiis/vllm-rocm-rhel9:17782445312026-05-11redhat
redhatresource-agents-0:4.9.0-54.el8_10.332026-05-06redhat
redhatfence-agents-0:4.16.0-13.el10_1.42026-05-06redhat
redhatfence-agents-0:4.10.0-98.el9_7.132026-05-06redhat
redhatstf/smart-gateway-rhel9-operator:17774361502026-05-06redhat
redhatansible-automation-platform-25/platform-resource-runner-rhel8:17774022642026-05-04redhat
redhatpython3.12-pyasn1-0:0.6.3-1.el9ap2026-05-04redhat
redhatansible-automation-platform-26/lightspeed-rhel9:17773872422026-05-04redhat
redhatfence-agents-0:4.2.1-129.el8_10.252026-04-30redhat
pippyasn1 @ 0.6.3 (fixes <= 0.6.2)—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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
pyasn10.4.8-1, 0.4.8-1+deb11u1
  • every version up to 0.4.8-1+deb11u2: fixed in 0.4.8-1+deb11u2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
pyasn10.4.8-3, 0.4.8-3+deb12u1
  • every version up to 0.4.8-3+deb12u2: fixed in 0.4.8-3+deb12u2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
pyasn10.6.1-1, 0.6.1-1+deb13u1
  • every version up to 0.6.1-1+deb13u2: fixed in 0.6.1-1+deb13u2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
pyasn10.6.1-1, 0.6.2-1, 0.6.2-1~bpo13+1
  • every version up to 0.6.3-1: fixed in 0.6.3-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
pyasn10.0.10a ... 0.6.2 (40 versions)
  • every version up to 0.6.3: fixed in 0.6.3
—

Weakness Classification(2)

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

Additional Vendor Advisories

(12)

Data Freshness Timeline

(refreshed 8× in last 7d / 37× 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.

Showing the most recent 100 of 318 rows on record for this CVE, as 97 entries (3 repeats merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 218 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 22:54 UTCEchelonGraph re-scored
  2. 2026-11-12 22:54 UTCGHSA enrichmentGHSA-jr27-m4p2-rc6r · GitHub severity HIGH · GitHub CVSS 7.5
  3. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  4. 2026-11-11 16:39 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  5. 2026-11-10 16:43 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  6. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  7. 2026-11-08 16:39 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  8. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  9. 2026-11-06 16:37 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  10. 2026-11-06 08:18 UTCEchelonGraph re-scored
  11. 2026-11-06 08:18 UTCVendor advisory
  12. 2026-11-06 08:18 UTCGHSA enrichmentGHSA-jr27-m4p2-rc6r · GitHub severity HIGH · GitHub CVSS 7.5
  13. 2026-11-05 16:37 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  14. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  15. 2026-11-03 16:47 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  16. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  17. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  18. 2026-11-01 07:55 UTCGHSA enrichmentGHSA-jr27-m4p2-rc6r · GitHub severity HIGH · GitHub CVSS 7.5
  19. 2026-11-01 07:55 UTCEchelonGraph re-scored
  20. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  21. 2026-10-30 18:53 UTCEchelonGraph re-scored
  22. 2026-10-30 18:53 UTCVendor advisory
  23. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  24. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  25. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
Show 72 more
  1. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  2. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  3. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  4. 2026-10-25 14:36 UTCEchelonGraph re-scored
  5. 2026-10-24 16:32 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  6. 2026-10-24 05:28 UTCEchelonGraph re-scored
  7. 2026-10-24 05:28 UTCVendor advisory
  8. 2026-10-23 16:31 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  9. 2026-10-22 16:34 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  10. 2026-10-21 16:32 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  11. 2026-10-20 16:33 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  12. 2026-10-19 16:31 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  13. 2026-10-18 16:31 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  14. 2026-10-18 03:49 UTCEchelonGraph re-scored
  15. 2026-10-17 16:33 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  16. 2026-10-17 16:02 UTCEchelonGraph re-scored
  17. 2026-10-17 16:02 UTCVendor advisory
  18. 2026-10-16 16:41 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  19. 2026-10-15 16:31 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  20. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  21. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  22. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  23. 2026-10-12 16:15 UTCEchelonGraph re-scored
  24. 2026-10-11 19:57 UTCEchelonGraph re-scored
  25. 2026-10-11 17:11 UTCEchelonGraph re-scored
  26. 2026-10-11 14:40 UTCEchelonGraph re-scored
  27. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  28. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  29. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  30. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  31. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  32. 2026-10-07 06:24 UTCOSV refresh
  33. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  34. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  35. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  36. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  37. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  38. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  39. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  40. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  41. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  42. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  43. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  44. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  45. 2026-09-17 12:11 UTCEchelonGraph re-scored
  46. 2026-09-17 12:11 UTCVendor advisory
  47. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  48. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  49. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  50. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  51. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  52. 2026-09-10 13:22 UTCEchelonGraph re-scored
  53. 2026-09-10 13:22 UTCVendor advisory
  54. 2026-09-10 12:28 UTCEchelonGraph re-scored
  55. 2026-09-10 12:28 UTCVendor advisory
  56. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  57. 2026-09-09 13:42 UTCEchelonGraph re-scored
  58. 2026-09-09 13:42 UTCVendor advisory
  59. 2026-09-09 12:41 UTCEchelonGraph re-scored
  60. 2026-09-09 12:41 UTCVendor advisory
  61. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  62. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  63. 2026-09-07 14:03 UTCEchelonGraph re-scored
  64. 2026-09-07 14:03 UTCVendor advisory
  65. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  66. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  67. 2026-09-03 12:29 UTCEchelonGraph re-scored
  68. 2026-09-03 12:29 UTCVendor advisory
  69. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  70. 2026-09-02 13:43 UTCEchelonGraph re-scored
  71. 2026-09-02 13:43 UTCVendor advisory
  72. 2026-09-02 12:39 UTCEchelonGraph re-scored

Frequently asked(5)

What is CVE-2026-30922?
CVE-2026-30922 is a high-severity vulnerability; its CVE record was published on March 18, 2026. pyasn1 is a generic ASN.1 library for Python. Prior to 0.6.3, the pyasn1 library is vulnerable to a Denial of Service (DoS) attack caused by uncontrolled recursion when decoding ASN.1 data with deeply nested structures. An attacker can supply a crafted payload containing thousands of nested…
When was the CVE record for CVE-2026-30922 published?
The CVE record for CVE-2026-30922 was published on March 18, 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 September 17, 2026; the record at its source may have been updated since.
Is CVE-2026-30922 actively exploited?
CVE-2026-30922 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-30922?
CVE-2026-30922 has a CVSS base score of 7.5 (the CNA's own assessment, by github_m; NVD's own analysis pending).
How do I remediate CVE-2026-30922?
A fix for CVE-2026-30922 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-30922 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-30922

Explore →

Is Your Infrastructure Affected by CVE-2026-30922?

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