LiveActive security incident?Get immediate response
CVE Record

CVE-2026-2636: Denial of Service in Microsoft OS

This vulnerability is caused by a CWE‑159: "Improper Handling of Invalid Use of Special Elements" weakness, which leads to an unrecoverable inconsistency in the CLFS.sys driver. This condition forces a call to the KeBugCheckEx function, allowing an unprivileged user to trigger a system crash. Microsoft silently fixed this vulnerability in the September 2025 cumulative update for Windows 11 2024 LTSC and Windows Server 2025. Windows 25H2 (released in September) was released with the patch. Windows 1123h2 and earlier versions remain vulnerable.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-2636 lets a low-privileged local Windows user crash the system. The business impact is availability disruption, not data theft or remote takeover based on current sources. It matters most on shared workstations, kiosks, terminal servers, and systems where untrusted users can log in locally.

Executive priority

Treat as a targeted availability risk. It is not described as remote code execution, but local users can crash affected systems. Prioritize patch verification on shared, business-critical, and hard-to-recover Windows assets.

Technical view

The issue is an improper handling weakness in CLFS.sys that can create an unrecoverable inconsistency and force KeBugCheckEx, causing a Windows bugcheck. CVSS is 5.5: local attack vector, low privileges required, no user interaction, high availability impact, and no confidentiality or integrity impact reported.

Likely exposure

Sources state Microsoft fixed this in the September 2025 cumulative update for Windows 11 2024 LTSC and Windows Server 2025. Windows 25H2 shipped with the fix. Windows 11 23H2 and earlier are reported as remaining vulnerable. The supplied affected-version metadata is incomplete, so confirm applicability against vendor and fleet data.

Exploitation context

No active exploitation is reported in the supplied sources, and the CVE is not marked KEV. Exploitation requires local access with low privileges. The practical risk is intentional system crashing by a user or malware already able to run locally.

Researcher notes

Evidence points to a CLFS.sys denial-of-service condition fixed silently for some Windows releases. Public source detail is limited, and Microsoft-specific affected-version data is not fully represented in the supplied CVE metadata. Avoid assuming broader fixes or exploitation beyond the cited advisory.

Mitigation direction

  • Apply the relevant September 2025 or later cumulative update where available.
  • Prioritize shared or multi-user Windows systems first.
  • Confirm whether Windows 11 23H2 and earlier have vendor guidance or upgrade paths.
  • Limit local interactive access to trusted users where patching is delayed.
  • Monitor Microsoft and Fortra advisories for updated affected-version details.

Validation and detection

  • Inventory Windows version and build across endpoints and servers.
  • Confirm Windows 11 2024 LTSC and Server 2025 have September 2025 or later updates.
  • Identify Windows 11 23H2 and earlier systems for risk review.
  • Check vulnerability scanner logic against the Fortra advisory and CVE record.
  • Review crash telemetry for unexpected CLFS.sys bugchecks.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-159: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-2636 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2026-2636Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftWindows OS0, 0affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-159 · source CWE mapping

Improper Handling of Invalid Use of Special Elements

Improper Handling of Invalid Use of Special Elements represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.