SSRF (Server-Side Request Forgery) in nanobot-ai (CVE-2026-49138)
Summary
SSRF in nanobot-ai (CVE-2026-49138). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.2.1 or later.
Original description
The description as published by the source.
Nanobot prior to version 0.2.1 contains a server-side request forgery vulnerability in the web_fetch tool that allows remote attackers to reach internal or private network hosts by supplying a URL that redirects to a loopback or private address via a 3xx Location header. Attackers can exploit the automatic HTTP redirect following behavior in the httpx library to bypass initial URL validation and cause the runtime to send outbound requests to internal hosts before final resolved URL validation is applied.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-49138 has been found in nanobot-ai.
Risk of unauthorized operations or information disclosure. CVSS score: 5.0/10.
What to do: upgrade nanobot-ai to 0.2.1 or later.
If unsure, ask your IT team or search "nanobot-ai CVE-2026-49138" on the vendor's site.
CVE-2026-49138 (nanobot-ai) — CWE-918 / CVSS v3 5.0
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.2.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in nanobot-ai.
Check the vendor advisory for the affected versions of nanobot-ai.
Severity: Medium (CVSS 5.0/10). Risk of unauthorized operations or information disclosure.
Update to 0.2.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'nanobot-ai' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'nanobot-ai' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
nanobot-aiを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade nanobot-ai to 0.2.1ステージング環境で 0.2.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- advisory vulncheck.com
- advisory github.com
- advisory github.com
- package github.com
- package pypi.org
- patch github.com
- report github.com