CVE-2026-50368
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 · uneditedStack-based buffer overflow in Active Directory Federation Services allows an unauthorized attacker to deny service 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 confidenceA stack-based buffer overflow vulnerability in Active Directory Federation Services (ADFS) allows unauthenticated remote attackers to cause a denial of service by sending specially crafted network requests to the ADFS service.
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.14393.9339< 10.0.17763.9020all versions= r2< 10.0.14393.9339< 10.0.17763.9020< 10.0.20348.5386< 10.0.26100.33158= 4.8.1= 4.8= 4.6.2= 4.7= 4.7.1= 4.7.2= 3.5CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify ADFS is installedRun 'Get-Service adfssrv' in PowerShell, or check for the 'ADFS' Windows feature via 'Get-WindowsOptionalFeature -Online | Where-Object {$_.FeatureName -like "*ADFS*"}'Affected if The ADFS service (adfssrv) exists or the ADFS feature is enabled on the system
-
Confirm ADFS service is runningRun 'Get-Service adfssrv' and check the Status column, or use 'Get-Service adfssrv | Select-Object Name, Status, StartType'Affected if The adfssrv service is installed and running (even if disabled, the vulnerable code may still be present)
-
Check Windows version against affected buildsRun 'winver' or execute '[System.Environment]::OSVersion.Version' in PowerShell, or check 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion' in the registry for the Build numberAffected if The Windows build number is less than 14393.9339 (Windows 10 1607/Server 2016), less than 17763.9020 (Windows 10 1809/Server 2019), less than 20348.5386 (Server 2022), or less than 26100.33158 (Server 2025), or if running Windows Server 2012/2012 R2 of any build
-
Check installed .NET Framework versionInspect the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full' (for .NET 4.x) or 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5' (for .NET 3.5), checking the Release value to identify the versionAffected if .NET Framework 4.8.1, 4.8, 4.7.2, 4.7.1, 4.7, 4.6.2, or 3.5 is installed (compare your installed version against these specific versions)
-
Assess ADFS network exposureRun 'Get-NetTCPConnection -LocalPort 443,808 -State Listen' (ADFS typically uses ports 443 and 808) to see if ADFS endpoints are listening, and review firewall rules with 'Get-NetFirewallRule | Where-Object {$_.DisplayName -like "*ADFS*"}'Affected if The ADFS service is listening on accessible network interfaces and exposed to untrusted networks
The system is affected if ADFS is installed, the Windows build or .NET Framework version falls within the affected ranges listed, and ADFS network endpoints are reachable.
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.
From vendor data10.0.14393.933910.0.17763.902010.0.20348.5386
Apply Microsoft security updates for ADFS when released; in the interim, restrict ADFS exposure to untrusted networks and implement network-level filtering to limit attack surface.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50368 — 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-50368 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