CVE.org (no NVD analysis yet)· CNA microsoft

CVE-2026-119905: Windows DNS Spoofing Vulnerability

Noroxi assessment

Priority: Monitor (action score 19/100)

Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org

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

MediumCVSS 4.9 · v3.1—Proof of concept No fix recorded

Path traversal

EUVD-2026-122404

Published: Nov 10, 2026
Updated: Nov 10, 2026
EPSS: —
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 19 / 40 · 4.9 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · —

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 4.9
CNA · microsoft: 4.9; agree

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Using windows server 2016? Add it to your stack and be the first to know about CVEs like this one. (Windows Server, Active Directory)

Versions reported by the vendor

Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.

Microsoft Windows Server 2016
- 10.0.14393.0 and later · before 10.0.14393.9688affected
Microsoft Windows Server 2016 (Server Core installation)
- 10.0.14393.0 and later · before 10.0.14393.9688affected
Microsoft Windows Server 2019
- 10.0.17763.0 and later · before 10.0.17763.9487affected
Microsoft Windows Server 2019 (Server Core installation)
- 10.0.17763.0 and later · before 10.0.17763.9487affected
Microsoft Windows Server 2022
- 10.0.20348.0 and later · before 10.0.20348.5870affected
Microsoft Windows Server 2025
- 10.0.26100.0 and later · before 10.0.26100.33822affected
Microsoft Windows Server 2025 (Server Core installation)
- 10.0.26100.0 and later · before 10.0.26100.33822affected

Same product

microsoft: all records

Other highest-scoring records for the same primary product.

CVE-2024-38076Windows Remote Desktop Licensing Service Remote Code Execution Vulnerability
40Plan
CVE-2021-34458Windows Kernel Remote Code Execution Vulnerability
40Plan
CVE-2026-88243Windows DHCP Server Remote Code Execution Vulnerability
39Monitor

Published before and after this one in the same product

← EarlierCVE-2026-119883Nov 10, 2026 · Data Deduplication Security Feature Bypass Vulnerability
13Monitor
← EarlierCVE-2026-119890Nov 10, 2026 · Windows DHCP Server Denial of Service Vulnerability
21Monitor
Later →CVE-2026-119951Nov 10, 2026 · Windows Deployment Services Remote Code Execution Vulnerability
32Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Proof-of-concept repository on GitHub	stars:0	2026-08-22

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

First PoCAug 22, 2026-81 d
PublishedNov 10, 2026
TodayNov 11, 2026same day

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
Administrator privileges are required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: High
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

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

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Exploit maturitynone → pocNov 11, 2026, 3:38 AM UTC
SSVC exploitation— → noneNov 10, 2026, 9:07 PM UTC
Exploit maturity— → noneNov 10, 2026, 8:07 PM UTC

For records you follow, these changes also arrive as notifications. →

References

msrc.microsoft.com/update-guide/vulnerability/CVE-2026-119905

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records