Weblate is a web based localization tool. The Create Component functionality in Weblate allows authorized users to add new translation components by specifying both a version control system and a source code repository URL to pull from. However, prior to version 5.15, the repository URL field is not validated or sanitized, allowing an attacker to supply arbitrary protocols, hostnames, and IP addresses, including localhost, internal network addresses, and local filenames. When the Mercurial version control system is selected, Weblate exposes the full server-side HTTP response for the provided URL. This effectively creates a server-side request forgery (SSRF) primitive that can probe internal services and return their contents. In addition to accessing internal HTTP endpoints, the behavior also enables local file enumeration by attempting file:// requests. While file contents may not always be returned, the application’s error messages clearly differentiate between files that exist and files that do not, revealing information about the server’s filesystem layout. In cloud environments, this behavior is particularly dangerous, as internal-only endpoints such as cloud metadata services may be accessible, potentially leading to credential disclosure and full environment compromise. This has been addressed in the Weblate 5.15 release. As a workaround, remove Mercurial from VCS_BACKENDS; the Git backend is not affected. The Git backend was already configured to block the file protocol and does not expose the HTTP response content in the error message.
CVE-2025-66407
“—” beside the score: it is equal to NVD's CVSS score.
This medium-severity CVE scores 5.0 under NVD CVSS v3. EPSS exploit probability: 0.2% (15th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2025-203462 (ENISA EUVD) · GHSA-hfpv-mc5v-p9mm (GitHub Security Advisories)Source: ENISA EUVD
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 5.0
- EG Score
- 5.0MEDIUMmedium confidence
- EG Risk
- 38EG Risk 38/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity50% × 45%Impact severity (EG Severity): CVSS 5.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.2% × 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
- 0.2%
- EPSS %ILE
- 15th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (5.0): severity, escalated by confirmed exploitation. This CVE's 5.0 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.0 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
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
May 26, 2026
Last Modified
October 7, 2026
Advisory Details (3)
Auto-updated Jun 27, 2026Server-Side Request Forgery while cloning repository · Advisory · WeblateOrg/weblate · GitHub
https://github.com/WeblateOrg/weblate/security/advisories/GHSA-hfpv-mc5v-p9mmfix(vcs): sanitize mercurial error messages
Fix merged in WeblateOrg/weblate PR #17103 on 2025-12-01 — awaiting tagged release
https://github.com/WeblateOrg/weblate/pull/17103feat(vcs): extended filtering of allowed VCS URLs
Fix merged in WeblateOrg/weblate PR #17102 on 2025-12-01 — awaiting tagged release
https://github.com/WeblateOrg/weblate/pull/17102Vendor Advisories for CVE-2025-66407(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| weblate | 1.9 ... 5.9.2 (157 versions) |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 37× 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 96 of 216 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 120 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-10-25 16:08 UTCEG score recompute
- 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-10-23 12:39 UTCEG score recompute
- 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-10-18 05:19 UTCEG score recompute
- 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-10-16 16:39 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-10-12 16:48 UTCEG score recompute
- 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-10-11 20:23 UTCEG score recompute
- 2026-10-11 18:35 UTCEG score recompute
Show 71 moreShow fewer
- 2026-10-11 15:10 UTCEG score recompute
- 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-10-08 17:10 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-10-07 19:21 UTCEG score recompute
- 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-09-30 01:39 UTCOSV refresh
- 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-09-19 15:42 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-09-15 03:10 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-09-11 01:53 UTCOSV refresh
- 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-23 15:58 UTCEG score recompute
- 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-21 21:23 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-20 18:03 UTCEG score recompute
- 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-17 09:33 UTCEG score recompute
- 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-16 03:05 UTCEG score recompute
- 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-14 01:42 UTCEG score recompute
- 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-12 20:23 UTCEG score recompute
- 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.2% · 15th percentile
- 2026-08-11 22:26 UTCEG score recompute
- 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-08-11 00:21 UTCEG score recompute
- 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-08-09 21:33 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-08-08 23:35 UTCEG score recompute
- 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.2% · 13th percentile
- 2026-08-07 16:58 UTCEG score recompute
Related CVEs(same product + same CWE)
Same product
10 shownPyPI:weblate
Frequently asked(5)
What is CVE-2025-66407?
When was the CVE record for CVE-2025-66407 published?
Is CVE-2025-66407 actively exploited?
What is the CVSS score of CVE-2025-66407?
How do I remediate CVE-2025-66407?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-66407
Is Your Infrastructure Affected by CVE-2025-66407?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.