CVE-2026-41103

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-12. The CNA's CVSS baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 4 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Incorrect implementation of authentication algorithm in Microsoft SSO Plugin for Jira & Confluence allows an unauthorized attacker to elevate privileges over a network.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/100

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 (value × EchelonGraph’s weight)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation0.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
55th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 12, 2026

Last Modified

August 10, 2026

Advisory Details (1)

Auto-updated Sep 16, 2026
Patch available. Sources: microsoft.
MicrosoftMentions a patch (unverified)

Security Update Guide - Microsoft Security Response Center

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

Vendor Advisories for CVE-2026-41103(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 13× in last 7d / 27× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 472 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 372 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-41103?
CVE-2026-41103 is a critical-severity vulnerability; its CVE record was published on May 12, 2026. Incorrect implementation of authentication algorithm in Microsoft SSO Plugin for Jira & Confluence allows an unauthorized attacker to elevate privileges over a network.
When was CVE-2026-41103 made public?
CVE-2026-41103 was made public on May 12, 2026: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on May 12, 2026. EchelonGraph's copy of the record carries a last-modified date of August 10, 2026; the record at its source may have been updated since.
Is CVE-2026-41103 actively exploited?
CVE-2026-41103 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-41103?
CVE-2026-41103 has a CVSS base score of 9.1 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-41103?
A fix for CVE-2026-41103 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-41103 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-41103?

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

Book a Demo →Browse All CVEs