Quick answers
- Is CVE-2026-49138 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-49138 being exploited in the wild.
- How severe is CVE-2026-49138?
- Medium severity, with a CVSS score of 5, published 1 June 2026.
- Which products and versions are affected?
- HKUDS Nanobot < 0.2.1; nanobot-ai (PyPI) < 0.2.1, ECOSYSTEM:introduced=0,fixed=0.2.1.
- Is there a fix for CVE-2026-49138?
- Yes. nanobot-ai (PyPI): upgrade to 0.2.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-49138 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-49138?
- Check whether you run HKUDS Nanobot or nanobot-ai (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- nanobot-ai (PyPI): upgrade to 0.2.1 or later
pip install "nanobot-ai>=0.2.1"
Technical details
A Server-Side Request Forgery (SSRF) vulnerability exists in Nanobot's web_fetch tool due to improper handling of HTTP redirects. The application uses the httpx library, which automatically follows 3xx Location headers. An attacker can provide a URL that passes initial validation but subsequently redirects to a loopback (127.0.0.1) or private IP address. Because the final resolved URL is not re-validated before the request is completed, the attacker can probe or interact with internal network services. This issue is fixed in version 0.2.1.
Affected products
- HKUDS nanobot-ai < 0.2.1
Identifiers
- CVE-2026-49138
- GHSA-434r-7c99-hwf3
- PYSEC-2026-3580
Timeline
- 2026-06-01: disclosed
- 2026-06-01: advisory
- 2026-07-27: patched: Advisory updated with patch details