Monthly
Symlink-following path traversal in RubyGems gem extraction allows arbitrary file writes outside the extraction root when a pre-existing symlink within the destination directory redirects to an external filesystem path. Affecting all RubyGems versions before 4.0.13, the flaw in `Gem::Package#extract_tar_gz` means that an attacker who can pre-position a symlink in the gem install directory before extraction occurs can cause extracted gem files to land at attacker-controlled locations outside the intended boundary. No public exploit identified at time of analysis and not listed in CISA KEV, but the CVSS 4.0 score of 6.9 reflects high integrity and availability impact once preconditions are satisfied.
Unbounded symlink-following in KubeVela's Terraform remote configuration loader allows any principal with `ComponentDefinition` create/update RBAC rights to OOM-kill the cluster-wide vela-core controller and halt all OAM application reconciliation. The root cause (CWE-59) is that `GetTerraformConfigurationFromRemote` in `pkg/controller/utils/capability.go` calls `os.ReadFile` on a symlink target without verifying the target is a regular file or bounding the read size; a repository containing `variables.tf -> /dev/zero` is sufficient to exhaust controller memory before HCL parsing is ever reached. No CISA KEV listing has been identified at time of analysis, but a complete proof-of-concept with exact reproduction commands is publicly disclosed in GHSA-fmgp-q6jx-gg3x, materially lowering the exploitation bar.
Symlink following in gitoxide before 0.52.1 and the gix crate before 0.83.0 allows an attacker who supplies a malicious repository to exfiltrate arbitrary files outside the repository boundary through submodule metadata. When Repository::submodules() processes a worktree .gitmodules that is a symlink, std::fs::read() transparently follows it to an attacker-chosen target, and the resulting bytes are parsed as submodule configuration, exposing attacker-controlled name, path, and url values. A proof-of-concept is publicly confirmed in the GHSA advisory; no CISA KEV listing was present at time of analysis.
Arbitrary file write outside the worktree boundary in gix-worktree-state (part of gitoxide) before 0.33.0 on Windows enables an attacker-controlled repository to overwrite files at arbitrary paths on a victim's filesystem. The flaw manifests when gix_worktree_state::checkout() performs an incremental materialization: a malicious repo first places a symlink entry at path P pointing outside the worktree, then a subsequent incremental checkout of a regular-file entry at the same path follows the Windows reparse point and writes attacker-supplied blob content through the link. No public exploit code is identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Symlink redirection in Spring Integration's Zip/UnZip transformer allows a local unprivileged user sharing the same host to hijack transformer output by pre-creating /tmp/ziptransformer as a symlink before application startup. Affected versions span the 6.4, 6.5, 7.0, and 7.1 release lines, covering a wide range of enterprise Java deployments that use Spring Integration's file transformation capabilities. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV, though the integrity and availability impact is rated High by the vendor-assigned CVSS score.
Filesystem containment bypass in NLTK's Downloader component allows local attackers with write access to a shared download directory to overwrite arbitrary files outside the intended install root by planting hardlinks before a download operation. All NLTK versions prior to 3.10.3 are affected via the Downloader.download and Downloader.incr_download methods, which fail to validate link targets during package extraction. No public exploit has been identified at time of analysis; risk is highest in shared multi-user environments such as HPC clusters or build servers where the NLTK data directory is world- or group-writable.
Symlink-following in the openssl-encrypt pip package (jahlives/openssl_encrypt) before 1.4.9 allows an evil-maid attacker with physical access to a target USB drive to bypass the verify-usb v2 integrity check and achieve code execution on the victim's machine. The attacker replaces a tool-tree directory with a symlink to a crafted copy that includes byte-identical visible source files and a planted __pycache__/*.pyc compiled bytecode file; CPython's rglob() does not enumerate symlinked directory contents, so the planted file is never counted, verify-usb reports PASSED, and the malicious bytecode executes when the victim launches the portable install. No public exploit has been identified at time of analysis, and the attack is gated behind physical drive access and victim interaction.
Symlink following in Dool (versions up to and including 1.3.8) allows a local attacker to cause arbitrary file truncation and overwriting when the tool is run with the non-default '--devel' flag. The vulnerable code path opens a log file without the O_NOFOLLOW flag (CWE-59), allowing a pre-placed symlink to redirect the write to any file the dool process can access - an impact that escalates from trivial to severe if dool runs under elevated privileges such as root. No public exploit code or CISA KEV active exploitation is identified; the issue was reported by CERT-PL and addressed upstream via pull request #116.
Local privilege escalation in Wibu-Systems CodeMeter Runtime allows a low-privileged local attacker to delete arbitrary files with SYSTEM privileges via an NTFS junction attack, potentially cascading to full system compromise. The cmu.exe utility creates predictable temporary files under C:\CM-Stick without validating NTFS reparse points before performing file operations; because the CodeMeter Runtime service runs as SYSTEM, any redirected file operation executes at the highest privilege level. A detailed public research writeup is available from shelltrail.com, substantially lowering the exploitation barrier; no public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV.
Remote code execution via symlink following in Plesk's Site Import and Migrator extensions allows network-accessible, low-privilege authenticated users to execute arbitrary code as root on the hosting server. Both webpros:plesk_migrator and webpros:plesk_site_import are affected across all versions per CPE wildcard data, with the flaw rooted in CWE-59 improper link resolution during privileged file operations. No public exploit or active exploitation is confirmed at time of analysis, but the low-complexity, network-accessible attack path and root-level impact make this a high-priority remediation target for Plesk hosting environments.
Symlink-following path traversal in RubyGems gem extraction allows arbitrary file writes outside the extraction root when a pre-existing symlink within the destination directory redirects to an external filesystem path. Affecting all RubyGems versions before 4.0.13, the flaw in `Gem::Package#extract_tar_gz` means that an attacker who can pre-position a symlink in the gem install directory before extraction occurs can cause extracted gem files to land at attacker-controlled locations outside the intended boundary. No public exploit identified at time of analysis and not listed in CISA KEV, but the CVSS 4.0 score of 6.9 reflects high integrity and availability impact once preconditions are satisfied.
Unbounded symlink-following in KubeVela's Terraform remote configuration loader allows any principal with `ComponentDefinition` create/update RBAC rights to OOM-kill the cluster-wide vela-core controller and halt all OAM application reconciliation. The root cause (CWE-59) is that `GetTerraformConfigurationFromRemote` in `pkg/controller/utils/capability.go` calls `os.ReadFile` on a symlink target without verifying the target is a regular file or bounding the read size; a repository containing `variables.tf -> /dev/zero` is sufficient to exhaust controller memory before HCL parsing is ever reached. No CISA KEV listing has been identified at time of analysis, but a complete proof-of-concept with exact reproduction commands is publicly disclosed in GHSA-fmgp-q6jx-gg3x, materially lowering the exploitation bar.
Symlink following in gitoxide before 0.52.1 and the gix crate before 0.83.0 allows an attacker who supplies a malicious repository to exfiltrate arbitrary files outside the repository boundary through submodule metadata. When Repository::submodules() processes a worktree .gitmodules that is a symlink, std::fs::read() transparently follows it to an attacker-chosen target, and the resulting bytes are parsed as submodule configuration, exposing attacker-controlled name, path, and url values. A proof-of-concept is publicly confirmed in the GHSA advisory; no CISA KEV listing was present at time of analysis.
Arbitrary file write outside the worktree boundary in gix-worktree-state (part of gitoxide) before 0.33.0 on Windows enables an attacker-controlled repository to overwrite files at arbitrary paths on a victim's filesystem. The flaw manifests when gix_worktree_state::checkout() performs an incremental materialization: a malicious repo first places a symlink entry at path P pointing outside the worktree, then a subsequent incremental checkout of a regular-file entry at the same path follows the Windows reparse point and writes attacker-supplied blob content through the link. No public exploit code is identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Symlink redirection in Spring Integration's Zip/UnZip transformer allows a local unprivileged user sharing the same host to hijack transformer output by pre-creating /tmp/ziptransformer as a symlink before application startup. Affected versions span the 6.4, 6.5, 7.0, and 7.1 release lines, covering a wide range of enterprise Java deployments that use Spring Integration's file transformation capabilities. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV, though the integrity and availability impact is rated High by the vendor-assigned CVSS score.
Filesystem containment bypass in NLTK's Downloader component allows local attackers with write access to a shared download directory to overwrite arbitrary files outside the intended install root by planting hardlinks before a download operation. All NLTK versions prior to 3.10.3 are affected via the Downloader.download and Downloader.incr_download methods, which fail to validate link targets during package extraction. No public exploit has been identified at time of analysis; risk is highest in shared multi-user environments such as HPC clusters or build servers where the NLTK data directory is world- or group-writable.
Symlink-following in the openssl-encrypt pip package (jahlives/openssl_encrypt) before 1.4.9 allows an evil-maid attacker with physical access to a target USB drive to bypass the verify-usb v2 integrity check and achieve code execution on the victim's machine. The attacker replaces a tool-tree directory with a symlink to a crafted copy that includes byte-identical visible source files and a planted __pycache__/*.pyc compiled bytecode file; CPython's rglob() does not enumerate symlinked directory contents, so the planted file is never counted, verify-usb reports PASSED, and the malicious bytecode executes when the victim launches the portable install. No public exploit has been identified at time of analysis, and the attack is gated behind physical drive access and victim interaction.
Symlink following in Dool (versions up to and including 1.3.8) allows a local attacker to cause arbitrary file truncation and overwriting when the tool is run with the non-default '--devel' flag. The vulnerable code path opens a log file without the O_NOFOLLOW flag (CWE-59), allowing a pre-placed symlink to redirect the write to any file the dool process can access - an impact that escalates from trivial to severe if dool runs under elevated privileges such as root. No public exploit code or CISA KEV active exploitation is identified; the issue was reported by CERT-PL and addressed upstream via pull request #116.
Local privilege escalation in Wibu-Systems CodeMeter Runtime allows a low-privileged local attacker to delete arbitrary files with SYSTEM privileges via an NTFS junction attack, potentially cascading to full system compromise. The cmu.exe utility creates predictable temporary files under C:\CM-Stick without validating NTFS reparse points before performing file operations; because the CodeMeter Runtime service runs as SYSTEM, any redirected file operation executes at the highest privilege level. A detailed public research writeup is available from shelltrail.com, substantially lowering the exploitation barrier; no public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV.
Remote code execution via symlink following in Plesk's Site Import and Migrator extensions allows network-accessible, low-privilege authenticated users to execute arbitrary code as root on the hosting server. Both webpros:plesk_migrator and webpros:plesk_site_import are affected across all versions per CPE wildcard data, with the flaw rooted in CWE-59 improper link resolution during privileged file operations. No public exploit or active exploitation is confirmed at time of analysis, but the low-complexity, network-accessible attack path and root-level impact make this a high-priority remediation target for Plesk hosting environments.