CVE-2026-59884

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 72% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — Patch released this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

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.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

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 Patch Available

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(4)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
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 rangeFixed inDependents
pyasn10.0.10a ... 0.6.3 (41 versions)0.6.4—
pyssn1—0.6.4—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
pyasn10.4.8-1 ... 0.6.4-1 (14 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
pyasn10.4.8-3 ... 0.6.4-1 (11 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
pyasn10.6.1-1 ... 0.6.4-1 (7 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
pyasn10.6.1-1, 0.6.2-1, 0.6.2-1~bpo13+1, 0.6.3-10.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 23× in last 7d / 112× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 155 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-59884?
CVE-2026-59884 is a high vulnerability 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 CVE-2026-59884 disclosed?
CVE-2026-59884 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59884 actively exploited?
CVE-2026-59884 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.3% of all scored CVEs.
What is the CVSS score of CVE-2026-59884?
CVE-2026-59884 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-59884?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59884, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs