Secuno
ENNL
Book demo

CVE-2026-92576

8.6 HIGH
  1. Published16 Sept 2026

Description

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.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeChanged
ConfidentialityHigh
IntegrityNone
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2025-565639.8
A Server-Side Request Forgery vulnerability exists in sat_proxy.php in Zenith Satellite…
CVE-2026-685369.8
Server-Side Request Forgery / Local File Inclusion in Apache MyFace Core. Older…
CVE-2026-925668.2
DataGear through 6.0.0 contains a server-side request forgery vulnerability in the…
CVE-2026-615599.6
`@zereight/mcp-gitlab` is a Model Context Protocol server for GitLab. Starting in…
CVE-2026-545498.3
Meta Ads MCP is a Model Context Protocol (MCP) server that lets AI assistants run Meta…
CVE-2026-634438.3
Coder allows organizations to provision remote development environments via Terraform.…

Frequently asked

Is CVE-2026-92576 being actively exploited?

CVE-2026-92576 is not in the CISA KEV catalog.

How severe is CVE-2026-92576?

CVE-2026-92576 has a CVSS 3.1 base score of 8.6, rated high.

How do I fix CVE-2026-92576?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-92576 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.