ChangeIntel IT change radar
Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources or documents need attention: 275/275 feeds/APIs · 469/469 docs · 9/9 advisories · checked 06:21 UTC Customize Public modeDiscuss ChangeIntel on Discord
CVE-2026-96222CriticalFix has a known issueSpoofingNetworkRevised 16 Oct

Active Directory Federation Services (AD FS) Spoofing Vulnerability

MSRC advisory NVD CVE.org

Assessment

Improper certificate validation in Active Directory Federation Services (AD FS) allows an unauthorized attacker to perform spoofing over a network.

Severity
Critical
CVSS base score
7.4CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
Impact
Spoofing
EPSS · 30-day forecast
0.6%FIRST forecast dated 7 Nov 2026, for the following 30 days · FIRST percentile 48.3% · about EPSS
Public detection template
No Nuclei template is listed in the current collected catalog
Exploitation detected
No known exploitation (MSRC assessment)
Exploitability
Exploitation Less Likely
Publicly disclosed
No (MSRC assessment)
Customer action
Required: follow the MSRC remediation guidance
Component
Active Directory Federation Services (AD FS)
Weakness
CWE-295: Improper Certificate Validation
Issued by
Microsoft
Published
13 Oct 2026 · October 2026
Last revised
16 Oct 2026Updated the Security Updates table to add download and KB article links for Microsoft Visual Studio. This is an informational change only; the fixed builds are unchanged.
CVSS 3.1 base metricsRed raises the risk · green lowers it
Attack vector
NetworkAV:N
Attack complexity
HighAC:H
Privileges required
NonePR:N
User interaction
NoneUI:N
Scope
UnchangedS:U
Confidentiality
HighC:H
Integrity
HighI:H
Availability
NoneA:N

Updates that fix it

23 KBs
KBTypeRestartApplies toKnown issuesOther CVEs
KB5126646 Security UpdateRequiredWindows Server 2025, Windows Server 2025 (Server Core installation)MitigatedUsers might be unable to sign in to OWA or send emails on Exchange ServerAll CVEs in KB5126646
KB5126651 Security UpdateRequiredWindows 10 Version 1809 for 32-bit Systems, Windows 10 Version 1809 for x64-based Systems, Windows Server 2019 and 1 moreMitigatedUsers might be unable to sign in to OWA or send emails on Exchange ServerAll CVEs in KB5126651
KB5126655 Security UpdateRequiredWindows Server 2022, Windows Server 2022 (Server Core installation)MitigatedUsers might be unable to sign in to OWA or send emails on Exchange ServerAll CVEs in KB5126655
KB5126836 Monthly RollupRequiredWindows Server 2012 R2, Windows Server 2012 R2 (Server Core installation)None listedAll CVEs in KB5126836
KB5126868 Security UpdateRequiredMicrosoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows 10 version 1607, Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2016, Windows 10 Version 1607 for 32-bit Systems and 3 moreMitigatedUsers might be unable to sign in to OWA or send emails on Exchange ServerAll CVEs in KB5126868
KB5127660 Security Update—Microsoft .NET Framework 3.5 on Windows Server 2012None listedAll CVEs in KB5127660
KB5127664 Security Update—Microsoft .NET Framework 3.5 on Windows Server 2012 R2None listedAll CVEs in KB5127664
KB5127666 Security Update—Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2019, Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 version 1809None listedAll CVEs in KB5127666
KB5127667 Security Update—Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2012None listedAll CVEs in KB5127667
KB5127668 Security Update—Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2012 R2None listedAll CVEs in KB5127668
KB5127683 Security Update—Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 version 21H2, Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 version 22H2None listedAll CVEs in KB5127683
KB5127684 Security Update—Microsoft .NET Framework 4.8 on Windows 10 version 1607, Microsoft .NET Framework 4.8 on Windows Server 2016None listedAll CVEs in KB5127684
KB5127685 Security Update—Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 version 1809, Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2019None listedAll CVEs in KB5127685
KB5127686 Security Update—Microsoft .NET Framework 4.8 on Windows Server 2012None listedAll CVEs in KB5127686
KB5127687 Security Update—Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2022None listedAll CVEs in KB5127687
KB5127688 Security Update—Microsoft .NET Framework 4.8 on Windows Server 2012 R2None listedAll CVEs in KB5127688
KB5127689 Security Update—Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 version 21H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 version 22H2None listedAll CVEs in KB5127689
KB5127690 Security Update—Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 24H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 25H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows Server 2025None listedAll CVEs in KB5127690
KB5127691 Security Update—Microsoft .NET Framework 4.8.1 on Windows 11 version 26H1None listedAll CVEs in KB5127691
KB5127692 Security Update—Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 23H2None listedAll CVEs in KB5127692
KB5127693 Security Update—Microsoft .NET Framework 3.5 AND 4.8.1 on Windows Server 2022None listedAll CVEs in KB5127693
KB5127694 Security Update—Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 26H2None listedAll CVEs in KB5127694
KB5127696 Security Update—Microsoft .NET Framework 3.5 on Windows 11 version 26H1None listedAll CVEs in KB5127696

Affected products

Developer Tools, ESU, Other, Windows
46 affected products

Independent patch analysis

Cisco Talos Intelligence

Microsoft Patch Tuesday for October 2026 — Snort rules and prominent vulnerabilities · 13 Oct 2026

Talos supplies analysis and cycle-level Snort rule references. Its article does not map each rule to a CVE or establish protection for your deployment. MSRC remains the source for vulnerability and fixing-update facts.

What changed

  1. Detection template: Unknown: detection-template evidence is incomplete or retained → No Nuclei template listed
  2. Detection template: No Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
  3. Detection template: Unknown: detection-template evidence is incomplete or retained → No Nuclei template listed
  4. Detection template: No Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
  5. Detection template: No Nuclei template listed · Customer action: Required: apply the update → Required: follow the MSRC remediation guidance · Public disclosure: No → No (MSRC assessment) · Exploitation detected: Not reported by MSRC → No known exploitation (MSRC assessment)
  6. Detection template: Unknown: exploit-code evidence is incomplete or retained → No Nuclei template listed · CISA KEV: Unknown: catalog evidence is incomplete or retained → Not listed in the collected catalog
  7. Detection template: No Nuclei template listed → Unknown: exploit-code evidence is incomplete or retained · CISA KEV: Not listed in the collected catalog → Unknown: catalog evidence is incomplete or retained
  8. Affected products: Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows 10 version 1607, Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2016, Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2019, Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 version 1809, Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 version 1809, Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 version 21H2, Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 version 22H2, Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2019, Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2022, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 version 21H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 version 22H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 23H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 24H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 25H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 26H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows Server 2022, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows Server 2025, Microsoft .NET Framework 3.5 on Windows 11 version 26H1, Microsoft .NET Framework 3.5 on Windows Server 2012, Microsoft .NET Framework 3.5 on Windows Server 2012 R2, Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2012, Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2012 R2, Microsoft .NET Framework 4.8 on Windows 10 version 1607, Microsoft .NET Framework 4.8 on Windows Server 2012, Microsoft .NET Framework 4.8 on Windows Server 2012 R2, Microsoft .NET Framework 4.8 on Windows Server 2016, Microsoft .NET Framework 4.8.1 on Windows 11 version 26H1, Microsoft Visual Studio 2022 version 17.14, Microsoft Visual Studio 2026 version 18.10, System.Security.Cryptography.Xml on .NET 8.0 installed on Linux, System.Security.Cryptography.Xml on .NET 8.0 installed on Mac OS, System.Security.Cryptography.Xml on .NET 8.0 installed on Windows, Windows 10 Version 1607 for 32-bit Systems, Windows 10 Version 1607 for x64-based Systems, Windows 10 Version 1809 for 32-bit Systems, Windows 10 Version 1809 for x64-based Systems, Windows Server 2012 R2, Windows Server 2012 R2 (Server Core installation), Windows Server 2016, Windows Server 2016 (Server Core installation), Windows Server 2019, Windows Server 2019 (Server Core installation), Windows Server 2022, Windows Server 2022 (Server Core installation), Windows Server 2025, Windows Server 2025 (Server Core installation) → Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows 10 version 1607, Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2016, Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2019, Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 version 1809, Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 version 1809, Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 version 21H2, Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 version 22H2, Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2019, Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2022, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 version 21H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 version 22H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 23H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 24H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 25H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 26H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows Server 2022, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows Server 2025, Microsoft .NET Framework 3.5 on Windows 11 version 26H1, Microsoft .NET Framework 3.5 on Windows Server 2012, Microsoft .NET Framework 3.5 on Windows Server 2012 R2, Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2012, Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2012 R2, Microsoft .NET Framework 4.8 on Windows 10 version 1607, Microsoft .NET Framework 4.8 on Windows Server 2012, Microsoft .NET Framework 4.8 on Windows Server 2012 R2, Microsoft .NET Framework 4.8 on Windows Server 2016, Microsoft .NET Framework 4.8.1 on Windows 11 version 26H1, Microsoft Visual Studio 2022 version 17.14, Microsoft Visual Studio 2026 version 18.10, System.Security.Cryptography.Xml on .NET 8.0 runtime installed on Linux, System.Security.Cryptography.Xml on .NET 8.0 runtime installed on Mac OS, System.Security.Cryptography.Xml on .NET 8.0 runtime installed on Windows, Windows 10 Version 1607 for 32-bit Systems, Windows 10 Version 1607 for x64-based Systems, Windows 10 Version 1809 for 32-bit Systems, Windows 10 Version 1809 for x64-based Systems, Windows Server 2012 R2, Windows Server 2012 R2 (Server Core installation), Windows Server 2016, Windows Server 2016 (Server Core installation), Windows Server 2019, Windows Server 2019 (Server Core installation), Windows Server 2022, Windows Server 2022 (Server Core installation), Windows Server 2025, Windows Server 2025 (Server Core installation)
  9. Publisher revision note: Information published. → Updated the Security Updates table to add download and KB article links for Microsoft Visual Studio. This is an informational change only; the fixed builds are unchanged.
