# CVE-2025-6152: Steel Browser files.routes.ts handleFileUpload path traversal

> Remote attackers can exploit a path traversal flaw in Steel Browser's file upload handler to read or modify arbitrary files on the system.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jun 2025
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-wcpr-fw9g-mjcm

## What is CVE-2025-6152?

CVE-2025-6152 is a medium-severity path traversal vulnerability in Steel Browser, published on 17 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, was found in Steel Browser up to 0.1.3. This affects the function handleFileUpload of the file api/src/modules/files/files.routes.ts. The manipulation of the argument filename leads to path traversal. It is possible to initiate the attack remotely. The patch is named 7ba93a10000fb77ee01731478ef40551a27bd5b9. It is recommended to apply a patch to fix this issue.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Steel Browser.

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

No fix has been published for CVE-2025-6152 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-6152 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6152 is a medium-severity path traversal vulnerability in Steel Browser, published on 17 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6152 exists.

Affected product: Steel Browser. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-6152/ (Markdown: https://insights.sbomify.com/CVE-2025-6152/index.md)
```

## Sources

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

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