# CVE-2026-59702: repomix - Server-Side Request Forgery via Unvalidated Repository URLs in POST /api/pack

> Unauthenticated attackers can exploit repomix to perform Server-Side Request Forgery, accessing private networks and local files via unvalidated URLs.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-5wj3-m77q-j278

## What is CVE-2026-59702?

CVE-2026-59702 is a critical server-side request forgery vulnerability in repomix, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

repomix contains a server-side request forgery vulnerability in the POST /api/pack endpoint that allows unauthenticated attackers to make arbitrary outbound requests. The endpoint fails to properly validate http://, https://, and file:// URLs before passing them to git clone, enabling attackers to access private network addresses, GCP metadata services, or local filesystem paths.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-59702 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59702 is a critical server-side request forgery vulnerability in repomix, published on 8 Jul 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-2026-59702 exists.

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

## Sources

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

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