Exploited CVEs / Atlassian / CVE-2026-21589

CVE-2026-21589

Atlassian Multiple Products Files or Directories Accessible to External Parties Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2026-10-18 (that deadline has passed); treat that date as the outer bound for your own environment. The fix is in the vendor advisory: Atlassian Security Advisories, linked below.

Our data comes from Microsoft, CISA and other public sources, and it can be wrong or out of date. If you are unsure, check the linked source before you act, and tell us when we are wrong so we can fix it.

Senserva AI read on CVE-2026-21589 CISA required action Official fix for CVE-2026-21589 Admin questions

Risk summary

HighCISA KEV

7.5

CVSS v3 base

9.3

CVSS v4

100%

EPSS exploit probability

High

Severity

2026-10-15

Added to KEV

2026-10-18 (past due)

CISA due date

Actively exploited Atlassian Multiple Products vulnerability, High severity, CVSS v3 7.5 (CVSS v4: 9.3). Added to the CISA KEV catalog 2026-10-15.

Patch now

Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.

The fix ships from the vendor: Atlassian Security Advisories.

Do this now: Federal remediation deadline 2026-10-18; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated October 15, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Senserva AI Opinion for CVE-2026-21589

CVE-2026-21589 is a files or directories accessible to external parties flaw that spans nearly the entire Atlassian Data Center lineup: Bitbucket, Confluence, Jira Service Management, Jira Software, Bamboo, Crowd, Crucible and Fisheye. Severity is High (CVSS 7.5), but the signals that matter are a 100% EPSS exploit probability and confirmed exploitation via the CISA KEV catalog (added 2026-10-15). Because one issue touches the source control, wiki, ticketing, CI and identity tools together, any internet-reachable instance could expose files from several systems at once, and no ransomware use has been reported so far.

Do this: Inventory every Atlassian Data Center product you run, apply the vendor's fixed versions for CVE-2026-21589 starting with internet-facing instances, and review access logs on those hosts for unexpected file requests.

AI-generated from public data, 2026-11-10. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2026-21589

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I run IT security. Facts for CVE-2026-21589, an actively exploited vulnerability (source: https://senserva.com/cve/CVE-2026-21589.html, data from CISA KEV, FIRST.org EPSS, NVD, refreshed daily (early morning US Central)):
- CVE-2026-21589: Atlassian Multiple Products Files or Directories Accessible to External Parties Vulnerability
- Affected: Atlassian Multiple Products
- Severity: High, CVSS v3 7.5, CVSS v4 9.3; EPSS 30-day exploitation probability 100%
- Added to CISA KEV: 2026-10-15; federal remediation due 2026-10-18
- Ransomware-linked: no
- 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 dis...
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) The fastest safe path to remediation. 4) How to check whether my environment is exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Full tracking and change history for CVE-2026-21589

Published: 2026-10-15
Last revised: 2026-10-15
Changes tracked: 6

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Senserva Watchevery change we have recorded for this one

What changed, and when

CISA confirmed active exploitation of CVE-2026-21589 on 2026-10-15, and its EPSS exploit probability moved from 13% to 100% by 2026-10-25.

Drawn by Senserva Vivid from the Senserva change record. Hover any point for its date and value.

2026-10-15 EPSS first scored at 2.8%; added to the CISA KEV catalog by CISA
2026-10-16 EPSS 2.8% to 12.7%
2026-10-18 EPSS 12.7% to 0.0%
2026-10-20 EPSS 0.0% to 12.7%
2026-10-25 EPSS 12.7% to 99.5%
2026-11-04 EPSS 99.5% to 99.7%

Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.

CISA required action

Federal remediation due date: 2026-10-18 (past due).

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.

Official fix for CVE-2026-21589

The authoritative fix and affected-version list are published by the vendor. Find the Multiple Products advisory on Atlassian Security Advisories.

Atlassian Security Advisories CISA KEV entry

Common questions about CVE-2026-21589

Is CVE-2026-21589 actively exploited?

Yes. CVE-2026-21589 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-10-15, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 100%.

What is the CISA deadline and required action for CVE-2026-21589?

CISA set the federal remediation due date at 2026-10-18, which has passed; treat any unremediated system as overdue. The verbatim 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.

What fixes CVE-2026-21589?

The authoritative fix is in the vendor advisory: see Atlassian Security Advisories for the patched Multiple Products versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2026-21589?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-21589's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed daily (early morning US Central).

Scope and sources

More exploited Atlassian CVEs: CVE-2021-26086 CVE-2023-22527 CVE-2023-22518 CVE-2023-22515 CVE-2022-36804 CVE-2022-26138 CVE-2022-26134 CVE-2021-26085
All Atlassian exploited CVEs on one page: Atlassian vulnerabilities actively exploited.
Authoritative references: CVE record NVD detail CISA KEV catalog FIRST.org EPSS

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.