# CVE-2026-22097: Missing firmware validation allows remote code execution

> Attackers can upload arbitrary firmware files due to missing signature validation, leading to remote code execution on the device.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2026
- **Updated:** 16 Jul 2026
- **Also known as:** GHSA-fmp2-hp5c-w25p

## What is CVE-2026-22097?

CVE-2026-22097 is a critical vulnerability in EVbee DC-80, published on 13 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The firmware update mechanism does not include cryptographic signature validation. This allows anyone with access to the firmware update capability to upload arbitrary files which can then lead to arbitrary code execution.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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


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

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

## Is CVE-2026-22097 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22097 is a critical vulnerability in EVbee DC-80, published on 13 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-22097 in the wild and no public exploit code.

Affected product: EVbee DC-80. 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-22097/ (Markdown: https://insights.sbomify.com/CVE-2026-22097/index.md)
```

## Sources

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

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