Page history

Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.

Cite this version
Field-level log (61)

Up to 100 recent field edits are shown; older edits may be outside retention.

  1. 7 Nov 2026 · 16:12:44 UTC EPSS0.6%; scored 6 Nov 2026 → 0.6%; scored 7 Nov 2026
  2. 6 Nov 2026 · 19:15:37 UTC EPSS0.6%; scored 5 Nov 2026 → 0.6%; scored 6 Nov 2026
  3. 6 Nov 2026 · 17:32:22 UTC Public detection templateUnknown: detection-template evidence is incomplete or retained → No Nuclei template listed
  4. 6 Nov 2026 · 17:32:22 UTC Source coverage: public-exploit-codeIncomplete → Current
  5. 6 Nov 2026 · 17:32:22 UTC Source coverage: first-epssIncomplete → Current
  6. 6 Nov 2026 · 17:32:22 UTC Source coverage: msrc-cvrfIncomplete → Current
  7. 6 Nov 2026 · 16:31:02 UTC Public detection templateNo Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
  8. 6 Nov 2026 · 16:31:02 UTC Source coverage: public-exploit-codeCurrent → Incomplete
  9. 6 Nov 2026 · 16:31:02 UTC Source coverage: first-epssCurrent → Incomplete
  10. 6 Nov 2026 · 16:31:02 UTC Source coverage: msrc-cvrfCurrent → Incomplete
  11. 5 Nov 2026 · 23:42:03 UTC EPSS0.6%; scored 4 Nov 2026 → 0.6%; scored 5 Nov 2026
  12. 5 Nov 2026 · 02:36:20 UTC EPSS0.6%; scored 3 Nov 2026 → 0.6%; scored 4 Nov 2026
  13. 4 Nov 2026 · 03:04:37 UTC EPSS0.6%; scored 2 Nov 2026 → 0.6%; scored 3 Nov 2026
  14. 3 Nov 2026 · 01:53:36 UTC EPSS0.6%; scored 1 Nov 2026 → 0.6%; scored 2 Nov 2026
  15. 2 Nov 2026 · 17:30:39 UTC Public detection templateUnknown: detection-template evidence is incomplete or retained → No Nuclei template listed
  16. 2 Nov 2026 · 17:30:39 UTC Source coverage: public-exploit-codeIncomplete → Current
  17. 2 Nov 2026 · 17:30:39 UTC Source coverage: first-epssIncomplete → Current
  18. 2 Nov 2026 · 17:30:39 UTC Source coverage: msrc-cvrfIncomplete → Current
  19. 2 Nov 2026 · 16:27:39 UTC Public detection templateNo Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
  20. 2 Nov 2026 · 16:27:39 UTC Source coverage: public-exploit-codeCurrent → Incomplete
  21. 2 Nov 2026 · 16:27:39 UTC Source coverage: first-epssCurrent → Incomplete
  22. 2 Nov 2026 · 16:27:39 UTC Source coverage: msrc-cvrfCurrent → Incomplete
  23. 2 Nov 2026 · 00:36:51 UTC EPSS0.6%; scored 31 Oct 2026 → 0.6%; scored 1 Nov 2026
  24. 31 Oct 2026 · 18:22:15 UTC EPSS0.6%; scored 30 Oct 2026 → 0.6%; scored 31 Oct 2026
  25. 30 Oct 2026 · 18:02:45 UTC EPSS0.6%; scored 29 Oct 2026 → 0.6%; scored 30 Oct 2026
  26. 29 Oct 2026 · 20:19:26 UTC Public detection templateNo Nuclei template listed
  27. 29 Oct 2026 · 20:19:26 UTC Customer actionRequired: apply the update → Required: follow the MSRC remediation guidance
  28. 29 Oct 2026 · 20:19:26 UTC Publicly disclosedNo → No (MSRC assessment)
  29. 29 Oct 2026 · 20:19:26 UTC Exploitation detectedNot reported by MSRC → No known exploitation (MSRC assessment)
  30. 29 Oct 2026 · 18:33:30 UTC EPSS0.6%; scored 28 Oct 2026 → 0.6%; scored 29 Oct 2026
  31. 28 Oct 2026 · 20:00:33 UTC EPSS0.6%; scored 27 Oct 2026 → 0.6%; scored 28 Oct 2026
  32. 27 Oct 2026 · 15:48:13 UTC EPSS0.6%; scored 26 Oct 2026 → 0.6%; scored 27 Oct 2026
  33. 26 Oct 2026 · 23:57:09 UTC EPSS0.6%; scored 25 Oct 2026 → 0.6%; scored 26 Oct 2026
  34. 25 Oct 2026 · 17:12:51 UTC EPSS0.6%; scored 24 Oct 2026 → 0.6%; scored 25 Oct 2026
  35. 25 Oct 2026 · 01:34:18 UTC EPSS0.6%; scored 23 Oct 2026 → 0.6%; scored 24 Oct 2026
  36. 23 Oct 2026 · 15:51:28 UTC EPSS0.6%; scored 22 Oct 2026 → 0.6%; scored 23 Oct 2026
  37. 23 Oct 2026 · 09:33:49 UTC Public exploit codeUnknown: exploit-code evidence is incomplete or retained → No Nuclei template listed
  38. 23 Oct 2026 · 09:33:49 UTC CISA KEVUnknown: catalog evidence is incomplete or retained → Not listed in the collected catalog
  39. 23 Oct 2026 · 09:33:49 UTC Source coverage: public-exploit-codeIncomplete → Current
  40. 23 Oct 2026 · 09:33:49 UTC Source coverage: first-epssIncomplete → Current
  41. 23 Oct 2026 · 09:33:49 UTC Source coverage: cisa-kevIncomplete → Current
  42. 23 Oct 2026 · 09:33:49 UTC Source coverage: msrc-cvrfIncomplete → Current
  43. 23 Oct 2026 · 08:31:50 UTC Public exploit codeNo Nuclei template listed → Unknown: exploit-code evidence is incomplete or retained
  44. 23 Oct 2026 · 08:31:50 UTC CISA KEVNot listed in the collected catalog → Unknown: catalog evidence is incomplete or retained
  45. 23 Oct 2026 · 08:31:50 UTC Source coverage: public-exploit-codeCurrent → Incomplete
  46. 23 Oct 2026 · 08:31:50 UTC Source coverage: first-epssCurrent → Incomplete
  47. 23 Oct 2026 · 08:31:50 UTC Source coverage: cisa-kevCurrent → Incomplete
  48. 23 Oct 2026 · 08:31:50 UTC Source coverage: msrc-cvrfCurrent → Incomplete
  49. 22 Oct 2026 · 22:02:57 UTC Affected productsMicrosoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows 10 version 1607, Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2016, Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2019, Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 version 1809, Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 version 1809, Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 version 21H2, Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 version 22H2, Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2019, Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2022, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 version 21H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 version 22H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 23H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 24H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 25H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 26H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows Server 2022, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows Server 2025, Microsoft .NET Framework 3.5 on Windows 11 version 26H1, Microsoft .NET Framework 3.5 on Windows Server 2012, Microsoft .NET Framework 3.5 on Windows Server 2012 R2, Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2012, Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2012 R2, Microsoft .NET Framework 4.8 on Windows 10 version 1607, Microsoft .NET Framework 4.8 on Windows Server 2012, Microsoft .NET Framework 4.8 on Windows Server 2012 R2, Microsoft .NET Framework 4.8 on Windows Server 2016, Microsoft .NET Framework 4.8.1 on Windows 11 version 26H1, Microsoft Visual Studio 2022 version 17.14, Microsoft Visual Studio 2026 version 18.10, System.Security.Cryptography.Xml on .NET 8.0 installed on Linux, System.Security.Cryptography.Xml on .NET 8.0 installed on Mac OS, System.Security.Cryptography.Xml on .NET 8.0 installed on Windows, Windows 10 Version 1607 for 32-bit Systems, Windows 10 Version 1607 for x64-based Systems, Windows 10 Version 1809 for 32-bit Systems, Windows 10 Version 1809 for x64-based Systems, Windows Server 2012 R2, Windows Server 2012 R2 (Server Core installation), Windows Server 2016, Windows Server 2016 (Server Core installation), Windows Server 2019, Windows Server 2019 (Server Core installation), Windows Server 2022, Windows Server 2022 (Server Core installation), Windows Server 2025, Windows Server 2025 (Server Core installation) → Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows 10 version 1607, Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2016, Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2019, Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 version 1809, Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 version 1809, Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 version 21H2, Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 version 22H2, Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2019, Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2022, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 version 21H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 version 22H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 23H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 24H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 25H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 26H2, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows Server 2022, Microsoft .NET Framework 3.5 AND 4.8.1 on Windows Server 2025, Microsoft .NET Framework 3.5 on Windows 11 version 26H1, Microsoft .NET Framework 3.5 on Windows Server 2012, Microsoft .NET Framework 3.5 on Windows Server 2012 R2, Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2012, Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2012 R2, Microsoft .NET Framework 4.8 on Windows 10 version 1607, Microsoft .NET Framework 4.8 on Windows Server 2012, Microsoft .NET Framework 4.8 on Windows Server 2012 R2, Microsoft .NET Framework 4.8 on Windows Server 2016, Microsoft .NET Framework 4.8.1 on Windows 11 version 26H1, Microsoft Visual Studio 2022 version 17.14, Microsoft Visual Studio 2026 version 18.10, System.Security.Cryptography.Xml on .NET 8.0 runtime installed on Linux, System.Security.Cryptography.Xml on .NET 8.0 runtime installed on Mac OS, System.Security.Cryptography.Xml on .NET 8.0 runtime installed on Windows, Windows 10 Version 1607 for 32-bit Systems, Windows 10 Version 1607 for x64-based Systems, Windows 10 Version 1809 for 32-bit Systems, Windows 10 Version 1809 for x64-based Systems, Windows Server 2012 R2, Windows Server 2012 R2 (Server Core installation), Windows Server 2016, Windows Server 2016 (Server Core installation), Windows Server 2019, Windows Server 2019 (Server Core installation), Windows Server 2022, Windows Server 2022 (Server Core installation), Windows Server 2025, Windows Server 2025 (Server Core installation)
  50. 22 Oct 2026 · 17:33:15 UTC EPSS0.6%; scored 21 Oct 2026 → 0.6%; scored 22 Oct 2026
  51. 21 Oct 2026 · 21:47:24 UTC EPSS0.6%; scored 20 Oct 2026 → 0.6%; scored 21 Oct 2026
  52. 20 Oct 2026 · 20:53:31 UTC EPSS0.6%; scored 19 Oct 2026 → 0.6%; scored 20 Oct 2026
  53. 19 Oct 2026 · 15:12:40 UTC EPSS0.6%; scored 18 Oct 2026 → 0.6%; scored 19 Oct 2026
  54. 19 Oct 2026 · 15:12:40 UTC Link: Cisco Talos analysishttps://blog.talosintelligence.com/microsoft-patch-tuesday-for-october-2026
  55. 18 Oct 2026 · 14:54:30 UTC EPSS0.6%; scored 16 Oct 2026 → 0.6%; scored 18 Oct 2026
  56. 18 Oct 2026 · 14:54:30 UTC Link: October 2026/security?release=2026-Oct#cves
  57. 17 Oct 2026 · 07:28:24 UTC Revision noteInformation published. → Updated the Security Updates table to add download and KB article links for Microsoft Visual Studio. This is an informational change only; the fixed builds are unchanged.
  58. 17 Oct 2026 · 07:28:24 UTC Last revised13 Oct 2026 07:00 UTC → 16 Oct 2026 07:00 UTC
  59. 16 Oct 2026 · 16:13:25 UTC EPSS0.6%; scored 15 Oct 2026 → 0.6%; scored 16 Oct 2026
  60. 15 Oct 2026 · 21:30:54 UTC EPSS0.6%; scored 14 Oct 2026 → 0.6%; scored 15 Oct 2026
  61. 15 Oct 2026 · 01:07:54 UTC EPSSNot scored → 0.6%; scored 14 Oct 2026

Explore global source statements, affected packages and advisory history for CVE-2026-96222. The catalog has a separate collection scope from Microsoft release records.

Collected exploitation and prediction evidence

Risk source coverage

CISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.

CVE-2026-96222

No KEV entry is attached to this observation; this is not evidence that exploitation is absent.

FIRST EPSS: 0.59 % · percentile 48.28 % · scored 7 Nov 2026.

Observed 07 Nov 2026 16:07:52 UTC · Complete immutable risk JSON

cve-program · CVE-2026-96222

Published

Active Directory Federation Services (AD FS) Spoofing Vulnerability

Improper certificate validation in Active Directory Federation Services (AD FS) allows an unauthorized attacker to perform spoofing over a network.

Source published
13 Oct 2026 19:00:31 UTC
Source modified
31 Oct 2026 18:06:49 UTC
Observed here
31 Oct 2026 20:04:47 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: cve-program · CVE Program Terms of Use. Source text is retained; field grouping and change labels are provided by ChangeIntel.

CVSS 3.1 · 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C

euvd · EUVD-2026-99750

Published

Improper certificate validation in Active Directory Federation Services (AD FS) allows an unauthorized attacker to perform spoofing over a network.

Improper certificate validation in Active Directory Federation Services (AD FS) allows an unauthorized attacker to perform spoofing over a network.

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Oct 13, 2026, 7:00:31 PM

