# 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-o...

Advisory record · `GHSA-q2jf-h9jm-m7p4`

- **Identifiers:** `GHSA-q2jf-h9jm-m7p4` · `BIT-django-2023-23969` · `CVE-2023-23969` · `PYSEC-2023-12`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** Yes: CVSS 7+ and EPSS
- **Weakness (CWE):** [CWE-770](https://cwe.mitre.org/data/definitions/770.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 1 Feb 2023
- **Updated:** 10 Jun 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 1 Feb 2023, 19:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 7.5 (7.0 or more) and EPSS 0.47 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `django` (PyPI): affected `>=3.2, <3.2.17 || >=4.0, <4.0.9 || >=4.1, <4.1.6`; fixed in `3.2.17`, `4.0.9`, `4.1.6`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Django versions 3.2 before 3.2.17, 4.0 before 4.0.9, and 4.1 before 4.1.6 are vulnerable. The framework caches parsed Accept-Language header values, so a remote attacker can send very large Accept-Language headers to cause excessive memory use and denial of service. Upgrade to Django 3.2.17, 4.0.9, or 4.1.6 or later.

Written 10 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`, from ADP (CISA-ADP)

- **CISA KEV:** Not listed.
- **EPSS:** 0.47, the 98th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 1 Feb 2023. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-q2jf-h9jm-m7p4](https://github.com/advisories/GHSA-q2jf-h9jm-m7p4)
- [OSV: GHSA-q2jf-h9jm-m7p4](https://osv.dev/vulnerability/GHSA-q2jf-h9jm-m7p4)
- <https://docs.djangoproject.com/en/4.1/releases/security/>
- <https://www.djangoproject.com/weblog/2023/feb/01/security-releases/>
- <https://groups.google.com/forum/#!forum/django-announce>
- <https://github.com/advisories/GHSA-q2jf-h9jm-m7p4>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-q2jf-h9jm-m7p4>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-q2jf-h9jm-m7p4/>. Everything for agents: <https://agentprime.io/llms.txt>.
