Django releases security updates for six CVEs
Django security releases address multiple vulnerabilities including CVE-2026-108147, CVE-2026-111211, CVE-2026-111362, CVE-2026-113593, CVE-2026-113733, and CVE-2026-114582.
40
CVE-2026-111211
Log injection in Django GeometryField before 6.1.3
- CVSS 4.0
- 6.9 medium
- EPSS
- —
- Published
- ·
- Modified
AI analysisSummaries by Vani AI
The flaw allows remote attackers to inject or forge log entries via crafted geometry values in submitted form data because django.contrib.gis.forms.widgets.BaseGeometryWidget.deserialize() does not escape invalid values before logging them. This affects django.contrib.gis.forms.GeometryField in vulnerable Django releases. Users of unsupported Django series may also be impacted. An attacker gains the ability to modify log files.
What to do: Upgrade to Django 6.1.3, 6.0.10 or 5.2.19. No workaround given.
| Product | Affected | Fixed in |
|---|---|---|
| Django | 6.1 | 6.1.3 |
| Django | 6.0 | 6.0.10 |
| Django | 5.2 | 5.2.19 |
Estimated exposure
nicheNo basis for an estimate.
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Description · NVD
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.
- Weakness
- CWE-117
- Vector
- 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X