← Back
CVE-2026-20230
CISA KEV
high
CVSS 8.6
[KEV] SSRF (Server-Side Request Forgery) in Cisco ssrf (CVE-2026-20230)
Summary
SSRF in Cisco ssrf (CVE-2026-20230). Data can be tampered with by attackers. Listed in CISA KEV — actively exploited.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-20230** has been found in Cisco ssrf.
Data can be tampered with by attackers. CVSS score: 8.6/10.
Note: CISA has officially confirmed this is **actively exploited in the wild**. Treat it with elevated urgency.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Cisco ssrf CVE-2026-20230" on the vendor's site.
CVE-2026-20230 (Cisco ssrf) — CWE-918 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Listed in CISA KEV — actively exploited, treat as top priority.
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 Cisco ssrf.
📍 Affected scope
Cisco ssrf — .
🔥 Severity
Severity: High (CVSS 8.6/10). Data can be tampered with by attackers **Listed in CISA KEV** — actively exploited in the wild, treat as top priority.
🔧 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 'ssrf' .` 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 'ssrf' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `ssrf` を grep し、稼働しているサービス・バージョンを把握する。
-
4Consider incident declaration escalate
Notify SOC / on-callCISA KEV登録済 = 実環境で悪用が観測されている。Step 3 で兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
References
- CISCO https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-cucm-ssrf-cXPnHcW?vs_f=Cisco%20Security%20Advisory%26vs_cat=Security%20Intelligence%26vs_type=RSS%26vs_p=Cisco%20Unified%20Communications%20Manager%20Server-Side%20Request%20Forgery%20Vulnerability%26vs_k=1
- exploit 134c704f-9b21-4f2e-91b3-4a467353bcc0
- patch [email protected]
- web https://nvd.nist.gov/vuln/detail/CVE-2026-20230
- web https://github.com/advisories/GHSA-fcv7-pchj-75c2
- web https://denizhalil.com/2026/06/12/cve-2026-20230-cisco-unified-cm-ssrf
- web 134c704f-9b21-4f2e-91b3-4a467353bcc0