CVE-2026-17534

MEDIUMPre-NVD 5.55.5—
EchelonGraph scoreHIGH confidence

Score 5.5 from GitHub Security Advisory published 2026-07-27. a secondary CVSS source baseline 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Kimi Code (@moonshot-ai/kimi-code) before 0.27.0 implements FetchURL SSRF hardening as a static hostname and IP-literal denylist in assertSafeFetchTarget, without resolving DNS or re-validating hosts after HTTP redirects. An attacker who can influence a FetchURL call (for example via prompt injection) can supply a crafted public hostname that resolves to loopback or another internal address, or a public URL that redirects to such a target, and thereby reach internal network services that the denylist was intended to block. FetchURL is included in the default auto-approve tool set, so the call does not require interactive user confirmation in manual mode.

CVSS v3
5.5
EG Score
5.5(high)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 27, 2026

Last Modified

July 27, 2026

Advisory Details (3)

Auto-updated Jul 27, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit, github_pr.
github_pr

fix(security): close FetchURL SSRF bypasses and DNS-rebinding window

Fix merged in MoonshotAI/kimi-code PR #1791 on 2026-07-17 — awaiting tagged release

https://github.com/MoonshotAI/kimi-code/pull/1791
github_commit

commit 31449728b72d (MoonshotAI/kimi-code)

Fix landed in MoonshotAI/kimi-code commit 31449728b72d — awaiting tagged release

https://github.com/MoonshotAI/kimi-code/commit/31449728b72df94e22bcb2de350a1e7624895e30
generic

GitHub - MoonshotAI/kimi-code: Kimi Code CLI — The Starting Point for Next-Gen Agents · GitHub

https://github.com/MoonshotAI/kimi-code

Vendor Advisories for CVE-2026-17534(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 10× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-29 16:36 UTCGHSA enrichment
  2. 2026-07-28 18:40 UTCEG score recompute
  3. 2026-07-28 18:40 UTCGHSA enrichment
  4. 2026-07-27 20:42 UTCEG score recompute
  5. 2026-07-27 20:42 UTCGHSA enrichment
  6. 2026-07-27 12:22 UTCEG score recompute
  7. 2026-07-27 11:23 UTCEG score recompute
  8. 2026-07-27 10:23 UTCEG score recompute
  9. 2026-07-27 10:12 UTCEG score recompute
  10. 2026-07-27 10:12 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-17534?
CVE-2026-17534 is a medium vulnerability published on July 27, 2026. Kimi Code (@moonshot-ai/kimi-code) before 0.27.0 implements FetchURL SSRF hardening as a static hostname and IP-literal denylist in assertSafeFetchTarget, without resolving DNS or re-validating hosts after HTTP redirects. An attacker who can influence a FetchURL call (for example via prompt…
When was CVE-2026-17534 disclosed?
CVE-2026-17534 was first published in the National Vulnerability Database on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-17534 actively exploited?
CVE-2026-17534 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.7% of all scored CVEs.
What is the CVSS score of CVE-2026-17534?
CVE-2026-17534 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-17534?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-17534, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-17534

Explore →

Is Your Infrastructure Affected by CVE-2026-17534?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs