Adjacent-network spoofing via unvalidated packet origin
Published Jul 14, 2026 · Updated Jul 14, 2026
Origin validation error in Windows NAT allows remote attackers to spoof network traffic over an adjacent network without authentication. Microsoft has not disclosed which NAT code path fails to validate packet origin or the precise crafted traffic it accepts. Exploitation requires adjacent-network access and high complexity; successful spoofing can compromise data and service availability across a security boundary.
Summary
What happened
Origin validation error in Windows NAT allows remote attackers to spoof network traffic over an adjacent network without authentication. Microsoft has not disclosed which NAT code path fails to validate packet origin or the precise crafted traffic it accepts. Exploitation requires adjacent-network access and high complexity; successful spoofing can compromise data and service availability across a security boundary.
The record
- CVE
- CVE-2026-56181
- Published
- Jul 14, 2026
- Updated
- Jul 14, 2026
- Vendor
- Microsoft
- Product
- Windows Server 2025 (Server Core installation)
- Classifications
- CWE-346
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 14, 2026CVE publishedPublication date reported by the CVE source.
- Jul 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.0.26100.0 <10.0.26100.33158
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo