How severe is CVE-2026-25250?

CVE-2026-25250 has a CVSS 3.x base score of 6.0, rated medium severity. It is exploitable over local access with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2026-25250 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (4th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-25250?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2026-25250 published?

CVE-2026-25250 was published on 2026-08-27 and last updated on 2026-09-09.

CVE-2026-25250

CVE-2026-25250 is a medium-severity vulnerability with a CVSS 3.x base score of 6.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-325.

Key facts

Severity: Medium (CVSS 3.x base score 6.0)
EPSS exploit prediction: 0% (4th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-325
Published: 2026-08-27
Last modified: 2026-09-09

Description

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

Frequently asked questions

What is CVE-2026-25250?: EAZ EazyFix 12.9 allows a Security Feature Bypass related to a "Missing Cryptographic Step" associated with "Secure Boot disable."
How severe is CVE-2026-25250?: CVE-2026-25250 has a CVSS 3.x base score of 6.0, rated medium severity. It is exploitable over local access with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2026-25250 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (4th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-25250?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2026-25250 published?: CVE-2026-25250 was published on 2026-08-27 and last updated on 2026-09-09.

References

Other CWE-325 vulnerabilities

CVE-2026-17666 — Critical (CVSS 9.1): Cryptographic Flaw in Enterprise in Google Chrome prior to 151.0.7922.72 allowed an attacker in a privileged network…
CVE-2026-16000 — High (CVSS 8.7): Missing cryptographic step in the DSTU 7624 CCM mode implementation (KCcmBlockCipher) in Legion of the Bouncy Castle…
CVE-2026-76784 — High (CVSS 8.7): Multiple TP-Link Kasa smart home devices contain insufficient cryptographic protections in the local device…
CVE-2026-4601 — High (CVSS 8.7): Versions of the package jsrsasign before 11.1.1 are vulnerable to Missing Cryptographic Step via the…
CVE-2025-30147 — High (CVSS 8.7): Besu Native contains scripts and tooling that is used to build and package the native libraries used by the Ethereum…
CVE-2026-100798 — High (CVSS 8.1): Cryptography misuse in Storage: Quota Manager component. This vulnerability was fixed in Firefox ESR 153.4, Thunderbird…

Browse all CWE-325 vulnerabilities →