dateUpdated: Oct 31, 2026, 6:06:49 PM

7 related source bulletins · separate from aliases

WID-SEC-W-2026-3893: Microsoft Entwicklerwerkzeuge: Mehrere Schwachstellen

CVE-2026-100205 · CVE-2026-102229 · CVE-2026-102231 · CVE-2026-102232 · CVE-2026-102233 · CVE-2026-102234 · CVE-2026-102235 · CVE-2026-102238 · CVE-2026-102851 · CVE-2026-102869 · CVE-2026-102870 · CVE-2026-103572 · CVE-2026-105016 · CVE-2026-105729 · CVE-2026-105732 · CVE-2026-108398 · CVE-2026-109468 · CVE-2026-58280 · CVE-2026-66822 · CVE-2026-69370 · CVE-2026-69651 · CVE-2026-70007 · CVE-2026-70035 · CVE-2026-70098 · CVE-2026-70159 · CVE-2026-70161 · CVE-2026-70162 · CVE-2026-70165 · CVE-2026-70174 · CVE-2026-70175 · CVE-2026-70179 · CVE-2026-70181 · CVE-2026-70183 · CVE-2026-70186 · CVE-2026-70188 · CVE-2026-70190 · CVE-2026-70194 · CVE-2026-70196 · CVE-2026-70197 · CVE-2026-83520 · CVE-2026-84008 · CVE-2026-85363 · CVE-2026-85790 · CVE-2026-87697 · CVE-2026-88092 · CVE-2026-92707 · CVE-2026-96222 · CVE-2026-96224 · CVE-2026-96225 · CVE-2026-96229 · CVE-2026-96230 · CVE-2026-96231 · CVE-2026-96232 · CVE-2026-96233 · CVE-2026-96234 · CVE-2026-96235 · CVE-2026-96236 · CVE-2026-96237 · CVE-2026-96238 · CVE-2026-96251 · CVE-2026-96303 · CVE-2026-96957 · CVE-2026-96958 · CVE-2026-96959 · CVE-2026-96960 · CVE-2026-97788 · CVE-2026-97801

