Quick answers
- Is CVE-2026-119833 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119833 being exploited in the wild.
- How severe is CVE-2026-119833?
- High severity, with a CVSS score of 7, published 10 November 2026.
- Which products and versions are affected?
- Microsoft Windows Message Queuing.
- Is there a fix for CVE-2026-119833?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-119833 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-119833?
- Check whether you run Microsoft Windows Message Queuing. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in Windows Message Queuing and involves dereferencing an untrusted pointer, which can be leveraged by an authenticated local attacker to escalate privileges. The attack requires prior system access or valid credentials but does not require network access. Successful exploitation grants the attacker SYSTEM-level privileges.
Affected products
- Microsoft Windows Message Queuing
Timeline
- 2026-11-10: disclosed