Quick answers
- Is CVE-2026-42991 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-42991 being exploited in the wild.
- How severe is CVE-2026-42991?
- High severity, with a CVSS score of 7.8, published 9 June 2026.
- Which products and versions are affected?
- Microsoft Windows Push Notifications.
- Is there a fix for CVE-2026-42991?
- 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-42991 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-42991?
- Check whether you run Microsoft Windows Push Notifications. 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
A race condition (CWE-362) exists in the Windows Push Notifications service due to improper synchronization when accessing shared resources. This flaw can lead to a use-after-free (CWE-416) scenario, which an attacker can leverage to execute code with elevated privileges. The attack requires local access and is characterized by high complexity, as the attacker must successfully time the concurrent execution to trigger the synchronization error. If successful, the attacker can bypass security boundaries and gain SYSTEM-level access.
Affected products
- Microsoft Windows Push Notifications
Timeline
- 2026-06-09: disclosed
- 2026-06-09: advisory