VULNpocalypse

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

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-04 15:41 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

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.

Description quoted from the CVE record (assigned by VulnCheck, published 2026-07-08).

Weakness: Server-Side Request Forgery (SSRF)

How it can be exploited

Exploitable over the network with low attack complexity with no special attack requirements needing no privileges and no user interaction. Impact: confidentiality high, integrity low, availability none. 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

CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: yes. Technical impact: partial.

Public exploit evidence (Exploit Observer)

Exploit Observer found 5 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 8 references on Exploit Observer

Live scores

EPSS
0.004
low predicted chance of attack
VEDAS
0.988
strong exploit evidence
On CISA KEV
Not listed
Detection rule
Nuclei · Suricata

Who is affected

ProductAffectedNot affected
repomixbefore 1.14.1
up to and including c748b52		Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

Fixed versions stated in the CVE record: 1.14.1.

Vendor guidance:

How to detect it

Nuclei template (active check)

Repomix - Server-Side Request Forgery

Repomix contains a server-side request forgery vulnerability in the unauthenticated POST /api/pack endpoint. The multipart url field is passed to git clone without validating the scheme or destination, so an attacker can supply an http:// URL and cause the server to issue an outbound request to arbitrary hosts, including private-network addresses and cloud metadata services.

Name and description quoted from the template, written by VEDAS.

The template sends 1 request (POST /api/pack); it confirms through an out-of-band callback (interactsh), so the scanner must be able to receive it; it decides using word matchers. Severity in the template: critical. Marked as not yet verified against a live vulnerable target.

Run it against a host you own or are authorised to test:

bash
nuclei -u https://your-host -t CVE-2026-59702.yaml
Show the template (50 lines)
yaml
id: CVE-2026-59702

info:
  name: "Repomix - Server-Side Request Forgery"
  author: vedas-arpsyndicate
  severity: critical
  description: |
    Repomix contains a server-side request forgery vulnerability in the unauthenticated
    POST /api/pack endpoint. The multipart url field is passed to git clone without validating
    the scheme or destination, so an attacker can supply an http:// URL and cause the server to
    issue an outbound request to arbitrary hosts, including private-network addresses and cloud
    metadata services.
  reference:
    - https://www.exploit.observer/?keyword=CVE-2026-59702&match=exact
    - https://subdomain.center/?engine=ammonites&keyword=repomix&match=exact
  classification:
    cvss-metrics: 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
    cvss-score: 9.2
    cve-id: CVE-2026-59702
    cwe-id: CWE-918
  metadata:
    verified: false
  tags: cve,cve2026,repomix,ssrf
http:
  - raw:
      - |
        POST /api/pack HTTP/1.1
        Host: {{Hostname}}
        Content-Type: multipart/form-data; boundary=----vedasboundary

        ------vedasboundary
        Content-Disposition: form-data; name="url"

        http://{{interactsh-url}}/
        ------vedasboundary
        Content-Disposition: form-data; name="format"

        plain
        ------vedasboundary
        Content-Disposition: form-data; name="options"

        {}
        ------vedasboundary--

    matchers-condition: and
    matchers:
      - type: word
        part: interactsh_protocol
        words:
          - "http"

CVE-2026-59702.yaml on GitHub

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-59702 Repomix SSRF. Add them to your Suricata rule set and reload.

Show the rules
suricata
alert http $EXTERNAL_NET any -> $HOME_NET any (msg:"VEDAS CVE-2026-59702 Repomix SSRF"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/api/pack"; nocase; http.request_body; content:"name=\"url\""; nocase; content:"://"; distance:0; classtype:web-application-attack; reference:cve,CVE-2026-59702; reference:url,https://www.exploit.observer/?keyword=CVE-2026-59702&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=repomix&match=exact; sid:1072403; rev:1;)

CVE-2026-59702.rules on GitHub

References

Vendor advisories and patches

Technical analysis and advisories

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.

Supporting partners

Feasible SecurityAskealGoTrust