CVE-2026-15830: Django Denial-of-Service Vulnerability via Nested Geometry Collections

django Updated 19 Aug 2026

Summary

19/08/2026
Yes i
Medium
Not published

CVE-2026-15830: Potential denial-of-service vulnerability via nested geometry collections. Affects django across 2 version ranges.

< 5.2.17 >= 6.0.0, < 6.0.8

Fixed in 5.2.17 or 6.0.8, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2026-15830 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Django is a high-level Python web framework that encourages rapid development and clean, pragmatic design. It provides a robust set of features, including an ORM, routing, and templating. GeoDjango is an extension of Django that adds geographic capabilities, allowing developers to create applications that can handle spatial data. However, certain versions of Django are vulnerable to a denial-of-service attack due to improper handling of deeply nested geometry collections.

Vulnerability Detail

An issue was discovered in Django versions 5.2 before 5.2.17 and 6.0 before 6.0.8. The vulnerability lies in GeoDjango's django.contrib.gis.geos.GEOSGeometry, which can be exploited by supplying deeply nested GEOMETRYCOLLECTION objects in well-known text (WKT), well-known binary (WKB), or hex-encoded WKB formats. This leads to unbounded recursion and a segmentation fault in the underlying GEOS library, potentially causing a denial-of-service condition. Earlier unsupported Django series may also be affected, although they were not evaluated.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 5.2.17 5.2.17
  • >= 6.0.0, < 6.0.8 6.0.8

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

As a temporary workaround, avoid using deeply nested GEOMETRYCOLLECTION objects in your applications until you can upgrade to a patched version of Django.

Conclusion

The CVE-2026-15830 vulnerability in Django poses a significant risk of denial-of-service attacks through nested geometry collections. It is crucial for developers using affected versions to update to the latest patched versions to mitigate this risk. Utilizing tools like Vulert can help in monitoring vulnerabilities in your applications.

See every vulnerability recorded for django →

Share this vulnerability

FAQ

CVE-2026-15830 is a vulnerability in Django that can lead to denial-of-service attacks through nested geometry collections.

Django versions 5.2 before 5.2.17 and 6.0 before 6.0.8 are affected. Earlier unsupported versions may also be vulnerable.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

Exploiting this vulnerability can lead to denial-of-service conditions, causing your application to crash or become unresponsive.

You can update Django by running the command: pip install --upgrade django, ensuring you install version 5.2.17 or 6.0.8 or later.

Related vulnerabilities

Recent vulnerabilities recorded for django.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 5.2.17 5.2.17
  • >= 6.0.0, < 6.0.8 6.0.8

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback