HKUDS nanobot before 0.3.0 contains a server-side request forgery vulnerability in the WebFetchTool component where the _validate_url() function fails to block internal IP ranges and private addresses. Attackers can send messages instructing the bot to fetch cloud metadata endpoints, localhost services, and RFC 1918 addresses to extract IAM credentials and internal service data.
CVE-2026-92576
Score 8.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-17. a secondary CVSS source baseline 8.6; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.6
- EG Score
- 8.6(high)
- EG Risk
- 70(Attend)EG Risk 70/100SSVC: Attend
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 computedSeverity86% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 34%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 17, 2026
Advisory Details (2)
Auto-updated Sep 16, 2026HKUDS nanobot before 0.3.0 Server-Side Request Forgery via WebFetchTool | Advisories | VulnCheck
https://www.vulncheck.com/advisories/hkuds-nanobot-before-0.3.0-server-side-request-forgery-via-webfetchtoolZDI-CAN-29369: Hong Kong University Data Intelligence Lab nanobot WebFetch Server-Side Request Forgery Information Disclosure Vulnerability · Advisory · HKUDS/nanobot · GitHub
https://github.com/HKUDS/nanobot/security/advisories/GHSA-vc5v-6vwm-wf9mVendor Advisories for CVE-2026-92576(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 23× in last 7d / 23× 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-09-21 02:44 UTCEG score recompute
- 2026-09-21 02:44 UTCGHSA enrichment
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-20 14:42 UTCGHSA enrichment
- 2026-09-20 02:34 UTCEG score recompute
- 2026-09-20 02:34 UTCGHSA enrichment
- 2026-09-19 14:32 UTCGHSA enrichment
- 2026-09-19 02:30 UTCEG score recompute
- 2026-09-19 02:30 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 14:28 UTCGHSA enrichment
- 2026-09-18 02:26 UTCEG score recompute
- 2026-09-18 02:26 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-17 14:24 UTCEG score recompute
- 2026-09-17 14:24 UTCGHSA enrichment
- 2026-09-17 13:42 UTCEG score recompute
- 2026-09-17 13:41 UTCGHSA enrichment
- 2026-09-17 10:28 UTCEG score recompute
- 2026-09-17 10:28 UTCGHSA enrichment
- 2026-09-16 22:26 UTCEG score recompute
- 2026-09-16 21:54 UTCEG score recompute
- 2026-09-16 21:54 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
Frequently asked(5)
What is CVE-2026-92576?
When was CVE-2026-92576 disclosed?
Is CVE-2026-92576 actively exploited?
What is the CVSS score of CVE-2026-92576?
How do I remediate CVE-2026-92576?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-92576
Is Your Infrastructure Affected by CVE-2026-92576?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.