CVE-2026-111211: Potential log injection via unescaped geometry form values

Q: Which deployments are exposed to this issue?

Deployments using django.contrib.gis.forms.GeometryField are exposed if they run Django 6.1 before 6.1.3, 6.0 before 6.0.10, or 5.2 before 5.2.19. The vulnerable code path is BaseGeometryWidget.deserialize() when it processes an invalid submitted geometry value.

Q: What does an attacker need to exploit it?

An attacker can submit a crafted invalid geometry value remotely. The supplied severity vector indicates no prior privileges or user interaction are required.

Q: What should be done if patching cannot happen immediately?

Prioritize updating to Django 6.1.3, 6.0.10, or 5.2.19, as applicable. Until then, treat logs generated from invalid geometry form submissions as potentially untrustworthy, because crafted input can inject or forge log entries.

Q: Are older unsupported Django branches known to be safe?

No. Unsupported series including 5.1.x, 5.0.x, and 4.2.x were not evaluated and may also be affected.

Published Nov 3, 2026

Updated

[Potential log injection via unescaped geometry form values]

Other sources

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.

— MITRE

Affected Software

13 affected componentsFixes available

debian/python-django*

debian/python-django<=3:3.2.25-0+deb12u3, <=3:3.2.25-0+deb12u6, <=3:4.2.28-0+deb13u2, <=3:4.2.28-0+deb13u1, <=3:5.2.17-2, <=3:5.2.18-2

ubuntu/python-django*

alpine/py3-django<5.2.19-r0

5.2.19-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade alpine/py3-django to a version that resolves this vulnerability.
Fixed in 5.2.19-r0

Event History

Nov 3, 2026

CVE Published

via OSV·12:00 AM

Data Sourced

via OSV·12:00 AM

DescriptionSeverityAffected Software

CVE Published

via MITRE·03:41 PM

Data Sourced

via MITRE·03:41 PM

DescriptionSeverityWeakness

Data Sourced

via OSV·03:41 PM

Weakness

Data Sourced

via NVD·04:17 PM

DescriptionSeverityWeakness

Event

via NVD·04:17 PM

Frequently Asked Questions

Which deployments are exposed to this issue?

Deployments using django.contrib.gis.forms.GeometryField are exposed if they run Django 6.1 before 6.1.3, 6.0 before 6.0.10, or 5.2 before 5.2.19. The vulnerable code path is BaseGeometryWidget.deserialize() when it processes an invalid submitted geometry value.

What does an attacker need to exploit it?

An attacker can submit a crafted invalid geometry value remotely. The supplied severity vector indicates no prior privileges or user interaction are required.

What should be done if patching cannot happen immediately?

Prioritize updating to Django 6.1.3, 6.0.10, or 5.2.19, as applicable. Until then, treat logs generated from invalid geometry form submissions as potentially untrustworthy, because crafted input can inject or forge log entries.

Are older unsupported Django branches known to be safe?

No. Unsupported series including 5.1.x, 5.0.x, and 4.2.x were not evaluated and may also be affected.

CVE-2026-111211: Potential log injection via unescaped geometry form values

Other sources

Affected Software

Remediation

Event History

Frequently Asked Questions

Which deployments are exposed to this issue?

What does an attacker need to exploit it?

What should be done if patching cannot happen immediately?

Are older unsupported Django branches known to be safe?

Company

Resources

Contact

Frequently Asked Questions

Which deployments are exposed to this issue?

What does an attacker need to exploit it?

What should be done if patching cannot happen immediately?

Are older unsupported Django branches known to be safe?