CVE-2026-103031wlc
NVD
Vulnerability Summary
Impact wlc follows URLs returned by a Weblate API, including pagination links and object, file, and repository URLs. Origin validation previously used Python’s urllib.parse, while the underlying HTTP transport used urllib3. A crafted URL containing a backslash before @ could be interpreted differently by the two parsers, pass the origin check, and connect to an attacker-selected host. A malicious or compromised Weblate server—or an attacker who convinces a user to connect wlc to an untrusted server—could cause requests to arbitrary systems reachable from the user’s machine. Targets may include loopback services, private network hosts, and cloud instance metadata endpoints. Depending on the invoked operation, this could expose sensitive data or trigger state-changing requests. Patches The issue was fixed in https://github.com/WeblateOrg/wlc/pull/1581 by validating request origins with urllib3’s parser, matching the parser used to select the actual HTTP connection target. Users should upgrade to wlc 2.1.1 or later. Workarounds Do not connect wlc to untrusted Weblate instances. If upgrading is not immediately possible, restrict outbound network access from systems running wlc so they can reach only the intended Weblate server. Running wlc in an isolated environment without access to internal services or cloud metadata endpoints also reduces exposure. There is no wlc configuration option that fully prevents this parser-differential issue; upgrading is the recommended remediation. References This issue was reported by dark_river via HackerOne.
CVSS v3.1 Base Metrics — Score 6.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NAttack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionRequired
ScopeChanged
ConfidentialityLow
IntegrityLow
AvailabilityNone
Affected & Patched Versions
- wlc <2.1.1
- wlc 2.1.1
What to do
Fix it during your normal patch cycle. No exploitation is confirmed yet.
- Check whether you run wlc and which version.
- Update to a patched version listed above, then confirm the new version.
Timeline
- Jul 25, 2026Published
- Jul 25, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new wlc CVEsYou are reading CVE-2026-103031. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsExternal References
Data last checked: Nov 19, 2026 02:00 UTC