CWE · MITRE source
CWE-61UNIX Symbolic Link (Symlink) Following
The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.
A product that allows UNIX symbolic links (symlink) as part of paths whether in internal code or through user input can allow an attacker to spoof the symbolic link and traverse the file system to unintended locations or access arbitrary files. The symbolic link can permit an attacker to read/write/corrupt a file that they originally did not have permissions to access.
Last updated: 22 August 2026 14:14 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: mostly · 2 mapping(s) from 2 framework(s): STIG oracle linux 8 1 (mostly) · CAPEC 1 (partial)
OWASP Top 10 for Web (2025)
This weakness contributes to A01:2025 Broken Access Control.
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
NIST 800-53 r5 controls that address this weakness (0)AI-assisted
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2026-54420 KEV | 8.7 | 8.5 | 0.0144 | 2026-06-14 |
CVE-2024-28185 UPD | 8.1 | 10.0 | 0.0706 | 2024-04-18 |
CVE-2024-28189 UPD | 8.1 | 10.0 | 0.0721 | 2024-04-18 |
CVE-2026-34078 UPD | 7.7 | 10.0 | 0.0168 | 2026-04-07 |
CVE-2026-39861 | 7.5 | 10.0 | 0.0071 | 2026-04-21 |
CVE-2024-54661 UPD | 7.4 | 9.8 | 0.0080 | 2024-12-04 |
CVE-2024-54148 UPD | 7.4 | 9.8 | 0.0085 | 2024-12-23 |
CVE-2025-23394 UPD | 7.3 | 9.8 | 0.0053 | 2025-05-26 |
CVE-2025-62161 | 7.2 | 10.0 | 0.0024 | 2025-11-06 |
CVE-2025-62596 | 7.1 | 10.0 | 0.0025 | 2025-11-06 |
CVE-2026-63125 | 7.0 | 9.9 | 0.0066 | 2026-08-21 |
CVE-2026-55447 | 6.8 | 9.6 | 0.0047 | 2026-06-23 |
CVE-2024-22014 UPD | 6.7 | 8.8 | 0.0076 | 2024-04-15 |
CVE-2025-55345 UPD | 6.7 | 8.8 | 0.0084 | 2025-08-13 |
CVE-2026-27976 UPD | 6.6 | 8.8 | 0.0049 | 2026-02-26 |
CVE-2026-29203 UPD | 6.6 | 8.8 | 0.0049 | 2026-05-08 |
CVE-2026-56748 UPD | 6.6 | 8.8 | 0.0058 | 2026-07-27 |
CVE-2023-37460 UPD | 6.5 | 8.1 | 0.0248 | 2023-07-25 |
CVE-2026-6475 UPD | 6.5 | 8.8 | 0.0032 | 2026-05-14 |
CVE-2021-32518 UPD | 6.2 | 7.5 | 0.0167 | 2021-07-07 |
CVE-2024-47515 UPD | 6.2 | 8.1 | 0.0056 | 2024-12-24 |
CVE-2025-67487 | 6.2 | 8.6 | 0.0041 | 2025-12-09 |
CVE-2025-33225 UPD | 6.2 | 8.4 | 0.0030 | 2025-12-16 |
CVE-2026-39860 UPD | 6.2 | 9.0 | 0.0019 | 2026-04-08 |
CVE-2019-16775 UPD | 6.1 | 7.7 | 0.0333 | 2019-12-13 |