CVE-2023-23969

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of service disruption.

Exploit odds

47.4% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2023-02-01 19:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 05:38 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 47.4% in the next 30 days (EPSS).
• Severity: 7.5 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2023-02-01 19:15 UTC

Last modified

2026-06-17 05:38 UTC

Exploit probability

47.4% · EPSS, next 30 days

Weakness

CWE-770 · Allocation without limits

Record status

Modified

Affected

• Djangoproject Django < 3.2.17
• Djangoproject Django < 4.0.9
• Djangoproject Django < 4.1.6
• Debian Linux 10.0

Attack profile CVSS 3.1 · 7.5

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2023-23969.md and follow it. Check whether this project is affected by CVE-2023-23969. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge