CVE-2026-42979

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-09. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Push Notifications allows an authorized attacker to elevate privileges locally.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
8.3%
KEV
Not listed

Published

June 9, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Jun 9, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-42979

Vendor Advisories for CVE-2026-42979(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 103× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 184 total refreshes for this CVE.

  1. 2026-07-24 14:17 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:12 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:24 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 02:29 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-16 23:59 UTCVendor advisory
  11. 2026-07-16 23:59 UTCGHSA enrichment
  12. 2026-07-16 17:03 UTCEPSS rescore
  13. 2026-07-16 08:58 UTCVendor advisory
  14. 2026-07-16 08:58 UTCGHSA enrichment
  15. 2026-07-15 19:57 UTCVendor advisory
  16. 2026-07-15 19:57 UTCGHSA enrichment
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-15 02:04 UTCGHSA enrichment
  19. 2026-07-15 02:00 UTCEPSS rescore
  20. 2026-07-14 12:24 UTCVendor advisory
  21. 2026-07-14 12:24 UTCGHSA enrichment
  22. 2026-07-13 22:30 UTCEPSS rescore
  23. 2026-07-13 20:25 UTCGHSA enrichment
  24. 2026-07-13 06:13 UTCEPSS rescore
  25. 2026-07-13 02:19 UTCVendor advisory
Show 75 more
  1. 2026-07-13 02:19 UTCGHSA enrichment
  2. 2026-07-12 08:01 UTCVendor advisory
  3. 2026-07-12 08:01 UTCGHSA enrichment
  4. 2026-07-12 05:46 UTCEPSS rescore
  5. 2026-07-11 18:55 UTCVendor advisory
  6. 2026-07-11 18:55 UTCGHSA enrichment
  7. 2026-07-11 07:51 UTCVendor advisory
  8. 2026-07-11 07:51 UTCGHSA enrichment
  9. 2026-07-10 19:51 UTCVendor advisory
  10. 2026-07-10 19:51 UTCGHSA enrichment
  11. 2026-07-10 00:00 UTCVendor advisory
  12. 2026-07-10 00:00 UTCGHSA enrichment
  13. 2026-07-09 19:10 UTCEPSS rescore
  14. 2026-07-09 09:40 UTCVendor advisory
  15. 2026-07-09 09:40 UTCGHSA enrichment
  16. 2026-07-08 22:21 UTCVendor advisory
  17. 2026-07-08 22:21 UTCGHSA enrichment
  18. 2026-07-08 15:16 UTCEPSS rescore
  19. 2026-07-08 11:18 UTCVendor advisory
  20. 2026-07-08 11:18 UTCGHSA enrichment
  21. 2026-07-07 23:23 UTCVendor advisory
  22. 2026-07-07 23:23 UTCGHSA enrichment
  23. 2026-07-07 13:46 UTCEPSS rescore
  24. 2026-07-06 16:27 UTCEPSS rescore
  25. 2026-07-06 02:23 UTCEPSS rescore
  26. 2026-07-06 02:23 UTCEPSS rescore
  27. 2026-07-06 00:42 UTCVendor advisory
  28. 2026-07-06 00:42 UTCGHSA enrichment
  29. 2026-07-05 13:35 UTCVendor advisory
  30. 2026-07-05 13:35 UTCGHSA enrichment
  31. 2026-07-05 02:30 UTCEPSS rescore
  32. 2026-07-05 00:40 UTCVendor advisory
  33. 2026-07-05 00:40 UTCGHSA enrichment
  34. 2026-07-04 13:28 UTCVendor advisory
  35. 2026-07-04 13:28 UTCGHSA enrichment
  36. 2026-07-04 06:31 UTCEPSS rescore
  37. 2026-07-03 15:36 UTCVendor advisory
  38. 2026-07-03 15:36 UTCGHSA enrichment
  39. 2026-07-03 01:35 UTCVendor advisory
  40. 2026-07-03 01:34 UTCGHSA enrichment
  41. 2026-07-02 14:25 UTCVendor advisory
  42. 2026-07-02 14:25 UTCGHSA enrichment
  43. 2026-07-02 03:21 UTCVendor advisory
  44. 2026-07-02 03:21 UTCGHSA enrichment
  45. 2026-07-01 16:18 UTCVendor advisory
  46. 2026-07-01 16:18 UTCGHSA enrichment
  47. 2026-07-01 15:06 UTCEPSS rescore
  48. 2026-07-01 05:15 UTCVendor advisory
  49. 2026-07-01 05:15 UTCGHSA enrichment
  50. 2026-06-30 23:22 UTCEPSS rescore
  51. 2026-06-30 17:47 UTCVendor advisory
  52. 2026-06-30 17:47 UTCGHSA enrichment
  53. 2026-06-30 06:07 UTCVendor advisory
  54. 2026-06-30 06:06 UTCGHSA enrichment
  55. 2026-06-29 19:03 UTCVendor advisory
  56. 2026-06-29 19:03 UTCGHSA enrichment
  57. 2026-06-29 14:06 UTCEPSS rescore
  58. 2026-06-29 06:56 UTCVendor advisory
  59. 2026-06-29 06:56 UTCGHSA enrichment
  60. 2026-06-28 19:48 UTCVendor advisory
  61. 2026-06-28 19:48 UTCGHSA enrichment
  62. 2026-06-28 14:07 UTCEPSS rescore
  63. 2026-06-28 08:45 UTCVendor advisory
  64. 2026-06-28 08:45 UTCGHSA enrichment
  65. 2026-06-28 04:56 UTCEPSS rescore
  66. 2026-06-27 21:43 UTCVendor advisory
  67. 2026-06-27 21:43 UTCGHSA enrichment
  68. 2026-06-27 10:40 UTCVendor advisory
  69. 2026-06-27 10:40 UTCGHSA enrichment
  70. 2026-06-27 03:08 UTCEPSS rescore
  71. 2026-06-26 23:37 UTCVendor advisory
  72. 2026-06-26 23:36 UTCGHSA enrichment
  73. 2026-06-26 12:34 UTCVendor advisory
  74. 2026-06-26 12:34 UTCGHSA enrichment
  75. 2026-06-25 19:08 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-42979?
CVE-2026-42979 is a high vulnerability published on June 9, 2026. Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Push Notifications allows an authorized attacker to elevate privileges locally.
When was CVE-2026-42979 disclosed?
CVE-2026-42979 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42979 actively exploited?
CVE-2026-42979 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 8.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-42979?
CVE-2026-42979 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-42979?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42979, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-42979

Explore →

Is Your Infrastructure Affected by CVE-2026-42979?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.