VulertSecurity VulertSecurity

Vulnerability Database · Bitnami · Package report

django: vulnerability history, versions and safety

django is a package in the Bitnami ecosystem. Vulert records 86 vulnerabilities for it across 49 affected ranges, from Mar 2024 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
86 vulnerabilities recorded C10 H36 M30 L10
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
33 in the last 12 months

Most recent disclosure 19 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all django vulnerabilities

Vulert verdict on django i

Updated on 22 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 19 Aug 2026. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 86 vulnerabilities on record across 2 years, 33 in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 86 over 2 years · 33 in the last year i
  • Latest disclosure 19 Aug 2026 i
  • Highest CVSS n/a i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
up to 5.2.17 (exclusive) 3
from 5.2.0 up to 5.2.17 (exclusive) 1
from 5.2.0 up to 5.2.16 (exclusive) 3
from 5.2.0 up to 5.2.15 (exclusive) 5
from 5.2.0 up to 5.2.14 (exclusive) 3
from 4.2.0 up to 5.1.7 (exclusive) 1
from 4.2.0 up to 5.1.5 (exclusive) 1
from 5.0.0 up to 5.0.14 (exclusive) 1
from 4.2.0 up to 5.0.3 (exclusive) 1
from 4.2.0 up to 4.2.30 (exclusive) 5
from 4.2.0 up to 4.2.29 (exclusive) 2
from 4.2.0 up to 4.2.28 (exclusive) 6
from 4.2.0 up to 4.2.27 (exclusive) 2
from 4.2.0 up to 4.2.26 (exclusive) 2
from 4.2.0 up to 4.2.25 (exclusive) 2
from 4.2.0 up to 4.2.24 (exclusive) 1
from 4.2.0 up to 4.2.23 (exclusive) 1
from 4.2.0 up to 4.2.17 (exclusive) 2
from 4.2.0 up to 4.2.16 (exclusive) 2
from 4.2.0 up to 4.2.15 (exclusive) 4
from 4.2.0 up to 4.2.14 (exclusive) 4
from 3.2.0 up to 3.2.25 (exclusive) 1
from 3.2.0 up to 3.2.24 (exclusive) 1
from 3.2.0 up to 3.2.23 (exclusive) 1
from 3.2.0 up to 3.2.22 (exclusive) 1
from 3.2.0 up to 3.2.21 (exclusive) 1
from 3.2.0 up to 3.2.20 (exclusive) 1
from 3.2.0 up to 3.2.19 (exclusive) 1
from 3.2.0 up to 3.2.18 (exclusive) 1
from 3.2.0 up to 3.2.17 (exclusive) 1
from 3.2.0 up to 3.2.16 (exclusive) 1
from 3.2.0 up to 3.2.15 (exclusive) 1
from 3.2.0 up to 3.2.14 (exclusive) 1
from 3.1.0 up to 3.1.13 (exclusive) 1
from 2.2.0 up to 2.2.28 (exclusive) 2
from 2.2.0 up to 2.2.27 (exclusive) 2
from 2.2.0 up to 2.2.26 (exclusive) 3
from 2.2.0 up to 2.2.25 (exclusive) 1
up to 2.2.24 (exclusive) 1
from 2.2.0 up to 2.2.24 (exclusive) 1
from 2.2.0 up to 2.2.22 (exclusive) 1
from 2.2.0 up to 2.2.21 (exclusive) 1
from 2.2.0 up to 2.2.20 (exclusive) 1
from 2.2.0 up to 2.2.19 (exclusive) 1
from 2.2.0 up to 2.2.18 (exclusive) 1
from 2.2.0 up to 2.2.16 (exclusive) 2
from 2.2.0 up to 2.2.13 (exclusive) 2
from 1.11.0 up to 1.11.29 (exclusive) 1
from 1.11.0 up to 1.11.28 (exclusive) 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 40
  • 2025 18
  • 2026 28

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 33 of the 86 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for django

The 5 most severe of 86 vulnerabilities recorded for this package

Search all 86 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-15920: Django URLField Cross-Site Scripting Vulnerability N/A medium 5.2.17 18 Aug 2026
CVE-2025-32873: Django Denial-of-Service Vulnerability in strip_tags Function N/A high 5.0.3 18 Jun 2025
CVE-2026-15307: Django Server-side File-write and Request Forgery via Spatial Lookups N/A high 5.2.17 19 Aug 2026
CVE-2023-46695: Django NFKC Normalization DoS Vulnerability N/A high 3.2.23 06 Mar 2024
CVE-2026-15830: Django Denial-of-Service Vulnerability via Nested Geometry Collections N/A medium 5.2.17 19 Aug 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About django

Is django safe to use?

Vulert records 86 vulnerabilities for django in Bitnami: 10 critical, 36 high, 30 medium and 10 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does django have?

86 vulnerabilities are recorded for django in the Bitnami ecosystem: 10 critical, 36 high, 30 medium and 10 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new django vulnerabilities disclosed?

33 vulnerabilities were recorded for django in the last 12 months, and the oldest entry in this database dates to 06 Mar 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of django are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor django for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the django version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.