Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍 PyPI

GHSA-mpf5-3vph-q75r

MEDIUM

GHSA-mpf5-3vph-q75r is a medium-severity (CVSS 4.3) CWE-862 vulnerability in weblate. O3 Security confirms whether GHSA-mpf5-3vph-q75r is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Weblate: Improper access control for the translation memory in API

Also known asCVE-2026-33214PYSEC-2026-152
Published
Apr 16, 2026
Updated
Jun 8, 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 Risk15th percentile0.00%
0.00%0.25%0.49%0.74%0.0%0.0%0.2%0.2%0.2%May 26Jul 26Aug 26

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

Impact

The translation memory API exposed unintended endpoints, which in turn didn't do proper access control.

Patches

Workarounds

Blocking access to /api/memory/ in the HTTP server removes access to this feature.

References

This issue was reported by ggamno via HackerOne.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIweblateall versions5.17

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. Fix

    Update weblate to 5.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mpf5-3vph-q75r is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-mpf5-3vph-q75r 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-mpf5-3vph-q75r. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact The translation memory API exposed unintended endpoints, which in turn didn't do proper access control. ### Patches * https://github.com/WeblateOrg/weblate/pull/18513 ### Workarounds Blocking access to `/api/memory/` in the HTTP server removes access to this feature. ### References This issue was reported by [ggamno](https://hackerone.com/ggamno) via HackerOne.
O3 Security · Impact-Aware SCA

Is GHSA-mpf5-3vph-q75r in your dependencies?

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