A vulnerability in the SharedSecretClusterAuthenticator component of Atlassian Bitbucket Data Center (versions 5.14.0 and later before 7.6.14, 7.7.0 and later prior to 7.17.6, 7.18.0 and later prior to 7.18.4, 7.19.0 and later prior to 7.19.4, and 7.20.0) allows remote, unauthenticated attackers to execute arbitrary code on the server. The flaw is due to unsafe Java deserialization, which can be exploited by sending crafted serialized objects to the vulnerable endpoint.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a Python exploit script (CVE-2022-26133.py) targeting Atlassian Bitbucket Data Center's Java deserialization vulnerability (CVE-2022-26133). The exploit allows for both verification (vulnerability check) and exploitation (arbitrary command execution) against a specified target. The script can be used in batch mode to check multiple targets or to execute supplied commands, including reverse shell payloads for both Windows and Linux. The main attack vector is network-based, connecting to the target's default port 5701. The README provides usage instructions and example payloads. No hardcoded IPs or domains are present, but the script expects the user to supply the target URL and desired command. The repository is operational and suitable for real-world exploitation, not just proof-of-concept.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.