Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-15307: An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango spatial lookups optimistic

47
This month
HIGH 8.8UPGRADE

CVE-2026-15307 is a high-severity flaw (CVSS 8.8) affecting django. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango spatial lookups optimistically parse the right-hand-side value as a raster by passing it to the `django.contrib.gis.gdal.GDALRaster` constructor. Any value used in a spatial lookup against a `GeometryField` or `RasterField` reaches this constructor, including untrusted input, for example a spatial-field filter submitted through the Django admin changelist query st

Why this priority

  • High severity

A fixed release or distro patch exists.

Risk facts

CVSS score8.8 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance1.1% (top 34%)
CISA exploited listNo
WeaknessCWE-73, CWE-918
Published2026-08-04
Last modified2026-10-23
Publisher (CNA): Django Software Foundation · Vendor: djangoproject

Last updated 2026-10-23 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

djangoproject django UPGRADE
Affected: < 5.2.17 · >= 6.0 and < 6.0.8
Fixed in: 5.2.17, 6.0.8
Safe to downgrade to: a release before 6.0
1. Check installed version
apt-cache policy django || rpm -q django || django --version
2. UPGRADE to 5.2.17 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade django
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade django
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 6.0 (Debian / Ubuntu)
apt-cache madison django sudo apt install django=<VERSION_BEFORE_6.0> sudo apt-mark hold django
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list django sudo dnf downgrade django-<VERSION_BEFORE_6.0> sudo dnf versionlock add django
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.

Exact fixes by distribution

Python (pip) · Django · FIXED · 5.2.17 · vulnerable: < 5.2.17 · source
pip install --upgrade "Django>=5.2.17" pip show Django
Fedora 46 · rubygem-eventmachine · FIXED · 1.2.7-37.fc46 · FEDORA-2026-7194c202a2 · source
sudo dnf upgrade --advisory=FEDORA-2026-7194c202a2
Debian 12 · python-django · NO FIX YET
Debian 13 · python-django · NO FIX YET
Alpine 3.24 · py3-django · FIXED · py3-django-5.2.17-r0
apk add --upgrade py3-django apk info -v py3-django

Advisories and coverage

Official advisories

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-15307?

django: upgrade to 5.2.17, 6.0.8. Exact commands for each OS are on this page.

Is CVE-2026-15307 being exploited?

CVE-2026-15307 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-15307 affect?

CVE-2026-15307 affects django. Severity is high (CVSS 8.8). An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango spatial lookups optimistically parse the right-hand-side value as a raster by passing it to the `django.contrib.gis.gdal.GDALRaster` constructor. Any value

How urgent is CVE-2026-15307?

Priority 47/100. High severity

Software pages

Django vulnerabilities

Related CVEs

References

← Back to latest CVEs