CVE-2026-59886

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 73% 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 — 3 sources updated 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 univ.Real type converted its mantissa, base, and exponent value to a Python float using exact big-integer exponentiation. A BER, CER, or DER encoded REAL value only a few bytes long can carry a very large exponent, causing float conversion through prettyPrint(), str(), comparison, arithmetic, int(), or an explicit float() call to consume excessive CPU and memory and hang applications that decode untrusted ASN.1 data and then print, log, or compare decoded objects. 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
27%
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

Uncontrolled resource consumption when converting decoded REAL values · Advisory · pyasn1/pyasn1 · GitHub

https://github.com/pyasn1/pyasn1/security/advisories/GHSA-hm4w-wwcw-mr6r
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 e60c691cb91a (pyasn1/pyasn1)

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

https://github.com/pyasn1/pyasn1/commit/e60c691cb91addb8fcefa2f537e85ede6fb1e886

Vendor Advisories for CVE-2026-59886(20)

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

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhui5/rhua-rhel9:17888805812026-09-09redhat
redhatrhelai3/bootc-gcp-cuda-rhel9:17882739772026-09-01redhat
redhatrhelai3/disk-image-cuda-rhel9:17882903142026-09-01redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17870735932026-08-27redhat
redhatpython-pyasn1-0:0.4.8-6.el9_2.22026-08-25redhat
redhatpython-pyasn1-0:0.1.9-7.el7_9.32026-08-25redhat
redhatrhaiis/model-opt-cuda-rhel9:17876011592026-08-25redhat
redhatrhtas/segment-reporting-rhel9:17873055252026-08-25redhat
redhatpython-pyasn1-0:0.6.2-1.el10_0.22026-08-25redhat
redhatpython-pyasn1-0:0.4.8-7.el9_8.12026-08-25redhat
redhatresource-agents-0:4.1.1-61.el7_9.242026-08-25redhat
redhatpython-pyasn1-0:0.3.7-6.el8_10.22026-08-25redhat
redhatpython-pyasn1-0:0.4.8-6.el9_4.22026-08-25redhat
redhatpython-pyasn1-0:0.3.7-6.el8_6.22026-08-25redhat
redhatpython-pyasn1-0:0.3.7-6.el8_4.22026-08-25redhat
redhatpython-pyasn1-0:0.4.8-6.el9_6.22026-08-25redhat
redhatpython-pyasn1-0:0.6.2-1.el10_2.12026-08-25redhat
redhatpython-pyasn1-0:0.3.7-6.el8_8.22026-08-25redhat
redhatansible-automation-platform-27/lightspeed-rhel9:17872175312026-08-24redhat
redhatautomation-controller-0:4.6.32-1.el9ap2026-08-24redhat
redhatautomation-controller-0:4.7.16-1.el9ap2026-08-24redhat
redhatfence-agents-0:4.2.1-112.el8_8.212026-08-24redhat
redhatresource-agents-0:4.9.0-40.el8_8.212026-08-24redhat
redhatfence-agents-0:4.10.0-86.el9_6.212026-08-24redhat
redhatfence-agents-0:4.2.1-65.el8_4.322026-08-24redhat
redhatresource-agents-0:4.1.1-90.el8_4.272026-08-24redhat
redhatfence-agents-0:4.10.0-62.el9_4.292026-08-24redhat
redhatresource-agents-0:4.9.0-16.el8_6.242026-08-24redhat
redhatfence-agents-0:4.2.1-89.el8_6.262026-08-24redhat
redhatfence-agents-0:4.10.0-43.el9_2.252026-08-24redhat

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 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~bpo13+1 (12 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
pyasn10.6.1-1 ... 0.6.4-1~bpo13+1 (8 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
pyasn10.6.1-1, 0.6.2-1, 0.6.2-1~bpo13+1, 0.6.3-1, 0.6.4-1~bpo13+10.6.4-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
pyasn10.0.10a ... 0.6.3 (41 versions)0.6.4—

Weakness Classification(2)

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

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 14× in last 7d / 68× 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 187 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-59886?
CVE-2026-59886 is a high vulnerability published on July 14, 2026. pyasn1 is a generic ASN.1 library for Python. Prior to 0.6.4, the univ.Real type converted its mantissa, base, and exponent value to a Python float using exact big-integer exponentiation. A BER, CER, or DER encoded REAL value only a few bytes long can carry a very large exponent, causing float…
When was CVE-2026-59886 disclosed?
CVE-2026-59886 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-59886 actively exploited?
CVE-2026-59886 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 73.1% of all scored CVEs.
What is the CVSS score of CVE-2026-59886?
CVE-2026-59886 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-59886?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59886, 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-59886

Explore →

Is Your Infrastructure Affected by CVE-2026-59886?

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

Start Free Scan →Browse All CVEs