CVE-2026-21580

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (43rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-62205 (ENISA EUVD) · GHSA-88w8-m3v4-74h6 (GitHub Security Advisories)Source: ENISA EUVD

9.3EG
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.5%CVSS: 9.3Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

This Critical severity Stored XSS, PrivEsc (Privilege Escalation), and Security Misconfiguration vulnerability was introduced in versions 7.1.1, 7.4.0, 7.13.0, 7.17.0, 7.19.0, 8.0.0, 8.5.0, 8.9.0, 9.0.1, 9.1.0, 9.2.0, 9.3.1, 9.4.0, 9.5.1, 10.0.2, 10.1.0 and 10.2.0 of Confluence Data Center and Server. This Stored XSS, PrivEsc (Privilege Escalation), and Security Misconfiguration vulnerability, with a CVSS Score of 8.6, allows an unauthenticated attacker to execute arbitrary HTML or JavaScript code on a victims browser, perform actions as a higher-privileged user, and to get into the system utilizing loopholes exposed from security best-practices being overlooked. Atlassian recommends that Confluence Data Center and Server customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions: Confluence Data Center and Server 9.2: Upgrade to a release greater than or equal to 9.2.21 Confluence Data Center and Server 10.2: Upgrade to a release greater than or equal to 10.2.13 See the release notes ([https://confluence.atlassian.com/doc/confluence-release-notes-327.html]). You can download the latest version of Confluence Data Center and Server from the download center ([https://www.atlassian.com/software/confluence/download-archives]). This vulnerability was reported via our Bug Bounty program.

CVSS v3
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
57
EG Risk 57/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity93% × 45%
Impact severity (EG Severity): CVSS 9.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 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: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
43rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.3): severity, escalated by confirmed exploitation. This CVE's 9.3 is its impact severity (EG Severity), not escalated.

EG Severity
9.3 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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

The CVE record names the fixed release. 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.

The score's inputs: 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

August 18, 2026

Last Modified

November 9, 2026

Advisory Details (2)

Auto-updated Oct 7, 2026
Fix named in the CVE record.
Web page

Security Bulletin - August 18 2026 | Atlassian Support | Atlassian Documentation

https://confluence.atlassian.com/pages/viewpage.action?pageId=1821999768

Vendor Advisories for CVE-2026-21580(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 16× in last 7d / 62× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 472 rows 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-11-13 16:51 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  2. 2026-11-13 01:55 UTCEchelonGraph re-scored
  3. 2026-11-13 01:55 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  4. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  5. 2026-11-12 02:19 UTCEchelonGraph re-scored
  6. 2026-11-12 02:18 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  7. 2026-11-11 16:39 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  8. 2026-11-11 02:42 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  9. 2026-11-10 20:03 UTCEchelonGraph re-scored
  10. 2026-11-10 20:03 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  11. 2026-11-10 16:43 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  12. 2026-11-09 20:27 UTCEchelonGraph re-scored
  13. 2026-11-09 20:27 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  14. 2026-11-09 20:26 UTCNVD updateCVSS v4 → 9.3
  15. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-11-09 05:06 UTCEchelonGraph re-scored
  17. 2026-11-09 05:06 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  18. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  19. 2026-11-08 05:30 UTCEchelonGraph re-scored
  20. 2026-11-08 05:30 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  21. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  22. 2026-11-07 05:53 UTCEchelonGraph re-scored
  23. 2026-11-07 05:53 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  24. 2026-11-06 16:37 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-11-06 06:17 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-11-06 06:17 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  2. 2026-11-05 16:37 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  3. 2026-11-05 06:41 UTCEchelonGraph re-scored
  4. 2026-11-05 06:41 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  5. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  6. 2026-11-04 07:04 UTCEchelonGraph re-scored
  7. 2026-11-04 07:04 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  8. 2026-11-03 16:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  9. 2026-11-03 07:26 UTCEchelonGraph re-scored
  10. 2026-11-03 07:26 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  11. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  12. 2026-11-02 07:49 UTCEchelonGraph re-scored
  13. 2026-11-02 07:49 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  14. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-11-01 08:12 UTCEchelonGraph re-scored
  16. 2026-11-01 08:12 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  17. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  18. 2026-10-31 08:36 UTCEchelonGraph re-scored
  19. 2026-10-31 08:35 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  20. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  21. 2026-10-30 08:59 UTCEchelonGraph re-scored
  22. 2026-10-30 08:59 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  23. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  24. 2026-10-29 09:23 UTCEchelonGraph re-scored
  25. 2026-10-29 09:23 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  26. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  27. 2026-10-28 09:47 UTCEchelonGraph re-scored
  28. 2026-10-28 09:47 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  29. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  30. 2026-10-27 09:19 UTCEchelonGraph re-scored
  31. 2026-10-27 09:19 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  32. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  33. 2026-10-26 09:18 UTCEchelonGraph re-scored
  34. 2026-10-26 09:18 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  35. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  36. 2026-10-25 14:43 UTCEchelonGraph re-scored
  37. 2026-10-25 09:43 UTCEchelonGraph re-scored
  38. 2026-10-25 09:43 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  39. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  40. 2026-10-24 10:07 UTCEchelonGraph re-scored
  41. 2026-10-24 10:06 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  42. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  43. 2026-10-23 10:26 UTCEchelonGraph re-scored
  44. 2026-10-23 10:26 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  45. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  46. 2026-10-22 10:50 UTCEchelonGraph re-scored
  47. 2026-10-22 10:49 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  48. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  49. 2026-10-21 11:10 UTCEchelonGraph re-scored
  50. 2026-10-21 11:10 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  51. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  52. 2026-10-20 11:34 UTCEchelonGraph re-scored
  53. 2026-10-20 11:34 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  54. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  55. 2026-10-19 11:56 UTCEchelonGraph re-scored
  56. 2026-10-19 11:56 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  57. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  58. 2026-10-18 09:59 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  59. 2026-10-18 03:56 UTCEchelonGraph re-scored
  60. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  61. 2026-10-17 07:33 UTCEchelonGraph re-scored
  62. 2026-10-17 07:33 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  63. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  64. 2026-10-16 07:54 UTCEchelonGraph re-scored
  65. 2026-10-16 07:54 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  66. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  67. 2026-10-15 06:55 UTCEchelonGraph re-scored
  68. 2026-10-15 06:55 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  69. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  70. 2026-10-14 02:44 UTCEchelonGraph re-scored
  71. 2026-10-14 02:43 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  72. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  73. 2026-10-12 22:52 UTCEchelonGraph re-scored
  74. 2026-10-12 22:52 UTCGHSA enrichmentGHSA-88w8-m3v4-74h6 · GitHub severity CRITICAL
  75. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile

Frequently asked(5)

What is CVE-2026-21580?
CVE-2026-21580 is a critical-severity vulnerability; its CVE record was published on August 18, 2026. This Critical severity Stored XSS, PrivEsc (Privilege Escalation), and Security Misconfiguration vulnerability was introduced in versions 7.1.1, 7.4.0, 7.13.0, 7.17.0, 7.19.0, 8.0.0, 8.5.0, 8.9.0, 9.0.1, 9.1.0, 9.2.0, 9.3.1, 9.4.0, 9.5.1, 10.0.2, 10.1.0 and 10.2.0 of Confluence Data Center and…
When was the CVE record for CVE-2026-21580 published?
The CVE record for CVE-2026-21580 was published on August 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 9, 2026; the record at its source may have been updated since.
Is CVE-2026-21580 actively exploited?
CVE-2026-21580 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-21580?
CVE-2026-21580 has a CVSS base score of 9.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-21580?
The CVE record for CVE-2026-21580 names the fix: "…Upgrade to a release greater than or equal to 9.2.21". The vendor advisories EchelonGraph has for CVE-2026-21580 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-21580?

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