Skip to content

WebCritical 9.3In CISA KEVPatch available

CVE-2026-21589

Unauthenticated arbitrary file read in Atlassian Data Center apps.

How scary is it?

updated 29 Oct 2026
  • Yes

    Works without logging in1

    No account and no user action needed (CVSS PR:N, UI:N).

  • Yes

    Reachable over the network1

    Can be attacked remotely (CVSS AV:N).

  • Yes

    Proof-of-concept code is public234

    1 Metasploit module · 13 GitHub proofs of concept · 1 Nuclei template. GitHub proofs of concept are unvetted: some are fake or carry malware. No Exploit-DB entry or Metasploit exploit module on record.

  • Yes

    Attacks seen in the wild5

    CISA lists it as exploited in the wild.

  • Yes

    On CISA's exploited list (since 15 Oct 2026)5

    CISA deadline for US federal agencies: 18 Oct 2026.

Scare-o-meter

Drop everything

Attackers are already on it. Patch now.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: Listed in CISA's Known Exploited Vulnerabilities catalog: it is being used in attacks.5 Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. You run one of these 16 products in an affected versionAtlassian Bamboo Data Center / Atlassian Bamboo Server / Atlassian Bitbucket Data Center (+13 more)

    Atlassian Bamboo Data Center: All other versions

    Atlassian Bamboo Server: All versions

    Atlassian Bitbucket Data Center: All other versions

    Atlassian Bitbucket Server: All versions

    Atlassian Confluence Data Center: All other versions

    Atlassian Confluence Server: All versions

    Atlassian Crowd Data Center: All other versions

    Atlassian Crowd Server: All versions

    And 8 more in the table below.

    As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.

    See the affected products table · Source 1

  2. An attacker can reach it over the network

    CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.

    Source 1

Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.

What to do

  1. Per the vendorUpgrade to a fixed releasePatch version 10.2.4 and later / Patch version 12.1.12 and later / Patch version 10.2.8 and later / Patch version 10.5.1 and later (+12 more)

    Atlassian Bamboo Data Center: Patch version 10.2.4 and later, Patch version 12.1.12 and later

    Atlassian Bitbucket Data Center: Patch version 10.2.8 and later, Patch version 10.5.1 and later, Patch version 9.4.26 and later

    Atlassian Confluence Data Center: Patch version 10.2.19 and later, Patch version 9.2.26 and later

    Atlassian Crowd Data Center: Patch version 7.2.4 and later, Patch version 7.1.1 and later, Patch version 7.0.3 and later, Patch version 6.3.7 and later

    Atlassian Crucible Data Center: Patch version 4.9.15 and later

    Atlassian Crucible Server: Patch version 4.9.15 and later

    Atlassian Fisheye Data Center: Patch version 4.9.15 and later

    Atlassian Fisheye Server: Patch version 4.9.15 and later

    Fixed releases as stated by the vendor in the CVE record.

    See the affected products table · Source 1

  2. CISA required actionApply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing…

    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.

    CISA's required action for this KEV entry, due 18 Oct 2026 for US federal agencies.

    Source 5

  3. Recommendation, AI-writtenUpgrade to Atlassian fixed versions immediately; restrict external access and rotate exposed credentials.

    Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.

Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.

Major vulnerability. Impacts widely deployed Atlassian Data Center products (Jira, Confluence, Bitbucket, Bamboo, Crowd, Crucible, Fisheye); unauthenticated file access can expose secrets and enable further compromise.

CVSS
9.3Criticalscored by the publisher (CNA)
Exploited in the wild
Yes, in CISA KEV since 15 Oct 2026CISA deadline for US federal agencies: 18 Oct 2026unvetted proof-of-concept code on github
EPSS
91.0%chance of exploitation in the next 30 daystop 0.2% of scored CVEsFIRST score of 21 Nov 2026
Fix
Fixed in Patch version 10.2.4 and later, Patch version 12.1.12 and later, Patch version 10.2.8 and laterper the vendor; 13 more listed below
Published
5 Oct 2026analysed here 6 Oct 2026

Do first. Upgrade to a fixed release: Patch version 10.2.4 and later, Patch version 12.1.12 and later, Patch version 10.2.8 and later, Patch version 10.5.1 and later (and 12 more below).

Summary

Impact

