← Back
CVE-2026-59702
critical
CVSS 9.3
SSRF (Server-Side Request Forgery) in CVE-2026-59702 (CVE-2026-59702)
Summary
SSRF in CVE-2026-59702 (CVE-2026-59702). Confidential information can be exposed externally. Exploitable via `POST /api/pack`.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-59702** has been found in CVE-2026-59702.
Attackers can target a specific entry point like `POST /api/pack` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-59702 CVE-2026-59702" on the vendor's site.
CVE-2026-59702 (CVE-2026-59702) — CWE-918 / CVSS v3 9.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/pack
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**SSRF** (CWE-918) exists in CVE-2026-59702. Attackers reach the vulnerable code path via `POST /api/pack` without authentication.
📍 Affected scope
CVE-2026-59702 — . Attack surface: POST /api/pack.
🔥 Severity
Severity: Critical (CVSS 9.3/10). Confidential information can be exposed externally
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `POST /api/pack` requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.依存マニフェストで影響コンポーネントを特定する。
-
3Hunt for indicators of compromise detect
grep 'POST /api/pack' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /api/pack` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
7Post-deployment verification verify
Replay attack against POST /api/pack on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
References
- web https://github.com/CrazyForks/repomix/commit/c748b524f41225e7fc6f89ad0084520901a453cf
- web https://github.com/yamadashy/repomix
- web https://github.com/yamadashy/repomix/issues/1703
- web https://www.vulncheck.com/advisories/repomix-server-side-request-forgery-via-unvalidated-repository-urls-in-post-api-pack
- web https://nvd.nist.gov/vuln/detail/CVE-2026-59702
- web https://github.com/advisories/GHSA-5wj3-m77q-j278