CVE-2026-50302
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 · uneditedImproper certificate validation in Windows Cryptographic Services allows an unauthorized attacker to bypass a security feature over a network.
In the news
Third-party coverage- Microsoft July 2026 Patch Tuesday fixes massive 570 flaws, 3 zero-days
- Microsoft CVE Summary - Bleeping Computer
Surfaced from public web coverage — external links open in a new tab.
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 confidenceThis vulnerability in Windows Cryptographic Services involves improper certificate validation that allows an unauthenticated remote attacker to bypass a security feature over a network. The flaw likely permits acceptance of invalid or maliciously crafted certificates, potentially enabling man-in-the-middle attacks or authentication 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< 10.0.19044.7548< 10.0.19045.7548< 10.0.26100.8875< 10.0.26200.8875< 10.0.28000.2269< 10.0.28000.2525< 10.0.20348.5386< 10.0.26100.33158CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows build versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the full build numberAffected if The build number is lower than the affected version thresholds for your Windows edition (10.0.19044.7548 for 21h2, 10.0.19045.7548 for 22h2, 10.0.26100.8875 for 11 24h2, 10.0.26200.8875 for 11 25h2, 10.0.28000.2269/2525 for 11 26h1, 10.0.20348.5386 for Server 2022, 10.0.26100.33158 for Server 2025)
-
Verify Cryptographic Services statusOpen Services (services.msc) and check that 'Cryptographic Services' is running, or run 'Get-Service CryptographicService' in PowerShellAffected if The service is running and the build version is below the affected thresholds
-
Review certificate validation event logsOpen Event Viewer, navigate to Application and Services Logs > Microsoft > Windows > CertificateServices-Deployment and check for validation failure events or warnings related to certificate chain validationAffected if Events indicate certificate validation failures or bypass attempts are being logged
-
Inspect auto-update root certificates configurationRun 'certutil -verifystore Root' and examine if the configuration allows third-party root certificates without proper validation, or check registry at HKLM\SOFTWARE\Microsoft\SystemCertificates for certificate chain policy settingsAffected if Certificate chain validation policy is set to allow invalid certificates or is disabled
A system is affected if it runs any of the listed Windows versions below the specified build thresholds and utilizes certificate validation for network authentication.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.19044.754810.0.19045.754810.0.20348.5386
Apply Microsoft security updates for Windows Cryptographic Services when available; verify that certificate chain validation is properly enforced for all trusted connections.
Windows 10 21h2: 10.0.19044.7548 | Windows 10 22h2: 10.0.19045.7548 | Windows 11 24h2: 10.0.26100.8875 | Windows 11 25h2: 10.0.26200.8875 | Windows 11 26h1: 10.0.28000.2525 | Windows Server 2022: 10.0.20348.5386 | Windows Server 2025: 10.0.26100.33158
- Identify the current Windows version by running 'winver' or 'systeminfo'
- Determine which affected version family applies to your system (e.g., Windows 10 22h2, Windows 11 24h2, Windows Server 2022, etc.)
- Apply the appropriate Windows update that corresponds to the fixed version number for your product: Windows 10 21h2: upgrade to 10.0.19044.7548 or later; Windows 10 22h2: upgrade to 10.0.19045.7548 or later; Windows 11 24h2: upgrade to 10.0.26100.8875 or later; Windows 11 25h2: upgrade to 10.0.26200.8875 or later; Windows 11 26h1: upgrade to 10.0.28000.2525 or later; Windows Server 2022: upgrade t
- Install the update via Windows Update, WSUS, or by downloading the specific KB from the Microsoft Update Catalog
- Restart the system as required by the update
- Verify the installed version matches or exceeds the fixed version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50302 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-50302 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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