Trusted Firmware-M: Unverified Ownership
CVE-2026-54467 is a high-severity unverified ownership vulnerability in Trusted Firmware-M from TrustedFirmware, with a CVSS 3.1 base score of 7.0 out of 10. It can be exploited with physical access to the device by an attacker with a low-privileged account, without any action from a user. The record lists version 00d1b3e716dc636f7ad4398980ae55427dc1731d as the first without the flaw, so updating Trusted Firmware-M to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.17% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Trusted Firmware-M to 00d1b3e716dc636f7ad4398980ae55427dc1731d or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| TrustedFirmware | Trusted Firmware-M | before 00d1b3e716dc636f7ad4398980ae55427dc1731d | 00d1b3e716dc636f7ad4398980ae55427dc1731d |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- PhysicalThe attacker must physically touch the device.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:P/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H. Scored by CNA (mitre.org).
Official description
On the Trusted Firmware-M (TF-M) 2 through 2.3.0 platform before 00d1b3e, mailbox initialization on PSOC64 and RP2350 accepts a non-secure, unvalidated, supplied pointer.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Unverified Ownership
The product does not properly verify that a critical resource is owned by the proper entity.
How developers prevent this class of flaw
- Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in Trusted Firmware-M
- 9.8 Critical severity
- 7.5 High severity
- 5.5 Medium severity
Arm Trusted Firmware Out-of-Bounds Write Exploited
Recent Unverified Ownership vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 8.1 High severity
- 7.8 High severity
- 7.2 High severity
Spotted an error? Tell us.