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.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A remote code execution vulnerability affecting Yealink Device Management, listed as one of the exploit vectors used by the MANGA Mirai variant.
One half of a critical exploit chain affecting Yealink Device Management; when chained with CVE-2021-27561, it enables pre-authentication root-level remote code execution.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.