# CVE-2026-124582: WebTorrent File Path torrent.js getFileModtimes path traversal


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-q97r-7gmj-rv8g

## What is CVE-2026-124582?

CVE-2026-124582 is a medium-severity vulnerability in WebTorrent, published on 9 Nov 2026. 

### Official description

A vulnerability was identified in WebTorrent up to 2.8.5/3.0.21. Affected by this vulnerability is the function getFileModtimes of the file torrent.js of the component File Path Handler. Such manipulation of the argument file.path leads to path traversal. The attack may be performed from remote. The exploit is publicly available and might be used. The reported GitHub issue was closed with the label "not planned".

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

## Which versions are affected by CVE-2026-124582?


## How do I fix CVE-2026-124582?

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

## Is CVE-2026-124582 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-124582 and fix it if it is affected.

What it is: CVE-2026-124582 is a medium-severity vulnerability in WebTorrent, published on 9 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-124582 exists.

Affected product: WebTorrent. 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-2026-124582/ (Markdown: https://insights.sbomify.com/CVE-2026-124582/index.md)
```

## Sources

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

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