# CVE-2025-21396: Microsoft Account Elevation of Privilege Vulnerability

> An unauthorized attacker can elevate privileges in Microsoft Account due to missing authorization checks, requiring a vendor patch.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H/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:** 29 Jan 2025
- **Updated:** 9 Jun 2026
- **Also known as:** GHSA-vcqr-f63g-v876

## What is CVE-2025-21396?

CVE-2025-21396 is a high-severity missing authorization vulnerability in Microsoft Account, published on 29 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing authorization in Microsoft Account allows an unauthorized attacker to elevate privileges over a network.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-21396?

It affects 1 product.


Products: Microsoft Account.

## How do I fix CVE-2025-21396?

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

## Is CVE-2025-21396 being exploited?

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

## Other vulnerabilities in Microsoft Account

- [CVE-2026-56165](https://insights.sbomify.com/CVE-2026-56165/): Microsoft Account Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2026-21264](https://insights.sbomify.com/CVE-2026-21264/): Microsoft Account Spoofing Vulnerability (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-21396 and fix it if it is affected.

What it is: CVE-2025-21396 is a high-severity missing authorization vulnerability in Microsoft Account, published on 29 Jan 2025. 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-2025-21396 in the wild and no public exploit code.

Affected product: Microsoft Account. 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-2025-21396/ (Markdown: https://insights.sbomify.com/CVE-2025-21396/index.md)
```

## Sources

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

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