How severe is CVE-2022-36804?

CVE-2022-36804 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which products are affected by CVE-2022-36804?

Affected package information for CVE-2022-36804 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2022-36804?

Apply the atlassian bitbucket security patch or hotfix for CVE-2022-36804 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2022-36804 across my infrastructure?

Inventory every atlassian bitbucket deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for remote code execution at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2022-36804 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2022-36804?

O3 detects and blocks CVE-2022-36804 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2022-36804 actively exploited in the wild?

Yes. There are 34 known exploit references for CVE-2022-36804, including 1 documented proof-of-concept exploit on Exploit-DB and 22 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-36804?

CVE-2022-36804 has an EPSS (Exploit Prediction Scoring System) score of 99.1%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2022-36804 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2022-36804 (Atlassian Bitbucket Server and Data Center Command Injection Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-09-30. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-10-21. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2022-36804?

CVE-2022-36804 is classified as OS Command Injection (CWE-78), CWE-88 (CWE-88). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2022-36804?

CVE-2022-36804 affects atlassian bitbucket (1 version, e.g. 8.3.0). Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2022-36804?

A Nuclei detection template exists for CVE-2022-36804, meaning automated scanners can fingerprint it. A Metasploit module references CVE-2022-36804, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2022-36804 published, and has it been updated?

CVE-2022-36804 was published on August 25, 2022 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2022-36804: Bitbucket OS Command Injection (High 8.8)

EPSS Exploitation Probability

via FIRST.org ↗

99.1%probability of exploitation in next 30 days

Very High Risk100th percentile-0.10%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

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 Products

1 product · 7 configurations

Application

bitbucketatlassian

≥ 8.2.0 && < 8.2.2

1 version

8.3.0

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every atlassian bitbucket deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for remote code execution at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Fix
Apply the atlassian bitbucket security patch or hotfix for CVE-2022-36804 on the affected version, following the vendor advisory for your exact build.
Workarounds
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2022-36804 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2022-36804. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Runtime Protection

Is CVE-2022-36804 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2022-36804 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works

CVE-2022-36804

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is CVE-2022-36804 being exploited in your environment?