Quick answers
- Is CVE-2026-22097 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-22097 being exploited in the wild.
- How severe is CVE-2026-22097?
- Informational severity, with a CVSS score of 9.3, published 13 July 2026.
- Which products and versions are affected?
- EVbee DC-80 versions before 1.5.1.
- Is there a fix for CVE-2026-22097?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-22097 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-22097?
- Check whether you run EVbee DC-80 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The EVbee DC-80 firmware update mechanism lacks cryptographic signature validation (CWE-347). An attacker with network access to the firmware update interface can upload and install a modified or entirely malicious firmware image. Because the system does not verify the origin or integrity of the update, the malicious file is executed with high privileges. This leads to full system compromise and arbitrary code execution. The vulnerability is addressed in version 1.5.1.
Affected products
- EVbee DC-80 versions before 1.5.1
Timeline
- 2026-07-13: advisory: CVE published by NVD and DIVD