CVE-2026-49785: UEFI Secure Boot Security Feature Bypass Vulnerability

Published Oct 13, 2026
·
Updated

Improper resource shutdown or release in Windows UEFI allows an authorized attacker to bypass a security feature locally.

Other sources

UEFI Secure Boot Security Feature Bypass Vulnerability

— Microsoft

Affected Software

32 affected componentsFixes available
Microsoft Windows 11=24H2
10.0.26100.9711
Microsoft Windows Server 2012 R2<6.3.9600.23470
6.3.9600.23470
Microsoft Windows 10=1809
10.0.17763.9376
Microsoft Windows Server 2016<10.0.14393.9612
10.0.14393.9612
Microsoft Windows 10=1607
10.0.14393.9612
Microsoft Windows Server 2016<10.0.14393.9612
10.0.14393.9612
Microsoft Windows Server 2012<6.2.9200.26434
6.2.9200.26434
Microsoft Windows Server 2025<10.0.26100.33650
10.0.26100.33650
Microsoft Windows 11=23H2
10.0.22631.7652
Microsoft Windows Server 2012 R2<6.3.9600.23470
6.3.9600.23470
Microsoft Windows 10=1607
10.0.14393.9612
Microsoft Windows 11=26H1
10.0.28000.3231
Microsoft Windows 10=21H2
10.0.19044.7807
Microsoft Windows 11=26H1
10.0.28000.3231
Microsoft Windows Server 2022<10.0.20348.5761
10.0.20348.5761
Microsoft Windows 10=22H2
10.0.19044.7807
Microsoft Windows 11=25H2
10.0.26200.9711
Microsoft Windows 11=24H2
10.0.26100.9711
Microsoft Windows Server 2012<6.2.9200.26434
6.2.9200.26434
Microsoft Windows 11=23H2
10.0.22631.7652
Microsoft Windows 10=22H2
10.0.19044.7807
Microsoft Windows 11=25H2
10.0.26200.9711
Microsoft Windows 10=21H2
10.0.19044.7807
Microsoft Windows Server 2025<10.0.26100.33650
10.0.26100.33650
Microsoft Windows 10=22H2
10.0.19044.7807
Microsoft Windows 10=21H2
10.0.19044.7807
Microsoft Windows Server 2019<10.0.17763.9376
10.0.17763.9376
Microsoft Windows 10=1809
10.0.17763.9376
Microsoft Windows Server 2019<10.0.17763.9376
10.0.17763.9376
Microsoft Windows Server 2022<10.0.20348.5761
10.0.20348.5761
Microsoft Windows 11=26H2
10.0.26300.9711
Microsoft Windows 11=26H2
10.0.26300.9711

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26100.9711Patch KB5127648
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.3.9600.23470Patch KB5126836
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.14393.9612Patch KB5126868
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.17763.9376Patch KB5126651
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.22631.7652Patch KB5126653
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26100.33650Patch KB5126646
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.2.9200.26434Patch KB5126835
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19044.7807Patch KB5126657
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.28000.3231Patch KB5127646
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.20348.5761Patch KB5126655
  11. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26200.9711Patch KB5127648
  12. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26300.9711Patch KB5127648

Event History

Oct 13, 2026
CVE Published
via Microsoft·02:00 PM
Data Sourced
via Microsoft·02:00 PM
DescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·06:59 PM
Data Sourced
via MITRE·06:59 PM
DescriptionSeverity

Frequently Asked Questions

1

Who is exposed to this issue?

The affected software list includes Microsoft Windows 10, Windows 11, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019, Windows Server 2022, and Windows Server 2025.

2

What access does an attacker need to exploit it?

An attacker needs local access and low-level privileges on the affected system. No user interaction is required.

3

Is this a remote exploitation risk?

The listed attack vector is local, so the provided data does not indicate exploitation directly over the network. Systems where untrusted or insufficiently trusted users can obtain local access should be prioritized.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203