Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-92576 – Server-Side Request Forgery (SSRF) – HKUDS nanobot before 0.3.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-92576 is a Server-Side Request Forgery (SSRF) vulnerability in HKUDS nanobot (PyPI package nanobot-ai), affecting all versions prior to 0.3.0. The flaw resides in the WebFetchTool component’s _validate_url() function, which fails to adequately block requests to internal IP ranges and private addresses. The issue is rated CRITICAL (CVSS v4.0 base score 9.2) and allows unauthenticated, network-based exploitation.

Technical details

  • Root cause: The _validate_url() function in nanobot’s WebFetchTool inadequately validates and filters URLs before the tool fetches them, failing to block internal/private IP ranges.
  • Trigger conditions: An attacker sends a message or prompt to the nanobot instance instructing it to use its web-fetching capability to retrieve a URL pointing at an internal or restricted destination.
  • Attack vector: Network-based; no authentication or user interaction is required beyond the ability to submit a message/prompt processed by the bot’s WebFetchTool.
  • Impact: The bot can be coerced into fetching cloud provider metadata endpoints, localhost services, and RFC 1918 (private) addresses, enabling extraction of IAM credentials and internal service data reachable from the host running nanobot.

Affected software

  • HKUDS nanobot (PyPI package nanobot-ai): all versions before 0.3.0
  • Version 0.3.0 and later are not affected (patched)

Severity

  • CVSS v3.1 Base Score: 8.6 (High) — Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
  • CVSS v4.0 Base Score: 9.2 (Critical) — Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade nanobot (nanobot-ai) to version 0.3.0 or later, which addresses the URL validation flaw.
  • If immediate upgrade is not possible:
    • Restrict outbound network traffic from hosts running nanobot to prevent access to cloud metadata endpoints (e.g., 169.254.169.254) and internal/private IP ranges (RFC 1918).
    • Enforce a strict allow-list of permitted external domains for any URL-fetching functionality exposed to the bot.
    • Disable or restrict the WebFetchTool capability where not required, and monitor egress traffic for anomalous internal fetch attempts.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge