CVE-2026-59702Public exploitNetwork attack vector

Unauthenticated SSRF via unchecked repository URLs

Published Jul 8, 2026 · Updated Jul 8, 2026

SSRF in yamadashy Repomix before 1.14.1 allows remote attackers to trigger server-side requests through POST /api/pack. The parseRemoteValue path accepts http://, https://, and file:// repository URLs after checking only an owner/repository shape, then processRemoteRepo passes the reconstructed URL to git clone without a public-host allowlist. Self-hosted or development deployments without the origin secret or Turnstile key are directly reachable; successful requests can probe internal services or access local Git repositories, while response bodies are not normally returned.

CVSS severity9.2
Critical
EPSS probability0.44%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

SSRF in yamadashy Repomix before 1.14.1 allows remote attackers to trigger server-side requests through POST /api/pack. The parseRemoteValue path accepts http://, https://, and file:// repository URLs after checking only an owner/repository shape, then processRemoteRepo passes the reconstructed URL to git clone without a public-host allowlist. Self-hosted or development deployments without the origin secret or Turnstile key are directly reachable; successful requests can probe internal services or access local Git repositories, while response bodies are not normally returned.

The record

CVE
CVE-2026-59702
Published
Jul 8, 2026
Updated
Jul 8, 2026
Vendor
yamadashy
Product
Repomix
Classifications
CWE-918, CAPEC-664, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jul 8, 2026CVE publishedPublication date reported by the CVE source.
  2. Jul 8, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <1.14.1
  2. Affected versionversion=0 <=c748b52

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

yamadashy · Repomixversion=0 <1.14.1; version=0 <=c748b52

Published CVSS scores

9.2VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N
9.3VulnCheckCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-918Server-Side Request Forgery (SSRF)
CAPEC-664Server Side Request Forgery
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo