Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The wlc package before 2.0.1 may send an unscoped API token to a URL defined in project configuration when run in an untrusted directory tree, such as a pull request checkout. An attacker who controls that configuration can receive the user's token if the user supplies it through WLC_KEY or --key without also setting the URL. Upgrade to wlc 2.0.1 or newer, which requires WLC_URL or --url alongside an unscoped key; until then, always set the API URL explicitly when using an unscoped key.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 2.3 | Low | 3.1 | CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0008, the 1st percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:09 UTC First seen by agentprime
- 31 Oct 2026, 14:09 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-3mqq-hv9c-85hc
- OSV: GHSA-3mqq-hv9c-85hc
- github.com/WeblateOrg/wlc/security/advisories/GHSA-3mqq-hv9c-85hc
- github.com/WeblateOrg/wlc/pull/1500
- github.com/WeblateOrg/wlc/commit/15cbdfc5b2c6183ef6864ea758091643a0ce6c89
- github.com/WeblateOrg/wlc
- github.com/WeblateOrg/wlc/releases/tag/2.0.1