CVE-2026-32294
Firmware Verification Bypass in JetKVM Allows Malicious Firmware Injection
Publication date: 2026-03-17
Last updated on: 2026-04-10
Assigner: Cybersecurity and Infrastructure Security Agency (CISA) U.S. Civilian Government
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| jetkvm | kvm | to 0.5.3 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-347 | The product does not verify, or incorrectly verifies, the cryptographic signature for data. |
| CWE-345 | The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
JetKVM versions prior to 0.5.4 do not verify the authenticity of downloaded firmware files. This means that an attacker positioned between the user and the update server (man-in-the-middle) or a compromised update server could alter the firmware and the associated SHA256 hash to bypass verification checks.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to install malicious firmware by modifying the firmware and its verification hash. This could lead to unauthorized code execution or control over the affected device, potentially compromising its integrity and security.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know