In Weblate releases before version 5.17, a repository‑boundary validation uses a simple string prefix check on resolved absolute paths. This check is not aware of individual path segments, allowing an attacker to create a symbolic link or junction whose external path starts with the same string as the repository root (e.g., "repo" and "repo_outside"). When such a path is resolved, the validation incorrectly accepts it as located within the repository, potentially exposing files that are outside the intended repository scope to the attacker. The vulnerability can compromise confidentiality by granting read access to arbitrary files stored on the server where Weblate is deployed.

The flaw affects all Weblate installations running a version older than 5.17. Weblate versions 5.17 and newer contain a fix that makes the boundary check path‑segment aware.

The vulnerability carries a CVSS score of 5, indicating medium severity. No EPSS score is available, and the issue is not listed in CISA’s KEV catalog. While the exact exploitation probability is uncertain, the required action of creating a symlink or junction suggests that the attack vector is local or trusted‑user based, but could be leveraged remotely if an attacker gains permission to modify repository configurations or upload content. The risk is therefore moderate, emphasizing that the side effect is data exposure rather than code execution or denial of service.