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.
CVE-2026-59702
Score 9.3 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-08. a secondary CVSS source baseline 9.3; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.3
- EG Score
- 9.3(high)
- EPSS
- —
- KEV
- Not listed
Published
July 8, 2026
Last Modified
July 8, 2026
Advisory Details (4)
Auto-updated Jul 8, 2026Website server allows SSRF via arbitrary http:// URLs to internal network endpoints · Issue #1703 · yamadashy/repomix · GitHub
https://github.com/yamadashy/repomix/issues/1703repomix - Server-Side Request Forgery via Unvalidated Repository URLs in POST /api/pack | Advisories | VulnCheck
https://www.vulncheck.com/advisories/repomix-server-side-request-forgery-via-unvalidated-repository-urls-in-post-api-packGitHub - yamadashy/repomix: 📦 Repomix is a powerful tool that packs your entire repository into a single, AI-friendly file. Perfect for when you need to feed your codebase to Large Language Models (LLMs) or other AI tools like Claude, ChatGPT, DeepSeek, Perplexity, Gemini, Gemma, Llama, Grok, and more. · GitHub
https://github.com/yamadashy/repomixcommit c748b524f412 (CrazyForks/repomix)
Fix landed in CrazyForks/repomix commit c748b524f412 — awaiting tagged release
https://github.com/CrazyForks/repomix/commit/c748b524f41225e7fc6f89ad0084520901a453cfVendor Advisories for CVE-2026-59702(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-08 19:39 UTCEG score recompute
- 2026-07-08 19:39 UTCGHSA enrichment
- 2026-07-08 15:46 UTCEG score recompute
- 2026-07-08 15:45 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
Frequently asked(4)
What is CVE-2026-59702?
When was CVE-2026-59702 disclosed?
What is the CVSS score of CVE-2026-59702?
How do I remediate CVE-2026-59702?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59702
Is Your Infrastructure Affected by CVE-2026-59702?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.