CVE-2026-33654: CWE-94: Improper Control of Generation of Code ('Code Injection') in HKUDS nanobot
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.
AI Analysis
Technical Summary
CVE-2026-33654 is a critical vulnerability classified under CWE-94 (Improper Control of Generation of Code) affecting the HKUDS nanobot personal AI assistant software. Specifically, the flaw resides in the email channel processing module (`nanobot/channels/email.py`) in versions prior to 0.1.4.post6. The nanobot automatically polls and processes emails sent to its monitored address, treating the email content as trusted input without proper sanitization or authentication. This design flaw allows a remote, unauthenticated attacker to craft malicious email prompts that inject arbitrary instructions into the large language model (LLM) powering the bot. Consequently, the attacker can execute arbitrary LLM commands and escalate to running system-level commands on the host machine. The attack requires no interaction from the bot owner, making it a zero-click exploit that bypasses channel isolation mechanisms intended to segregate input sources. The vulnerability was publicly disclosed on March 27, 2026, with a CVSS 4.0 base score of 8.9, indicating high severity due to network attack vector, no required privileges or user interaction, and high impact on confidentiality, integrity, and availability. Although no active exploits have been reported, the vulnerability poses a significant risk to users of affected nanobot versions. The vendor released version 0.1.6 to patch this issue, emphasizing the need for immediate updates. The vulnerability also relates to CWE-290 (Authentication Bypass) and CWE-1336 (Improper Input Validation), highlighting multiple security weaknesses in input handling and trust assumptions.
Potential Impact
The impact of CVE-2026-33654 is substantial for organizations and individuals using vulnerable versions of the HKUDS nanobot AI assistant. Exploitation allows attackers to execute arbitrary code and system commands remotely without authentication or user interaction, potentially leading to full system compromise. Confidentiality is at risk as attackers can access sensitive data processed or stored by the bot. Integrity is compromised since attackers can manipulate the bot's behavior and outputs, potentially causing misinformation or unauthorized actions. Availability may be affected if attackers disrupt bot operations or use the system as a foothold for further attacks. The stealthy zero-click nature of the exploit increases the likelihood of undetected breaches. Organizations integrating nanobot into workflows or automation pipelines face risks of lateral movement and escalation within their networks. Additionally, the vulnerability undermines trust in AI assistant security, potentially impacting adoption and compliance with data protection regulations. Although no known exploits exist currently, the high severity and ease of exploitation necessitate urgent mitigation to prevent future attacks.
Mitigation Recommendations
To mitigate CVE-2026-33654, organizations should immediately upgrade HKUDS nanobot to version 0.1.6 or later, where the vulnerability is patched. Until upgrades are feasible, restrict the bot's email channel to accept messages only from trusted, authenticated sources using strong email authentication mechanisms such as SPF, DKIM, and DMARC. Implement network-level controls to limit inbound email traffic to known safe senders. Employ email content filtering and sandboxing to detect and block malicious payloads before processing. Review and harden the bot’s input validation and sanitization routines to prevent injection attacks. Monitor bot activity logs for unusual or unauthorized commands indicative of exploitation attempts. Consider disabling or isolating the email channel if it is not essential to reduce the attack surface. Conduct regular security assessments and penetration testing focused on AI assistant integrations. Educate users about the risks of unsolicited emails triggering automated processes. Finally, maintain up-to-date threat intelligence to respond promptly to any emerging exploits targeting this vulnerability.
Affected Countries
United States, China, Germany, United Kingdom, Japan, South Korea, Canada, Australia, France, India
CVE-2026-33654: CWE-94: Improper Control of Generation of Code ('Code Injection') in HKUDS nanobot
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-33654 is a critical vulnerability classified under CWE-94 (Improper Control of Generation of Code) affecting the HKUDS nanobot personal AI assistant software. Specifically, the flaw resides in the email channel processing module (`nanobot/channels/email.py`) in versions prior to 0.1.4.post6. The nanobot automatically polls and processes emails sent to its monitored address, treating the email content as trusted input without proper sanitization or authentication. This design flaw allows a remote, unauthenticated attacker to craft malicious email prompts that inject arbitrary instructions into the large language model (LLM) powering the bot. Consequently, the attacker can execute arbitrary LLM commands and escalate to running system-level commands on the host machine. The attack requires no interaction from the bot owner, making it a zero-click exploit that bypasses channel isolation mechanisms intended to segregate input sources. The vulnerability was publicly disclosed on March 27, 2026, with a CVSS 4.0 base score of 8.9, indicating high severity due to network attack vector, no required privileges or user interaction, and high impact on confidentiality, integrity, and availability. Although no active exploits have been reported, the vulnerability poses a significant risk to users of affected nanobot versions. The vendor released version 0.1.6 to patch this issue, emphasizing the need for immediate updates. The vulnerability also relates to CWE-290 (Authentication Bypass) and CWE-1336 (Improper Input Validation), highlighting multiple security weaknesses in input handling and trust assumptions.
Potential Impact
The impact of CVE-2026-33654 is substantial for organizations and individuals using vulnerable versions of the HKUDS nanobot AI assistant. Exploitation allows attackers to execute arbitrary code and system commands remotely without authentication or user interaction, potentially leading to full system compromise. Confidentiality is at risk as attackers can access sensitive data processed or stored by the bot. Integrity is compromised since attackers can manipulate the bot's behavior and outputs, potentially causing misinformation or unauthorized actions. Availability may be affected if attackers disrupt bot operations or use the system as a foothold for further attacks. The stealthy zero-click nature of the exploit increases the likelihood of undetected breaches. Organizations integrating nanobot into workflows or automation pipelines face risks of lateral movement and escalation within their networks. Additionally, the vulnerability undermines trust in AI assistant security, potentially impacting adoption and compliance with data protection regulations. Although no known exploits exist currently, the high severity and ease of exploitation necessitate urgent mitigation to prevent future attacks.
Mitigation Recommendations
To mitigate CVE-2026-33654, organizations should immediately upgrade HKUDS nanobot to version 0.1.6 or later, where the vulnerability is patched. Until upgrades are feasible, restrict the bot's email channel to accept messages only from trusted, authenticated sources using strong email authentication mechanisms such as SPF, DKIM, and DMARC. Implement network-level controls to limit inbound email traffic to known safe senders. Employ email content filtering and sandboxing to detect and block malicious payloads before processing. Review and harden the bot’s input validation and sanitization routines to prevent injection attacks. Monitor bot activity logs for unusual or unauthorized commands indicative of exploitation attempts. Consider disabling or isolating the email channel if it is not essential to reduce the attack surface. Conduct regular security assessments and penetration testing focused on AI assistant integrations. Educate users about the risks of unsolicited emails triggering automated processes. Finally, maintain up-to-date threat intelligence to respond promptly to any emerging exploits targeting this vulnerability.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-23T15:23:42.218Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69c6e1b93c064ed76febd414
Added to database: 3/27/2026, 7:59:53 PM
Last enriched: 3/27/2026, 8:15:20 PM
Last updated: 3/27/2026, 11:40:54 PM
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.