CVE-2026-25250: Medium severity Microsoft Windows 10 vulnerability

Published Apr 14, 2026
·
Updated

EAZ EazyFix 12.9 allows a Security Feature Bypass related to a "Missing Cryptographic Step" associated with "Secure Boot disable."

Other sources

Missing cryptographic step in Windows Secure Boot allows an authorized attacker to bypass a security feature locally.

Microsoft

MITRE: CVE-2026-25250 Secure Boot disable Eazy Fix

Microsoft

Affected Software

31 affected componentsFixes available
Microsoft Windows 10=1607
10.0.14393.9060
Microsoft Windows Server 2025<10.0.26100.32690
10.0.26100.32690
Microsoft Windows Server 2016<10.0.14393.9060
10.0.14393.9060
Microsoft Windows Server 2016<10.0.14393.9060
10.0.14393.9060
Microsoft Windows Server 2012<6.2.9200.26026
6.2.9200.26026
Microsoft Windows Server 2012 R2<6.3.9600.23132
6.3.9600.23132
Microsoft Windows 11=24H2
10.0.26100.8246
Microsoft Windows Server 2012<6.2.9200.26026
6.2.9200.26026
Microsoft Windows 10=1607
10.0.14393.9060
Microsoft Windows 11=24H2
10.0.26100.8246
Microsoft Windows 11=23H2
10.0.22631.6936
Microsoft Windows Server 2022, 23H2 Edition<10.0.25398.2274
10.0.25398.2274
Microsoft Windows 11=23H2
10.0.22631.6936
Microsoft Windows Server 2012 R2<6.3.9600.23132
6.3.9600.23132
Microsoft Windows 10=22H2
10.0.19045.7184
Microsoft Windows 11=25H2
10.0.26200.8246
Microsoft Windows Server 2025<10.0.26100.32690
10.0.26100.32690
Microsoft Windows 10=22H2
10.0.19045.7184
Microsoft Windows 10=22H2
10.0.19045.7184
Microsoft Windows 10=21H2
10.0.19044.7184
Microsoft Windows 10=21H2
10.0.19044.7184
Microsoft Windows 11=25H2
10.0.26200.8246
Microsoft Windows 10=21H2
10.0.19044.7184
Microsoft Windows Server 2022<10.0.20348.5020
10.0.20348.5020
Microsoft Windows Server 2022<10.0.20348.5020
10.0.20348.5020
Microsoft Windows Server 2019<10.0.17763.8644
10.0.17763.8644
Microsoft Windows 11=26H1
10.0.28000.1836
Microsoft Windows Server 2019<10.0.17763.8644
10.0.17763.8644
Microsoft Windows 11=26H1
10.0.28000.1836
Microsoft Windows 10=1809
10.0.17763.8644
Microsoft Windows 10=1809
10.0.17763.8644

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.14393.9060Patch KB5082198
  2. Upgrade

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

    Fixed in 10.0.26100.32690Patch KB5082063
  3. Upgrade

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

    Fixed in 6.2.9200.26026Patch KB5082127
  4. Upgrade

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

    Fixed in 6.3.9600.23132Patch KB5082126
  5. Upgrade

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

    Fixed in 10.0.26100.8246Patch KB5083769
  6. Upgrade

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

    Fixed in 10.0.22631.6936Patch KB5082052
  7. Upgrade

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

    Fixed in 10.0.25398.2274Patch KB5082060
  8. Upgrade

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

    Fixed in 10.0.19045.7184Patch KB5082200
  9. Upgrade

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

    Fixed in 10.0.26200.8246Patch KB5083769
  10. Upgrade

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

    Fixed in 10.0.19044.7184Patch KB5082200
  11. Upgrade

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

    Fixed in 10.0.20348.5020Patch KB5082142
  12. Upgrade

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

    Fixed in 10.0.17763.8644Patch KB5082123
  13. Upgrade

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

    Fixed in 10.0.28000.1836Patch KB5083768
  14. Upgrade

    Upgrade EAZ EazyFix to a version that resolves this vulnerability.

    Fixed in 12.9
  15. Upgrade

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

    Patch CVE-2026-25250

Event History

Apr 14, 2026
CVE Published
via Microsoft·02:00 PM
Data Sourced
via Microsoft·02:00 PM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·02:00 PM
Affected Software
Updated
via Microsoft·02:00 PM
Affected Software
Updated
via Microsoft·02:00 PM
Description
Aug 27, 2026
CVE Published
via MITRE·04:55 PM
Data Sourced
via MITRE·04:55 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What is the severity of CVE-2026-25250?

CVE-2026-25250 has a high-severity rating due to the potential for an attacker to bypass critical security features in Windows Secure Boot.

2

How do I fix CVE-2026-25250?

To address CVE-2026-25250, apply the relevant security patches provided by Microsoft for affected products.

3

Which Microsoft products are affected by CVE-2026-25250?

CVE-2026-25250 impacts various Microsoft products including Windows Server 2012, Windows Server 2016, Windows 10, and Windows 11.

4

Can I disable Secure Boot to mitigate CVE-2026-25250?

Disabling Secure Boot is not recommended as it will expose the system to higher security risks; applying patches is the preferred solution.

5

Is CVE-2026-25250 exploitable remotely?

CVE-2026-25250 is primarily a local vulnerability, requiring physical access to the system for exploitation.

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