Is django 6.1 vulnerable?

PyPI · 4 releases from 6.1.0 to 6.1.3 · latest django is 6.1.3 · checked 18 Nov 2026

No known advisories in the last release

django 6.1.3, the last 6.1 release, has no known advisories. 1 advisory affects earlier 6.1.x releases, so update to 6.1.3.

Update within 6.1:pip install 'django>=6.1.3'

Is your project on an affected django?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 6.1.x, affecting earlier releases

  • MediumCVE-2026-15830GHSA-q238-5cxm-5c9h4 Aug 2026

    Django GeoDjango vulnerable to denial of service through deeply nested geometry collections

    Affected
    <5.2.17 · >=6.0a1 <6.0.8 · >=6.1a1 <6.1.1
    Fixed in
    5.2.17, 6.0.8, 6.1.1

Every django 6.1.x release

Affected: 6.1.0. 6.1.1 and later are not affected.

VersionKnown advisories
django 6.1.3None
django 6.1.2None
django 6.1.1None
django 6.1.0CVE-2026-15830

Which of your client projects are still on django 6.1?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact django version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other django versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.