CVE-2026-21589

CRITICALNVD 7.59.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-10-15), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.5 retained for reference. The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 7.5 HIGH under GitHub Security Advisory CVSS. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Exploited in the wild

Also known asEUVD-2026-92807 (ENISA EUVD) · GHSA-gr66-x5pq-8g2g (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictMitigate nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 91%CVSS: 7.5Exploit: Metasploit · other public PoCExposed services: Not assessed

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

This is a vulnerability in Bitbucket Data Center, Confluence Data Center, Jira Service Management Data Center, Jira Software Data Center, Bamboo Data Center. Crowd Data Center, Crucible and Fisheye. This Arbitrary File Access vulnerability allows an unauthenticated attacker to access specific files within the web application root directory in affected versions. Exploitation requires prior knowledge of the target file's exact name and path; this vulnerability does not allow attackers to enumerate or list directory contents. In some configurations, there may be some sensitive files that make this highly severe. This vulnerability allows an unauthenticated remote attacker to access specific files within the web application root directory in affected versions. The vulnerability must be addressed for affected versions of: -- Bitbucket Data Center, introduced in version >= 4.6.0, fix versions: 9.4.26, 10.2.8, 10.5.1 -- Confluence Data Center, introduced in version >= 5.10.0, fix versions 9.2.26, 10.2.19 -- Crowd Data Center, introduced in version >= 2.11.0, fix versions 6.3.7, 7.0.3, 7.1.7, 7.2.4 -- Jira Software Data Center, introduced in version >= 7.1.0, fix versions 9.12.40, 10.3.26, 11.3.12 -- Jira Service Management Data Center, introduced in version >= 3.1.0, fix versions 5.12.40, 10.3.26, 11.3.12 -- Bamboo Data Center >= 7.0.1, fix versions 10.2.24, 12.1.12 -- Crucible, fix versions 4.9.15 -- Fisheye, fix version 4.9.15 -- Exploitation requires prior knowledge of the target file's exact name and path. The vulnerability does not include the capability to enumerate or list directory contents.

CVSS v3
7.5
EG Score
9.0CRITICALhigh confidence
EG Risk
74
EG Risk 74/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (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: No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
91%
EPSS %ILE
99th
KEV
⚠ Exploited

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.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 7.5 HIGH.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
91% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: this CVE is in CISA's KEV catalog, and CISA's required action for it, quoted below, applies whether or not a fix is released.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, Attend at medium and Act at high mission impact.

No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (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 & forensic triage if the affected system is publicly exposed; 14 days if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: this CVE is in CISA's KEV catalog, and CISA's required action for it, quoted below, applies whether or not a fix is released.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable no (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

CISA required action“Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html?ref=labs.watchtowr.com · https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk · https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk · https://nvd.nist.gov/vuln/detail/CVE-2026-21589

Published

October 5, 2026

Last Modified

October 29, 2026

Advisory Details (10)

Auto-updated Nov 13, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). No fix on record yet. Sources: cisa.
CISA🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-21589
Web page

GitHub - watchtowrlabs/watchTowr-vs-Atlassian-CVE-2026-21589 · GitHub

https://github.com/watchtowrlabs/watchTowr-vs-Atlassian-CVE-2026-21589

Vendor and National Authority Advisories for CVE-2026-21589(2)

These vendors and national cybersecurity authorities published their own advisory mentioning this CVE — often with remediation steps + affected product lists not in NVD. An authority's is an excerpt, in the language it published it in, not translated, and credited to it with a link.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 39× 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 169 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 69 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-22 14:42 UTCEchelonGraph re-scored
  2. 2026-11-22 14:42 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  3. 2026-11-21 15:34 UTCEchelonGraph re-scored
  4. 2026-11-21 15:34 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  5. 2026-11-20 16:37 UTCEPSS rescoreEPSS 91% · 99th percentile
  6. 2026-11-20 16:27 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  7. 2026-11-19 22:26 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  8. 2026-11-19 17:17 UTCEchelonGraph re-scored
  9. 2026-11-19 17:17 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  10. 2026-11-18 18:09 UTCEchelonGraph re-scored
  11. 2026-11-18 18:09 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  12. 2026-11-17 19:00 UTCEchelonGraph re-scored
  13. 2026-11-17 19:00 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  14. 2026-11-16 19:52 UTCEchelonGraph re-scored
  15. 2026-11-16 19:51 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  16. 2026-11-15 20:42 UTCEchelonGraph re-scored
  17. 2026-11-15 20:42 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  18. 2026-11-14 21:33 UTCEchelonGraph re-scored
  19. 2026-11-14 21:33 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  20. 2026-11-13 22:25 UTCEchelonGraph re-scored
  21. 2026-11-13 22:25 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  22. 2026-11-13 16:51 UTCEPSS rescoreEPSS 99.7% · 99th percentile
  23. 2026-11-12 23:15 UTCEchelonGraph re-scored
  24. 2026-11-12 23:15 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  25. 2026-11-12 00:07 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-11-12 00:06 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  2. 2026-11-11 00:57 UTCEchelonGraph re-scored
  3. 2026-11-11 00:57 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  4. 2026-11-10 01:49 UTCEchelonGraph re-scored
  5. 2026-11-10 01:49 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  6. 2026-11-09 02:41 UTCEchelonGraph re-scored
  7. 2026-11-09 02:41 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  8. 2026-11-09 02:34 UTCEchelonGraph re-scoredAssessed: 9.0 CRITICAL
  9. 2026-11-09 02:34 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  10. 2026-11-08 21:42 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  11. 2026-11-07 22:34 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  12. 2026-11-06 23:26 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  13. 2026-11-06 00:17 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  14. 2026-11-05 01:09 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  15. 2026-11-04 16:35 UTCEPSS rescoreEPSS 99.7% · 99th percentile
  16. 2026-11-04 01:59 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  17. 2026-11-03 02:50 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  18. 2026-11-02 03:41 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  19. 2026-11-01 04:33 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  20. 2026-10-31 05:24 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  21. 2026-10-30 06:16 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  22. 2026-10-29 07:08 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  23. 2026-10-28 08:00 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  24. 2026-10-27 08:50 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  25. 2026-10-26 09:43 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  26. 2026-10-25 16:32 UTCEPSS rescoreEPSS 99% · 99th percentile
  27. 2026-10-25 14:43 UTCEchelonGraph re-scored
  28. 2026-10-25 10:35 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  29. 2026-10-24 16:32 UTCEPSS rescoreEPSS 13% · 96th percentile
  30. 2026-10-24 11:26 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  31. 2026-10-23 16:31 UTCEPSS rescoreEPSS 13% · 96th percentile
  32. 2026-10-23 12:16 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  33. 2026-10-22 16:34 UTCEPSS rescoreEPSS 13% · 96th percentile
  34. 2026-10-22 13:05 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  35. 2026-10-21 16:32 UTCEPSS rescoreEPSS 13% · 96th percentile
  36. 2026-10-21 13:54 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  37. 2026-10-20 16:32 UTCEPSS rescoreEPSS 13% · 96th percentile
  38. 2026-10-20 14:45 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  39. 2026-10-19 15:36 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  40. 2026-10-18 16:27 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  41. 2026-10-18 12:44 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  42. 2026-10-18 03:56 UTCEchelonGraph re-scored
  43. 2026-10-17 13:35 UTCEchelonGraph re-scored
  44. 2026-10-17 13:35 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  45. 2026-10-16 20:47 UTCEchelonGraph re-scored▼ 9.00
  46. 2026-10-16 16:41 UTCEPSS rescoreEPSS 13% · 96th percentile
  47. 2026-10-16 14:27 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  48. 2026-10-16 04:27 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  49. 2026-10-16 04:09 UTCEchelonGraph re-scored
  50. 2026-10-16 04:08 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL · GitHub CVSS 7.5
  51. 2026-10-15 20:05 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL
  52. 2026-10-15 19:48 UTCEchelonGraph re-scored▼ 0.30
  53. 2026-10-15 19:47 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL
  54. 2026-10-15 19:45 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  55. 2026-10-15 18:28 UTCEchelonGraph re-scored
  56. 2026-10-15 18:27 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL
  57. 2026-10-15 17:55 UTCEchelonGraph re-scored
  58. 2026-10-15 17:55 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL
  59. 2026-10-15 17:34 UTCEchelonGraph re-scored
  60. 2026-10-15 17:34 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL
  61. 2026-10-15 17:30 UTCCISA KEV update
  62. 2026-10-15 16:31 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  63. 2026-10-15 15:27 UTCEchelonGraph re-scored
  64. 2026-10-15 15:26 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL
  65. 2026-10-15 14:23 UTCEchelonGraph re-scored
  66. 2026-10-15 14:23 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL
  67. 2026-10-14 17:29 UTCEchelonGraph re-scored
  68. 2026-10-14 17:29 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL
  69. 2026-10-14 16:34 UTCEchelonGraph re-scored
  70. 2026-10-14 16:34 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL
  71. 2026-10-14 16:32 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  72. 2026-10-14 02:43 UTCEchelonGraph re-scored
  73. 2026-10-14 02:43 UTCGHSA enrichmentGHSA-gr66-x5pq-8g2g · GitHub severity CRITICAL
  74. 2026-10-13 16:33 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  75. 2026-10-12 22:52 UTCEchelonGraph re-scored

Publicly available exploits

(6 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 3 GitHub PoCs), as are 1 Nuclei detection template, 1 GitHub checker repository. A detection template checks whether a system is affected; it is not necessarily exploit code. A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code. No fix is confirmed yet, so defenders should restrict or isolate affected systems accordingly until one is published.

  • Metasploitauxiliary/admin/http/atlassian_data_center_cve_2026_21589✓ verified
    Recorded Nov 20, 2026

    Atlassian Data Center CVE-2026-21589 Arbitrary File Read and Crowd Privilege Escalation

    Open source ↗
  • GitHub checkerynsmroztas/AtlasSniper
    Published Oct 7, 2026

    CVE-2026-21589 detector for Atlassian Data Center webresource traversal. Pre-auth webroot file read confirm for Jira, Confluence and Bitbucket.

    Open source ↗
  • Nucleihttp/cves/2026/CVE-2026-21589.yaml
    Published Oct 7, 2026

    Atlassian Jira/Confluence/Bitbucket - Pre-Auth Arbitrary File Read

    Open source ↗
  • GitHub PoCMarcusProgram/CVE-2026-21589
    Published Oct 6, 2026
    Open source ↗
  • GitHub PoCtc4dy/CVE-2026-21589-PoC-Exploit
    Published Oct 6, 2026

    CVE-2026-21589 - Atlassian Data Center Unauth Arbitrary File Read (CVSS 9.3). Red/Blue Team suite with 2 tools: Full Exploit (path traversal, WEB-INF read, interactive shell, 8 products, mass scan, SOCKS5/Tor, stealth) and SafeChecker (non-intrusive version audit, WAF detection, IoC guidance, JSON/CSV/JSONL reports). Use Ethically, Stay Legal.

    Open source ↗
  • GitHub PoCwatchtowrlabs/watchTowr-vs-Atlassian-CVE-2026-21589
    Published Oct 6, 2026
    Open source ↗

Frequently asked(6)

What is CVE-2026-21589?
CVE-2026-21589 is a critical-severity vulnerability; its CVE record was published on October 5, 2026. This is a vulnerability in Bitbucket Data Center, Confluence Data Center, Jira Service Management Data Center, Jira Software Data Center, Bamboo Data Center. Crowd Data Center, Crucible and Fisheye. This Arbitrary File Access vulnerability allows an unauthenticated attacker to access specific files…
When was the CVE record for CVE-2026-21589 published?
The CVE record for CVE-2026-21589 was published on October 5, 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 October 29, 2026; the record at its source may have been updated since.
Is CVE-2026-21589 actively exploited?
Yes. CISA added CVE-2026-21589 to the Known Exploited Vulnerabilities catalog on October 15, 2026, affecting Atlassian Multiple Products. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation.
What is the CVSS score of CVE-2026-21589?
CVE-2026-21589 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2026-21589?
CVE-2026-21589 affects Atlassian Multiple Products.
How do I remediate CVE-2026-21589?
No fix for CVE-2026-21589 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-21589 are linked in the Vendor and National Authority Advisories panel on this page. NCSC-NL's advisory for CVE-2026-21589 is also listed there, in Dutch, as NCSC-NL published it; not translated.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-21589?

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