CVE-2026-59884

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (48th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week
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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

pyasn1 is a generic ASN.1 library for Python. Prior to 0.6.4, the BER decoder shared by the CER and DER codecs parses long-form tags by accumulating continuation octets without an upper bound on the tag ID size, allowing a crafted input to force construction of an arbitrarily large integer with CPU cost growing quadratically and to trigger unhandled ValueError exceptions in Python 3.11+ error formatting paths. Any application decoding untrusted BER, CER, or DER input is affected. This issue is fixed in version 0.6.4.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (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.6%
EPSS %ILE
48th
KEV
Not listed

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 none (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.

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

July 14, 2026

Last Modified

July 21, 2026

Advisory Details (3)

Auto-updated Jul 15, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

pyasn1 BER/CER/DER decoder denial of service via unbounded long-form tag IDs · Advisory · pyasn1/pyasn1 · GitHub

Affected: 0.6.4. Long-form tag IDs are now limited to 20 octets (140-bit tag IDs, matching

https://github.com/pyasn1/pyasn1/security/advisories/GHSA-m4p7-r5rc-7g4j
GitHub release Patch Available

Release 0.6.4

Patch available: pyasn1/pyasn1 v0.6.4

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

commit 628e36ecbb52 (pyasn1/pyasn1)

Patch available: pyasn1/pyasn1 v0.6.4 (contains commit 628e36ecbb52)

https://github.com/pyasn1/pyasn1/commit/628e36ecbb5277a3f01572ce418ef54271b165a5

Vendor Advisories for CVE-2026-59884(8)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython3-pyasn1 (0.6.3-1ubuntu0.1) @ resolute2026-10-13ubuntu
redhatrhoai/odh-mlflow-rhel9:17896536062026-09-30redhat
redhatrhelai3/disk-image-cuda-rhel9:17882903142026-09-01redhat
redhatrhelai3/bootc-gcp-cuda-rhel9:17882739772026-09-01redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17870735932026-08-27redhat
redhatrhaiis/model-opt-cuda-rhel9:17876011592026-08-25redhat
redhatjaeger-main-2.19.0-1.1.hum12026-07-15redhat

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

(6 across 5 ecosystems)
PyPI(2)
PackageVulnerable rangeFix by version rangeDependents
pyasn10.0.10a ... 0.6.3 (41 versions)
  • every version up to 0.6.4: fixed in 0.6.4
—
pyssn1—0.6.4 (one range)—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
pyasn10.4.8-1 ... 0.6.4-1 (14 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
pyasn10.4.8-3, 0.4.8-3+deb12u1, 0.4.8-3+deb12u2
  • every version up to 0.4.8-3+deb12u3: fixed in 0.4.8-3+deb12u3
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
pyasn10.6.1-1, 0.6.1-1+deb13u1, 0.6.1-1+deb13u2
  • every version up to 0.6.1-1+deb13u3: fixed in 0.6.1-1+deb13u3
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
pyasn10.6.1-1, 0.6.2-1, 0.6.2-1~bpo13+1, 0.6.3-1, 0.6.4-1~bpo13+1
  • every version up to 0.6.4-1: fixed in 0.6.4-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 13× in last 7d / 42× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 100 of 224 refreshes on record for this CVE.

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. None are among the latest 100 rows. The 124 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  2. 2026-10-13 15:48 UTCEG score recompute
  3. 2026-10-13 15:48 UTCVendor advisory
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  5. 2026-10-12 15:52 UTCEG score recompute
  6. 2026-10-11 19:36 UTCEG score recompute
  7. 2026-10-11 16:51 UTCEG score recompute
  8. 2026-10-11 14:13 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  15. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  17. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  18. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  19. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  20. 2026-10-01 13:23 UTCEG score recompute
  21. 2026-10-01 13:23 UTCVendor advisory
  22. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  23. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  24. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  25. 2026-09-28 09:20 UTCEG score recompute
Show 75 more
  1. 2026-09-28 09:20 UTCVendor advisory
  2. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  3. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  4. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  5. 2026-09-24 09:51 UTCEG score recompute
  6. 2026-09-24 09:51 UTCVendor advisory
  7. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  8. 2026-09-23 03:55 UTCEG score recompute
  9. 2026-09-23 03:55 UTCVendor advisory
  10. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  11. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  12. 2026-09-18 04:53 UTCEG score recompute
  13. 2026-09-18 04:53 UTCVendor advisory
  14. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  15. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  16. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  17. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  18. 2026-09-14 11:06 UTCVendor advisory
  19. 2026-09-13 23:27 UTCEG score recompute
  20. 2026-09-13 23:27 UTCVendor advisory
  21. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  22. 2026-09-13 07:53 UTCEG score recompute
  23. 2026-09-13 07:53 UTCVendor advisory
  24. 2026-09-12 13:24 UTCVendor advisory
  25. 2026-09-12 01:45 UTCEG score recompute
  26. 2026-09-12 01:45 UTCVendor advisory
  27. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  28. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  29. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  30. 2026-09-08 01:44 UTCEG score recompute
  31. 2026-09-08 01:44 UTCVendor advisory
  32. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  33. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  34. 2026-09-06 13:46 UTCVendor advisory
  35. 2026-09-05 21:17 UTCEG score recompute
  36. 2026-09-05 21:17 UTCVendor advisory
  37. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  38. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  39. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  40. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  41. 2026-08-31 05:38 UTCEG score recompute
  42. 2026-08-31 05:38 UTCVendor advisory
  43. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  44. 2026-08-30 16:57 UTCVendor advisory
  45. 2026-08-30 05:19 UTCEG score recompute
  46. 2026-08-30 05:19 UTCVendor advisory
  47. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  48. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  49. 2026-08-28 02:01 UTCEG score recompute
  50. 2026-08-28 02:01 UTCVendor advisory
  51. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  52. 2026-08-27 13:48 UTCVendor advisory
  53. 2026-08-27 01:25 UTCEG score recompute
  54. 2026-08-27 01:25 UTCVendor advisory
  55. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  56. 2026-08-26 13:48 UTCVendor advisory
  57. 2026-08-26 01:43 UTCEG score recompute
  58. 2026-08-26 01:43 UTCVendor advisory
  59. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  60. 2026-08-25 09:20 UTCVendor advisory
  61. 2026-08-24 21:43 UTCEG score recompute
  62. 2026-08-24 21:43 UTCVendor advisory
  63. 2026-08-24 09:55 UTCEG score recompute
  64. 2026-08-24 09:55 UTCVendor advisory
  65. 2026-08-23 22:17 UTCVendor advisory
  66. 2026-08-23 10:25 UTCEG score recompute
  67. 2026-08-23 10:25 UTCVendor advisory
  68. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  69. 2026-08-22 22:43 UTCVendor advisory
  70. 2026-08-22 11:06 UTCEG score recompute
  71. 2026-08-22 11:06 UTCVendor advisory
  72. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  73. 2026-08-21 23:29 UTCVendor advisory
  74. 2026-08-21 11:48 UTCVendor advisory
  75. 2026-08-20 23:54 UTCEG score recompute

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-59884?
CVE-2026-59884 is a high-severity vulnerability; its CVE record was published on July 14, 2026. pyasn1 is a generic ASN.1 library for Python. Prior to 0.6.4, the BER decoder shared by the CER and DER codecs parses long-form tags by accumulating continuation octets without an upper bound on the tag ID size, allowing a crafted input to force construction of an arbitrarily large integer with CPU…
When was the CVE record for CVE-2026-59884 published?
The CVE record for CVE-2026-59884 was published on July 14, 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 July 21, 2026; the record at its source may have been updated since.
Is CVE-2026-59884 actively exploited?
CVE-2026-59884 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59884?
CVE-2026-59884 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-59884?
A fix for CVE-2026-59884 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-59884 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-59884

Explore →

Is Your Infrastructure Affected by CVE-2026-59884?

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

Book a Demo →Browse All CVEs