RHSA-2026:86594: Red Hat Security Advisory: .NET 8.0 security, bug fix, and enhancement update

CVE-2026-58280 · CVE-2026-66822 · CVE-2026-69651 · CVE-2026-70159 · CVE-2026-70175 · CVE-2026-70179 · CVE-2026-70181 · CVE-2026-70183 · CVE-2026-70186 · CVE-2026-70188 · CVE-2026-70196 · CVE-2026-84008 · CVE-2026-88092 · CVE-2026-92707 · CVE-2026-96222 · CVE-2026-96225 · CVE-2026-96230 · CVE-2026-96231 · CVE-2026-96233 · CVE-2026-96236 · CVE-2026-96237 · CVE-2026-96238 · CVE-2026-96958 · CVE-2026-96959 · CVE-2026-96960

RHSA-2026:86169: Red Hat Security Advisory: .NET 8.0 security, bug fix, and enhancement update

CVE-2026-58280 · CVE-2026-66822 · CVE-2026-69651 · CVE-2026-70159 · CVE-2026-70175 · CVE-2026-70179 · CVE-2026-70181 · CVE-2026-70183 · CVE-2026-70186 · CVE-2026-70188 · CVE-2026-70196 · CVE-2026-84008 · CVE-2026-88092 · CVE-2026-92707 · CVE-2026-96222 · CVE-2026-96225 · CVE-2026-96230 · CVE-2026-96231 · CVE-2026-96233 · CVE-2026-96236 · CVE-2026-96237 · CVE-2026-96238 · CVE-2026-96958 · CVE-2026-96959 · CVE-2026-96960

RHSA-2026:88474: Red Hat Security Advisory: .NET 8.0 security update

CVE-2026-58280 · CVE-2026-58649 · CVE-2026-66822 · CVE-2026-69651 · CVE-2026-70159 · CVE-2026-70175 · CVE-2026-70179 · CVE-2026-70181 · CVE-2026-70183 · CVE-2026-70186 · CVE-2026-70188 · CVE-2026-70196 · CVE-2026-84008 · CVE-2026-88092 · CVE-2026-92707 · CVE-2026-96222 · CVE-2026-96225 · CVE-2026-96230 · CVE-2026-96231 · CVE-2026-96233 · CVE-2026-96236 · CVE-2026-96237 · CVE-2026-96238 · CVE-2026-96958 · CVE-2026-96959 · CVE-2026-96960

RHSA-2026:88425: Red Hat Security Advisory: .NET 8.0 security update

CVE-2026-58280 · CVE-2026-58649 · CVE-2026-66822 · CVE-2026-69651 · CVE-2026-70159 · CVE-2026-70175 · CVE-2026-70179 · CVE-2026-70181 · CVE-2026-70183 · CVE-2026-70186 · CVE-2026-70188 · CVE-2026-70196 · CVE-2026-84008 · CVE-2026-88092 · CVE-2026-92707 · CVE-2026-96222 · CVE-2026-96225 · CVE-2026-96230 · CVE-2026-96231 · CVE-2026-96233 · CVE-2026-96236 · CVE-2026-96237 · CVE-2026-96238 · CVE-2026-96958 · CVE-2026-96959 · CVE-2026-96960

