How severe is GHSA-gr35-vpx2-qxhc?

GHSA-gr35-vpx2-qxhc has a CVSS score of 2.6/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-gr35-vpx2-qxhc?

GHSA-gr35-vpx2-qxhc affects the following packages: weblate (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-gr35-vpx2-qxhc?

Update weblate to 5.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gr35-vpx2-qxhc is resolved across your whole dependency graph.

How do I detect GHSA-gr35-vpx2-qxhc in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for weblate. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-gr35-vpx2-qxhc 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.

How does O3 Security protect against GHSA-gr35-vpx2-qxhc?

O3 pinpoints whether GHSA-gr35-vpx2-qxhc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-gr35-vpx2-qxhc actively exploited in the wild?

No public exploit code has been indexed for GHSA-gr35-vpx2-qxhc 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-gr35-vpx2-qxhc?

GHSA-gr35-vpx2-qxhc 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-gr35-vpx2-qxhc?

GHSA-gr35-vpx2-qxhc is classified as CWE-212 (CWE-212). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-gr35-vpx2-qxhc published, and has it been updated?

GHSA-gr35-vpx2-qxhc was published on November 5, 2025 and was last updated on June 6, 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

GHSA-gr35-vpx2-qxhc

LOW

Weblate leaks the IP of project member inviting user to be reviewer in Audit log

Also known asCVE-2025-64326PYSEC-2025-126PYSEC-2025-230

Published

Nov 5, 2025

Updated

Jun 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk5th percentile+0.13%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐍weblate

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

Summary

Weblate leaks the IP address of the project member inviting the user to the project in the audit log.

Details

The audit log included IP addresses from admin-triggered actions, and those could be viewed by invited users.

Impact

The inviting user's (admin's) IP address could be leaked to invited users.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`weblate`	all versions	5.14.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for weblate. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update weblate to 5.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gr35-vpx2-qxhc 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.
How O3 protects you
O3 pinpoints whether GHSA-gr35-vpx2-qxhc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-gr35-vpx2-qxhc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Weblate leaks the IP address of the project member inviting the user to the project in the audit log. ### Details The audit log included IP addresses from admin-triggered actions, and those could be viewed by invited users. ### Impact The inviting user's (admin's) IP address could be leaked to invited users.

O3 Security · Impact-Aware SCA

Is GHSA-gr35-vpx2-qxhc in your dependencies?

O3 detects GHSA-gr35-vpx2-qxhc across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works