CVE
Atlassian Bamboo Data Center unauthenticated code execution in CI server
Introduced in Bamboo Data Center 10.2.0, 11.0.0, 12.0.0 and 12.1.0. The vendor's listed fix for the 10.2 line is 10.2.26 or later.
Written by a model from the sources below. Verify against them.
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in 10.2.26
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 10.2.26.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 9/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Atlassian Bamboo Data Center has an improper authorization flaw that lets an unauthenticated attacker gain access to resources or functions they should not reach. The attacker can exploit it from the adjacent network without logging in or any user action, and it could expose sensitive information or possibly lead to arbitrary code execution.
Original description
This High severity Improper Authorization vulnerability was introduced in versions 10.2.0, 11.0.0, 12.0.0, and 12.1.0 of Bamboo Data Center.
This Improper Authorization vulnerability, with a CVSS Score of 7.6, allows an unauthenticated attacker to gain unintended access and can lead to the exposure of resources or functionality, possibly providing attackers with sensitive information or even execute arbitrary code.
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 10.2: Upgrade to a release greater than or equal to 10.2.26
Bamboo Data Center 12.1: Upgrade to a release greater than or equal to 12.1.13
Bamboo Data Center 13.0: Upgrade to a release greater than or equal to 13.0.1
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 Penetration Testing program.
Who should check
Teams running Atlassian Bamboo Data Center versions 10.2.0 through 10.2.24, 11.0.x, 12.0.x, or 12.1.x, prior to the fixed releases.
“This High severity Improper Authorization vulnerability was introduced in versions 10.2.0, 11.0.0, 12.0.0, and 12.1.0 of Bamboo Data Center.”
cve.now Index
- Exploitation0/40No signal
- Exposure?/25Unknown. Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.6/10CVSS 7.6, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 10.2.26.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-21595 (This High severity Improper Authorization vulnerability was introduced in versions 10.2.0, 11.0.0, 12.0.0, and 12.1.0 of Bamboo Data Center.), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-21595 (entry last updated 2026-11-17):
Affected:
- Atlassian Bamboo Data Center: versions 12.1.0 to 12.1.12, 12.0.0 to 12.0.2, 11.0.0 to 11.0.8, 10.2.0 to 10.2.24
Fixed versions: 10.2.26.
Conditions (all must be true for the bug to be hit):
- Bamboo Data Center versions 10.2.0, 11.0.0, 12.0.0, and 12.1.0 (the vulnerability was introduced in these versions). (source: https://jira.atlassian.com/browse/BAM-26630)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: adjacent access, no login, no user action.
CISA KEV: CVE-2026-21595 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-21595 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://confluence.atlassian.com/pages/viewpage.action?pageId=1874690748
- https://jira.atlassian.com/browse/BAM-26630
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-21595
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-21595"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Atlassian Bamboo Data Center
12.1.0 to 12.1.12, 12.0.0 to 12.0.2, 11.0.0 to 11.0.8, 10.2.0 to 10.2.24
Evidence 4
Vendor advisory · 2
Establishes: Affected and fixed versions.
- Link
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-21595
Is CVE-2026-21595 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An improper authorization flaw lets an unauthenticated attacker gain unintended access, which can expose resources or functionality, possibly sensitive information, or even allow arbitrary code execution.Source: jira.atlassian.com
Which versions are affected by CVE-2026-21595?
Bamboo Data Center: versions 12.1.0 to 12.1.12, 12.0.0 to 12.0.2, 11.0.0 to 11.0.8, 10.2.0 to 10.2.24.Source: cve.now feed data
Am I affected, and how do I check?
Bamboo Data Center versions 10.2.0, 11.0.0, 12.0.0 and 12.1.0 are where the vulnerability was introduced. Compare your installed Bamboo Data Center version against that list.Source: jira.atlassian.com
How do I fix CVE-2026-21595?
For the 10.2 line, upgrade to 10.2.26 or later, which is the fix named in the advisory. The advisory does not name fixed versions for the 11.0.0, 12.0.0 or 12.1.0 lines.Source: jira.atlassian.com