CVE-2026-49176

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this weekElevated
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: Elevated riskExposed: 0

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

Improper privilege management in Windows WalletService allows an authorized attacker to elevate privileges locally.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
51(Track)
EG Risk 51/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%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

July 14, 2026

Last Modified

August 28, 2026

Advisory Details (1)

Auto-updated Jul 14, 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-49176

Vendor Advisories for CVE-2026-49176(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 34× in last 7d / 175× 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 247 total refreshes for this CVE.

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

Publicly available exploits

(2 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoC777erp/CVE-2026-49176_BOF
    First seen Jul 29, 2026

    CVE-2026-49176 WalletService LPE — standalone PoC + Cobalt Strike BOF (SYSTEM command on interactive session)

    Open source ↗
  • GitHub PoCDavidCarliez/CVE-2026-49176_LPE_POC
    First seen Jul 16, 2026

    Local privilege-escalation proof of concept for the Windows WalletService vulnerability fixed in July 2026.

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-49176?
CVE-2026-49176 is a high vulnerability published on July 14, 2026. Improper privilege management in Windows WalletService allows an authorized attacker to elevate privileges locally.
When was CVE-2026-49176 disclosed?
CVE-2026-49176 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49176 actively exploited?
CVE-2026-49176 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 61.2% of all scored CVEs.
What is the CVSS score of CVE-2026-49176?
CVE-2026-49176 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-49176?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49176, 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-49176

Explore →

Is Your Infrastructure Affected by CVE-2026-49176?

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

Start Free Scan →Browse All CVEs