Windows 10 1507Operating system · Microsoft

CVE-2023-36036

HIGH · 7.8 CVSS v3.1 Published 2023-11-14

Fix available

A fix is available. Upgrade to 10.0.10240.20308 / 10.0.14393.6452 or later.

See remediation →

96/100

Remediation priority · Urgent

In the wild Zero-click Patch available

Official description

NVD · unedited

Windows Cloud Files Mini Filter Driver Elevation of Privilege Vulnerability

Technical summary

dbcve analysis · moderate confidence

This is an elevation of privilege vulnerability in the Windows Cloud Files Mini Filter Driver. The vulnerability allows a local attacker to gain elevated privileges on the affected system. The Cloud Files Mini Filter Driver is a kernel-mode component that handles cloud storage file operations.

MitigationApply the Microsoft security update for CVE-2023-36036 via Windows Update or Microsoft Update Catalog. Organizations should prioritize patching affected Windows systems as part of their regular patch management cycle.

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

Affected products & versions

NVD · CPE data

Windows 10 1507Operating system

Affected:< 10.0.10240.20308

Windows 10 1607Operating system

Affected:< 10.0.14393.6452

Windows 10 1809Operating system

Affected:< 10.0.17763.5122

Windows 10 21h2Operating system

Affected:< 10.0.19041.3693

Windows 10 22h2Operating system

Affected:< 10.0.19045.3693

Windows 11 21h2Operating system

Affected:< 10.0.22000.2600

Windows 11 22h2Operating system

Affected:< 10.0.22621.2715

Windows 11 23h2Operating system

Affected:< 10.0.22621.2715

CVSS breakdown

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?

dbcve checks

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

Check Windows build version

Open Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to get the full build number. Alternatively, run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild'

Affected if The displayed build number falls below the fixed version for your Windows release (e.g., < 10.0.10240.20308 for Win10 1507, < 10.0.22621.2715 for Win11 22h2/23h2)
Identify exact Windows release

Run 'winver' to confirm your specific Windows 10 release (1507, 1607, 1809, 21h2, 22h2) or Windows 11 release (21h2, 22h2, 23h2). This determines which vulnerability threshold applies.

Affected if You cannot determine your exact Windows release and build, or your specific release version is listed in the affected products with a vulnerable build number
Locate the Cloud Files Mini Filter Driver

Check if the Cloud Files Mini Filter Driver (cldflt.sys) exists on the system. Search in the Windows\System32\drivers directory or run 'dir /s /b C:\Windows\System32\drivers\cldflt.sys'

Affected if The driver file cldflt.sys exists on the system (the driver is present in all affected Windows versions where the vulnerability applies)
Verify driver is loaded

Open Command Prompt as Administrator and run 'fltmc filters' to list loaded mini-filter drivers, or check 'sc query cldfnt' to see if the Cloud Files filter service is active

Affected if The Cloud Files Mini Filter Driver is shown as loaded or running (fltmc filters output includes cldflt, or the service is in a running state)
Confirm kernel driver version

Right-click the cldflt.sys file in File Explorer, select Properties, then view the Details tab for the File Version. Or run 'powershell (Get-Item "C:\Windows\System32\drivers\cldflt.sys").VersionInfo'

Affected if The driver file version is lower than the patched version corresponding to your Windows build (this requires comparing against Microsoft's published driver version for the security update)

Your environment is affected if you are running any of the listed Windows 10 or Windows 11 versions with a build number below the fixed threshold AND the Cloud Files Mini Filter Driver (cldflt.sys) is present and loaded on your system.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 10.0.10240.20308 / 10.0.14393.6452 / 10.0.17763.5122 or later

Fixed in 10.0.10240.2030810.0.14393.645210.0.17763.5122

Vendor patch msrc.microsoft.com →

Interim mitigation

Apply the Microsoft security update for CVE-2023-36036 via Windows Update or Microsoft Update Catalog. Organizations should prioritize patching affected Windows systems as part of their regular patch management cycle.

Recommended fix High confidence

Open Settings > Update & Security > Windows Update
Click 'Check for updates' to download and install the latest security updates
Ensure the update includes the patch for CVE-2023-36036 (Windows Cloud Files Mini Filter Driver)
Restart the system after updates are installed
Verify the installed Windows version meets or exceeds the fixed build number for your Windows release

Caveat Standard Windows update; minimal risk - updates include security fixes and are routinely applied

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

Fix this in Windows 10 1507 Exploited in the wild — priority engagement

Consultation2.0 h
Implementation4.0 h
Testing3.0 h
Review / QA1.0 h

10.0 hours of engineering $1,750

Get it fixed fast

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2023-36036 — 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

Primary sources

msrc.microsoft.comPatch / commit
msrc.microsoft.comPatchVendor Advisory
www.cisa.govUS Government Resource
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2023-36036?

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.

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

At a glance

Exploited in the wildOn CISA’s known-exploited list · agencies must fix by 2023-12-05

A fix existsUpgrade to 10.0.10240.20308 / 10.0.14393.6452 or later

Severity 7.8 High

Exploit likelihood EPSS, next 30 days 16.7%

Affects: Windows 10 1507

Remediation

Being exploited — close it fast

Fix this in Windows 10 1507 10 hrs · Moderate

Typical engagement from $1,750

Get it fixed fast See the full breakdown ↓

This CVE is on CISA’s actively-exploited list, so the clock is real — a vetted specialist can deliver a reviewed fix for your staging environment quickly.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References