Skip to main content

ZHOME A0101 CVE-2026-121260

| EUVDEUVD-2026-115917 HIGH
Code Injection (CWE-94)
2026-11-03 VulDB
8.5
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate with admin privileges to device
  2. Delivery
    Send crafted request to zrUsb API endpoint
  3. Exploit
    Inject Lua passed to loadstring
  4. Execution
    Execute arbitrary code on device
  5. Impact
    Full device compromise

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an authenticated session with high privileges (CVSS PR:H) on the ZHOME A0101 device, reaching the zrUsb API handler whose input is passed to the Lua loadstring function in usr/lib/lua/luci/controller/api/zrUsb.lua; that call compiling attacker-controlled data is the injection point. The attack is network-reachable (AV:N) and needs no user interaction (UI:N), and complexity is low (AC:L) once authenticated. Limiting factors: the PR:H requirement means an attacker must already possess administrative credentials or hijack an admin session, so risk is highest where the management interface is exposed to untrusted or multi-tenant users. No vendor fix is available because the vendor did not respond to disclosure.

Impact

The CVSS 4.0 base score of 8.5 (High) reflects a network-reachable (AV:N), low-complexity (AC:L) code-injection flaw with full confidentiality, integrity and availability impact on both the vulnerable and subsequent systems (VC/VI/VA:H, SC/SI/SA:H). The single most important mitigating signal is PR:H: exploitation requires high privileges, i.e. an already-authenticated administrative session on the device, which sharply narrows the realistic threat from 'any remote attacker' to 'an authenticated/insider or credential-compromised actor.' Exploit maturity is E:P (Proof-of-Concept), consistent with the input, which lists a GitHub PoC reference that is not verified as working exploit code. No CISA KEV listing and no EPSS score are present in the provided data, so there is no evidence of active exploitation or a quantified exploitation probability - the vuln.today decision label is 'this_week' rather than 'act_now'/'emergency.' The practical picture is a genuinely serious RCE primitive gated behind privileged access, with no vendor patch because the vendor did not respond to disclosure; prioritize it where the device exposes its management interface to untrusted users, but it is not a drop-everything unauthenticated internet-worm scenario given PR:H.

Exploit ScenarioDerived

An attacker holding high-privilege (administrative) access to the ZHOME A0101 management interface sends a crafted request to the zrUsb API endpoint whose input is passed to the Lua loadstring function in zrUsb.lua, causing attacker-supplied Lua to be compiled and executed on the device. With AC:L the step is reliable once the attacker is authenticated, yielding code execution in the handler's context. A public PoC reference exists on GitHub; it is not verified as working exploit code.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
1 PoC candidate (unverified) No patch listed yet

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv2 – Nov 03, 2026

Code injection in the Lua Handler of Ziroom ZHOME A0101 (version 1.0.1.0, Build 202004151405) lets a remote attacker with high privileges pass attacker-controlled data into the Lua loadstring function through the zrUsb API controller, resulting in code execution with full confidentiality, integrity and availability impact on the device and on subsequent systems (CVSS 4.0 score 8.5, scope-changed). Exploitation requires an authenticated administrative session (PR:H) but needs no user interaction and is low complexity once that access is obtained, so exposure is greatest where the management interface is reachable from untrusted or multi-tenant networks. A public PoC reference has been published; it is not verified as working exploit code, and the vendor did not respond to disclosure so no vendor fix is available.

Earlier versions of this analysis (1)
v1 Nov 03, 2026 - 16:11 CVSS 9.4

Remote code injection in Ziroom ZHOME A0101 firmware lets an attacker with existing administrative access execute arbitrary Lua code through the zrUsb.lua API handler, with high confidentiality, integrity, and availability impact. The flaw is rated 9.4 on CVSS 4.0 but is gated by PR:H, so it is not an unauthenticated default-config takeover; the device must be network-reachable and the attacker must already hold high privileges. A public PoC reference exists, but it is not verified as working exploit code, and no CISA KEV listing was provided.

RemediationAI

