CVE-2026-119821 · Infrastructure
NO FIX YET
Windows Network Connection Broker does not check authorization properly, so a user who already has an account on the machine can raise their privileges. The sources describe no remote trigger, so the impact is local privilege escalation to a higher-privileged account.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Windows machines where a person or process already has a local account can use this flaw to elevate privileges. The sources do not list affected Windows builds or the fixed update. Machines with no untrusted local users carry lower risk.
Not affected if no-local-untrusted-users
Who cares windows
winver and compare it to the fixed build in Microsoft's advisory for CVE-2026-119821No fix yet, per the sources.
Improper authorization in Windows Network Connection Broker allows an authorized attacker to elevate privileges locally.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.