CVE Tools
Track your stack

CVE-2026-15337

Potential denial-of-service vulnerability in check_for_language()

No known exploitation. EPSS puts it in the 49th percentile. Fixed versions are out.

CVSS 3.15.3MediumEPSS percentile49th0.6% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix1 product2 fixed builds listed below
Check it yourself

OpenVAS · 17 checks

e.g. OID 1.3.6.1.4.1.25623.1.0.139168

Run the check

Published Updated Sources: CVE.org, NVD

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • djangoproject DjangoAffected: ≥ 6.0, < 6.0.8Upgrade to: 6.0.8Affected: ≥ 5.2, < 5.2.17Upgrade to: 5.2.17Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS49th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.6% chance of exploitation activity in the next 30 days, which ranks it in the 49th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

11 events over 81 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Patch availablerecord updated
  3. Patch availablerecord updated
  4. Record updated
  5. OpenVAS check added
  6. Publishedweakness classified, record updated

Affected products

And 1 more affected product. See all after sign-in

Scale

How widely the affected products are used. This is not a count of vulnerable hosts.

Estimate Public sources, each figure dated. How much of it is already patched is not known.

Django

Library

  • 41.1Mdownloads / month

    PyPI downloads, last 30 days (pypistats, mirrors excluded).

    PyPI ↗ · as of 2 Nov 2026 · High confidence

Version split: unknown. No public source for this product.

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Scored 5.3 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity NoneNo integrity impact
  • Availability LowReduced performance or intermittent disruption of service

Weaknesses

Sources

References in the record

And 4 more references. See all after sign-in

In the news

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Django, not every advisory.