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 51% 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: 0.8%CVSS: 9.8Exploit: None knownExposed services: Not assessed

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.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/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
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
EPSS PROB
0.8%
EPSS %ILE
53rd
KEV
Not listed

Published

April 8, 2026

Last Modified

September 10, 2026

Advisory Details (10)

Auto-updated Oct 8, 2026
Patch available. Sources: redhat, github.
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:24483
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:23361
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:22840
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:22629
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:22465
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:21017
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:20338
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:19375
generic

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

http://www.openwall.com/lists/oss-security/2026/04/08/12
githubMentions a patch (unverified)

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 rangeFix by version rangeDependents
py3-cryptography—
  • 45.0.0 up to 46.0.7-r0: fixed in 46.0.7-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
py3-cryptography—
  • 45.0.0 up to 46.0.7-r0: fixed in 46.0.7-r0
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-cryptography43.0.0-3 ... 46.0.6-1 (11 versions)
  • every version up to 46.0.7-1: fixed in 46.0.7-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
cryptography45.0.0 ... 46.0.6 (15 versions)
  • 45.0.0 up to 46.0.7: fixed in 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 7× in last 7d / 28× 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 274 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:17 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-01 19:49 UTCEPSS rescore
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-29 20:02 UTCOSV refresh
  11. 2026-09-28 13:51 UTCEPSS rescore
  12. 2026-09-27 13:48 UTCEPSS rescore
  13. 2026-09-26 15:58 UTCEPSS rescore
  14. 2026-09-26 00:26 UTCEPSS rescore
  15. 2026-09-20 20:15 UTCEPSS rescore
  16. 2026-09-18 19:28 UTCEPSS rescore
  17. 2026-09-18 19:28 UTCEPSS rescore
  18. 2026-09-17 19:30 UTCEPSS rescore
  19. 2026-09-16 14:08 UTCEPSS rescore
  20. 2026-09-16 05:15 UTCEPSS rescore
  21. 2026-09-15 03:11 UTCEPSS rescore
  22. 2026-09-13 16:47 UTCEPSS rescore
  23. 2026-09-12 15:01 UTCEPSS rescore
  24. 2026-09-11 14:53 UTCEPSS rescore
  25. 2026-09-11 09:37 UTCEPSS rescore
Show 75 more
  1. 2026-09-10 13:40 UTCVendor advisory
  2. 2026-09-10 12:28 UTCEG score recompute
  3. 2026-09-10 12:28 UTCVendor advisory
  4. 2026-09-10 09:34 UTCEPSS rescore
  5. 2026-09-08 22:00 UTCEPSS rescore
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-07 13:16 UTCEG score recompute
  8. 2026-09-07 13:16 UTCVendor advisory
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-03 23:16 UTCOSV refresh
  12. 2026-09-02 14:12 UTCEPSS rescore
  13. 2026-09-01 13:53 UTCEPSS rescore
  14. 2026-09-01 04:39 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-21 23:49 UTCEPSS rescore
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-19 17:03 UTCEPSS rescore
  25. 2026-08-18 13:48 UTCEPSS rescore
  26. 2026-08-17 13:47 UTCEPSS rescore
  27. 2026-08-17 12:20 UTCVendor advisory
  28. 2026-08-17 12:13 UTCEG score recompute
  29. 2026-08-17 12:13 UTCVendor advisory
  30. 2026-08-16 14:56 UTCEPSS rescore
  31. 2026-08-16 11:24 UTCVendor advisory
  32. 2026-08-16 07:17 UTCEG score recompute
  33. 2026-08-16 07:17 UTCVendor advisory
  34. 2026-08-16 02:14 UTCEPSS rescore
  35. 2026-08-15 01:30 UTCEPSS rescore
  36. 2026-08-14 22:33 UTCVendor advisory
  37. 2026-08-14 18:26 UTCVendor advisory
  38. 2026-08-14 13:32 UTCVendor advisory
  39. 2026-08-14 09:20 UTCVendor advisory
  40. 2026-08-14 05:13 UTCEG score recompute
  41. 2026-08-14 05:13 UTCVendor advisory
  42. 2026-08-13 22:00 UTCEPSS rescore
  43. 2026-08-13 09:31 UTCVendor advisory
  44. 2026-08-13 03:41 UTCVendor advisory
  45. 2026-08-12 23:34 UTCVendor advisory
  46. 2026-08-12 19:28 UTCEG score recompute
  47. 2026-08-12 19:28 UTCVendor advisory
  48. 2026-08-12 13:51 UTCEPSS rescore
  49. 2026-08-12 12:38 UTCVendor advisory
  50. 2026-08-12 12:13 UTCVendor advisory
  51. 2026-08-11 23:51 UTCVendor advisory
  52. 2026-08-11 19:45 UTCEG score recompute
  53. 2026-08-11 19:45 UTCVendor advisory
  54. 2026-08-11 13:43 UTCEPSS rescore
  55. 2026-08-11 07:12 UTCVendor advisory
  56. 2026-08-11 03:05 UTCEG score recompute
  57. 2026-08-11 03:05 UTCVendor advisory
  58. 2026-08-11 00:00 UTCEPSS rescore
  59. 2026-08-10 12:27 UTCVendor advisory
  60. 2026-08-10 09:28 UTCVendor advisory
  61. 2026-08-10 05:22 UTCVendor advisory
  62. 2026-08-10 01:15 UTCVendor advisory
  63. 2026-08-09 21:08 UTCVendor advisory
  64. 2026-08-09 17:02 UTCEG score recompute
  65. 2026-08-09 17:02 UTCVendor advisory
  66. 2026-08-09 13:46 UTCEPSS rescore
  67. 2026-08-09 12:55 UTCVendor advisory
  68. 2026-08-09 08:48 UTCVendor advisory
  69. 2026-08-09 04:42 UTCEG score recompute
  70. 2026-08-09 04:42 UTCVendor advisory
  71. 2026-08-08 16:37 UTCEPSS rescore
  72. 2026-08-08 11:22 UTCVendor advisory
  73. 2026-08-08 07:15 UTCVendor advisory
  74. 2026-08-08 03:08 UTCVendor advisory
  75. 2026-08-07 23:02 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 on April 8, 2026, with the most recent update on September 10, 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 0.8% probability of exploitation in the next 30 days (53rd percentile of EPSS-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?
A fix for CVE-2026-39892 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-39892 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-39892

Explore →

Is Your Infrastructure Affected by CVE-2026-39892?

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