CVE-2025-0938

MEDIUMNVD 6.36.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under NVD CVSS v3. EPSS exploit probability: 1.5%, top 28% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 6.3Exploit: None knownExposed: 0

A fix is available — apply it.

The Python standard library functions urllib.parse.urlsplit and urlparse accepted domain names that included square brackets which isn't valid according to RFC 3986. Square brackets are only meant to be used as delimiters for specifying IPv6 and IPvFuture hosts in URLs. This could result in differential parsing across the Python URL parser and other specification-compliant URL parsers.

CVSS v3
6.3
EG Score
6.3(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

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
Severity63% × 45%
Exploitation2% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
74%
KEV
Not listed

Published

January 31, 2025

Last Modified

July 31, 2026

Advisory Details (9)

Auto-updated Jul 30, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr, github_commit.
github_commit

commit ff4e5c25666f (python/cpython)

Fix landed in python/cpython commit ff4e5c25666f — awaiting tagged release

https://github.com/python/cpython/commit/ff4e5c25666f63544071a6b075ae8b25c98b7a32
github_commit

commit b8b4b713c5f8 (python/cpython)

Fix landed in python/cpython commit b8b4b713c5f8 — awaiting tagged release

https://github.com/python/cpython/commit/b8b4b713c5f8ec0958c7ef8d29d6711889bc94ab
github_commit

commit 526617ed68cd (python/cpython)

Fix landed in python/cpython commit 526617ed68cd — awaiting tagged release

https://github.com/python/cpython/commit/526617ed68cde460236c973e5d0a8bad4de896ba
github_commit

commit a7084f6075c9 (python/cpython)

Fix landed in python/cpython commit a7084f6075c9 — awaiting tagged release

https://github.com/python/cpython/commit/a7084f6075c9595ba60119ce8c62f1496f50c568
github_commit

commit 90e526ae67b1 (python/cpython)

Fix landed in python/cpython commit 90e526ae67b1 — awaiting tagged release

https://github.com/python/cpython/commit/90e526ae67b172ed7c6c56e7edad36263b0f9403
github_commit

commit d89a5f6a6e65 (python/cpython)

Fix landed in python/cpython commit d89a5f6a6e65 — awaiting tagged release

https://github.com/python/cpython/commit/d89a5f6a6e65511a5f6e0618c4c30a7aa5aba56a
generic

Mailman 3 [CVE-2025-0938] URL parser allowed square brackets in domain names - Security-announce - python.org

https://mail.python.org/archives/list/[email protected]/thread/K4EUG6EKV6JYFIC24BASYOZS4M5XOQIB/
github_pr

gh-105704: Disallow square brackets (`[` and `]`) in domain names for parsed URLs

Fix merged in python/cpython PR #129418 on 2025-01-31 — awaiting tagged release

https://github.com/python/cpython/pull/129418
generic

[CVE-2025-0938] urlparse does not flag hostname *containing* [ or ] as incorrect · Issue #105704 · python/cpython · GitHub

https://github.com/python/cpython/issues/105704

Patch Availability(11)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(15 across 11 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.5+dfsg-2, 7.3.5+dfsg-2+deb11u1, 7.3.5+dfsg-2+deb11u2, 7.3.5+dfsg-2+deb11u3, 7.3.5+dfsg-2+deb11u47.3.5+dfsg-2+deb11u5
python3.93.9.2-1, 3.9.2-1+deb11u1, 3.9.2-1+deb11u23.9.2-1+deb11u3
Debian:12(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.11+dfsg-2 ... 7.3.23+dfsg-1 (29 versions)
python3.113.11.2-6 ... 3.11.2-6+deb12u5 (6 versions)3.11.2-6+deb12u6
Debian:13(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.18+dfsg-2
python3.133.13.2-1
Debian:14(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.18+dfsg-2
python3.133.13.2-1
Alpine:v3.18(1)
PackageVulnerable rangeFixed inDependents
python33.11.12-r0
Alpine:v3.19(1)
PackageVulnerable rangeFixed inDependents
python33.11.12-r0
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
python33.12.9-r0
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
python33.12.9-r0
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
python33.12.9-r0
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
python33.12.9-r0
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
python33.12.9-r0

Weakness Classification(1)

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

Additional Vendor Advisories

(9)

Data Freshness Timeline

(refreshed 6× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 179 total refreshes for this CVE.

  1. 2026-09-07 16:00 UTCEPSS rescore
  2. 2026-09-06 13:46 UTCEPSS rescore
  3. 2026-09-04 13:59 UTCEPSS rescore
  4. 2026-09-04 05:05 UTCEPSS rescore
  5. 2026-09-02 14:10 UTCEPSS rescore
  6. 2026-09-01 19:35 UTCOSV refresh
  7. 2026-09-01 13:52 UTCEPSS rescore
  8. 2026-08-30 19:16 UTCEPSS rescore
  9. 2026-08-30 19:16 UTCEPSS rescore
  10. 2026-08-30 01:21 UTCEPSS rescore
  11. 2026-08-28 21:39 UTCEPSS rescore
  12. 2026-08-27 14:24 UTCEPSS rescore
  13. 2026-08-26 14:44 UTCEPSS rescore
  14. 2026-08-25 13:47 UTCEPSS rescore
  15. 2026-08-24 14:15 UTCEPSS rescore
  16. 2026-08-23 00:18 UTCEPSS rescore
  17. 2026-08-21 23:47 UTCEPSS rescore
  18. 2026-08-20 22:54 UTCEPSS rescore
  19. 2026-08-19 17:02 UTCEPSS rescore
  20. 2026-08-18 13:47 UTCEPSS rescore
  21. 2026-08-17 13:46 UTCEPSS rescore
  22. 2026-08-16 14:55 UTCEPSS rescore
  23. 2026-08-16 02:13 UTCEPSS rescore
  24. 2026-08-15 21:07 UTCOSV refresh
  25. 2026-08-15 01:29 UTCEPSS rescore
Show 75 more
  1. 2026-08-13 21:59 UTCEPSS rescore
  2. 2026-08-12 13:49 UTCEPSS rescore
  3. 2026-08-10 23:58 UTCEPSS rescore
  4. 2026-08-09 13:45 UTCEPSS rescore
  5. 2026-08-08 16:35 UTCEPSS rescore
  6. 2026-08-07 16:26 UTCEPSS rescore
  7. 2026-08-06 13:45 UTCEPSS rescore
  8. 2026-08-05 19:16 UTCEPSS rescore
  9. 2026-08-05 19:16 UTCEPSS rescore
  10. 2026-08-04 15:08 UTCEPSS rescore
  11. 2026-08-04 10:37 UTCEPSS rescore
  12. 2026-08-03 10:35 UTCEPSS rescore
  13. 2026-08-02 02:25 UTCEPSS rescore
  14. 2026-08-01 04:14 UTCEPSS rescore
  15. 2026-07-31 14:25 UTCVendor advisory
  16. 2026-07-31 14:25 UTCGHSA enrichment
  17. 2026-07-31 14:09 UTCVendor advisory
  18. 2026-07-31 14:09 UTCGHSA enrichment
  19. 2026-07-30 23:20 UTCVendor advisory
  20. 2026-07-30 23:20 UTCGHSA enrichment
  21. 2026-07-30 22:22 UTCEG score recompute
  22. 2026-07-30 22:22 UTCVendor advisory
  23. 2026-07-30 22:22 UTCGHSA enrichment
  24. 2026-07-30 16:26 UTCEPSS rescore
  25. 2026-07-30 01:29 UTCEPSS rescore
  26. 2026-07-28 15:35 UTCEPSS rescore
  27. 2026-07-27 14:12 UTCEPSS rescore
  28. 2026-07-26 14:53 UTCEPSS rescore
  29. 2026-07-25 14:17 UTCEPSS rescore
  30. 2026-07-25 14:17 UTCEPSS rescore
  31. 2026-07-23 14:17 UTCEPSS rescore
  32. 2026-07-23 02:47 UTCEG score recompute
  33. 2026-07-22 14:07 UTCEPSS rescore
  34. 2026-07-22 14:07 UTCEPSS rescore
  35. 2026-07-21 15:24 UTCEPSS rescore
  36. 2026-07-20 17:07 UTCEPSS rescore
  37. 2026-07-19 14:30 UTCEPSS rescore
  38. 2026-07-19 02:28 UTCEPSS rescore
  39. 2026-07-19 02:28 UTCEPSS rescore
  40. 2026-07-18 10:03 UTCEPSS rescore
  41. 2026-07-18 10:03 UTCEPSS rescore
  42. 2026-07-16 17:02 UTCEPSS rescore
  43. 2026-07-16 17:02 UTCEPSS rescore
  44. 2026-07-15 16:57 UTCEPSS rescore
  45. 2026-07-15 16:57 UTCEPSS rescore
  46. 2026-07-15 01:59 UTCEPSS rescore
  47. 2026-07-15 01:59 UTCEPSS rescore
  48. 2026-07-14 08:40 UTCOSV refresh
  49. 2026-07-13 22:29 UTCEPSS rescore
  50. 2026-07-13 22:29 UTCEPSS rescore
  51. 2026-07-13 06:12 UTCEPSS rescore
  52. 2026-07-12 05:45 UTCEPSS rescore
  53. 2026-07-12 05:45 UTCEPSS rescore
  54. 2026-07-11 08:26 UTCEPSS rescore
  55. 2026-07-09 19:09 UTCEPSS rescore
  56. 2026-07-09 19:09 UTCEPSS rescore
  57. 2026-07-08 15:14 UTCEPSS rescore
  58. 2026-07-07 13:45 UTCEPSS rescore
  59. 2026-07-06 16:26 UTCEPSS rescore
  60. 2026-07-06 16:26 UTCEPSS rescore
  61. 2026-07-06 02:22 UTCEPSS rescore
  62. 2026-07-05 02:30 UTCEPSS rescore
  63. 2026-07-04 06:30 UTCEPSS rescore
  64. 2026-07-04 06:30 UTCEPSS rescore
  65. 2026-07-02 17:00 UTCEPSS rescore
  66. 2026-07-01 15:06 UTCEPSS rescore
  67. 2026-06-30 23:21 UTCEPSS rescore
  68. 2026-06-28 14:07 UTCEPSS rescore
  69. 2026-06-28 14:07 UTCEPSS rescore
  70. 2026-06-28 04:55 UTCEPSS rescore
  71. 2026-06-28 04:55 UTCEPSS rescore
  72. 2026-06-27 03:08 UTCEPSS rescore
  73. 2026-06-26 09:23 UTCOSV refresh
  74. 2026-06-25 13:49 UTCEPSS rescore
  75. 2026-06-25 13:49 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-0938?
CVE-2025-0938 is a medium vulnerability published on January 31, 2025. The Python standard library functions urllib.parse.urlsplit and urlparse accepted domain names that included square brackets which isn't valid according to RFC 3986. Square brackets are only meant to be used as delimiters for specifying IPv6 and IPvFuture hosts in URLs. This could result in…
When was CVE-2025-0938 disclosed?
CVE-2025-0938 was first published in the National Vulnerability Database on January 31, 2025, with the most recent update on July 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-0938 actively exploited?
CVE-2025-0938 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 26.5% of all scored CVEs.
What is the CVSS score of CVE-2025-0938?
CVE-2025-0938 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2025-0938?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-0938, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-0938

Explore →

Is Your Infrastructure Affected by CVE-2025-0938?

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