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.0%, top 93% 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
Trending — 3 sources updated this week
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: NoneExposed: 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)
EPSS
46.9%
KEV
Not listed

Published

April 8, 2026

Last Modified

July 10, 2026

Advisory Details (10)

Auto-updated Jul 11, 2026
Patch available. Sources: github, redhat.
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:24483
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:23361
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:22840
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:22629
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:22465
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:21017
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:20338
redhat Patch Available
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
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

Vendor Advisories for CVE-2026-39892(19)

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

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-vllm-gaudi-rhel9:17800690692026-06-10redhat
redhatquay/quay-rhel8:17808913952026-06-09redhat
redhatpython3.12-cryptography-0:46.0.7-1.el9ap2026-06-09redhat
redhatansible-automation-platform-tech-preview/metrics-service-rhel9:17797608442026-06-09redhat
redhatrhtas/model-transparency-rhel9:17809148862026-06-08redhat
redhatquay/quay-rhel8:17798114732026-06-04redhat
redhatquay/quay-rhel8:17798222612026-06-03redhat
redhatquay/quay-rhel9:17799222052026-06-02redhat
redhatquay/quay-rhel8:17798114122026-06-02redhat
redhatquay/quay-rhel8:17796893922026-05-26redhat
redhatdiscovery/discovery-server-rhel9:17793952282026-05-21redhat
redhatquay/quay-rhel9:17792040862026-05-19redhat
redhatpython-cryptography-main-46.0.7-1.hum12026-04-09redhat

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

(1 across 1 ecosystem)
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.

Data Freshness Timeline

(refreshed 11× in last 7d / 43× 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 134 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 July 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 46.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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.

Start Free Scan →Browse All CVEs