No vendor-released patch has been identified; the vendor was contacted about the disclosure and did not respond, so there is no fixed firmware version to cite and no advisory from Ziroom. Because the only complete fix is removal of the loadstring call in usr/lib/lua/luci/controller/api/zrUsb.lua (replacing it with a non-evaluating parser or strict allow-list of accepted values), teams that cannot obtain vendor firmware should compensate directly: restrict the device's web management interface so it is reachable only from a trusted management VLAN or bastion, since the flaw requires network reach to the zrUsb API and the trade-off is loss of remote administrative convenience; disable or firewall the zrUsb API endpoint entirely if USB-related management is not in use, accepting that USB management features become unavailable; and rotate administrative credentials and audit for session hijacking, because PR:H means anyone holding an admin session can already trigger the injection. Do not rely on the presence of authentication as a boundary control where the interface is exposed to untrusted or multi-tenant users. Reference material is at https://vuldb.com/vuln/430226 and https://github.com/Wlz1112/ZHOME_A0101/blob/main/zrusb_loadstring_code_injection.md.

Affected VersionsENISA

ZHOME A0101 1.0.1.0 Build 202004151405

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is the Lua Handler of the ZHOME A0101 gateway/appliance firmware, specifically the LuCI-style controller file usr/lib/lua/luci/controller/api/zrUsb.lua - the naming indicates an OpenWrt/LuCI-derived web management stack where controller modules register API endpoints and dispatch requests to Lua functions. In this file the loadstring primitive is used directly on data derived from the request, which is the classic CWE-94 (Improper Control of Generation of Code) pattern: loadstring compiles a string into an executable Lua chunk at runtime, so any attacker-supplied text that reaches it is evaluated as Lua rather than treated as inert data. Because the interpreter runs with the privileges of the web management service on the device, successful injection yields arbitrary code execution in that context. The supplied CPE (cpe:2.3:a:ziroom:zhome_a0101:*:*:*:*:*:*:*:*) does not constrain a version, and EUVD lists only the single build string 1.0.1.0 Build 202004151405 as affected; no information is available about whether later builds corrected the call. The precise request syntax, parameter name and the exact path by which input reaches loadstring are not described in the available sources - only the affected file and function are identified.

Know when Zhome A0101 gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 8.5 CRITICAL
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P
vuln.today AI 9.1 CRITICAL

Network-reachable code injection needing admin privileges gives AV:N/AC:L/PR:H/UI:N; code execution escaping the web handler to the device OS yields S:C with full C/I/A.

3.1 AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
High
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
High
Subsequent system: Integrity
High
Subsequent system: Availability
High

Lifecycle Timeline

4
Analysis Updated
Nov 03, 2026 - 16:28 vuln.today
v2 - CVSS changed
Severity Changed
Nov 03, 2026 - 16:22 NVD
CRITICAL HIGH
CVSS changed
Nov 03, 2026 - 16:22 NVD
9.4 (CRITICAL) 8.5 (HIGH)
CVE Published
Nov 03, 2026 - 15:30 cve.org
CRITICAL 9.4

DescriptionCVE.org

A flaw has been found in Ziroom ZHOME A0101 1.0.1.0 Build 202004151405. This issue affects the function loadstring of the file usr/lib/lua/luci/controller/api/zrUsb.lua of the component Lua Handler. This manipulation causes code injection. Remote exploitation of the attack is possible. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Technical POC Analysis

CWE-94: Code Injection.

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Latest POC

1 PoC candidate from github (unverified)

Sign in to open the public PoC links collected for this CVE.

Executive ViewAI

Why It Matters

CVE-2026-121260 is a high-severity code injection flaw in the Ziroom ZHOME A0101 smart home hub that allows an attacker with administrative access to execute arbitrary code, potentially compromising the device and other systems on the network. Since the vendor has not provided a patch, any exposed management interfaces pose a significant risk to organizational security, especially in multi-tenant or internet-facing deployments. Leadership should prioritize identifying and isolating affected devices to prevent potential lateral movement and data breaches.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include restricting management interface access to trusted networks, enforcing strong authentication, network segmentation, and continuous monitoring for anomalous activity.

Threat Intelligence Overview

Prevalence
Low
niche IoT smart-home controller, narrow regional deployment
Data Quality
5 sources
Confidence: Medium
EUVD NVD CVE.org Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS N/A
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

62
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy