2026-10-06HIGHexploitedAtlassian's CVE-2026-21589 record, rejected on 16 October, was restored on 19 October; the exploited flaw stands
Atlassian Jira Software Data Center
product · product:atlassian-jira-software-data-center
Coverage
1
first 2026-10-06 → last 2026-10-20
Latest activity
2026-10-17
Atlassian's CVE-2026-21589 record, rejected on 16 October, was restored on 19 October; the exploited flaw…
Peak priority
high
1 high
Targets
technology
sectors: technology
Sources cited
14
13 hosts
Action items (3)
Do-now tasks recorded on the entries about Atlassian Jira Software Data Center, newest first. Check the date before acting on an older one.
- Upgrade every Bitbucket, Confluence, Jira Service Management, Jira Software, Bamboo and Crowd Data Center installation to a fixed version of its line (Bitbucket 9.4.26, 10.2.8 or 10.5.1; Confluence 9.2.26 or 10.2.19; Jira Service Management 5.12.40, 10.3.26 or 11.3.12; Jira Software 9.12.40, 10.3.26 or 11.3.12; Bamboo 10.2.24 or 12.1.12; Crowd 6.3.7, 7.0.3, 7.1.7 or 7.2.4) and Crucible and Fisheye to 4.9.15, internet-reachable instances first; until each is upgraded, take it off the internet or put Atlassian's web application firewall or Tomcat rewrite rule in front of it.2026-10-06CVE-2026-21589
- On every Jira instance that was internet-reachable and unpatched and is integrated with Crowd, treat the Crowd application password in its WEB-INF/classes/crowd.properties as readable: rotate it after the upgrade and review Crowd for user accounts created or group memberships changed since the exposure began; on every affected instance search the web server and proxy logs back to 2026-10-05, the day the advisory published (honeypots recorded the first attempts on 2026-10-06), for '..' next to '/', '\\' or '::'.2026-10-06CVE-2026-21589
- Confirm that every vulnerability scanner, SIEM enrichment rule and ticket keyed on CVE-2026-21589 reports each affected Atlassian instance as open again; where a feed dropped the ID while the record was rejected between 2026-10-16 and 2026-10-19, re-run it so no exploited instance stays reported as closed.2026-10-06CVE-2026-21589
Defender insights
What each entry about Atlassian Jira Software Data Center tells a defender to do, newest first.
Exposure · detection
Story timeline
Hunting pivots
CVEs (exploited first)
Releases covered
Atlassian Jira Software Data Center
ATT&CK techniques (6 across 7 tactics)
6 techniques observed across 1 entry about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.1 · compare on the matrix · Navigator layer (JSON)
- ReconnaissanceActive Scanning: Vulnerability Scanning
- Initial AccessValid Accounts · Exploit Public-Facing Application
- PersistenceValid Accounts · Create Account
- Privilege EscalationValid Accounts
- StealthValid Accounts
- Credential AccessUnsecured Credentials: Credentials In Files
- CollectionData from Local System
Reconnaissance TA0043
T1595.002Active Scanning: Vulnerability Scanning×1
Adversaries may scan victims for vulnerabilities that can be used during targeting. Vulnerability scans typically check if the configuration of a target host/application (ex: software and version) potentially aligns with the target of a specific exploit the adversary may seek to use.
Evidence: 2026-10-06/cve-2026-21589-atlassian-data-center-arbitrary-file-access · ATT&CK page ↗
Initial Access TA0001
T1078Valid Accounts×1
Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.
Evidence: 2026-10-06/cve-2026-21589-atlassian-data-center-arbitrary-file-access · ATT&CK page ↗
T1190Exploit Public-Facing Application×1
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.
Evidence: 2026-10-06/cve-2026-21589-atlassian-data-center-arbitrary-file-access · ATT&CK page ↗
Persistence TA0003
T1078Valid Accounts×1
Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.
Evidence: 2026-10-06/cve-2026-21589-atlassian-data-center-arbitrary-file-access · ATT&CK page ↗
T1136Create Account×1
Adversaries may create an account to maintain access to victim systems. With a sufficient level of access, creating such accounts may be used to establish secondary credentialed access that does not require persistent remote access tools to be deployed on the system.
Evidence: 2026-10-06/cve-2026-21589-atlassian-data-center-arbitrary-file-access · ATT&CK page ↗
Privilege Escalation TA0004
T1078Valid Accounts×1
Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.
Evidence: 2026-10-06/cve-2026-21589-atlassian-data-center-arbitrary-file-access · ATT&CK page ↗
Stealth TA0005
T1078Valid Accounts×1
Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.
Evidence: 2026-10-06/cve-2026-21589-atlassian-data-center-arbitrary-file-access · ATT&CK page ↗
Credential Access TA0006
T1552.001Unsecured Credentials: Credentials In Files×1
Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials. These can be files created by users to store their own credentials, shared credential stores for a group of individuals, configuration files containing passwords for a system or service, or source code/binary files containing embedded passwords.
Evidence: 2026-10-06/cve-2026-21589-atlassian-data-center-arbitrary-file-access · ATT&CK page ↗
Collection TA0009
T1005Data from Local System×1
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
Evidence: 2026-10-06/cve-2026-21589-atlassian-data-center-arbitrary-file-access · ATT&CK page ↗
Entries about Atlassian Jira Software Data Center (1)
Co-occurring entities
Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.
- Atlassian Bamboo Data Center×1
- Atlassian Bitbucket Data Center×1
- Atlassian Confluence Data Center×1
- Atlassian Crowd Data Center×1
- Atlassian Crucible×1
- Atlassian Data Center (Bitbucket, Confluence, Jira Service Management, Jira Software, Bamboo, Crowd, Crucible, Fisheye): unauthenticated arbitrary file access in the web application root, CVSS 4.0 9.3; exploited, CISA KEV; the CVE record was rejected by Atlassian on 2026-10-16 and shows restored in ENISA's database on 2026-10-19 while the advisory and fixes stand×1
- Atlassian Fisheye×1
- Atlassian Jira Service Management Data Center×1
Where this entity is cited
Source distribution
- jira.atlassian.com2 (14%)
- bleepingcomputer.com1 (7%)
- cisa.gov1 (7%)
- confluence.atlassian.com1 (7%)
- cyber.gc.ca1 (7%)
- euvd.enisa.europa.eu1 (7%)
- euvdservices.enisa.europa.eu1 (7%)
- github.com1 (7%)
- other5 (36%)
All cited sources (14)
- bleepingcomputer.comBleepingComputerhttps://www.bleepingcomputer.com/news/security/hackers-exploit-critical-atlassian-flaw-after-public-poc-release/
- cisa.govCISAhttps://www.cisa.gov/news-events/alerts/2026/10/15/cisa-adds-one-known-exploited-vulnerability-catalog
- confluence.atlassian.comAtlassianhttps://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html
- cyber.gc.caCanadian Centre for Cyber Security (AV26-1002, update 1)https://cyber.gc.ca/en/alerts-advisories/atlassian-security-advisory-av26-1002
- euvd.enisa.europa.euENISA EUVDhttps://euvd.enisa.europa.eu/enisa/eu_vulnerability_database/EUVD-2026-92807
- euvdservices.enisa.europa.euENISA EUVDhttps://euvdservices.enisa.europa.eu/api/enisaid?id=EUVD-2026-92807
- github.comwatchTowr Labs (GitHub)https://github.com/watchtowrlabs/watchTowr-vs-Atlassian-CVE-2026-21589
- isc.sans.eduSANS Internet Storm Centerhttps://isc.sans.edu/diary/33406
- jira.atlassian.comAtlassianhttps://jira.atlassian.com/browse/CONFSERVER-104488
- jira.atlassian.comAtlassianhttps://jira.atlassian.com/browse/CWD-6610
- labs.watchtowr.comwatchTowr Labshttps://labs.watchtowr.com/you-wont-hear-about-these-even-in-myths-atlassian-jira-confluence-and-more-pre-auth-arbitrary-file-read-cve-2026-21589/
- previdian.comPrevidianhttps://previdian.com/CVE-2026-21589
- security-hub.ncsc.admin.chNCSC Switzerland (Security Hub advisory)https://security-hub.ncsc.admin.ch/#/posts/13032
- theregister.comThe Registerhttps://www.theregister.com/security/2026/10/06/atlassian-warns-of-critical-file-access-flaw-in-its-datacenter-products/5301284