Skip to content

GHSA-2p9g-x3cv-5hh4 CVE-2026-55227 PYSEC-2026-3941

Private Weblate projects vulnerable to observable object existence disclosure via globally scoped object lookups

Medium PyPI
Severity
4.3 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.32%
Chance of exploitation in the next 30 days. Higher than 25.43% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-203 Observable Discrepancy
Fix
2026.7
Upgrade weblate to this version or later

Description

Impact

The several endpoints could leak object existence information to users who had no access to it by HTTP status code 403 instead of 404.

Patches

References

Thanks to Yaohui Wang for reporting this via GitHub.

Affected versions

PyPI

PackageVulnerableFixed in
weblate
< 2026.7
2026.7

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

weblate PyPI → 2026.7

pip
pip install --upgrade "weblate>=2026.7"
poetry
poetry add "weblate>=2026.7"
uv
uv add "weblate>=2026.7"

Severity breakdown

CVSS 3.1 4.3

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Weakness

CWE-203: Observable Discrepancy

The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.

How to prevent it
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
  • Implementation: Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success. If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files. Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-2q2q-jr9g-v9rf
Weblate has IDOR in GroupViewSet that allows authenticated project manager to gain unauthorized read access to any private project
High Also affects weblate
GHSA-vmfc-9982-2m45
Weblate SSRF: outbound URL guard misses some private ranges
Medium Also affects weblate
GHSA-6wxc-8mgq-w26m
Weblate: Stored HTML injection in editor search preview
Medium Also affects weblate
GHSA-5cmv-3rc4-7279
Weblate vulnerable to XSS via crafted Markdown
Medium Also affects weblate
GHSA-gcg5-86jr-f7jg
Weblate Vulnerable to Private Translation Enumeration via Screenshot API
Medium Also affects weblate
GHSA-cwcx-382v-8m9g
Weblate Vulnerable to Authenticated SSRF via Project Backup Import bypassing validate_repo_url
High Also affects weblate
GHSA-6j8j-4qp3-36p2
Weblate Doesn't Invalidate API Token on Password Change
Medium Also affects weblate
GHSA-ffgh-3jrf-8wvh
Weblate: Prefix-Based Repository Boundary Check Bypass via Symlink/Junction Path Prefix Collision
Medium Also affects weblate
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor