Microsoft Teams Spoofing Vulnerability
- Exploited
- No known exploitation
- Fix
- Fixed in 1416/1.0.0.2026202302
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1416/1.0.0.2026202302.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 28/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
Microsoft Teams is affected by a spoofing flaw caused by improper handling of input in web page generation (cross-site scripting). An attacker can reach it remotely over the network without logging in and without any user action, and can use it to impersonate or mislead users.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Improper neutralization of input during web page generation ('cross-site scripting') in Microsoft Teams allows an unauthorized attacker to perform spoofing over a network.
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 33 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1416/1.0.0.2026202302.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-116926 (Microsoft Teams Spoofing Vulnerability), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-116926 (entry last updated 2026-11-10): Affected: - Microsoft Microsoft Teams for Android: from 1.0.0, fixed in 1416/1.0.0.2026202302 Fixed versions: 1416/1.0.0.2026202302. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-116926 is not listed as of cve.now's last read. This KEV status is for CVE-2026-116926 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-116926 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-116926 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-116926.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Microsoft Microsoft Teams for Android
From 1.0.0 · fixed in 1416/1.0.0.2026202302
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Patch
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-116926
Is CVE-2026-116926 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-116926?
Microsoft Teams for Android: from 1.0.0 before 1416/1.0.0.2026202302.Source: cve.now feed data
How do I fix CVE-2026-116926?
Upgrade to a fixed version: 1416/1.0.0.2026202302.Source: cve.now feed data