# CVE-2025-70950: gohttp is vulnerable to directory traversal via a crafted request

> Attackers can perform directory traversal via crafted requests in the gohttp library, potentially reading unauthorized files.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 May 2026
- **Updated:** 19 May 2026
- **Also known as:** GHSA-rg3p-p27c-2f39, GO-2026-5619

## What is CVE-2025-70950?

CVE-2025-70950 is a high-severity path traversal vulnerability in n/a, published on 19 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in gohttp commit 34ea51 allows attackers to execute a directory traversal via supplying a crafted request.

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

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

3 open source packages ship an affected version, including github.com/itang/gohttp.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/itang/gohttp` | Go | All versions | None |
| `github.com/itang/gohttp` | Go | All versions to 0.0.0-20170713062009-34ea516ae408 | None |
| `github.com/itang/gohttp` | Go | All versions to 0.0.0-20170713062009-34ea516ae408 | None |

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

Upgrade to a fixed version.

## Is CVE-2025-70950 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-70950 is a high-severity path traversal vulnerability in n/a, published on 19 May 2026. 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-70950 exists.

Affected packages and fixed versions:
- github.com/itang/gohttp (Go): affected all versions; no fix listed
- github.com/itang/gohttp (Go): affected all versions up to 0.0.0-20170713062009-34ea516ae408; no fix listed
- github.com/itang/gohttp (Go): affected all versions up to 0.0.0-20170713062009-34ea516ae408; no fix listed

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

## Sources

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

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