RHSA-2026:86168: Red Hat Security Advisory: .NET 8.0 security, bug fix, and enhancement update

CVE-2026-58280 · CVE-2026-66822 · CVE-2026-69651 · CVE-2026-70159 · CVE-2026-70175 · CVE-2026-70179 · CVE-2026-70181 · CVE-2026-70183 · CVE-2026-70186 · CVE-2026-70188 · CVE-2026-70196 · CVE-2026-84008 · CVE-2026-88092 · CVE-2026-92707 · CVE-2026-96222 · CVE-2026-96225 · CVE-2026-96230 · CVE-2026-96231 · CVE-2026-96233 · CVE-2026-96236 · CVE-2026-96237 · CVE-2026-96238 · CVE-2026-96958 · CVE-2026-96959 · CVE-2026-96960

RHSA-2026:88422: Red Hat Security Advisory: .NET 8.0 security update

CVE-2026-58280 · CVE-2026-58649 · CVE-2026-66822 · CVE-2026-69651 · CVE-2026-70159 · CVE-2026-70175 · CVE-2026-70179 · CVE-2026-70181 · CVE-2026-70183 · CVE-2026-70186 · CVE-2026-70188 · CVE-2026-70196 · CVE-2026-84008 · CVE-2026-88092 · CVE-2026-92707 · CVE-2026-96222 · CVE-2026-96225 · CVE-2026-96230 · CVE-2026-96231 · CVE-2026-96233 · CVE-2026-96236 · CVE-2026-96237 · CVE-2026-96238 · CVE-2026-96958 · CVE-2026-96959 · CVE-2026-96960

Source published
Oct 13, 2026, 7:00:31 PM (timezone not stated)
Source modified
Oct 31, 2026, 6:06:49 PM (timezone not stated)
Observed here
7 Nov 2026 15:26:52 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: euvd · ENISA EUVD · source terms and attribution apply. Source text is retained; field grouping and change labels are provided by ChangeIntel.

EUVD CVSS 3.1 · 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C

nvd · CVE-2026-96222

Published

Improper certificate validation in Active Directory Federation Services (AD FS) allows an unauthorized attacker to perform spoofing over a network.

Improper certificate validation in Active Directory Federation Services (AD FS) allows an unauthorized attacker to perform spoofing over a network.

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-295

Original publisher date fields

published: 2026-10-13T19:21:48.030

lastModified: 2026-10-22T22:19:55.133

38 source CPE criteria · context only
  • cpe:2.3:o:microsoft:windows_10_1607:*:*:*:*:*:*:x64:*
  • cpe:2.3:o:microsoft:windows_10_1607:*:*:*:*:*:*:x86:*
  • cpe:2.3:o:microsoft:windows_10_1809:*:*:*:*:*:*:x64:*
  • cpe:2.3:o:microsoft:windows_10_1809:*:*:*:*:*:*:x86:*
  • cpe:2.3:o:microsoft:windows_server_2012:-:*:*:*:*:*:*:*
  • cpe:2.3:o:microsoft:windows_server_2012:r2:*:*:*:*:*:*:*
  • cpe:2.3:o:microsoft:windows_server_2016:*:*:*:*:*:*:x64:*
  • cpe:2.3:o:microsoft:windows_server_2019:*:*:*:*:*:*:x64:*
  • cpe:2.3:o:microsoft:windows_server_2022:*:*:*:*:*:*:x64:*
  • cpe:2.3:o:microsoft:windows_server_2025:*:*:*:*:*:*:x64:*
  • cpe:2.3:a:microsoft:.net:*:*:*:*:*:*:*:*
  • cpe:2.3:o:apple:macos:-:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*
  • cpe:2.3:o:microsoft:windows:-:*:*:*:*:*:*:*
  • cpe:2.3:a:microsoft:visual_studio_2022:*:*:*:*:*:-:*:*
  • cpe:2.3:a:microsoft:visual_studio_2026:*:*:*:*:*:-:*:*
  • cpe:2.3:a:microsoft:.net_framework:4.8.1:*:*:*:*:*:*:*
  • cpe:2.3:o:microsoft:windows_11_26h1:-:*:*:*:*:*:arm64:*
  • cpe:2.3:o:microsoft:windows_11_26h1:-:*:*:*:*:*:x64:*
  • cpe:2.3:a:microsoft:.net_framework:4.8:*:*:*:*:*:*:*
  • cpe:2.3:o:microsoft:windows_10_1607:-:*:*:*:*:*:*:*
  • cpe:2.3:o:microsoft:windows_server_2016:-:*:*:*:*:*:*:*
  • cpe:2.3:a:microsoft:.net_framework:4.6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:microsoft:.net_framework:4.7:*:*:*:*:*:*:*
  • cpe:2.3:a:microsoft:.net_framework:4.7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:microsoft:.net_framework:4.7.2:*:*:*:*:*:*:*
  • cpe:2.3:a:microsoft:.net_framework:3.5:*:*:*:*:*:*:*
  • cpe:2.3:o:microsoft:windows_10_1809:-:*:*:*:*:*:*:*
  • cpe:2.3:o:microsoft:windows_10_21h2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:microsoft:windows_10_22h2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:microsoft:windows_server_2019:-:*:*:*:*:*:*:*
  • cpe:2.3:o:microsoft:windows_server_2022:-:*:*:*:*:*:*:*
  • cpe:2.3:o:microsoft:windows_11_23h2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:microsoft:windows_11_24h2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:microsoft:windows_11_25h2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:microsoft:windows_11_26h2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:microsoft:windows_server_2025:-:*:*:*:*:*:*:*
  • cpe:2.3:o:microsoft:windows_11_26h1:-:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
