Is CVE-2026-111211 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-111211 being exploited in the wild.

How severe is CVE-2026-111211?

Medium severity, with a CVSS score of 5.3, published 3 November 2026.

Which products and versions are affected?

Django Software Foundation Django 6.1 before 6.1.3, 6.0 before 6.0.10, 5.2 before 5.2.19.

Is there a fix for CVE-2026-111211?

Yes: fixed in Django 6.1.3, 6.0.10, 5.2.19. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-111211 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-111211?

Check whether you run Django Software Foundation Django at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-111211: Django log injection in BaseGeometryWidget.deserialize()

CVE-2026-111211 · Severity: medium · CVSS 5.3 · Published 2026-11-03

Django is a Python web framework used to build web applications. The geographic information system (GIS) forms component fails to escape invalid geometry values before logging them, allowing remote attackers to inject forged or malicious log entries by submitting crafted geometry data. This enables attackers to pollute application logs with false entries, potentially covering up other activity or deceiving administrators reviewing logs.

Technologies: Django Software Foundation Django. Vendors: Django Software Foundation.

Quick answers

Is CVE-2026-111211 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-111211 being exploited in the wild.
How severe is CVE-2026-111211?: Medium severity, with a CVSS score of 5.3, published 3 November 2026.
Which products and versions are affected?: Django Software Foundation Django 6.1 before 6.1.3, 6.0 before 6.0.10, 5.2 before 5.2.19.
Is there a fix for CVE-2026-111211?: Yes: fixed in Django 6.1.3, 6.0.10, 5.2.19. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-111211 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-111211?: Check whether you run Django Software Foundation Django at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: Django 6.1.3, 6.0.10, 5.2.19

Technical details

The vulnerability exists in django.contrib.gis.forms.widgets.BaseGeometryWidget.deserialize(), which is called by django.contrib.gis.forms.GeometryField when processing form submissions. Invalid submitted geometry values are logged without proper escaping, enabling log injection. An unauthenticated remote attacker can submit a crafted geometry value via a network request to inject or forge arbitrary log entries.

Affected products

Django Software Foundation Django 6.1 before 6.1.3, 6.0 before 6.0.10, 5.2 before 5.2.19

Timeline

2026-11-03: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.