CVE-2026-0714
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA physical attack vulnerability exists in certain Moxa industrial computers using TPM-backed LUKS full-disk encryption on Moxa Industrial Linux 3, where the discrete TPM is connected to the CPU via an SPI bus. Exploitation requires invasive physical access, including opening the device and attaching external equipment to the SPI bus to capture TPM communications. If successful, the captured data may allow offline decryption of eMMC contents. This attack cannot be performed through brief or opportunistic physical access and requires extended physical access, possession of the device, appropriate equipment, and sufficient time for signal capture and analysis. Remote exploitation is not possible.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA physical attack vulnerability in Moxa industrial computers allows interception of TPM-to-CPU SPI bus communications by attaching external equipment directly to the SPI bus after opening the device. Captured TPM signals can enable offline decryption of LUKS-encrypted eMMC storage contents.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.4<= 1.4<= 1.4<= 1.4<= 1.4<= 1.2<= 1.2<= 1.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the Moxa device modelLocate the model number label on the physical device or check the device documentation/packaging. Models are in the format 'Uc XXXXa' or 'Uc XXXXa T' with regional suffixes (Us, Ap, Eu, Lte, Wifi).Affected if The model matches any of these: Uc 1222a, Uc 2222a T Us, Uc 2222a T, Uc 2222a T Ap, Uc 2222a T Eu, Uc 3434a T Lte Wifi, Uc 3424a T Lte, Uc 3420a T Lte.
-
Determine the installed firmware versionAccess the device admin interface or console and retrieve the firmware version information, typically found in system information or about pages.Affected if The firmware version is 1.4 or lower for Uc 1222a/Uc 2222a models, or 1.2 or lower for Uc 3434a/Uc 3424a/Uc 3420a models.
-
Confirm LUKS encryption is in useCheck the device configuration or documentation to determine if LUKS-encrypted eMMC storage is implemented for data at rest protection.Affected if LUKS encryption is enabled on the eMMC storage device.
-
Assess physical access controlsInspect the device enclosure for locks, tamper-evident seals, and evaluate the physical location security (restricted area, locked cabinet, or controlled access).Affected if The device is accessible in an unsecured location or the enclosure lacks physical locks and tamper protection.
You are affected if your Moxa device model matches the list, runs firmware at or below the specified version, uses LUKS-encrypted eMMC storage, and lacks adequate physical access controls.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataPhysical security controls (locked enclosures, tamper-evident seals, restricted access) are the primary mitigation; hardware redesign with SPI bus encryption or signal shielding would be required for a technical fix.
- Consultation8.0 h
- Implementation40.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $20,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0714 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0714 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data