13 Oct 2026 19:21:48 UTC
Source modified
22 Oct 2026 22:19:55 UTC
Observed here
25 Oct 2026 16:19:28 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: nvd · NIST NVD usage terms; underlying source attribution retained. Source text is retained; field grouping and change labels are provided by ChangeIntel.

CVSS 3.1 · [email protected] · Secondary · 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

osv · GHSA-vrv5-2jg9-4mmr

Published

Microsoft Security Advisory CVE-2026-96222 - .NET Spoofing Vulnerability

## Executive summary Microsoft is releasing this security advisory to provide information about a vulnerability in System.Security.Cryptography.Xml. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. `KeyInfoX509Data` can accept serialized certificate formats containing attacker-controlled chain metadata instead of requiring a plain X.509 certificate, contributing to certificate-forgery and token-spoofing paths. ## Announcement Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/474 ## CVSS Details - **Version:** 3.1 - **Severity:** High - **Score:** 7.4 - **Vector:** `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N` - **Weakness:** CWE-295 (Improper Certificate Validation) ## Affected Platforms - **Platforms:** Windows, Linux, macOS - **Architectures:** All ## <a name="affected-packages"></a>Affected Packages The vulnerability affects Microsoft .NET projects that use an affected package version listed below. Package name | Affected version | Patched version ------------ | ---------------- | --------------- [System.Security.Cryptography.Xml](https://www.nuget.org/packages/System.Security.Cryptography.Xml) | >= 8.0.0, <= 8.0.4 | 8.0.5 ## Advisory FAQ ### <a name="how-affected"></a>How do I know if I am affected? If using a package listed in [affected packages](#affected-packages), you're exposed to the vulnerability. ### <a name="how-fix"></a>How do I fix the issue? 1. To fix the issue please install the latest version of .NET. If you have installed one or more .NET SDKs through Visual Studio, Visual Studio will prompt you to update Visual Studio, which will also update your .NET SDKs. 2. If your application references the vulnerable package, update the package reference to the patched version. You can list the versions you have installed by running the `dotnet --info` command. Once you have installed the updated runtime or SDK, restart your apps for the update to take effect. Additionally, if you've deployed [self-contained applications](https://docs.microsoft.com/dotnet/core/deploying/#self-contained-deployments-scd) targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed. ## Other Information ### Reporting Security Issues If you have found a potential security issue in a supported version of .NET, please report it to the Microsoft Security Response Center (MSRC) via the [MSRC Researcher Portal](https://msrc.microsoft.com/report/vulnerability/new). Further information can be found in the MSRC [Report an Issue FAQ](https://www.microsoft.com/msrc/faqs-report-an-issue). Security reports made through MSRC may qualify for the Microsoft .NET Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at https://aka.ms/corebounty. ### Support You can ask questions about this issue on GitHub in the .NET GitHub organization. The main repos are located at https://github.com/dotnet/runtime. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked discussion issue. ### Disclaimer The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply. ### External Links [CVE-2026-96222](https://www.cve.org/CVERecord?id=CVE-2026-96222) ### Acknowledgements - Vaisha Bernard with Eye Security ### Revisions V1.0 (10/13/2026): Advisory published.

Source published
13 Oct 2026 20:45:13 UTC
Source modified
21 Oct 2026 12:11:16 UTC
Observed here
23 Oct 2026 16:01:25 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · GitHub Advisory Database · CC-BY-4.0. Source text is retained; field grouping and change labels are provided by ChangeIntel.

CVSS_V3 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Publisher rating · HIGH

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 8 Nov 06:21 UTC · 275 of 275 readable · 273 fully read · documentation 469/469 current

No accounts or analytics; your preferences stay in your browser. Information, not advice. ChangeIntel is an independent tool and is not affiliated with or endorsed by Microsoft, Apple, Google, Broadcom (VMware), Jamf, Oracle, Mozilla, or any other vendor it covers. Product names are trademarks of their owners. Built by Evotec.