Unauthenticated remote read of specific files in the webapp root (exact path required), exposing configs/keys/credentials and enabling data theft or lateral movement.

Triage

Exploitable
At runtime
Attack vector
network
Weakness
Can a WAF block it?
Partly. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
Atlassian Bamboo Data CenterAll other versionsVendor says fixed in: Patch version 10.2.4 and later, Patch version 12.1.12 and later
Atlassian Bamboo ServerAll versionsVendor says fixed in: not stated
Atlassian Bitbucket Data CenterAll other versionsVendor says fixed in: Patch version 10.2.8 and later, Patch version 10.5.1 and later, Patch version 9.4.26 and later
Atlassian Bitbucket ServerAll versionsVendor says fixed in: not stated
Atlassian Confluence Data CenterAll other versionsVendor says fixed in: Patch version 10.2.19 and later, Patch version 9.2.26 and later
Atlassian Confluence ServerAll versionsVendor says fixed in: not stated
Atlassian Crowd Data CenterAll other versionsVendor says fixed in: Patch version 7.2.4 and later, Patch version 7.1.1 and later, Patch version 7.0.3 and later, Patch version 6.3.7 and later
Atlassian Crowd ServerAll versionsVendor says fixed in: not stated
Atlassian Crucible Data CenterAll other versionsVendor says fixed in: Patch version 4.9.15 and later
Atlassian Crucible ServerAll other versionsVendor says fixed in: Patch version 4.9.15 and later
Atlassian Fisheye Data CenterAll other versionsVendor says fixed in: Patch version 4.9.15 and later
Atlassian Fisheye ServerAll other versionsVendor says fixed in: Patch version 4.9.15 and later
Atlassian Jira Service Management Data CenterAll other versionsVendor says fixed in: Patch version 11.3.12 and later, Patch version 10.3.26 and later, Patch version 5.12.40 and later
Atlassian Jira Service Management ServerAll other versionsVendor says fixed in: Patch version 5.12.40 and later
Atlassian Jira Software Data CenterAll other versionsVendor says fixed in: Patch version 11.3.12 and later, Patch version 10.3.26 and later, Patch version 9.12.40 and later
Atlassian Jira Software ServerAll other versionsVendor says fixed in: Patch version 9.12.40 and later

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • Bitbucket Data Center
  • Confluence Data Center
  • Jira Software Data Center
  • Jira Service Management Data Center
  • Bamboo Data Center
  • Crowd Data Center
  • Crucible
  • Fisheye

Fix and mitigation

Action required

Immediate action required

WAF and other mitigations

Can a WAF block it? Partly. Cloudflare publishes WAF a rule written for this CVE. Such rules block the known exploit requests and buy time, but attackers can change the request to get past them, so they do not replace the patch.

Also consider: patch · enable the vendor rule in block mode

Based on WAF vendor rules published for this CVE. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Listed since 15 Oct 2026.
CISA due date
18 Oct 2026, the remediation deadline for US federal agencies
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.
Public exploit code
Unvetted proof-of-concept code on GitHub: 1 Metasploit module · 13 GitHub proofs of concept · 1 Nuclei template
CISA SSVC
exploitation active, automatable no, technical impact totalAssessed by CISA 16 Oct 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 5 Oct 2026Published
  2. 6 Oct 2026First proof-of-concept repository on GitHub (unvetted)same day later
  3. 6 Oct 2026Analysed by vulneraibility.comsame day later
  4. 15 Oct 2026Added to CISA KEV (exploited in the wild)9 days later
  5. 16 Oct 2026CISA SSVC assessment: exploitation active1 day later
  6. 18 Oct 2026CISA remediation due date (US federal agencies)2 days later
  7. 29 Oct 2026CVE record last updated12 days later

Common questions

Is CVE-2026-21589 being exploited?

Yes. CVE-2026-21589 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2026-21589?

CVE-2026-21589 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-21589?

Yes. A fix has been recorded for CVE-2026-21589. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-21589 affect?

CVE-2026-21589 affects Bitbucket Data Center, Confluence Data Center, Jira Software Data Center, Jira Service Management Data Center, and 4 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-21589?

Upgrade to Atlassian fixed versions immediately; restrict external access and rotate exposed credentials.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

10 references in the CVE record, grouped by the tags the record gives them.

Exploits (1)

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

Other links (9)

Show 3 more

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.