/

CVE-2026-61792

Severity:

HIGH RISK

(7.7)

Path Traversal (CWE-22) in Weblate App Store Metadata

CVE-2026-61792

Deferred

Vulnerability type

Category:

Path Traversal

CWE:

CWE-22, CWE-59, CWE-693

Impact:

Arbitrary File Disclosure

Severity:

HIGH RISK

(7.7)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A path traversal vulnerability in Weblate's App store metadata download feature allows a project administrator to read files outside the project's repository. The issue becomes risky when attacker-influenced paths are resolved without reliably confining them to the intended repository directory.

Affected context

The vulnerability affects Weblate deployments using the App store metadata download functionality in versions before 2026.7. It occurs when a project-administrator-level user can influence a metadata path and the resulting file access is not fully restricted to the associated repository. This issue represents an incomplete remediation of an earlier path traversal vulnerability.

Exploit preconditions

  • Attack surface: Weblate's App store metadata download feature - Required access: Project administrator privileges - Trigger point: Processing and resolving an attacker-influenced metadata

file path

  • Why exploitation is possible: Path resolution does not consistently

enforce repository confinement, allowing references to files outside the

intended directory

Why this happens

The underlying bug is insufficient canonicalization and confinement of user-influenced filesystem paths. A path is accepted for repository-related access without reliably verifying that its resolved location remains beneath the authorized repository root. This maps primarily to CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), with related concerns involving link resolution (CWE-59) and incomplete application of a security control (CWE-693).

Potential impact

  • An attacker may read sensitive files from the Weblate host.
  • Exposed files could contain credentials, configuration data, or source code.
  • The disclosure could enable follow-on compromise of connected services.
  • Project or organizational confidentiality could be reduced.

General mitigation guidance

Mitigation generally focuses on enforcing a single trusted repository root for every file access. Common defensive patterns include canonicalizing paths before authorization, rejecting traversal components, verifying that resolved paths remain descendants of the permitted directory, and handling symbolic links according to an explicit security policy. File access should use secure-by-default APIs, minimize trust in user-controlled metadata, and run application processes with only the filesystem privileges they require.

How teams detect issues like this

Detection can include static analysis for filesystem APIs that concatenate user-controlled values, especially where canonicalization and containment checks are absent. Code review should examine repository download handlers, archive or metadata processing, symbolic-link behavior, and authorization after path resolution. Runtime monitoring can alert on repository features accessing unexpected host paths, while policy enforcement can restrict Weblate service accounts from reading sensitive locations. Automated security review tools may help identify incomplete traversal defenses.

Sources

SourceLink
github.comgithub.com/WeblateOrg/weblate/commit/299fb28315674ae3fb010e96031951cacfe367db
github.comgithub.com/WeblateOrg/weblate/commit/33a9acb5ad223a927a56ffd741bbddf28a54a5e3
github.comgithub.com/WeblateOrg/weblate/security/advisories/GHSA-xwj4-fp82-r2rj

Frequently asked

questions

Exploitation generally requires project administrator privileges in Weblate,

rather than unauthenticated access.

A successful attacker may read files outside the affected project's

repository, subject to the permissions of the Weblate process.

Resolve paths canonically and authorize them only when they remain within the

intended repository root, including an explicit policy for symbolic links.

Treat metadata paths as untrusted input, use secure path-handling APIs, apply

least-privilege filesystem permissions, and test traversal and link-resolution

cases during code review and automated security testing.

Find out what's already
exploitable in your codebase.