How severe is CVE-2025-2230?

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

Is CVE-2025-2230 being actively exploited?

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

How do I fix CVE-2025-2230?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-2230 have an EU (EUVD) identifier?

Yes. CVE-2025-2230 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-6388.

When was CVE-2025-2230 published?

CVE-2025-2230 was published on 2025-03-13 and last updated on 2026-06-17.

CVE-2025-2230

CVE-2025-2230 is a high-severity vulnerability with a CVSS 3.x base score of 7.7. 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-287.

Key facts

Severity: High (CVSS 3.x base score 7.7)
CVSS v4: 8.5
EPSS exploit prediction: 0% (12th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-6388
Weakness: CWE-287
Published: 2025-03-13
Last modified: 2026-06-17

Description

A flaw exists in the Windows login flow where an AuthContext token can be exploited for replay attacks and authentication bypass.

Frequently asked questions

What is CVE-2025-2230?: A flaw exists in the Windows login flow where an AuthContext token can be exploited for replay attacks and authentication bypass.
How severe is CVE-2025-2230?: CVE-2025-2230 has a CVSS 3.x base score of 7.7, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2025-2230 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (12th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-2230?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-2230 have an EU (EUVD) identifier?: Yes. CVE-2025-2230 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-6388.
When was CVE-2025-2230 published?: CVE-2025-2230 was published on 2025-03-13 and last updated on 2026-06-17.

References

Other CWE-287 (Improper Authentication) vulnerabilities

CVE-2026-45480 — Critical (CVSS 10.0): Improper authentication in Azure Active Directory allows an unauthorized attacker to elevate privileges over a network.
CVE-2026-46389 — Critical (CVSS 10.0): UDS Identity Config builds the Keycloak configuration image (realm, plugins, theme, truststore, JARs) consumed by UDS…
CVE-2026-10611 — Critical (CVSS 10.0): An authentication bypass vulnerability exists in MISP when LDAP mixed authentication is enabled with OTP enforcement.…
CVE-2026-47280 — Critical (CVSS 10.0): Improper authentication in Azure Resource Manager (ARM) allows an unauthorized attacker to elevate privileges over a…
CVE-2026-42822 — Critical (CVSS 10.0): Improper authentication in Azure Local Disconnected Operations allows an unauthorized attacker to elevate privileges…
CVE-2026-20182 — Critical (CVSS 10.0): May 2026: This security advisory provides the details and fix information for a vulnerability that was discovered and…

Browse all CWE-287 (Improper Authentication) vulnerabilities →