API traffic interception via prefix-matched localhost hostnames
Published Jan 12, 2026 · Updated Jan 12, 2026
Improper certificate validation in Weblate Client before 1.17.0 allows context-dependent attackers to intercept API traffic. Weblate.should_verify_ssl treated any URL authority beginning with 127.0.0.1 as localhost and disabled TLS certificate verification instead of comparing the parsed hostname exactly. The attack requires a crafted API URL in an untrusted wlc configuration and user invocation, exposing request or response data to interception.
Summary
What happened
Improper certificate validation in Weblate Client before 1.17.0 allows context-dependent attackers to intercept API traffic. Weblate.should_verify_ssl treated any URL authority beginning with 127.0.0.1 as localhost and disabled TLS certificate verification instead of comparing the parsed hostname exactly. The attack requires a crafted API URL in an untrusted wlc configuration and user invocation, exposing request or response data to interception.
The record
- CVE
- CVE-2026-22250
- Published
- Jan 12, 2026
- Updated
- Jan 12, 2026
- Vendor
- Weblate
- Product
- Weblate Client
- Classifications
- CWE-295, T1557
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 12, 2026CVE publishedPublication date reported by the CVE source.
- Jan 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.17.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo