# CVE-2025-67487: Static Web Server is vulnerable to symbolic link Path Traversal

> An attacker with write access to the web root can create symlinks to read files outside the intended directory.

- **Severity:** Medium 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Dec 2025
- **Updated:** 9 Dec 2025
- **Also known as:** GHSA-459f-x8vq-xjjm

## What is CVE-2025-67487?

CVE-2025-67487 is a medium-severity path traversal vulnerability in static-web-server, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Static Web Server (SWS) is a production-ready web server suitable for static web files or assets. Versions 2.40.0 and below contain symbolic links (symlinks) which can be used to access files or directories outside the intended web root folder. 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. This issue is fixed in version 2.40.1.

Weakness: CWE-59 (Improper Link Resolution Before File Access), CWE-61 (UNIX Symbolic Link (Symlink) Following)

## Which versions are affected by CVE-2025-67487?

2 open source packages ship an affected version, including static-web-server. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `static-web-server` | crates.io | All versions | 2.40.1 |
| `static-web-server` | crates.io | All versions | 2.40.1 |

Products: Static-Web-Server Static Web Server.

## How do I fix CVE-2025-67487?

Upgrade static-web-server to 2.40.1 or later.

## Is CVE-2025-67487 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-67487 exists.

## Other vulnerabilities in static-web-server

- [CVE-2026-27480](https://insights.sbomify.com/CVE-2026-27480/): Static Web Server: Timing-Based Username Enumeration in Basic Authentication (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-67487 and fix it if it is affected.

What it is: CVE-2025-67487 is a medium-severity path traversal vulnerability in static-web-server, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-67487 exists.

Affected packages and fixed versions:
- static-web-server (crates.io): affected all versions; fixed in 2.40.1
- static-web-server (crates.io): affected all versions; fixed in 2.40.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-67487/ (Markdown: https://insights.sbomify.com/CVE-2025-67487/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-67487
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-67487
- OSV: https://osv.dev/vulnerability/CVE-2025-67487

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-67487/
Summaries are generated and may contain mistakes; the official description above is the record.
