dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-26228

HIGH · 7.8 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 10.0.10240.20596 / 10.0.14393.6897 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Windows Cryptographic Services Security Feature Bypass Vulnerability

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a Windows cryptographic services security feature bypass vulnerability with a CVSS 7.8. The vulnerability allows attackers to circumvent security mechanisms in Windows cryptographic services, potentially enabling further exploitation. The exact method of bypass is not specified in the available description.

MitigationApply the Microsoft security update for CVE-2024-26228 via Windows Update or Microsoft Update catalog to remediate the cryptographic services security feature bypass.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:< 10.0.10240.20596
Windows 10 1607Operating system
Affected:< 10.0.14393.6897
Windows 10 1809Operating system
Affected:< 10.0.17763.5696
Windows 10 21h2Operating system
Affected:< 10.0.19044.4291
Windows 10 22h2Operating system
Affected:< 10.0.19045.4291
Windows 11 21h2Operating system
Affected:< 10.0.22000.2899
Windows 11 22h2Operating system
Affected:< 10.0.22621.3447
Windows 11 23h2Operating system
Affected:< 10.0.22631.3447

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows version and build number
    Open Command Prompt and run: winver OR run: systeminfo | findstr /B /C:"OS Name" /C:"OS Version"
    Affected if The displayed version and build number is lower than the affected version ranges listed for your Windows edition
  2. Obtain exact OS build number
    Run: reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuildNumber and reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v UBR
    Affected if The combined build number (CurrentBuild.UBR) is below the vulnerable thresholds for your Windows 10 or 11 release
  3. Confirm Windows 10 release version
    Run: reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v ReleaseId to identify if you are on 1507, 1607, 1809, 21h2, or 22h2
    Affected if The release ID matches an affected version with a build number below the corresponding threshold
  4. Confirm Windows 11 release version
    Run: reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v DisplayVersion to identify if you are on 21h2, 22h2, or 23h2
    Affected if The display version matches an affected version with a build number below the corresponding threshold
  5. Verify cryptographic services component
    Check that the Windows Cryptographic Services are present and functional by reviewing: sc query cryptsvc
    Affected if Cryptographic services are running and the OS version is below the patched build numbers

You are affected if your Windows 10 or Windows 11 build number is lower than the minimum version listed for your specific release (10.0.10240.20596 for 1507, 10.0.14393.6897 for 1607, 10.0.17763.5696 for 1809, 10.0.19044.4291 for 21h2, 10.0.19045.4291 for 22h2, 10.0.22000.2899 for 11 21h2, 10.0.22621.3447 for 11 22h2, or 10.0.22631.3447 for 11 23h2).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.20596 / 10.0.14393.6897 / 10.0.17763.5696 or later
Fixed in 10.0.10240.2059610.0.14393.689710.0.17763.5696
Interim mitigation

Apply the Microsoft security update for CVE-2024-26228 via Windows Update or Microsoft Update catalog to remediate the cryptographic services security feature bypass.

Recommended fix High confidence

Install the corresponding Microsoft security update for CVE-2024-26228 (April 2024 security update)

  1. Identify the current Windows version by running 'winver' or checking System Information
  2. Determine if the current build number is below the fixed version for your Windows release
  3. For Windows 10 1507: Upgrade to build 10.0.10240.20596 or later
  4. For Windows 10 1607: Upgrade to build 10.0.14393.6897 or later
  5. For Windows 10 1809: Upgrade to build 10.0.17763.5696 or later
  6. For Windows 10 21h2: Upgrade to build 10.0.19044.4291 or later
  7. For Windows 10 22h2: Upgrade to build 10.0.19045.4291 or later
  8. For Windows 11 21h2: Upgrade to build 10.0.22000.2899 or later
Caveat Standard Windows security update with no expected breaking changes; as a cryptographic services patch, it may affect certificate validation or crypto operations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,872.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-26228 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-26228 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data