# CVE-2026-105036: EnergizeLab Firmware Updates Downloaded over HTTP Without Integrity Checks

> Attackers can inject malicious firmware updates into EnergizeLab robots and desktop apps by intercepting unencrypted HTTP traffic, leading to remote code execution.

- **Severity:** High 7.5 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-vrv5-9jjj-m294

## What is CVE-2026-105036?

CVE-2026-105036 is a high-severity vulnerability in EnergizeLab AI Station firmware (RK3562), published on 15 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-494 (Download of Code Without Integrity Check)

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


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

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

## Is CVE-2026-105036 being exploited?

There is no known exploitation of CVE-2026-105036 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105036 is a high-severity vulnerability in EnergizeLab AI Station firmware (RK3562), published on 15 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105036 in the wild and no public exploit code.

Affected product: EnergizeLab AI Station firmware (RK3562). 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-105036/ (Markdown: https://insights.sbomify.com/CVE-2026-105036/index.md)
```

## Sources

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

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