CVE-2022-26133

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-04-21. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 71%
CISA-KEV: Not listedEPSS: 71%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

SharedSecretClusterAuthenticator in 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 allow a remote, unauthenticated attacker to execute arbitrary code via Java deserialization.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
88(Track)
EG Risk 88/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation71% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.3%
KEV
Not listed

Published

April 20, 2022

Last Modified

November 21, 2024

Advisory Details (2)

Auto-updated May 25, 2026
No patch confirmed yet.
generic

Multiple Products Security Advisory - Hazelcast Vulnerable To Remote Code Execution - CVE-2016-10750, CVE-2022-26133 | Atlassian Support | Atlassian Documentation

https://confluence.atlassian.com/security/multiple-products-security-advisory-hazelcast-vulnerable-to-remote-code-execution-cve-2016-10750-1116292387.html

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 19× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 02:09 UTCEG score recompute
  2. 2026-07-22 22:56 UTCEG score recompute
  3. 2026-07-22 14:06 UTCEPSS rescore
  4. 2026-07-22 14:06 UTCEPSS rescore
  5. 2026-07-20 17:05 UTCEPSS rescore
  6. 2026-07-19 14:29 UTCEPSS rescore
  7. 2026-07-19 02:27 UTCEPSS rescore
  8. 2026-07-15 16:56 UTCEPSS rescore
  9. 2026-07-15 16:56 UTCEPSS rescore
  10. 2026-07-13 06:11 UTCEPSS rescore
  11. 2026-07-13 06:11 UTCEPSS rescore
  12. 2026-07-12 05:44 UTCEPSS rescore
  13. 2026-07-09 19:07 UTCEPSS rescore
  14. 2026-07-07 13:44 UTCEPSS rescore
  15. 2026-07-06 02:21 UTCEPSS rescore
  16. 2026-07-01 15:04 UTCEPSS rescore
  17. 2026-06-25 13:48 UTCEPSS rescore
  18. 2026-06-24 14:03 UTCEPSS rescore
  19. 2026-06-24 14:03 UTCEPSS rescore
  20. 2026-06-23 21:31 UTCEPSS rescore
  21. 2026-06-23 21:31 UTCEPSS rescore
  22. 2026-06-21 01:58 UTCEPSS rescore
  23. 2026-06-21 01:58 UTCEPSS rescore
  24. 2026-06-19 19:24 UTCEPSS rescore
  25. 2026-06-19 19:24 UTCEPSS rescore
Show 33 more
  1. 2026-06-17 17:51 UTCEPSS rescore
  2. 2026-06-17 17:51 UTCEPSS rescore
  3. 2026-06-16 17:51 UTCEPSS rescore
  4. 2026-06-15 17:46 UTCEPSS rescore
  5. 2026-06-12 23:10 UTCEPSS rescore
  6. 2026-06-12 23:10 UTCEPSS rescore
  7. 2026-06-10 22:16 UTCEPSS rescore
  8. 2026-06-08 14:15 UTCEPSS rescore
  9. 2026-06-08 14:15 UTCEPSS rescore
  10. 2026-06-07 15:23 UTCEPSS rescore
  11. 2026-06-07 15:23 UTCEPSS rescore
  12. 2026-06-06 13:46 UTCEPSS rescore
  13. 2026-06-06 13:46 UTCEPSS rescore
  14. 2026-06-05 22:45 UTCEPSS rescore
  15. 2026-06-05 06:09 UTCEPSS rescore
  16. 2026-06-05 06:09 UTCEPSS rescore
  17. 2026-06-04 13:11 UTCEPSS rescore
  18. 2026-06-04 13:11 UTCEPSS rescore
  19. 2026-06-02 20:11 UTCEPSS rescore
  20. 2026-06-02 20:11 UTCEPSS rescore
  21. 2026-06-02 20:11 UTCEPSS rescore
  22. 2026-05-31 22:29 UTCEPSS rescore
  23. 2026-05-31 22:29 UTCEPSS rescore
  24. 2026-05-31 00:15 UTCEPSS rescore
  25. 2026-05-31 00:15 UTCEPSS rescore
  26. 2026-05-29 13:42 UTCEPSS rescore
  27. 2026-05-28 13:43 UTCEPSS rescore
  28. 2026-05-28 13:43 UTCEPSS rescore
  29. 2026-05-28 13:43 UTCEPSS rescore
  30. 2026-05-27 13:39 UTCEPSS rescore
  31. 2026-05-27 13:39 UTCEPSS rescore
  32. 2026-05-25 23:23 UTCEG score recompute
  33. 2026-05-25 23:23 UTCGHSA enrichment

Publicly available exploits

(2 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCabbarhissarh/CVE-2022-26133
    First seen Jun 4, 2022

    CVE-2022-26133 Exploit

    Open source ↗
  • GitHub PoCPear1y/CVE-2022-26133
    First seen May 9, 2022

    Atlassian Bitbucket Data Center RCE(CVE-2022-26133) verification.

    Open source ↗

Frequently asked(5)

What is CVE-2022-26133?
CVE-2022-26133 is a critical vulnerability published on April 20, 2022. SharedSecretClusterAuthenticator in 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 allow a remote, unauthenticated attacker to execute arbitrary code via Java…
When was CVE-2022-26133 disclosed?
CVE-2022-26133 was first published in the National Vulnerability Database on April 20, 2022, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-26133 actively exploited?
CVE-2022-26133 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-26133?
CVE-2022-26133 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2022-26133?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-26133, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2022-26133

Explore →

Is Your Infrastructure Affected by CVE-2022-26133?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.