Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain MITM position on network path
-
DeliveryIntercept plaintext HTTP update request
-
ExploitSubstitute malicious firmware payload
-
ExecutionDevice installs unsigned update
-
ImpactFull device compromise and control
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V15 - Secure Coding and Architecture Code integrity verification
|
| Exploitation Conditions | Requires the attacker to occupy a man-in-the-middle position on the network path between the affected device/app and its update server (e.g., ARP spoofing on the shared LAN, a rogue Wi-Fi access point, or a compromised router/upstream link), because updates are fetched over cleartext HTTP with no signature or hash verification. Exploitation is also gated by an update check actually occurring (attacker may need to wait for or induce an update), and reachability depends on whether update traffic stays on the LAN (adjacent, AV:A) or crosses the internet. No authentication and no user interaction are required once the MITM position is held, but the privileged-network-position prerequisite is the primary limiting factor and makes default-configuration remote exploitation from an arbitrary internet host infeasible. |
| Impact | The provided CVSS 3.1 vector (AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, base 7.5) describes an unauthenticated but adjacent-network, high-complexity attack yielding full confidentiality, integrity and availability impact - consistent with CWE-494 (download of code without integrity check), where a man-in-the-middle substitutes a malicious firmware update delivered over plain HTTP. The AC:H and AV:A metrics are the key risk dampeners: the attacker must already hold a privileged position on the network path (LAN MITM, rogue AP, or compromised router/upstream) and win against the update transaction, so this is not a spray-and-pray internet-wide bug. No EPSS score, no CISA KEV listing, and no vendor-confirmed exploitation were supplied, so there is no signal of active or widespread exploitation. POC availability is unclear: one reference is a GitHub repository ('your-secrets-are-safe-with-me') whose exploit status is unverified, so it is NOT counted as confirmed public exploit code. Note a vector tension worth verifying with the vendor: MITM against an update channel that traverses the public internet could arguably justify AV:N rather than AV:A - if the devices fetch updates over WAN rather than only LAN, real-world reachability is broader than AV:A implies. Overall this is a genuine but conditional/high-barrier risk, not a high-CVSS-low-real-risk paper cut, because successful exploitation gives full device takeover via attacker-controlled firmware. |
| Exploit ScenarioDerived | An attacker positioned on the same network segment as an Eilik/EnergizeLab device (or on a compromised router/AP in the update path) intercepts the plaintext HTTP firmware-update request and returns a crafted malicious firmware image, which the device or Windows app installs without checking any signature or hash. The attacker thereby gains full control of the robot/station or the updating host. No confirmed public exploit is identified at time of analysis, though one referenced GitHub repository may contain related material. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 15, 2026
Firmware updates for EnergizeLab AI Station, EilikO Linux robot firmware v2.1_20260617182218_release, and the EnergizeLab Windows desktop app 3.1.2 are delivered over plain HTTP without integrity or authenticity verification, allowing a network-adjacent attacker who can intercept traffic to substitute malicious updates and gain full control of the affected device or Windows host. The flaw is CWE-494 (download of code without integrity check), with a CVSS 3.1 base score of 7.5 (AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), meaning the attack is unauthenticated but requires an adjacent-network man-in-the-middle position and high complexity. No public exploit code or CISA KEV entry is identified in the provided data; exploitation depends on the attacker holding a MITM position, such as ARP spoofing, a rogue Wi-Fi access point, or a compromised router, and on an update check occurring.
RemediationAI
No vendor-released patch is identified in the provided data, so remediation currently depends on compensating controls. Isolate affected EnergizeLab AI Station and EilikO robot devices on a dedicated management VLAN or SSID with no untrusted hosts, enable Dynamic ARP Inspection and DHCP snooping on managed switches, prefer wired Ethernet over Wi-Fi, and monitor for rogue access points or ARP spoofing; the trade-off is reduced cloud or remote functionality and additional switch configuration. For the Windows desktop app 3.1.2, avoid running firmware updates on shared or untrusted networks, restrict outbound access to update endpoints via host firewall or force updates through a trusted, tightly controlled proxy or VPN, and manually verify any vendor-published hashes if available; these controls do not fix the missing code-signing verification and may break automatic update workflows. When EnergizeLab publishes a fixed firmware or app version, upgrade all three components (AI Station firmware, EilikO robot firmware, and Windows desktop app) and verify the update over a trusted channel; check the referenced GitHub, GCVE, and news links for updated guidance. Do not rely on HTTPS interception alone, because the affected clients do not validate update authenticity.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected EnergizeLab products fetch firmware or application updates over cleartext HTTP and do not validate a cryptographic signature or hash before applying the downloaded image, which is the root cause class CWE-494. The CVSS vector AV:A indicates the attacker must be on the same Layer 2 network segment or otherwise adjacent; AC:H reflects the multiple conditions required, including a MITM position plus a triggered update check; PR:N and UI:N mean no credentials or user interaction are needed once that position is held. Because the update channel is unauthenticated and unsigned, any party able to modify the HTTP response can replace the legitimate firmware or executable with attacker-controlled code, producing high confidentiality, integrity, and availability impact. The CPE data maps the affected components to EnergizeLab robot firmware (mode 104000), AI Station firmware (RK3562), and the Windows desktop app (EnergizeLabSetup-3.1.2-win.exe). The supplied references include a GitHub write-up, a GCVE record, and a The Verge article, but no vendor advisory or patched version is provided.
Know when Ai Station Firmware Rk3562 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
AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
MITM network position is required (AV:A, AC:H), no auth or interaction (PR:N/UI:N), and malicious firmware grants full device takeover (C:H/I:H/A:H); AV could be N if updates cross the WAN.
Primary rating from Vendor (AHA).
CVSS VectorVendor: AHA
DescriptionCVE.org
EnergizeLab AI Station firmware, EilikO Linux robot firmware v2.1_20260617182218_release, and the EnergizeLab Windows desktop app 3.1.2 download firmware updates over plain HTTP and do not verify their integrity or authenticity. An attacker able to intercept or modify the traffic can substitute a malicious update.
Executive ViewAI
Organizations using EnergizeLab AI Station, EilikO Linux robot firmware, or the EnergizeLab Windows desktop app face a high-severity risk from insecure update delivery. An unauthenticated network-adjacent attacker could intercept and replace legitimate updates with malicious code, gaining full control of affected devices and Windows hosts, which could lead to data compromise or operational disruption. No public exploit identified at time of analysis, but no vendor-released patch identified at time of analysis, making immediate mitigation essential.
Interim mitigations include disabling automatic update checks on affected devices, isolating affected systems on a separate network segment, and using VPN or other encrypted tunnels for update delivery. Additionally, monitor network traffic for ARP spoofing or rogue access points that could enable man-in-the-middle attacks.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-102432
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB