CVE-2023-23969

HIGHNVD 7.58.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.0 because EPSS predicts 47% probability of exploitation within the next 30 days (top 1.3% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Elevated
8.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 47%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

In Django 3.2 before 3.2.17, 4.0 before 4.0.9, and 4.1 before 4.1.6, the parsed values of Accept-Language headers are cached in order to avoid repetitive parsing. This leads to a potential denial-of-service vector via excessive memory usage if the raw value of Accept-Language headers is very large.

CVSS v3
7.5
EG Score
8.0(high)
EG Risk
70(Track)
EG Risk 70/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
Severity80% × 45%
Exploitation47% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
47%
EPSS %ILE
99%
KEV
Not listed

Published

February 1, 2023

Last Modified

March 27, 2025

References (14)

Vendor Advisories for CVE-2023-23969(1)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython-django-doc (2:2.2.12-1ubuntu0.15) @ focal2026-05-25ubuntu
ubuntupython-django (1.8.7-1ubuntu5.15+esm6) @ xenial2026-05-25ubuntu
redhatpython-django-0:3.2.18-1.el8pc2023-05-03redhat
redhatpython-django-0:3.2.18-1.0.1.el8ui2023-05-03redhat

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

(6 across 6 ecosystems)
Debian:10(1)
PackageVulnerable rangeFixed inDependents
python-django1:1.11.21-1 ... 1:1.11.29-1~deb10u1 (11 versions)1:1.11.29-1+deb10u6—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
python-django2:2.2.24-1, 2:2.2.25-1~deb11u1, 2:2.2.26-1~deb11u1, 2:2.2.28-1~deb11u12:2.2.28-1~deb11u2—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
python-django—3:3.2.17-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-django—3:3.2.17-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-django—3:3.2.17-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
django3.2 ... 4.1.5 (32 versions)4.1.6—

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

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 8× 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 133 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2023-23969?
CVE-2023-23969 is a high vulnerability published on February 1, 2023. In Django 3.2 before 3.2.17, 4.0 before 4.0.9, and 4.1 before 4.1.6, the parsed values of Accept-Language headers are cached in order to avoid repetitive parsing. This leads to a potential denial-of-service vector via excessive memory usage if the raw value of Accept-Language headers is very large.
When was CVE-2023-23969 disclosed?
CVE-2023-23969 was first published in the National Vulnerability Database on February 1, 2023, with the most recent update on March 27, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-23969 actively exploited?
CVE-2023-23969 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 47% probability of exploitation in the next 30 days, which ranks it in the top 1.2% of all scored CVEs.
What is the CVSS score of CVE-2023-23969?
CVE-2023-23969 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.0.
How do I remediate CVE-2023-23969?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-23969, 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-2023-23969

Explore →

Is Your Infrastructure Affected by CVE-2023-23969?

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

Start Free Scan →Browse All CVEs