Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-15337: An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. `django.utils.translation.check_for_

35
Routine
MEDIUM 5.3REMOTEUPGRADE

CVE-2026-15337 is a medium-severity flaw (CVSS 5.3) affecting django. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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, s

Why this priority

  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score5.3 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.6% (top 52%)
CISA exploited listNo
WeaknessCWE-789
Published2026-08-04
Last modified2026-10-23
Publisher (CNA): Django Software Foundation · Vendor: djangoproject

Last updated 2026-10-23 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

djangoproject django UPGRADE
Affected: < 5.2.17 · >= 6.0 and < 6.0.8
Fixed in: 5.2.17, 6.0.8
Safe to downgrade to: a release before 6.0
1. Check installed version
apt-cache policy django || rpm -q django || django --version
2. UPGRADE to 5.2.17 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade django
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade django
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 6.0 (Debian / Ubuntu)
apt-cache madison django sudo apt install django=<VERSION_BEFORE_6.0> sudo apt-mark hold django
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list django sudo dnf downgrade django-<VERSION_BEFORE_6.0> sudo dnf versionlock add django
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-15337?

django: upgrade to 5.2.17, 6.0.8. Exact commands for each OS are on this page.

Is CVE-2026-15337 being exploited?

CVE-2026-15337 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-15337 affect?

CVE-2026-15337 affects django. Severity is medium (CVSS 5.3). 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 retai

How urgent is CVE-2026-15337?

Priority 35/100. Remotely exploitable, no login, no user action

Software pages

Django vulnerabilities

Related CVEs

References

← Back to latest CVEs