Weblate is a web-based localization tool. In versions prior to 2026.7, several endpoints look up objects in a globally scoped manner rather than restricting the lookup to projects the user can access, so they return HTTP 403 (Forbidden) instead of 404 (Not Found) when a user requests an object they are not authorized to see. This difference lets unauthorized users infer whether a given object exists in a private Weblate project. The issue has been fixed in version 2026.7.
CVE-2026-55227
This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(medium)
- EG Risk
- 19(Track)EG Risk 19/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity43% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 8%
- KEV
- Not listed
Published
August 26, 2026
Last Modified
August 27, 2026
Advisory Details (2)
Auto-updated Aug 26, 2026commit 836bc082803d (WeblateOrg/weblate)
Fix landed in WeblateOrg/weblate commit 836bc082803d — awaiting tagged release
https://github.com/WeblateOrg/weblate/commit/836bc082803d49d02f2831ec8339268eb66bcdaeObservable object existence disclosure in private Weblate projects via globally scoped object lookups · Advisory · WeblateOrg/weblate · GitHub
https://github.com/WeblateOrg/weblate/security/advisories/GHSA-2p9g-x3cv-5hh4Vendor Advisories for CVE-2026-55227(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| weblate | 1.9 ... 5.9.2 (168 versions) | 2026.7 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 21:08 UTCEG score recompute
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 17:30 UTCEG score recompute
- 2026-08-27 17:07 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 21:25 UTCEG score recompute
- 2026-08-26 21:03 UTCEG score recompute
- 2026-08-26 21:01 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-55227?
When was CVE-2026-55227 disclosed?
Is CVE-2026-55227 actively exploited?
What is the CVSS score of CVE-2026-55227?
How do I remediate CVE-2026-55227?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55227
Is Your Infrastructure Affected by CVE-2026-55227?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.