# CVE-2026-33654: Zero-Click Indirect Prompt Injection and Authentication Bypass via Email Polling

> Remote attackers can execute arbitrary code via prompt injection in email processing, bypassing authentication without user interaction.

- **Severity:** High 8.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Mar 2026
- **Updated:** 30 Mar 2026
- **Also known as:** GHSA-4gmr-2vc8-7qh3

## What is CVE-2026-33654?

CVE-2026-33654 is a high-severity code injection vulnerability in HKUDS nanobot, published on 27 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

nanobot is a personal AI assistant. Prior to version 0.1.6, an indirect prompt injection vulnerability exists in the email channel processing module (`nanobot/channels/email.py`), allowing a remote, unauthenticated attacker to execute arbitrary LLM instructions (and subsequently, system tools) without any interaction from the bot owner. By sending an email containing malicious prompts to the bot's monitored email address, the bot automatically polls, ingests, and processes the email content as highly trusted input, fully bypassing channel isolation and resulting in a stealthy, zero-click attack. Version 0.1.6 patches the issue.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-290 (Authentication Bypass by Spoofing), CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

## Which versions are affected by CVE-2026-33654?

It affects 1 product.


Products: Nanobot Nanobot.

## How do I fix CVE-2026-33654?

No fix has been published for CVE-2026-33654 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-33654 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33654 exists.

## Other vulnerabilities in HKUDS nanobot

- [CVE-2026-35589](https://insights.sbomify.com/CVE-2026-35589/): nanobot: Cross-Site WebSocket Hijacking in WhatsApp Bridge (CVE-2026-2577 Fix Update) (high 8.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33654 and fix it if it is affected.

What it is: CVE-2026-33654 is a high-severity code injection vulnerability in HKUDS nanobot, published on 27 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33654 exists.

Affected product: HKUDS nanobot. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33654/ (Markdown: https://insights.sbomify.com/CVE-2026-33654/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33654
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33654
- OSV: https://osv.dev/vulnerability/CVE-2026-33654

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33654/
Summaries are generated and may contain mistakes; the official description above is the record.