HKUDS nanobot Provider-returned Image URL image_generation.py _download_image_data_url server-side request forgery
A vulnerability has been found in HKUDS nanobot up to 0.2.1. This affects the function _download_image_data_url of the file nanobot/providers/image_generation.py of the component Provider-returned Image URL Handler. The manipulation leads to server-side request forgery. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The identifier of the patch is 5095. It is recommended to apply a patch to fix this issue. The vendor explains: "We confirm that provider-returned image URLs required the same SSRF protections applied to other network retrieval paths. (...) The patch is currently available on main and is planned for the next patch release, v0.3.1."
- Published
- Aug 7, 2026
- Updated
- Aug 14, 2026
- EPSS
- 0.4% · 28th percentile
- CWE
- CWE-918
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
8
Monitor
Low priority for now.
- CVSS
- 8 / 40 · 2.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · VulDB
- 5.3
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulDB). Independent of NVD's CPE analysis and usually ahead of it.
HKUDS nanobot
- 0.2.0, 0.2.1affected
Same product
hkuds: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-2577Nanobot Unauthenticated WhatsApp Session Hijack via WebSocket Bridge40Plan
- CVE-2026-92576HKUDS nanobot before 0.3.0 Server-Side Request Forgery via WebFetchTool36Monitor
- CVE-2026-48716nanobot: Path traversal via unsanitized WhatsApp document fileName enables arbitrary file write34Monitor
- CVE-2026-49139Nanobot < 0.2.1 SSRF via Microsoft Teams Channel serviceUrl Poisoning28Monitor
- CVE-2026-90809HKUDS nanobot ExecTool shell.py ExecTool._spawn argument injection27Monitor
- CVE-2026-90808HKUDS nanobot ExecTool shell.py ExecTool._spawn incomplete blacklist21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- VulDB CNA Teamcoordinator
- Eric-c (VulDB User)reporter
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-9257640 days apartHKUDS nanobot before 0.3.0 Server-Side Request Forgery via WebFetchTool36Monitor
- CVE-2026-4913967 days apartNanobot < 0.2.1 SSRF via Microsoft Teams Channel serviceUrl Poisoning28Monitor
- CVE-2026-4913867 days apartNanobot < 0.2.1 SSRF via web_fetch Tool Redirect Following21Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2026-2577172 days apartNanobot Unauthenticated WhatsApp Session Hijack via WebSocket Bridge40Plan
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-918 · Server-Side Request Forgery (SSRF)CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- gist.github.com/YLChen-007/44bc77ac259e461c6938cc6c286c4430
- github.com/HKUDS/nanobot/
- github.com/HKUDS/nanobot/pull/5095
- vuldb.com/cve/CVE-2026-19246
- vuldb.com/submit/865113
- vuldb.com/vuln/387000
- vuldb.com/vuln/387000/cti
Vendor advisories and official records. Exploit/PoC links are deliberately left out.