What is the CVSS score of EUVD-2026-44034?

EUVD-2026-44034 has a CVSS 3.1 base score of 7.1 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N. EPSS exploitation probability: 0.2%.

Which versions of Windows CryptoAPI are affected by EUVD-2026-44034?

Windows CryptoAPI vulnerability (CVE-2026-55144) affects Windows 11 and Windows Server 2022/2025, creating risk for organizations dependent on Windows-based cryptographic operations.. A patch is available.

How to fix or mitigate EUVD-2026-44034?

Within 24 hours, inventory all Windows 11 (24H2, 25H2, 26H1) and Windows Server 2022/2025 systems and identify those handling cryptographically sensitive or regulated data. Within 7 days, obtain the MSRC-released patch, validate it in test environments against dependent applications, and establish a deployment schedule prioritizing systems with the highest cryptographic workloads. Complete patch deployment to all affected systems within 30 days and document patch application status for compliance audit trails.

Windows CryptoAPI EUVD-2026-44034

| CVE-2026-55144 HIGH

Missing Cryptographic Step (CWE-325)

2026-07-14 microsoft

GHSA-4r8r-cjr4-hvqr

Information Disclosure Microsoft Windows Server 2022 Windows Server 2025 Windows 11 Version 24H2 Windows 11 Version 25H2 Windows 11 Version 26H1 Windows Server 2025 Server Core Installation

7.1

CVSS 3.1 · Vendor: microsoft

Severity by source

Vendor (microsoft) PRIMARY

7.1 HIGH

AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

vuln.today AI

7.1 HIGH

Local, authenticated foothold required (AV:L, PR:L) with low complexity and no UI; a missing crypto step enables data tampering and disclosure (I:H, C:H) with no availability effect.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

Analysis Generated

Jul 14, 2026 - 17:56 vuln.today

CVE Published

Jul 14, 2026 - 17:05 nvd

HIGH 7.1

DescriptionCVE.org

Missing cryptographic step in Windows CryptoAPI allows an authorized attacker to perform tampering locally.

AnalysisAI

Local tampering in Windows CryptoAPI (Crypt32) on Windows 11 (24H2/25H2/26H1) and Windows Server 2022/2025 stems from a missing cryptographic step, letting an authenticated local attacker undermine the integrity and confidentiality of cryptographically protected data. Microsoft rates it 7.1 (High) with high confidentiality and integrity impact; there is no public exploit identified at time of analysis and it is not on the CISA KEV list. A vendor patch is available through the MSRC update guide.

Technical ContextAI

Windows CryptoAPI (the crypt32.dll / cryptographic services stack) is the core OS component that applications rely on for certificate validation, signature verification, encryption, and key handling. The root cause is CWE-325 (Missing Required Cryptographic Step): a required operation in a cryptographic routine is omitted, weakening the guarantees the algorithm is supposed to provide. When a step such as a validation, padding check, integrity/MAC verification, or nonce/parameter handling is skipped, protected data can be forged or altered without detection, which is why Microsoft characterizes the impact as tampering. The CPE data scopes the flaw to Microsoft Windows 11 versions 24H2, 25H2 and 26H1, plus Windows Server 2022 and Windows Server 2025 (including the Server Core installation).

RemediationAI

Patch available per vendor advisory - apply the Microsoft security update for CVE-2026-55144 delivered through the monthly Windows cumulative update for your specific SKU, tracked at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-55144; the exact fixed build/KB is not provided in the input data and should be taken from that advisory. Because exploitation requires authenticated local access, compensating controls until patching completes include restricting and monitoring interactive and remote-interactive logon rights to trusted administrators, enforcing least privilege to reduce the pool of low-privileged accounts that satisfy PR:L, and prioritizing patch deployment on multi-user and shared servers (Server 2022/2025, Server Core) where more principals can reach the local attack surface. No component-disable workaround is documented for CryptoAPI, and disabling cryptographic services is not viable as it would break certificate and signature validation across the OS, so patching is the only reliable fix.