← Back
CVE-2026-22664
high
CVSS 7.7
SSRF (Server-Side Request Forgery) in fka (CVE-2026-22664)
Summary
SSRF in fka (CVE-2026-22664). Confidential information can be exposed externally. Exploitable via `Authorization header`.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-22664** has been found in fka.
Attackers can target a specific entry point like `Authorization header` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "fka CVE-2026-22664" on the vendor's site.
CVE-2026-22664 (fka) — CWE-918 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: Authorization header
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 fka. Attackers reach the vulnerable code path via `Authorization header` without authentication.
📍 Affected scope
fka — . Attack surface: Authorization header.
🔥 Severity
Severity: High (CVSS 7.7/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 request patterns matching this CVE's known IOCs. Run `grep -r 'fka' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'fka' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `fka` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory [email protected]
- exploit 134c704f-9b21-4f2e-91b3-4a467353bcc0
- patch [email protected]