CWE-61: UNIX Symbolic Link (Symlink) Following
low-riskThe 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.
Common Consequences
Detection Methods
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
Real-World Examples (10)
| CVE | CVSS | EPSS | KEV |
|---|---|---|---|
| CVE-2024-28185 | 10.0 | 65.0% | — |
| CVE-2024-28189 | 10.0 | 57.6% | — |
| CVE-2023-37460 | 8.1 | 36.6% | — |
| CVE-2019-11251 | 4.8 | 3.4% | — |
| CVE-2019-11249 | 6.5 | 2.8% | — |
| CVE-2021-4287 | 5.0 | 1.7% | — |
| CVE-2019-11246 | 6.5 | 1.5% | — |
| CVE-2017-14798 | 7.3 | 0.8% | — |
| CVE-2021-39134 | 8.2 | 0.7% | — |
| CVE-2025-23394 | 9.8 | 0.7% | — |