How severe is GHSA-2mmv-7rrp-g8xh?

GHSA-2mmv-7rrp-g8xh has a CVSS score of 2.5/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-2mmv-7rrp-g8xh?

GHSA-2mmv-7rrp-g8xh affects the following packages: wlc (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-2mmv-7rrp-g8xh?

Update wlc to 1.17.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2mmv-7rrp-g8xh is resolved across your whole dependency graph.

How do I detect GHSA-2mmv-7rrp-g8xh in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wlc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2mmv-7rrp-g8xh if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-2mmv-7rrp-g8xh actively exploited in the wild?

No public exploit code has been indexed for GHSA-2mmv-7rrp-g8xh yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-2mmv-7rrp-g8xh?

GHSA-2mmv-7rrp-g8xh has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 5th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-2mmv-7rrp-g8xh?

GHSA-2mmv-7rrp-g8xh is classified as CWE-295 (CWE-295). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-2mmv-7rrp-g8xh published, and has it been updated?

GHSA-2mmv-7rrp-g8xh was published on January 12, 2026 and was last updated on July 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

LOW severity

Weblate command-line client susceptible to SSL verification skipGHSA-2mmv-7rrp-g8xh

LOWFix: WeblateOrg/wlc#1097

GHSA-2mmv-7rrp-g8xh is a low-severity (CVSS 2.5) CWE-295 vulnerability in wlc. A fix is available for wlc — see the affected versions and patch details below.

Also known asCVE-2026-22250PYSEC-2026-2051

Published

Jan 12, 2026

Updated

Jul 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-2mmv-7rrp-g8xh.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs5th percentile — riskier than 5% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐍wlc

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

The SSL verification would be skipped for some crafted URLs.

Patches

https://github.com/WeblateOrg/wlc/pull/1097

Workarounds

Avoid using untrusted wlc configurations, as that might cause insecure connections.

References

This issue was reported to us by wh1zee via HackerOne.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`wlc`	all versions	1.17.0`pip install --upgrade 'wlc==1.17.0'`

Affected Products

1 product · 1 configurations

Application

wlcweblate

< 1.17.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wlc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update wlc to 1.17.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2mmv-7rrp-g8xh is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact The SSL verification would be skipped for some crafted URLs. ### Patches * https://github.com/WeblateOrg/wlc/pull/1097 ### Workarounds Avoid using untrusted wlc configurations, as that might cause insecure connections. ### References This issue was reported to us by [wh1zee](https://hackerone.com/wh1zee) via HackerOne.