Skip to content
Fencer Intel
medium 4.9

CVE-2026-119905 json

Windows DNS Spoofing Vulnerability

published yesterday modified 17h ago also EUVD-2026-122404

cvss
4.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 66%
public exploits
0
none known

Summary

Improper input validation in Windows DNS allows an authorized attacker to perform spoofing over a network.

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-119905 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 Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
yesterday

Exploit prediction

1.12% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C
NVD 3.1 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/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-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

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.