# CVE-2026-105035: EnergizeLab FirmwareUpdater Universal Hard-Coded AES Key

> Attackers can decrypt and forge firmware packages for EnergizeLab devices by exploiting a hard-coded AES key in the updater.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-mqqq-chp3-ffv9

## What is CVE-2026-105035?

CVE-2026-105035 is a high-severity vulnerability in EnergizeLab FirmwareUpdater, published on 15 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The EnergizeLab FirmwareUpdater (AArch64 ELF, distributed in the CDN bin.zip) uses a single hard-coded AES key shared by all installations. An attacker who recovers the key from the updater can decrypt and forge firmware packages for any device that trusts it.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

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


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

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

## Is CVE-2026-105035 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105035 is a high-severity vulnerability in EnergizeLab FirmwareUpdater, published on 15 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-105035 in the wild and no public exploit code.

Affected product: EnergizeLab FirmwareUpdater. 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-105035/ (Markdown: https://insights.sbomify.com/CVE-2026-105035/index.md)
```

## Sources

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

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