CVE-2026-39892

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.7%, top 52% 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, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. From 45.0.0 to before 46.0.7, if a non-contiguous buffer was passed to APIs which accepted Python buffers (e.g. Hash.update()), this could lead to buffer overflows. This vulnerability is fixed in 46.0.7.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
59(Track)
EG Risk 59/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
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

April 8, 2026

Last Modified

August 17, 2026

Advisory Details (10)

Auto-updated Aug 24, 2026
Patch available. Sources: github, redhat.
generic

oss-security - PyCA cryptography 46.0.7 released, fixes CVE-2026-39892

http://www.openwall.com/lists/oss-security/2026/04/08/12
github Patch Available

Buffer overflow if non-contiguous buffers were passed to APIs · Advisory · pyca/cryptography · GitHub

https://github.com/pyca/cryptography/security/advisories/GHSA-p423-j2cm-9vmq

Patch Availability(24)

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)
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
py3-cryptography46.0.7-r0
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
py3-cryptography46.0.7-r0
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-cryptography43.0.0-3 ... 46.0.6-1 (11 versions)46.0.7-1
PyPI(1)
PackageVulnerable rangeFixed inDependents
cryptography45.0.0 ... 46.0.6 (15 versions)46.0.7

Weakness Classification(2)

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

Additional Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 5× in last 7d / 96× 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 230 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-39892?
CVE-2026-39892 is a critical vulnerability published on April 8, 2026. cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. From 45.0.0 to before 46.0.7, if a non-contiguous buffer was passed to APIs which accepted Python buffers (e.g. Hash.update()), this could lead to buffer overflows. This vulnerability is fixed in…
When was CVE-2026-39892 disclosed?
CVE-2026-39892 was first published in the National Vulnerability Database on April 8, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-39892 actively exploited?
CVE-2026-39892 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 51.5% of all scored CVEs.
What is the CVSS score of CVE-2026-39892?
CVE-2026-39892 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-39892?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-39892, 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-39892

Explore →

Is Your Infrastructure Affected by CVE-2026-39892?

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