CVE-2026-119883 json
Data Deduplication Security Feature Bypass Vulnerability
published yesterday modified 16h ago also EUVD-2026-122391
- cvss
- 3.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
Improper authorization in Data Deduplication allows an authorized attacker to bypass a security feature locally.
Patch / fix
- Microsoft Windows Server 2016 10.0.14393.9688
- Microsoft Windows Server 2016 (Server Core installation) 10.0.14393.9688
- Microsoft Windows Server 2019 10.0.17763.9487
- Microsoft Windows Server 2019 (Server Core installation) 10.0.17763.9487
- Microsoft Windows Server 2022 10.0.20348.5870
- Microsoft Windows Server 2025 10.0.26100.33822
- Microsoft Windows Server 2025 (Server Core installation) 10.0.26100.33822
Is CVE-2026-119883 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N/E:U/RL:O/RC:C |
| CNA | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
Affected products
- Microsoft Windows Server 2016
- Microsoft Windows Server 2016 (Server Core installation)
- Microsoft Windows Server 2019
- Microsoft Windows Server 2019 (Server Core installation)
- Microsoft Windows Server 2022
- Microsoft Windows Server 2025
- Microsoft Windows Server 2025 (Server Core installation)
Classification
- Weakness
-
- CWE-862 Missing Authorization
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2026-119883
vendor-advisory, patch
Sources
- CVE List CVE-2026-119883
- NVD CVE-2026-119883
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.