Skip to content

GHSA-3g2f-4rjg-9385 CVE-2026-21889 PYSEC-2026-2037

Weblate leaks information via screenshots

High PyPI
Severity
0.0 / 10
High · CVSS 4.0
Exploit chance (EPSS)
0.39%
Chance of exploitation in the next 30 days. Higher than 32.79% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-284 Improper Access Control
Fix
5.15.2
Upgrade weblate to this version or later

Description

Impact

The screenshot images were served directly by the HTTP server without proper access control. This could allow an unauthenticated user to access screenshots after guessing their filename.

Patches

References

Thanks to Lukas May and Michael Leu for reporting this.

Affected versions

PyPI

PackageVulnerableFixed in
weblate
< 5.15.2
5.15.2

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 → 5.15.2

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

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N

Attack vector
Network
Attack complexity
High
Attack requirements
None
Privileges required
Low
User interaction
None
Confidentiality (vulnerable system)
Low
Integrity (vulnerable system)
None
Availability (vulnerable system)
None
Confidentiality (subsequent systems)
Low
Integrity (subsequent systems)
None
Availability (subsequent systems)
None

CVSS 3.1 7.5

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

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

Weakness

CWE-284: Improper Access Control

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

How to prevent it
  • Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • 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.

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-2p9g-x3cv-5hh4
Private Weblate projects vulnerable to observable object existence disclosure via globally scoped object lookups
Medium 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
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