VYPR

CWE-61

UNIX Symbolic Link (Symlink) Following

CompoundIncompleteLikelihood: High

Description

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.

Hierarchy (View 1000)

Parents

Children

none

Related attack patterns (CAPEC)

CAPEC-27

CVEs mapped to this weakness (183)

page 10 of 10
  • CVE-2026-14699LowJul 5, 2026
    Zcaceres
    Markdownify Mcp
    risk 0.00cvss 3.3epss 0.00

    A weakness has been identified in zcaceres markdownify-mcp up to 1.1.0. The affected element is the function assertPathAllowed of the file src/Markdownify.ts. Executing a manipulation can lead to symlink following. The attack can only be executed locally. The pull request to fix…

  • CVE-2026-13748MedJun 29, 2026
    Snowflake
    Snowflake CLI
    risk 0.00cvss 6.3epss 0.00

    Improper restriction of file path resolution in Snowflake CLI versions prior to 3.19 allowed arbitrary local file content to be read and transmitted to Snowflake services. An attacker could exploit this by supplying crafted repository or project content that referenced files…

  • CVE-2025-43853MedMay 15, 2025
    Bytecodealliance
    Webassembly Micro Runtime
    risk 0.00cvss 5.5epss 0.00

    The WebAssembly Micro Runtime's (WAMR) iwasm package is the executable binary built with WAMR VMcore which supports WebAssembly System Interface (WASI) and command line interface. Anyone running WAMR up to and including version 2.2.0 or WAMR built with libc-uvwasi on Windows is…