Skip to main content
Mallory
MediumExploited in the wildCISA KEVVulnerability

CVE-2021-27562: Improper NSPE handler-mode access control in Arm Trusted Firmware-M

Published May 25, 2021 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.5Medium · v3.1
EPSS3.1%88th percentile
CISA KEVYesAdded Nov 3, 2021
In the wildActivePer CISA KEV
Vendors
TrustedfirmwareARM Holdings
IdentifiersCVE-2021-27562CWE-284

CVE-2021-27562 affects Arm Trusted Firmware-M through version 1.2. The vulnerability allows code executing in the non-secure world to invoke secure functions while under NSPE handler mode in a way that violates expected isolation boundaries between non-secure and secure execution contexts. As a result, non-secure code may trigger erroneous behavior in the secure side, including system halt conditions, overwriting secure data, or causing secure data to be printed. The issue is an access-control and isolation failure in the handling of secure function calls from the non-secure processing environment rather than a conventional memory corruption flaw in an application-layer component.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can break the security guarantees of TrustZone-based isolation in affected firmware. An attacker with the ability to execute code in the non-secure world may cause denial of service by halting the system, compromise integrity by overwriting secure-world data, and compromise confidentiality by causing secure data to be disclosed through output generated by the secure side. The impact is therefore a combination of denial of service, secure data corruption, and secure information exposure.

Mitigation

If you can’t patch tonight, do this now.

Until patched firmware can be deployed, reduce exposure by minimizing the ability of non-secure code to invoke sensitive secure services, restricting or disabling unnecessary secure callable interfaces, and hardening the non-secure execution environment to prevent attacker-controlled code execution there. Additional defensive measures include limiting debug or diagnostic output paths that could expose secure data and reviewing TrustZone partition boundaries and handler-mode transition logic for unsafe call paths.

Remediation

Patch, then assume compromise.

Upgrade Arm Trusted Firmware-M to a fixed release newer than 1.2 that corrects the handling of secure function calls originating from NSPE handler mode. Rebuild and redeploy affected firmware images incorporating the vendor fix, and validate that secure gateway entry points and NSPE-to-secure transitions enforce the intended execution-context restrictions.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
ARM HoldingsTrusted Firmware-Moperating_system
TrustedfirmwareTrusted Firmware-Mapplication
FAQ

Frequently asked questions

Is CVE-2021-27562 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Nov 3, 2021.
Is there a public exploit for CVE-2021-27562?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2021-27562.
Is there a patch for CVE-2021-27562?
Upgrade Arm Trusted Firmware-M to a fixed release newer than 1.2 that corrects the handling of secure function calls originating from NSPE handler mode. Rebuild and redeploy affected firmware images incorporating the vendor fix, and validate that secure gateway entry points and NSPE-to-secure transitions enforce the intended execution-context restrictions.
What products are affected by CVE-2021-27562?
Trustedfirmware Trusted Firmware-M and ARM Holdings Trusted Firmware-M.
How severe is CVE-2021-27562?
CVE-2021-27562 has a CVSS v3.1 score of 5.5 (Medium) and an EPSS score of 3.1% (88th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware2Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.