ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-15307

CVE-2026-15307 is listed by An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8..

Published Aug 4, 2026 · catalog updated Oct 24, 2026 · the affected product

Last checked Nov 7, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-15307. EPSS is 1.13%. Act only if a listed version of the affected product is installed.

Gaps on this record

  • No plain product name is stored. The page cannot tell you which product to check.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
High8.7
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
1.13%
Remediation
Version ranges on file
Affected products
cpe djangoproject/django

CVE-2026-15307 is listed by An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8..

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe djangoproject/django< 5.2.17
  • cpe djangoproject/django< 6.0.8

How to fix CVE-2026-15307

  • Upgrade

    CVE-2026-15307 lists a fix boundary at 5.2.17. Compare the installed build with that boundary before you change production.

  • Version check

    Affected < 5.2.17

  • Advisory

    Open the inventory_high record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-15307. EPSS is 1.13%. Act only if a listed version of the affected product is installed.

Which versions are affected?

Compare what you have installed with < 5.2.17, < 6.0.8. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-73; CWE-918: Server-Side Request Forgery (SSRF). EPSS 1.13%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Django security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Aug 4, 2026 · Monitored products — high

    Detected

    CVE-2026-15307 is listed by An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8..

  2. Oct 24, 2026 · Monitored products — high

    Updated

    CVE-2026-15307 is listed by An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8..

Sources

  • Monitored products — highVendor advisoryCVE-2026-15307

    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 constructor. Any value used in a spatial lookup against a or reaches this constructor, including untrusted input, for example a spatial-field filter submitted through the Django admin changelist query string by a staff u

    nvd.nist.gov

References

Freshness

Last verified in this catalog Nov 7, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Monitored products — highNov 7, 2026