CVE-2026-41095
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 · uneditedUse after free in Data Deduplication allows an authorized attacker to elevate privileges locally.
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 use-after-free vulnerability exists in the Data Deduplication feature (likely Windows Server) that allows an authenticated local attacker to execute arbitrary code with elevated privileges. The vulnerability involves improper memory management where memory is accessed after it has been freed, potentially leading to arbitrary code execution.
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= r2< 10.0.14393.9140< 10.0.17763.8755< 10.0.20348.5074< 10.0.25398.2330< 10.0.26100.32772CVSS 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
- 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? 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.
-
Confirm Data Deduplication feature is installedRun PowerShell command: Get-WindowsOptionalFeature -Online -FeatureName *Dedup* | Select-Object FeatureName, StateAffected if The FeatureName shows DataDeduplication and State is Enabled
-
Check Windows Server version and build numberRun PowerShell command: $os = Get-CimInstance Win32_OperatingSystem; Write-Output "Version: $($os.Version)" ; Write-Output "Build: $($os.BuildNumber)"Affected if The version or build number falls within the affected ranges: Server 2016 < 14393.9140, Server 2019 < 17763.8755, Server 2022 < 20348.5074, Server 2022 23h2 < 25398.2330, Server 2025 < 26100.32772, or is Server 2012 R2
-
Verify Data Deduplication service exists and check its stateRun PowerShell command: Get-Service -Name Ddpsvc -ErrorAction SilentlyContinue | Select-Object Name, Status, StartTypeAffected if The service Ddpsvc exists and is running (vulnerable attack surface requires the feature to be enabled)
-
Confirm deduplication volume configurationRun PowerShell command: Get-DedupVolume -ErrorAction SilentlyContinue | Select-Object Volume, Enabled, DeduplicationRateAffected if Any volume shows Enabled equals True (indicates deduplication is actively processing data and the vulnerable code path is in use)
The environment is affected if Data Deduplication is enabled on a Windows Server version that is older than the fixed build numbers listed, or if running Windows Server 2012 R2.
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.914010.0.17763.875510.0.20348.5074
Apply the relevant Microsoft security patch for Data Deduplication when released. Until then, limit local administrative access and monitor for suspicious processes.
Windows Server 2016 to build 10.0.14393.9140+ | Windows Server 2019 to build 10.0.17763.8755+ | Windows Server 2022 to build 10.0.20348.5074+ | Windows Server 2022 23h2 to build 10.0.25398.2330+ | Windows Server 2025 to build 10.0.26100.32772+
- Identify the Windows Server version currently installed by running 'winver' or 'systeminfo' in Command Prompt
- Determine which Data Deduplication update is required for your Windows Server version from Microsoft Security Response Center (msrc.microsoft.com)
- For Windows Server 2016: Apply update to reach build 10.0.14393.9140 or later
- For Windows Server 2019: Apply update to reach build 10.0.17763.8755 or later
- For Windows Server 2022: Apply update to reach build 10.0.20348.5074 or later
- For Windows Server 2022 23h2: Apply update to reach build 10.0.25398.2330 or later
- For Windows Server 2025: Apply update to reach build 10.0.26100.32772 or later
- Verify successful patching by checking the build version again after updates are applied
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-41095 — 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-41095 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