Which versions of Repomix are affected by EUVD-2026-42298?

Repomix's hosted API contains a critical server-side request forgery vulnerability (CVE-2026-59702, CVSS 9.2) allowing unauthenticated attackers to access internal networks, cloud metadata endpoints,…. A patch is available.

How to fix or mitigate EUVD-2026-42298?

Within 24 hours: Apply the latest Repomix security patch to all hosted API instances and notify all users. Within 7 days: Review POST /api/pack endpoint logs for exploitation attempts (requests with internal, metadata, or file:// URLs) and confirm patch deployment. Within 30 days: Conduct full security audit of Repomix deployment and enforce URL scheme validation on all user-supplied URL inputs.

Repomix EUVD-2026-42298

Q: What is the CVSS score of EUVD-2026-42298?

EUVD-2026-42298 has a CVSS 4.0 base score of 9.2 (Critical). CVSS vector: 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.3%.

| CVE-2026-59702 CRITICAL

Server-Side Request Forgery (SSRF) (CWE-918)

2026-07-08 VulnCheck

GHSA-5wj3-m77q-j278

SSRF Repomix

9.2

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

9.2 CRITICAL

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

9.3 CRITICAL

Unauthenticated network endpoint (PR:N/UI:N/AC:L); SSRF crosses a trust boundary to internal/metadata systems (S:C) with high confidentiality (C:H) and only minor integrity impact.

3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

Jul 08, 2026 - 16:19 vuln.today

DescriptionCVE.org

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.

AnalysisAI

Server-side request forgery in Repomix's hosted API (POST /api/pack) lets unauthenticated remote attackers coerce the server into making arbitrary outbound requests. Because the endpoint passes user-supplied URLs to git clone without validating the http://, https://, or file:// schemes, an attacker can reach internal-only network addresses, cloud metadata endpoints (e.g. GCP), and read local filesystem paths. VulnCheck reported the flaw and a vendor fix exists; no public exploit is identified at time of analysis.

Technical ContextAI

Repomix is an open-source tool that packages a repository into a single AI-friendly file; its optional web/server mode exposes a POST /api/pack endpoint that accepts a repository URL and shells out to git clone to fetch it. The root cause is CWE-918 (Server-Side Request Forgery): the endpoint trusts the user-controlled URL and does not enforce an allowlist of schemes or block private/link-local address ranges before invoking git clone. Because git's transport layer honors http://, https://, and file:// URLs, the same unvalidated input becomes both an SSRF primitive (arbitrary outbound HTTP to internal services and the cloud metadata service at 169.254.169.254) and a local file disclosure primitive via file:// paths. The affected package is identified by CPE cpe:2.3:a:repomix:repomix:*:*:*:*:*:*:*:*, covering all versions prior to the fix.

RemediationAI

Patch available per vendor advisory - an upstream fix commit exists (https://github.com/CrazyForks/repomix/commit/c748b524f41225e7fc6f89ad0084520901a453cf); a released patched version is not independently confirmed from the provided data, so upgrade to the latest Repomix release that incorporates this commit and verify the fix is present. If you cannot upgrade immediately, do not expose the Repomix web server to untrusted networks: restrict access to the POST /api/pack endpoint via network ACLs or authentication, and prefer running Repomix only as a local CLI (server mode is what carries the exposure). As compensating controls, block the server's egress to link-local and cloud metadata ranges (169.254.169.254/32 and 169.254.0.0/16) and to RFC1918 private ranges at the host or cloud firewall, and enforce IMDSv2 / disable the legacy metadata endpoint in GCP/AWS to blunt credential theft; note these egress restrictions may break legitimate clones of internally hosted repositories. Also disallow the file:// scheme for any repository input. Track and reference the upstream issue https://github.com/yamadashy/repomix/issues/1703 for the authoritative fixed release.