Microsoft · Same-origin Policy Bypass
Affects MicrosoftSource GCVE Database
Not known to be exploited · CVSS 9.3 Critical · patch available : patch Microsoft as a priority.
Data as of 14 Nov 2026, 09:16 UTC
- Patch
- Available
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Security Response Center Microsoft | Affected
| Fixed in
|
Description
CVE-2026-8950 is a vulnerability in Microsoft’s Networking: HTTP component that allows bypassing the same-origin policy. The same-origin policy is a critical security mechanism that restricts how documents or scripts loaded from one origin can interact with resources from another origin. This vulnerability could potentially allow unauthorized cross-origin interactions. The affected version is Microsoft version 4.0. No CVSS score or detailed impact information is provided, and no known exploits are reported in the wild.