CVE-2026-54467

Secure-memory corruption via unvalidated mailbox pointers

Published Aug 26, 2026 · Updated Aug 26, 2026

Memory corruption in Trusted Firmware-M 2 through 2.3.0 allows attackers to corrupt secure memory on PSOC64 and RP2350 devices. During secondary-core boot, platform mailbox initialization stores non-secure status and slot pointers without confirming that their ranges are non-secure read/write memory. Physically proximate attackers with low privileges who control the mailbox data can trigger secure-context reads and writes, causing memory corruption or persistent reset loops.

CVSS severity7.0
High
EPSS probability0.15%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Memory corruption in Trusted Firmware-M 2 through 2.3.0 allows attackers to corrupt secure memory on PSOC64 and RP2350 devices. During secondary-core boot, platform mailbox initialization stores non-secure status and slot pointers without confirming that their ranges are non-secure read/write memory. Physically proximate attackers with low privileges who control the mailbox data can trigger secure-context reads and writes, causing memory corruption or persistent reset loops.

The record

CVE
CVE-2026-54467
Published
Aug 26, 2026
Updated
Aug 26, 2026
Vendor
Trusted Firmware
Product
Trusted Firmware-M
Classifications
CWE-283
Attack vector
physical
Privileges
Unavailable

Timeline

How it unfolded

  1. Aug 26, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 26, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <00d1b3e716dc636f7ad4398980ae55427dc1731d

What conditions does exploitation require?

Attack vectorphysical
Required privilegesUnavailable in this record.

What is affected?

Trusted Firmware · Trusted Firmware-Mversion=0 <00d1b3e716dc636f7ad4398980ae55427dc1731d

Published CVSS scores

7.0MITRECVSS:3.1/AV:P/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorphysical
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-283Unverified Ownership

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo