How many CVEs have patched resolve_symlinks?

2 published CVEs changed resolve_symlinks in WeblateOrg/weblate, in 3 distinct patches totalling 17 changed lines, between 2025 and 2026.

What is the latest CVE that changed resolve_symlinks?

CVE-2026-40256 (Weblate: Prefix-Based Repository Boundary Check Bypass via Symlink/Junction Path Prefix Collision), published 2026-04-15, changed lines 177 to 191 of weblate/vcs/base.py.

How does resolve_symlinks compare to the rest of WeblateOrg/weblate?

WeblateOrg/weblate has 44 CVEs with a located fix in total; 2 of them changed resolve_symlinks.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

WeblateOrg/weblate

Function

resolve_symlinks

Name: resolve_symlinks in WeblateOrg/weblate: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

weblate/vcs/base.py

Last patched April 15, 2026

2

CVEs

That changed this function

3

Distinct patches

Backports counted once

17

Lines changed

Added plus removed

2025–2026

Years

By CVE publication date

Overview

resolve_symlinks in WeblateOrg/weblate was changed by 2 published CVE fixes between 2025 and 2026, in 3 distinct patches that added or removed 17 lines in total.

WeblateOrg/weblate has 44 CVEs with a located fix in total, so 5% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed resolve_symlinks, newest first, with the lines each fix touched.

Weblate: Prefix-Based Repository Boundary Check Bypass via Symlink/Junction Path Prefix Collision
CVE-2026-40256 · lines 177–191 · +8 −5
Medium · CVSS 5.0
EPSS 0.4%2026-04-15
Weblate has an arbitrary file read via symbolic links
CVE-2025-68279 · lines 183–186 · +4 −0
High · CVSS 7.7
EPSS 0.4%2025-12-18

Get an alert when the next CVE fix lands in WeblateOrg/weblate, with the patched functions.

Monitor weblate CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in WeblateOrg/weblate changed by the most CVE fixes.

get_remote_branch3 CVEs · weblate/vcs/git.py validate3 CVEs · weblate/api/serializers.py get_file2 CVEs · weblate/vcs/mercurial.py commit2 CVEs · weblate/vcs/mercurial.py zip_download2 CVEs · weblate/utils/views.py add2 CVEs · weblate/trans/models/component.py

All patched functions in WeblateOrg/weblate

Frequently asked questions

Common questions about CVE fixes to resolve_symlinks.

How many CVEs have patched resolve_symlinks?: 2 published CVEs changed resolve_symlinks in WeblateOrg/weblate, in 3 distinct patches totalling 17 changed lines, between 2025 and 2026.
What is the latest CVE that changed resolve_symlinks?: CVE-2026-40256 (Weblate: Prefix-Based Repository Boundary Check Bypass via Symlink/Junction Path Prefix Collision), published 2026-04-15, changed lines 177 to 191 of weblate/vcs/base.py.
How does resolve_symlinks compare to the rest of WeblateOrg/weblate?: WeblateOrg/weblate has 44 CVEs with a located fix in total; 2 of them changed resolve_symlinks.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track WeblateOrg/weblate CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing