In FreedomBox before 26.15, unprivileged user accounts can read/write files for which they lack permissions by setting the authorized_keys file to be a symlink. NOTE: FreedomBox is a Debian Pure Blend, which means that it distributes its software through Debian repositories.
CVE-2026-100395 is a vulnerability in LXC version 7.0.0 and earlier where the lxc-copy tool and the liblxc clone() API can follow attacker-controlled symbolic links when updating /etc/hostname in a copied container root filesystem. This can lead to a privileged process overwriting files outside the intended container root filesystem if the source rootfs is attacker-controlled or less trusted. The issue arises because the clone operation preserves symlinks before updating the hostname, allowing a symlink to point outside the destination rootfs. Unprivileged users and independent cloning implementations are not affected. Using the LXC_CLONE_KEEPNAME flag avoids the hostname update and mitigates the issue.
Node Version Manager (nvm) versions 0.2.0 through 0.40.8 do not properly check if the .nvmrc file is a symbolic link. This allows an attacker to craft a symlinked .nvmrc pointing to arbitrary files, causing nvm commands to read and print the contents of those files in command output or logs. Version 0.41.0 fixes this by not printing the contents of symlinked .nvmrc files and only accepting valid version strings or aliases.
In BuildKit versions prior to v0.34.1, a malicious client with access to the BuildKit control APIs can submit a build request that sets an extended attribute on a file outside the BuildKit state directory. Extended attributes in the trusted. or security. namespaces may also be set, potentially giving a program on the host elevated privileges. This issue affects build services that accept build requests from untrusted users. The issue is fixed in v0.34.1.
NVIDIA Slurm is subject to a symlink resolution issue in the container cleanup code that could allow an attacker to remove files outside of their control on the compute node.
Pi-hole is a DNS sinkhole that protects devices from unwanted content without installing any client-side software. From 6.4.2 until 6.5, the root-run advanced/Scripts/updatecheck.sh cron job applies truncate -s 0 and chmod 644 to /etc/pihole/versions while following symbolic links in a directory owned by the pihole user. An attacker executing as pihole can replace that path with a symlink so the scheduled root operations truncate or create an arbitrary root-owned file, or race the operations so chmod makes a sensitive target world-readable without truncating it. This issue is fixed in version 6.5.
zip is a zip library for Rust that supports reading and writing simple ZIP files. From 7.2.0 until 9.0.0, ZipArchive::extract and ZipArchive::extract_unwrapped_root_dir use safe_prepare_path in src/read/zipfile.rs and simplified_components in src/path.rs to validate symbolic link targets with a lexical prefix comparison rather than resolving each intermediate link. An attacker who knows or can guess the absolute extraction destination can create a chain whose apparent target remains under the destination while an intermediate symlink resolves outside it, allowing attacker-controlled files to be created or overwritten with the extracting process's privileges. On Windows, discarded drive and UNC prefixes can permit a single-link escape when the process has SeCreateSymbolicLinkPrivilege, such as through administrator rights or Developer Mode. This regression is distinct from CVE-2025-29787. This issue is fixed in version 9.0.0.
The AsyncHttpClient library allows Java applications to execute HTTP requests and asynchronously process HTTP responses. From 2.0.0 until 2.16.1 and 3.0.12, PropertiesBasedResumableProcessor stores resumable download state at the predictable shared path $java.io.tmpdir/ahc/ResumableAsyncHandler.properties with default permissions and link-following file operations. A local user who can read the shared store can see download URLs, including embedded user information or query tokens. A local user who can write within or pre-create the affected shared store directory can plant a symbolic link that the client follows when saving state, truncating and overwriting a target file writable by the client process. The filesystem path is used when ResumableAsyncHandler decorates another AsyncHandler, while the no-argument constructors use a no-op processor and are unaffected. This issue is fixed in versions 2.16.1 and 3.0.12.
CVE-2026-50612 is a critical vulnerability in QNAP Systems Inc. QuMagie involving a Unix symbolic link (symlink) following flaw. A remote attacker with a user account can exploit this to compromise system security. The issue is fixed in QuMagie version 2.9.2 and later.
CVE-2026-41541 is a medium severity vulnerability in QNAP Systems Inc.'s Qsync Central involving a Unix symbolic link (symlink) following issue. A remote attacker with a user account can exploit this vulnerability to compromise system security. The vulnerability has been fixed in Qsync Central versions 5.0.0.7 and later, 5.1.0.3 and later, 5.2.0.5 and later, and 5.3.0.2 and later.
The ngx_cache_purge module before version 3.0.4 allows file deletion via a symbolic link (symlink) attack when nginx and the served application run under the same user account. This occurs because the module follows symlinks during cache purge operations, relying on nginx's ngx_walk_tree() which uses stat() and thus follows symlinks. Version 3.0.4 fixes the issue for symlinks created at arbitrary earlier times but does not address a time-of-check to time-of-use (TOCTOU) race condition.
CVE-2026-107810 is a high-severity vulnerability in 0xJacky's nginx-ui versions from 2.0.0 up to but not including 2.5.0. It involves improper link resolution before file access in the backup and restore functionality, allowing an authenticated user with backup creation and restoration privileges to inject malicious symlinks. This can lead to persistent configuration injection or denial of service. The issue is fixed in version 2.5.0.
Claude Code validated that a target file path resided within the project working directory at permission-check time, but re-resolved the path at write time without repeating that validation. This time-of-check to time-of-use (TOCTOU) gap allowed an attacker who could write to the workspace to atomically replace a project file with a symlink, causing Claude Code to follow the symlink and write its output to an arbitrary file outside the project sandbox. Exploitation required the ability to win a race condition against the write operation and write access to the shared workspace, enabling a lower-privileged attacker to redirect benign edits to sensitive files (e.g., shell configuration) in a higher-privileged session.
Users on standard Claude Code auto-update have received this fix already. Users performing manual updates are advised to update to the latest version.
Thank you to hackerone.com/c_h4ck_0 for reporting this issue.
CVE-2026-91099 is a medium severity vulnerability in HP Linux Imaging and Printing Software (HPLIP) involving symbolic link (symlink) following (CWE-61). Multiple vulnerabilities were identified and remediated by HP affecting several components that could allow remote code execution, privilege escalation, denial of service, information disclosure, or unauthorized file modification under certain conditions. The affected versions are those prior to 3.26.6. The CVSS 4.0 base score is 5.1, indicating a medium impact. No known exploits are reported in the wild. HP has remediated these issues, but no direct patch link is provided in the data.
CVE-2026-57825 is a medium severity vulnerability in the opam package manager for OCaml. Versions before 2.5.2 mishandle symbolic links during the processing of .install files, allowing the sandbox protection mechanism to be bypassed. This flaw can lead to integrity violations but does not impact confidentiality or availability.
Dell PowerProtect Cyber Recovery versions prior to 20.3 contain a UNIX Symbolic Link (Symlink) Following vulnerability (CWE-61). This flaw allows a low privileged local attacker to potentially perform script injection. The vulnerability has a medium severity with a CVSS score of 5.8. No official patch or remediation guidance has been provided yet by the vendor.
CVE-2026-75038 is a vulnerability in the ilya-zlobintsev LACT software up to version 0.10.0 that involves unsafe following of UNIX symbolic links (symlinks). This flaw can be exploited locally to cause a denial-of-service condition. The vulnerability does not impact confidentiality but can affect integrity and availability. No official patch or fix information is provided in the available data.
Incus is a system container and virtual machine manager. Prior to version 7.3.0, an unprivileged, project-confined Incus user (a non-admin TLS/RBAC identity with `can_create_images` and `can_create_instances`) can execute arbitrary code as root on the host. A crafted image ships `backup.yaml` as a symlink to a host file. When the root daemon writes the instance's backup file, it follows the symlink. Version 7.3.0 patches the issue.
CVE-2026-64846 is a vulnerability in the Nix package manager prior to version 2.35.0. It involves a time-of-check/time-of-use (TOCTOU) race condition related to symbolic link handling during the LocalStore restore path when using the recursive-nix experimental feature. This race condition can allow the Nix process or nix-daemon to create or truncate an empty file outside the build sandbox with the daemon user's permissions. The vulnerability does not allow arbitrary content writes and requires winning the race. The issue is fixed in version 2.35.0.
Dell AppSync Version 4.6.0.0, Dell Metro Node Version 8.0.0, Dell UCC Edge Version 3.0.1, Dell VxRail Version 8.0.322, Dell PowerMax Version 10.3.0, Dell Unity Version 5.4, Dell PowerFlex Manager Version 4.5.4, Dell PowerFlex Intelligent Catalog Versions 46.377.00 and 46.382.00 and Dell PowerFlex Rack version 4.5.4 and prior versions, contain(s) an UNIX Symbolic Link (Symlink) Following vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Elevation of privileges.