Microsoft 365 Session Replay Attack

Microsoft 365

An attacker compromised Microsoft 365 accounts at 79 organizations by replaying stolen sign-in sessions.

Do this now

Check Microsoft's advisory for a fix to the session replay issue and restrict Microsoft 365 sign-ins to trusted networks meanwhile.

First seen: 23 Oct 2026
Last update: 23 Oct 2026, 11:45 UTC
Source: news
On the menu as: Azure / M365

Check this repository for exposure to one security incident from pwned.coffee. Report first, change nothing until I say so.

## Microsoft 365 Session Replay Attack
Severity: unknown. Patch status: fix status unknown.
Affected: Microsoft 365

An attacker compromised Microsoft 365 accounts at 79 organizations by replaying stolen sign-in sessions.

## Steps
1. This incident involves a provider (azure). Search config, CI and env templates (.env.example, wrangler.toml, vercel.json, terraform, workflow secrets) for credentials stored there. List each secret by name, where it is used, and how to rotate it. Never print secret values.
2. No source names a fix yet; check the vendor advisory. Until one ships: restrict network access to it.

## Report
A table: file, product or package, version in use, affected yes/no, exact fix. Then anything a human has to check outside the repo.

If you have the pwned.coffee MCP server (https://pwned.coffee/mcp), call lookup_cve for the latest, and check_repo with this repo's lockfiles, Dockerfiles and workflows for a full receipt.
Sources: https://www.helpnetsecurity.com/2026/10/23/microsoft-365-accounts-stolen-sessions/ https://thehackernews.com/2026/10/microsoft-365-token-replay-attacks.html
https://pwned.coffee/i/microsoft-365-session-replay-attack

Receipt

Exploitation: No known exploitation
Score: No CVSS published yet: severity unknown.
Last checked: 26 Oct 2026, 11:17 UTC

Sources: KEV – CVE record – Vendor –

Sources

Wrong fix version, or a source we missed? Send it back to chef@pwned.coffee with the source, and we'll correct it here.

Totalone coffee