CVE-2023-23931

MEDIUMNVD 4.84.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.8 under NVD CVSS v3. EPSS exploit probability: 1.3% (69th percentile of EPSS-scored CVEs). 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
Elevated
4.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1.3%CVSS: 4.8Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In affected versions Cipher.update_into would accept Python objects which implement the buffer protocol, but provide only immutable buffers. This would allow immutable objects (such as bytes) to be mutated, thus violating fundamental rules of Python and resulting in corrupted output. This now correctly raises an exception. This issue has been present since update_into was originally introduced in cryptography 1.8.

CVSS v3
4.8
EG Score
4.8MEDIUMmedium confidence
EG Risk
38
EG Risk 38/100CISA SSVC

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
Severity48% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
1.3%
EPSS %ILE
69th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

February 7, 2023

Last Modified

November 3, 2025

References (6)

Vendor Advisories for CVE-2023-23931(8)

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

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython3-cryptography (38.0.4-4ubuntu0.23.10.1) @ mantic2026-05-25ubuntu
redhatpython39-devel:3.9-8100020240214182535.7044f6c12024-05-22redhat
redhatquay/quay-rhel8:v3.10.0-1502023-11-30redhat
redhatpython-cryptography-0:3.2.1-6.el82023-11-14redhat
redhatrh-python38-python-cryptography-0:2.8-6.el72023-11-08redhat
redhatpython-cryptography-0:36.0.1-4.el92023-11-07redhat
redhatautomation-controller-0:4.4.3-1.el9ap2023-09-05redhat
redhatpython-cryptography-0:38.0.4-2.el9ap2023-08-21redhat

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

(8 across 8 ecosystems)
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
py3-cryptography—
  • 1.8 up to 39.0.1-r0: fixed in 39.0.1-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
py3-cryptography—
  • 1.8 up to 39.0.1-r0: fixed in 39.0.1-r0
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
python-cryptography2.6.1-3, 2.6.1-3+deb10u1, 2.6.1-3+deb10u2, 2.6.1-3+deb10u3
  • every version up to 2.6.1-3+deb10u3: fixed in 2.6.1-3+deb10u3
  • every version up to 2.6.1-3+deb10u4: fixed in 2.6.1-3+deb10u4
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
python-cryptography3.3.2-1
  • every version up to 3.3.2-1+deb11u1: fixed in 3.3.2-1+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-cryptography—
  • every version up to 38.0.4-3: fixed in 38.0.4-3
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-cryptography—
  • every version up to 38.0.4-3: fixed in 38.0.4-3
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-cryptography—
  • every version up to 38.0.4-3: fixed in 38.0.4-3
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
cryptography1.8 ... 39.0.0 (61 versions)
  • 1.8 up to 39.0.1: fixed in 39.0.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 6× in last 7d / 26× 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 186 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2023-23931?
CVE-2023-23931 is a medium vulnerability published on February 7, 2023. cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In affected versions Cipher.updateinto would accept Python objects which implement the buffer protocol, but provide only immutable buffers. This would allow immutable objects (such as bytes) to…
When was CVE-2023-23931 disclosed?
CVE-2023-23931 was first published on February 7, 2023, with the most recent update on November 3, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-23931 actively exploited?
CVE-2023-23931 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.3% probability of exploitation in the next 30 days (69th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-23931?
CVE-2023-23931 has a CVSS v3 base score of 4.8 (NVD).
How do I remediate CVE-2023-23931?
A fix for CVE-2023-23931 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-23931 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-2023-23931

Explore →

Is Your Infrastructure Affected by CVE-2023-23931?

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

Book a Demo →Browse All CVEs