cve.bz

CVE-2026-111211

6.9 mediumEPSS 0.5%

Medium (6.9). EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19. `django.contrib.gis.forms.widgets.BaseGeometryWidget.deserialize()`, used by `django.contrib.gis.forms.GeometryField`, does not escape invalid submitted values before logging them, which allows remote attackers to inject or forge log entries via a crafted geometry value. 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 Aaron chen for reporting this issue.

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS
0.5% estimated probability of exploitation activity in the next 30 days; 45th percentile. Scored 2026-11-04. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-03. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-117 Improper Output Neutralization for Logs
OWASP Top 10
A09:2025 Logging & Alerting Failures
Published
Modified
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-111211 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-111211?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-111211?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-111211 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Versions

From the CNA's record in the CVE List.

ProductAffected
djangoproject Djangofrom 6.1 before 6.1.3
djangoproject Djangofrom 6.0 before 6.0.10
djangoproject Djangofrom 5.2 before 5.2.19

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14python-djangono fix listedDEBIAN-CVE-2026-111211
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 5 morepython-djangono fix listedUBUNTU-CVE-2026-111211
Alpinev3.24py3-django5.2.19-r0ALPINE-CVE-2026-111211

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpine.

Attack patterns (CAPEC)

  • CAPEC-81 Web Server Logs Tampering Likelihood: Medium · Severity: High
  • CAPEC-93 Log Injection-Tampering-Forging Likelihood: High · Severity: High
  • CAPEC-268 Audit Log Manipulation

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON