CVE-2026-50695
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) enables an unauthenticated remote attacker to cause denial of service by overflowing a stack buffer, likely through malformed 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.9020< 10.0.19044.7548< 10.0.19045.7548< 10.0.26100.8875< 10.0.26200.8875< 10.0.28000.2269< 10.0.28000.2525all versions= r2CVSS 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 installedCheck if the Active Directory Federation Services role is installed. On Windows Server, run Get-WindowsFeature -Name ADFS-Federation or check Programs and Features for AD FS. On Windows 10/11 client, check Services for 'ADFS' service or look for ADFS-related components in Windows Features.Affected if ADFS role or component is present on the system
-
Confirm ADFS service is runningCheck the status of the AD FS service by running Get-Service -Name ADFS or reviewing services.msc. Also check if the ADFS endpoints are listening on ports 443 or 8080 using netstat -an | findstr ':443' or Test-NetConnection -Port 443.Affected if The ADFS service is running and exposed via network listeners
-
Check Windows version against affected rangesRun winver or systeminfo | findstr /B /C:'OS Name' /C:'OS Version' to determine the exact Windows build number. Compare against: Windows 10 1607 (<10.0.14393.9339), 1809 (<10.0.17763.9020), 21h2 (<10.0.19044.7548), 22h2 (<10.0.19045.7548); Windows 11 24h2 (<10.0.26100.8875), 25h2 (<10.0.26200.8875), 26h1 (<10.0.28000.2269 or <10.0.28000.2525); Windows Server 2012/2012 R2 (all versions).Affected if The installed Windows version is lower than the fixed build numbers for your Windows release
-
Verify ADFS network exposureReview firewall rules and network configuration to determine if ADFS endpoints are accessible from untrusted networks. Check for inbound rules on ports 443 and 8080 in Windows Firewall or external network devices.Affected if ADFS service is reachable from untrusted network segments or the internet
A system is affected if ADFS is installed and running, the Windows version falls below the specified build numbers, and the ADFS service is network-accessible.
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.14393.933910.0.17763.902010.0.19044.7548
Apply Microsoft security updates for ADFS when released; restrict network access to ADFS endpoints to trusted sources until patch is available.
Windows 10 1607: build 10.0.14393.9339 or later; Windows 10 1809: build 10.0.17763.9020 or later; Windows 10 21h2: build 10.0.19044.7548 or later; Windows 10 22h2: build 10.0.19045.7548 or later; Windows 11 24h2: build 10.0.26100.8875 or later; Windows 11 25h2: build 10.0.26200.8875 or later; Window
- 1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
- 2. For Windows 10 systems: Navigate to Settings > Update & Security > Windows Update and check for updates; apply the update that brings the build to the fixed version or later
- 3. For Windows 11 systems: Use Windows Update to install the latest cumulative update containing the fix
- 4. For Windows Server 2012/2012 R2: Since Microsoft no longer supports this version, migrate to a supported Windows Server version (2016, 2019, 2022, or 2025)
- 5. After updating, verify the new build number matches or exceeds the fixed version: winver or systeminfo
- 6. For ADFS servers specifically, restart the ADFS service after the update using 'net stop adfssrv && net start adfssrv'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50695 — 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-50695 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