CVE-2026-41105

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

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

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

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

Server-side request forgery (ssrf) in Azure Notification Service allows an authorized attacker to elevate privileges over a network.

CVSS v3
8.1
EG Score
8.1(medium)
EPSS
53.2%
KEV
Not listed

Published

May 7, 2026

Last Modified

June 19, 2026

Advisory Details (1)

Auto-updated May 7, 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-41105

Vendor Advisories for CVE-2026-41105(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 52× 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 163 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-41105?
CVE-2026-41105 is a high vulnerability published on May 7, 2026. Server-side request forgery (ssrf) in Azure Notification Service allows an authorized attacker to elevate privileges over a network.
When was CVE-2026-41105 disclosed?
CVE-2026-41105 was first published in the National Vulnerability Database on May 7, 2026, with the most recent update on June 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41105 actively exploited?
CVE-2026-41105 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 53.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41105?
CVE-2026-41105 has a CVSS v4.0 base score of 8.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-41105?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41105, 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-41105

Explore →

Is Your Infrastructure Affected by CVE-2026-41105?

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

Start Free Scan →Browse All CVEs