A vulnerability was found in mf-yang openclaw-cn up to 0.2.1. This affects the function clickViaPlaywright of the file src/browser/routes/agent.act.ts of the component Browser Control HTTP API. Performing a manipulation results in server-side request forgery. It is possible to initiate the attack remotely. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2026-17458
This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(low)
- EG Risk
- 33(Track)EG Risk 33/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 computedSeverity63% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
July 26, 2026
Last Modified
July 26, 2026
Advisory Details (2)
Auto-updated Jul 26, 2026GitHub - mf-yang/openclaw-cn: 中文社区版OpenClaw,同原版保持定期更新,已内置钉钉、企业微信、飞书、QQ、微信以及国内网络环境优化。你的专属个人AI助手。支持所有操作系统和平台。🦞 · GitHub
https://github.com/mf-yang/openclaw-cn/[Security] Browser interaction-driven navigation bypasses `browser.ssrfPolicy` and reaches loopback/private targets · Issue #562 · mf-yang/openclaw-cn · GitHub
https://github.com/mf-yang/openclaw-cn/issues/562Vendor Advisories for CVE-2026-17458(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 4× in last 7d / 4× 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.
- 2026-07-26 11:36 UTCEG score recompute
- 2026-07-26 11:34 UTCNVD updateCVSS v4 → 2.1
- 2026-07-26 10:20 UTCEG score recompute
- 2026-07-26 10:17 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-14721EG 10.0EPSS p95CRITICAL
- CVE-2018-18843EG 10.0CRITICAL
- CVE-2018-19047EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-3774EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2018-1789NVD 8.4EG 9.9CRITICAL
Frequently asked(4)
What is CVE-2026-17458?
When was CVE-2026-17458 disclosed?
What is the CVSS score of CVE-2026-17458?
How do I remediate CVE-2026-17458?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-17458
Is Your Infrastructure Affected by CVE-2026-17458?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.