This High severity Security Misconfiguration vulnerability was introduced in versions 10.2.0, 11.0.0, 12.0.0, and 12.1.0 of Bamboo Data Center. This Security Misconfiguration vulnerability, with a CVSS Score of 8.9, allows an authenticated attacker to to get into the system utilizing loopholes exposed from security best-practices being overlooked. 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 Atlassian (Internal) program.
CVE-2026-21600
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 8.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (20th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-127149 (ENISA EUVD) · GHSA-7q92-qv9c-rqq3 (GitHub Security Advisories)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
The CVE record names the fixed release — apply it.
- CVSS
- 8.9
- EG Score
- 8.9HIGHmedium confidence
- EG Risk
- 40EG Risk 40/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity89% × 45%Impact severity (EG Severity): CVSS 8.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.3% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: The CVE record names the fixed release. Apply it within your standard update timelines. - EPSS PROB
- 0.3%
- EPSS %ILE
- 20th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.9): severity, escalated by confirmed exploitation. This CVE's 8.9 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.9 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
- EG Likelihood
- 0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-20). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
The CVE record names the fixed release. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 17, 2026
Last Modified
November 20, 2026
Advisory Details (2)
Auto-updated Nov 17, 2026Security Bulletin - November 17 2026 | Atlassian Support | Atlassian Documentation
https://confluence.atlassian.com/pages/viewpage.action?pageId=1874690748Vendor and National Authority Advisories for CVE-2026-21600(2)
These vendors and national cybersecurity authorities published their own advisory mentioning this CVE — often with remediation steps + affected product lists not in NVD. An authority's is an excerpt, in the language it published it in, not translated, and credited to it with a link.
- NCSC-2026-0496NCSC-NL
Kwetsbaarheden verholpen in Atlassian producten
Source: NCSC-NL · In Dutch, as NCSC-NL published it; not translated. · NCSC-NL's rating: Kans: medium · Schade: high
- GHSA-7q92-qv9c-rqq3GitHub Security AdvisoriesHigh
This High severity Security Misconfiguration vulnerability was introduced in versions 10.2.0, 11...
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-21 16:39 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-11-20 18:10 UTCEchelonGraph re-scored
- 2026-11-20 18:10 UTCGHSA enrichmentGHSA-7q92-qv9c-rqq3 · GitHub severity HIGH
- 2026-11-20 16:37 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-11-20 01:32 UTCEchelonGraph re-scored
- 2026-11-20 01:32 UTCGHSA enrichmentGHSA-7q92-qv9c-rqq3 · GitHub severity HIGH
- 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-11-18 16:34 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-11-17 19:28 UTCEchelonGraph re-scored
- 2026-11-17 19:28 UTCGHSA enrichmentGHSA-7q92-qv9c-rqq3 · GitHub severity HIGH
- 2026-11-17 19:03 UTCENISA EUVD ID recordedEUVD-2026-127149 · Source: ENISA EUVD
- 2026-11-17 18:38 UTCEchelonGraph re-scored
- 2026-11-17 18:38 UTCGHSA enrichmentGHSA-7q92-qv9c-rqq3 · GitHub severity HIGH
- 2026-11-17 18:28 UTCEchelonGraph re-scored
- 2026-11-17 18:03 UTCEchelonGraph re-scoredFirst assessed: 8.9 HIGH
- 2026-11-17 18:02 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-21600?
When was the CVE record for CVE-2026-21600 published?
Is CVE-2026-21600 actively exploited?
What is the CVSS score of CVE-2026-21600?
How do I remediate CVE-2026-21600?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-21600
Is Your Infrastructure Affected by CVE-2026-21600?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.