CVE-2023-22516: This High severity RCE (Remote Code Execution) vulnerability was introduced in versions 8.1.0, 8.2.0, 9.0.0, 9

This month

HIGH 8.8UPGRADE

CVE-2023-22516 is a high-severity flaw (CVSS 8.8) affecting bamboo. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

This High severity RCE (Remote Code Execution) vulnerability was introduced in versions 8.1.0, 8.2.0, 9.0.0, 9.1.0, 9.2.0, and 9.3.0 of Bamboo Data Center and Server. This RCE (Remote Code Execution) vulnerability, with a CVSS Score of 8.5, allows an authenticated attacker to execute arbitrary code which has high impact to confidentiality, high impact to integrity, high impact to availability, and requires no user interaction. Atlassian rec

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	1.2% (top 31%)
CISA exploited list	No
Published	2023-11-21
Last modified	2026-06-17

Publisher (CNA): Atlassian · Vendor: atlassian

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2023-11-21 18:15 UTCPublished CVE record published
2026-06-17 05:35 UTCUpdated Record last modified

atlassian bamboo UPGRADE

Affected: >= 8.1.0 and < 9.2.7 · >= 9.3.0 and < 9.3.4

Fixed in: 9.2.7, 9.3.4

Safe to downgrade to: a release before 8.1.0

1. Check installed version

apt-cache policy bamboo || rpm -q bamboo || bamboo --version

2. UPGRADE to 9.2.7 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade bamboo

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade bamboo

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 8.1.0 (Debian / Ubuntu)

apt-cache madison bamboo sudo apt install bamboo=<VERSION_BEFORE_8.1.0> sudo apt-mark hold bamboo

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list bamboo sudo dnf downgrade bamboo-<VERSION_BEFORE_8.1.0> sudo dnf versionlock add bamboo

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2023-22516?

bamboo: upgrade to 9.2.7, 9.3.4. Exact commands for each OS are on this page.

Is CVE-2023-22516 being exploited?

CVE-2023-22516 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2023-22516 affect?

CVE-2023-22516 affects bamboo. Severity is high (CVSS 8.8). This High severity RCE (Remote Code Execution) vulnerability was introduced in versions 8.1.0, 8.2.0, 9.0.0, 9.1.0, 9.2.0, and 9.3.0 of Bamboo Data Center and Server. This RCE (Remote Code Execution) vulnerability, with a CVSS Score of 8

How urgent is CVE-2023-22516?

Priority 48/100. High severity

Related CVEs

CVE-2026-21571 HIGH 8.8 UPGRADE This Critical severity OS Command Injection vulnerability was introduced in versions 9.6.0, 10.0.0, 10.1.0, 10
CVE-2026-21584 HIGH 8.1 UPGRADE This High severity Improper Authorization vulnerability was introduced in versions 10.0.0, 10.1.0, 10.2.0, 11.
CVE-2026-21570 HIGH 8.8 UPGRADE This High severity RCE (Remote Code Execution) vulnerability was introduced in versions 9.6.0, 10.0.0, 10.1.0
CVE-2024-21689 HIGH 8.0 UPGRADE This High severity RCE (Remote Code Execution) vulnerability CVE-2024-21689 was introduced in versions 9.1.0,
CVE-2024-21687 HIGH 8.1 UPGRADE This High severity File Inclusion vulnerability was introduced in versions 9.0.0, 9.1.0, 9.2.0, 9.3.0, 9.4.0,

References

← Back to latest CVEs