CVE-2026-9266
HIGHDescription
A Missing Required Cryptographic Step vulnerability has been identified in Moxa's embedded Linux firmware for industrial computers and controllers. This vulnerability represents an incomplete remediation of CVE-2026-0714. The firmware introduced TPM2 parameter encryption as a countermeasure against CVE-2026-0714. However, an omission in the authorization session configuration causes the parameter encryption to provide no effective protection. An attacker with invasive physical access to the device can still capture TPM communications on the SPI bus and derive the LUKS disk encryption key in plaintext. While successful exploitation results in full compromise of the encrypted disk volume, the attack requires invasive physical access, including opening the device and attaching external equipment to the SPI bus. Remote exploitation is not possible, and the attack does not affect any downstream systems.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v4 Vector
Exploitability
Impact
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Exploit Intelligence
Low risk: more likely to be exploited than 0% of all known CVEs.
References
Related Vulnerabilities
Other CWE-325 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2021-22946 | High | 7.5 | 4.5% | - | Fix |
| CVE-2020-15086 | Critical | 9.8 | 2.7% | - | Fix |
| CVE-2021-33560 | High | 7.5 | 2.3% | - | Fix |
| CVE-2020-15098 | High | 8.8 | 2.2% | - | Fix |
| CVE-2019-3738 | Medium | 6.5 | 1.7% | - | Fix |
| CVE-2016-9574 | Medium | 5.9 | 1.4% | - | Fix |
Common questions
How do I fix CVE-2026-9266?
No published fix for CVE-2026-9266 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-9266 being actively exploited?
Not that we know of. CVE-2026-9266 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.07% is the estimated probability that it will be exploited in the next 30 days. That is higher than 0% of all scored CVEs.
How severe is CVE-2026-9266?
CVE-2026-9266 has a CVSS v4 base score of 7.0, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-9266
Markdown
[](https://tridentstack.com/cve/CVE-2026-9266)HTML
<a href="https://tridentstack.com/cve/CVE-2026-9266"><img src="https://tridentstack.com/cve/badge/CVE-2026-9266.svg" alt="CVE-2026-9266"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-06-17.