Trusted firmware-m
This hub aggregates every CVE we track for Trusted firmware-m. Use it to gauge the current risk picture and drill into individual advisories.
other
7
CVEs tracked
0
Critical
4
High
1
In CISA KEV
Severity distribution
HIGH4MEDIUM3
Monthly trend
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
0
2024-102026-09
Latest CVEs
The 7 most recently published vulnerabilities affecting Trusted firmware-m.
- CVE-2026-54467On 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.7.0
- CVE-2023-51712An issue was discovered in Trusted Firmware-M through 2.0.0. The lack of argument verification in the logging subsystem allows attackers to read sensitive data via the login function.4.7
- CVE-2023-40271In Trusted Firmware-M through TF-Mv1.8.0, for platforms that integrate the CryptoCell accelerator, when the CryptoCell PSA Driver software Interface is selected, and the Authenticated Encryption wi...7.5
- CVE-2021-43619Trusted Firmware M 1.4.x through 1.4.1 has a buffer overflow issue in the Firmware Update partition. In the IPC model, a psa_fwu_write caller from SPE or NSPE can overwrite stack memory locations.7.8
- CVE-2021-40327Trusted Firmware-M (TF-M) 1.4.0, when Profile Small is used, has incorrect access control. NSPE can access a secure key (held by the Crypto service) based solely on knowledge of its key ID. For exa...5.9
- CVE-2021-27562In Arm Trusted Firmware M through 1.2, the NS world may trigger a system halt, an overwrite of secure data, or the printing out of secure data when calling secure functions under the NSPE handler m...KEV5.5
- CVE-2021-32032In Trusted Firmware-M through 1.3.0, cleaning up the memory allocated for a multi-part cryptographic operation (in the event of a failure) can prevent the abort() operation in the associated crypto...7.5
Product normalization is registry-driven with AI assist and human review. How it works