CVE-2022-36804 Atlassian Bitbucket Server and Data Center Command Injection Vulnerability
Multiple API endpoints of Atlassian Bitbucket Server and Data Center contain a command injection vulnerability where an attacker with access to a public Bitbucket repository, or with read permissions to a private one, can execute code by sending a malicious HTTP request.
From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.
Should You Worry?
- CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 30 Sep 2022.
- Rated High severity (CVSS 8.8, scored by CISA).
- It has been in the catalogue for 1,498 days. Systems still unpatched now have almost certainly been scanned for it.
What It Is
Multiple API endpoints in Atlassian Bitbucket Server and Data Center 7.0.0 before version 7.6.17, from version 7.7.0 before version 7.17.10, from version 7.18.0 before version 7.21.4, from version 8.0.0 before version 8.0.3, from version 8.1.0 before version 8.1.3, and from version 8.2.0 before version 8.2.2, and from version 8.3.0 before 8.3.1 allows remote attackers with read permissions to a public or private Bitbucket repository to execute arbitrary code by sending a malicious HTTP request. This vulnerability was reported via our Bug Bounty Program by TheGrandPew.
Affected Versions
| Product | Versions |
|---|---|
| Atlassian Bitbucket Server | 7.0.0 to before unspecified unspecified to before 7.6.17 7.7.0 to before unspecified unspecified to before 7.17.10 7.18.0 to before unspecified unspecified to before 7.21.4 |
| Atlassian Bitbucket Data Center | 7.0.0 to before unspecified unspecified to before 7.6.17 7.7.0 to before unspecified unspecified to before 7.17.10 7.18.0 to before unspecified unspecified to before 7.21.4 |
From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.
What To Do Now
- 1
Find it
Search your asset inventory and external attack surface for Atlassian Bitbucket Server and Data Center. Include cloud images, appliances and anything a supplier runs for you.
Attack Surface Management - 2
- 3
Hunt for compromise
If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.
Incident Response - 4
Prove it is fixed
Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.
Penetration Testing
The Compliance Clock
General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.
Not Sure If You Are Exposed?
Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2022-36804 and every other exploited flaw on the list.