CVE-2026-54467: High severity Arm Trusted Firmware-M (TF-M) vulnerability

Published Aug 26, 2026
·
Updated

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.

Affected Software

1 affected component
Arm Trusted Firmware-M (TF-M)>=2<2.3.0

Event History

Aug 26, 2026
CVE Published
via MITRE·04:03 AM
Data Sourced
via MITRE·04:03 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments should be prioritized for review?

Prioritize TF-M deployments on PSOC64 or RP2350 using versions 2 through 2.3.0 that do not include commit 00d1b3e. Other platforms are not identified in the available information.

2

What access and conditions are required for exploitation?

The vulnerability involves a non-secure supplied pointer during mailbox initialization. The provided vector indicates physical access, low privileges, no user interaction, and high attack complexity are required.

3

How can I determine whether a build is affected?

Check whether the target is PSOC64 or RP2350, whether it uses TF-M 2 through 2.3.0, and whether commit 00d1b3e is present. A build meeting the platform and version conditions but lacking that commit should be treated as affected.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203