# CVE-2026-62918: Microsoft Teams Spoofing Vulnerability

> An attacker can spoof identities in Microsoft Teams by exploiting improper cryptographic signature verification, requiring a patch to mitigate.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-p2wf-cwq4-f5gj

## What is CVE-2026-62918?

CVE-2026-62918 is a high-severity vulnerability in Microsoft Teams, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper verification of cryptographic signature in Microsoft Teams allows an unauthorized attacker to perform spoofing over a network.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2026-62918?

It affects 1 product.


Products: Microsoft Teams.

## How do I fix CVE-2026-62918?

No fix has been published for CVE-2026-62918 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-62918 being exploited?

There is no known exploitation of CVE-2026-62918 in the wild and no public exploit code.

## Other vulnerabilities in Microsoft Teams

- [CVE-2026-65667](https://insights.sbomify.com/CVE-2026-65667/): Microsoft Teams Elevation of Privilege Vulnerability (critical 10.0)
- [CVE-2026-62896](https://insights.sbomify.com/CVE-2026-62896/): Microsoft Teams Elevation of Privilege Vulnerability (critical 9.6)
- [CVE-2026-33823](https://insights.sbomify.com/CVE-2026-33823/): Microsoft Team Events Portal Information Disclosure Vulnerability (critical 9.6)
- [CVE-2026-65767](https://insights.sbomify.com/CVE-2026-65767/): Microsoft Teams for Android Spoofing Vulnerability (high 8.8)
- [CVE-2026-65768](https://insights.sbomify.com/CVE-2026-65768/): Microsoft Teams Remote Code Execution Vulnerability (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62918 and fix it if it is affected.

What it is: CVE-2026-62918 is a high-severity vulnerability in Microsoft Teams, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-62918 in the wild and no public exploit code.

Affected product: Microsoft Teams. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-62918/ (Markdown: https://insights.sbomify.com/CVE-2026-62918/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-62918
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-62918
- OSV: https://osv.dev/vulnerability/CVE-2026-62918

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-62918/
Summaries are generated and may contain mistakes; the official description above is the record.