Static Web Server vulnerable to a symbolic link path traversal

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.5 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P · score source

EPSS

• CVE-2025-67487: 0.42% estimated exploitation activity in the next 30 days; percentile 36.13 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Symbolic links (symlinks) could be used to access files or directories outside the intended web root folder. Details SWS generally does not prevent symlinks from escaping the web server’s root directory. Therefore, if a malicious actor gains access to the web server’s root directory, they could create symlinks to access other files outside the designated web root folder either by URL or via the directory listing. PoC - Serve a directory (web root) with SWS. - Create a symlink inside the web root that points to a file outside the web root. e.g. ln -s escape.txt $HOME/.bashrc - Open http://localhost/escape.txt in your browser. - The file content will be served. Impact Any web server that runs with elevated privileges (e.g., root/administrator) and handles user-supplied file uploads is primarily impacted.

Published by the source

8 Dec 2025, 22:18 UTC

Last modified by the source

9 Dec 2025, 19:17 UTC

Source last checked

26 Oct 2026, 15:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-459f-x8vq-xjjm

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-67487

Advisory: Static Web Server vulnerable to a symbolic link path traversal
IDs: CVE-2025-67487, GHSA-459f-x8vq-xjjm
Record: https://patchnext.com/advisories/cve-2025-67487 (revision 1, source checked 26 Oct 2026, 15:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: static-web-server 2.40.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io static-web-server: affected <= 2.40.0; fixed in 2.40.1

## Suggested inspection (read-only)
- crates.io static-web-server: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on static-web-server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-459f-x8vq-xjjm (GitHub-reviewed advisory GHSA-459f-x8vq-xjjm lists affected ranges: crates.io static-web-server >=0 <=2.40.0)

Commands are suggestions: review each one before running it.