CVE-2026-25673

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.5 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 1.1% (65th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from CISA-ADP (Vulnrichment) CVSS v3.1
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

An issue was discovered in 6.0 before 6.0.3, 5.2 before 5.2.12, and 4.2 before 4.2.29. URLField.to_python() in Django calls urllib.parse.urlsplit(), which performs NFKC normalization on Windows that is disproportionately slow for certain Unicode characters, allowing a remote attacker to cause denial of service via large URL inputs containing these characters. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Seokchan Yoon for reporting this issue.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation1.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.1%
EPSS %ILE
65th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 3, 2026

Last Modified

July 15, 2026

Advisory Details (6)

Auto-updated Jul 6, 2026
Patch available. Sources: redhat.
Red Hat
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-25673.json
Red Hat

2444115 – (CVE-2026-25673) CVE-2026-25673 django: Django: Denial of Service via slow URL normalization on Windows

https://bugzilla.redhat.com/show_bug.cgi?id=2444115
Red HatMentions a patch (unverified)

cve-details

https://access.redhat.com/security/cve/CVE-2026-25673
Web page

Django security releases issued: 6.0.3, 5.2.12, and 4.2.29 | Weblog | Django

https://www.djangoproject.com/weblog/2026/mar/03/security-releases/
Web page
https://groups.google.com/g/django-announce
Web page

Archive of security issues | Django documentation | Django

https://docs.djangoproject.com/en/dev/releases/security/

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
django4.2 ... 6.0.2 (44 versions)
  • 6.0 up to 6.0.3: fixed in 6.0.3
  • 5.2 up to 5.2.12: fixed in 5.2.12
  • 4.2 up to 4.2.29: fixed in 4.2.29
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 26× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 90 of 116 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 10 repeat rows among the latest 100 are merged into the row they repeat. The 26 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 20:01 UTCEG score recompute
  2. 2026-10-11 17:14 UTCEG score recompute
  3. 2026-10-11 14:45 UTCEG score recompute
  4. 2026-10-11 13:48 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  6. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  7. 2026-10-09 05:28 UTCOSV refresh
  8. 2026-10-08 17:11 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  9. 2026-10-07 23:47 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  10. 2026-10-06 15:17 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  11. 2026-10-05 17:42 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  12. 2026-10-04 23:21 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  13. 2026-10-03 14:25 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  14. 2026-10-01 19:49 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  15. 2026-09-30 15:03 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  16. 2026-09-28 13:51 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  17. 2026-09-26 15:58 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  18. 2026-09-26 00:26 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  19. 2026-09-24 14:03 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  20. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  21. 2026-09-19 12:32 UTCOSV refresh
  22. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  23. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  24. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  25. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
Show 65 more
  1. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  2. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  3. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  4. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  5. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  6. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  7. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  8. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  9. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  10. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  11. 2026-08-31 16:04 UTCOSV refresh
  12. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  13. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  14. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  15. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  16. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  17. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  18. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  19. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  20. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  21. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  22. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  23. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  24. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  25. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  26. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  27. 2026-08-14 08:41 UTCEG score recompute
  28. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  29. 2026-08-13 00:31 UTCEG score recompute
  30. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  31. 2026-08-11 23:22 UTCEG score recompute
  32. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  33. 2026-08-11 05:55 UTCEG score recompute
  34. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  35. 2026-08-09 19:58 UTCEG score recompute
  36. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  37. 2026-08-09 08:18 UTCEG score recompute
  38. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  39. 2026-08-07 20:14 UTCEG score recompute
  40. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  41. 2026-08-06 02:48 UTCEG score recompute
  42. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  43. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  44. 2026-08-04 04:33 UTCEG score recompute
  45. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  46. 2026-08-02 19:08 UTCEG score recompute
  47. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  48. 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  49. 2026-07-30 16:27 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  50. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  51. 2026-07-28 15:36 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  52. 2026-07-26 14:54 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  53. 2026-07-25 14:17 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  54. 2026-07-24 14:17 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  55. 2026-07-23 14:18 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  56. 2026-07-23 03:07 UTCEG score recompute
  57. 2026-07-22 14:08 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  58. 2026-07-21 15:24 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  59. 2026-07-20 17:08 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  60. 2026-07-19 14:31 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  61. 2026-07-19 02:28 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  62. 2026-07-18 10:04 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  63. 2026-07-18 06:59 UTCOSV refresh
  64. 2026-07-16 17:03 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  65. 2026-07-15 16:57 UTCEPSS rescoreEPSS 0.7% · 50th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-25673?
CVE-2026-25673 is a high-severity vulnerability; its CVE record was published on March 3, 2026. An issue was discovered in 6.0 before 6.0.3, 5.2 before 5.2.12, and 4.2 before 4.2.29. URLField.to_python() in Django calls urllib.parse.urlsplit(), which performs NFKC normalization on Windows that is disproportionately slow for certain Unicode characters, allowing a remote attacker to cause…
When was CVE-2026-25673 made public?
CVE-2026-25673 was made public on March 3, 2026: that is the date its CVE record's CNA, Django Software Foundation, gives for when the vulnerability was made public. The CVE record itself was published on March 3, 2026. EchelonGraph's copy of the record carries a last-modified date of July 15, 2026; the record at its source may have been updated since.
Is CVE-2026-25673 actively exploited?
CVE-2026-25673 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (65th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-25673?
CVE-2026-25673 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-25673?
A fix for CVE-2026-25673 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-25673

Explore →

Is Your Infrastructure Affected by CVE-2026-25673?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs