CVE-2026-59702
Unauthenticated SSRF in repomix /api/pack allows arbitrary outbound and file requests.
Is CVE-2026-59702 being exploited?
Not confirmed. CVE-2026-59702 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.44% probability of exploitation in the next 30 days.
How severe is CVE-2026-59702?
CVE-2026-59702 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-59702?
Not known from our data. No patch reference has been recorded for CVE-2026-59702, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-59702 affect?
CVE-2026-59702 affects repomix server (POST /api/pack), servers running repomix, internal services reachable from repomix host. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-59702?
Apply vendor patch if released; block egress to internal/metadata IPs and disable endpoint until fixed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated SSRF allows attacker to make arbitrary http/https/file requests, access internal services, GCP metadata, or local files.
Immediate action required
- affected< 1.14.1
- affected<= c748b52
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.