BambooApplication · Atlassian
CVE-2026-21570
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThis High severity RCE (Remote Code Execution) vulnerability was introduced in versions 9.6.0, 10.0.0, 10.1.0, 10.2.0, 11.0.0, 11.1.0, 12.0.0, and 12.1.0 of Bamboo Data Center. This RCE (Remote Code Execution) vulnerability, with a CVSS Score of 8.6, allows an authenticated attacker to execute malicious code on the remote system. Atlassian recommends that Bamboo Data Center customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions: Bamboo Data Center 9.6: Upgrade to a release greater than or equal to 9.6.24 Bamboo Data Center 10.2: Upgrade to a release greater than or equal to 10.2.16 Bamboo Data Center 12.1: Upgrade to a release greater than or equal to 12.1.3 See the release notes ([https://confluence.atlassian.com/bambooreleases/bamboo-release-notes-1189793869.html]). You can download the latest version of Bamboo Data Center from the download center ([https://www.atlassian.com/software/bamboo/download-archives]). This vulnerability was reported via our Atlassian (Internal) program.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAn authenticated remote code execution vulnerability in Bamboo Data Center allows attackers with valid credentials to execute arbitrary code on the affected system. The specific attack vector and vulnerable component are not detailed in the available information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
BambooApplication
>= 9.6.1, < 9.6.24>= 10.0.0, < 10.2.16>= 11.0.0, < 12.1.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Bamboo Data Center is deployedCheck if the environment is running Atlassian Bamboo Data Center (the clustered/enterprise variant) rather than Bamboo Server (the single-server variant). This can be verified in the Bamboo administration console under 'General configuration' or by checking the installation directory for Data Center-specific components.Affected if The product is Bamboo Data Center (not Server); the Server variant has different patching timelines.
-
Identify the installed Bamboo Data Center versionLog into Bamboo as an administrator and navigate to 'General configuration' > 'About' to view the exact version number, or run: `java -jar atlassian-bamboo/WEB-INF/lib/bamboo-*.jar --version` from the installation directory.Affected if The displayed version falls within 9.x before 9.6.24, 10.x before 10.2.16, or 12.x before 12.1.3.
-
Compare version against affected rangesCross-reference the identified version with the affected ranges: 9.0.0 through 9.6.23, 10.0.0 through 10.2.15, and 12.0.0 through 12.1.2 are all vulnerable.Affected if The installed version is less than 9.6.24 in the 9.x branch, less than 10.2.16 in the 10.x branch, or less than 12.1.3 in the 12.x branch.
-
Verify authentication is required for exploitationConfirm that this is an authenticated vulnerability requiring valid Bamboo user credentials. Review the 'User management' section to ensure all accounts are expected and authorized.Affected if Any valid Bamboo user account could potentially be leveraged to exploit this RCE if the version is within the affected ranges.
You are affected if Bamboo Data Center is running and the installed version is 9.x before 9.6.24, 10.x before 10.2.16, or 12.x before 12.1.3.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped9.6.2410.2.1612.1.3
Upgrade Bamboo Data Center to version 9.6.24 or higher for the 9.x branch, 10.2.16 or higher for the 10.x branch, or 12.1.3 or higher for the 12.x branch to remediate this RCE vulnerability.
Latest Bamboo Data Center release (minimum: 9.6.24 for 9.6.x, 10.2.16 for 10.x, or 12.1.3 for 12.x)
- 1. Back up your Bamboo Data Center instance and database before upgrading
- 2. Identify your current Bamboo version from the affected list (9.6.0-9.6.x, 10.0.0-10.2.x, or 12.0.0-12.1.x)
- 3. Download the appropriate fixed version from Atlassian's download center: Bamboo 9.6.24 or later, Bamboo 10.2.16 or later, or Bamboo 12.1.3 or later
- 4. Review Atlassian's upgrade documentation and release notes for your target version
- 5. Perform the upgrade following standard Bamboo Data Center upgrade procedures
- 6. Verify the upgrade completed successfully by checking the Bamboo administration console
- 7. Test critical Bamboo functionality to ensure the upgrade did not introduce issues
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Bamboo
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21570 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-21570 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data