# CVE-2026-15830 — djangoproject Django

> As of 2026-10-08, CVE-2026-15830 is a MEDIUM-severity vulnerability in djangoproject Django, CVSS v3.1 5.3, EPSS 1.1% (65.0th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-15830, most recently “August 2026 Patch Roundup: 11 Critical/High CVEs in Veeam VSPC (CVE-2026-58073, CVSS 9.5), HashiCorp Terraform MCP Server (CVE-2026-16498, CVSS 10.0), and Django”.

**Last updated:** 2026-10-08

## What is CVE-2026-15830?

An issue was discovered in Django 6.0 before 6.0.9 and 5.2 before 5.2.18. GeoDjango's `django.contrib.gis.geos.GEOSGeometry` is subject to a potential denial-of-service when parsing deeply nested `GEOMETRYCOLLECTION` objects supplied as well-known text (WKT), well-known binary (WKB), or hex-encoded WKB, which triggers unbounded recursion and a segmentation fault in the underlying GEOS library. Spatial field lookups and the `django.contrib.gis.forms.GeometryField` form field are also affected. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Andrew MacPherson and kimchunbok_ for reporting this issue.

The record classifies CVE-2026-15830 under weakness class [CWE-674](https://intel.threadlinqs.com/cwe/CWE-674). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 67 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 5.3 — MEDIUM (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **CVSS v4.0 base score:** 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **EPSS (FIRST):** 1.1% probability of exploitation in the next 30 days, higher than 65.0% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 5.3/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-08-04, last modified 2026-10-08

## Is CVE-2026-15830 being exploited?

It currently carries a trending score of 35 in the Threadlinqs vulnerability feed.

## Affected products and versions

- **djangoproject**: Django

## How to fix CVE-2026-15830

No vendor patch reference has been recorded for CVE-2026-15830 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-15830

1 tracked threat in the Threadlinqs corpus references CVE-2026-15830, either in the campaign’s CVE list or as an indicator on the campaign record.

- [August 2026 Patch Roundup: 11 Critical/High CVEs in Veeam VSPC (CVE-2026-58073, CVSS 9.5), HashiCorp Terraform MCP Server (CVE-2026-16498, CVSS 10.0), and Django](https://intel.threadlinqs.com/threat/TL-2026-1891) — CRITICAL · 2026-08-05

## Sources

Enriched from CVE.org, FIRST EPSS. Last verified by Threadlinqs on 2026-10-10.

**Vendor advisory and patch**

- [docs.djangoproject.com — vendor advisory](https://docs.djangoproject.com/en/dev/releases/security/)
- [github.com — patch](https://github.com/django/django/commit/d2e59b77fe18de318a8272c2a7bbc798d84d1d0d)
- [github.com — patch (9e4a3f186b6b07b483bfd9195ea06734663fcd06)](https://github.com/django/django/commit/9e4a3f186b6b07b483bfd9195ea06734663fcd06)
- [github.com — patch (6af5da31775417c610dbf9c3f1b5b8333d42daf6)](https://github.com/django/django/commit/6af5da31775417c610dbf9c3f1b5b8333d42daf6)
- [github.com — patch (ba80833fa656dd09660b97c4429331067db1b080)](https://github.com/django/django/commit/ba80833fa656dd09660b97c4429331067db1b080)

**Mailing list and disclosure**

- [groups.google.com — mailing list](https://groups.google.com/g/django-announce)

_Showing 6 of 11 recorded references._

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-15830
Full detection coverage and IOCs for threats exploiting CVE-2026-15830 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp