CVE-2026-32185 is an Important spoofing vulnerability in Microsoft Teams for Android. According to Microsoft, the issue is caused by files or directories being accessible to external parties, mapped to CWE-552. This improper exposure can allow an unauthorized attacker to perform spoofing locally within the Teams application. While Microsoft has not publicly described the exact vulnerable function or code path, the available advisory information indicates the flaw arises from Teams' handling of file or directory access in a way that can enable impersonation of trusted elements or content presented to the user.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A spoofing vulnerability in Microsoft Teams for Android caused by files or directories being accessible to external parties, enabling an unauthorized local attacker to spoof trusted elements within the application.
A Microsoft Teams spoofing vulnerability caused by files or directories being accessible to external parties, allowing an unauthorized attacker to perform spoofing locally.
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.