PyPI package
Django 6.1.0 vulnerability, and the version that fixes it
Django 6.1.0 has 1 known vulnerability; 6.1.1 fixes it.
PyPI (opens in a new tab) describes it as “A high-level Python web framework that encourages rapid development and clean, pragmatic design.”
- Known vulnerabilities
- 1
- None rated high or critical
- Released
- Aug 5, 2026
- Latest is 6.1.2
- Django 6.1 support
- Supported
- Until Dec 31, 2027
- Licence
- BSD-3-Clause
- Pulls in
- 2 packages
- Resolved by deps.dev
What to upgrade to
6.1.1 is the closest release with no known vulnerabilities.
6.1.1Upgrade to this
Fixes the known vulnerability. Released Sep 2, 2026.
No known vulnerabilitiesNewest 6.x release and the latest release. Released Oct 6, 2026.
No known vulnerabilities
6.1.1 came out on Sep 2, 2026. A coding agent trained before then doesn’t know it exists, so it may suggest an older release. AI knowledge cutoff dates
Hand the fix to your coding agent
One task with the upgrade, the file to change and why. Paste it into Claude Code, Cursor or Codex.
Findings
- WarningVulnerability
CVE-2026-15830 in django 6.1.0
EPSS: top 35%Django GeoDjango vulnerable to denial of service through deeply nested geometry collections. Fixed in 6.1.1.
Every advisory for Django 6.1.0
Known exploited first (CISA KEV), then by how likely they are to be exploited (FIRST EPSS), then by severity. Each id links to its OSV.dev record.
WarningCVE-2026-15830 on OSV.dev (opens in a new tab)GHSA-q238-5cxm-5c9hEPSS: top 35%
Django GeoDjango vulnerable to denial of service through deeply nested geometry collections
Fixed in 6.1.1. Published Aug 4, 2026.
Is Django the only one?
Paste a public GitHub repo or drop your requirements.txt or pyproject.toml and see every vulnerable, end-of-life or deprecated dependency, with one fix task. Free, no sign-up.
How this page is checked
StackPrism asks OSV.dev which advisories affect exactly Django 6.1.0, merges duplicates filed under several ids, and ranks them with CISA’s Known Exploited Vulnerabilities list and FIRST EPSS. Release dates and deprecation come from deps.dev and PyPI, support dates from endoflife.date. No AI writes this page: every sentence comes from that data, refreshed every few hours.
Last checked against PyPI, OSV.dev, deps.dev, CISA KEV, FIRST EPSS and endoflife.date.