You are using an out of date browser. It may not display this or other websites correctly. You should upgrade or use an alternative browser.
symlink traversal
About this tag
Symlink traversal vulnerabilities allow attackers to break out of intended file system boundaries by following symbolic links to access or overwrite files outside the container or application sandbox. On WindowsForum.com, discussions cover high-severity CVEs in container build tools like Buildah (CVE-2024-1753) and Podman (CVE-2025-9566), where malicious Containerfiles or kube play commands can mount host directories or overwrite host files. Also covered is CVE-2025-8110 in Gogs, a self-hosted Git service, where a symlink path traversal in the PutContents API enables arbitrary file access. These threads emphasize the importance of input validation, path sanitization, and prompt patching to prevent container escapes and host compromise.
The container build toolchain that many organizations treat as a routine developer utility just produced a reminder: a single badly-validated path can break the isolation model that makes containers safe. In March 2024 Buildah (and downstream Podman Build) was assigned CVE-2024-1753 — a...
Podman’s kube play command contains a symlink traversal flaw that can let a malicious or compromised container cause Podman to overwrite arbitrary files on the host filesystem — a high‑severity integrity and availability risk that was fixed in Podman v5.6.1 but remains a critical operational...
CISA confirmed on January 12, 2026 that it has added a high‑severity Gogs path‑traversal vulnerability, tracked as CVE‑2025‑8110, to its Known Exploited Vulnerabilities (KEV) Catalog — a move that triggers urgent remediation requirements for federal agencies under Binding Operational Directive...