dbcve.org
BambooApplication · Atlassian

CVE-2022-26136

CRITICAL · 9.8 CVSS v3.1 Published 2022-07-20
Fix available
A fix is available. Upgrade to 4.3.8 / 4.4.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability in multiple Atlassian products allows a remote, unauthenticated attacker to bypass Servlet Filters used by first and third party apps. The impact depends on which filters are used by each app, and how the filters are used. This vulnerability can result in authentication bypass and cross-site scripting. Atlassian has released updates that fix the root cause of this vulnerability, but has not exhaustively enumerated all potential consequences of this vulnerability. Atlassian Bamboo versions are affected before 8.0.9, from 8.1.0 before 8.1.8, and from 8.2.0 before 8.2.4. Atlassian Bitbucket versions are affected before 7.6.16, from 7.7.0 before 7.17.8, from 7.18.0 before 7.19.5, from 7.20.0 before 7.20.2, from 7.21.0 before 7.21.2, and versions 8.0.0 and 8.1.0. Atlassian Confluence versions are affected before 7.4.17, from 7.5.0 before 7.13.7, from 7.14.0 before 7.14.3, from 7.15.0 before 7.15.2, from 7.16.0 before 7.16.4, from 7.17.0 before 7.17.4, and version 7.21.0. Atlassian Crowd versions are affected before 4.3.8, from 4.4.0 before 4.4.2, and version 5.0.0. Atlassian Fisheye and Crucible versions before 4.8.10 are affected. Atlassian Jira versions are affected before 8.13.22, from 8.14.0 before 8.20.10, and from 8.21.0 before 8.22.4. Atlassian Jira Service Management versions are affected before 4.13.22, from 4.14.0 before 4.20.10, and from 4.21.0 before 4.22.4.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
BambooApplication
Affected:>= 7.2.0, < 7.2.10>= 8.0.0, < 8.0.9>= 8.1.0, < 8.1.8>= 8.2.0, < 8.2.4
BitbucketApplication
Affected:< 7.6.16>= 7.7.0, < 7.17.8>= 7.18.0, < 7.19.5>= 7.20.0, < 7.20.2>= 7.21.0, < 7.21.2= 8.0.0= 8.1.0
Confluence Data CenterApplication
Affected:< 7.4.17>= 7.5.0, < 7.13.7>= 7.14.0, < 7.14.3>= 7.15.0, < 7.15.2>= 7.16.0, < 7.16.4>= 7.17.0, < 7.17.4= 7.18.0
Confluence ServerApplication
Affected:< 7.4.17>= 7.5.0, < 7.13.7>= 7.14.0, < 7.14.3>= 7.15.0, < 7.15.2>= 7.16.0, < 7.16.4>= 7.17.0, < 7.17.4= 7.18.0
CrowdApplication
Affected:< 4.3.8>= 4.4.0, < 4.4.2= 5.0.0
CrucibleApplication
Affected:< 4.8.10
FisheyeApplication
Affected:< 4.8.10
Jira Data CenterApplication
Affected:>= 8.13.0, < 8.13.22>= 8.14.0, < 8.20.10>= 8.21.0, < 8.22.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.3.8 / 4.4.2 / 4.8.10 or later
Fixed in 4.3.84.4.24.8.10
Vendor patch jira.atlassian.com →
Recommended fix High confidence

Upgrade to the latest LTS or latest stable release in your product line (e.g., Jira 8.22.4+, Confluence 7.21.0+, Bitbucket 7.21.2+, Bamboo 8.2.4+)

  1. 1. Identify the affected Atlassian product and current installed version in your environment.
  2. 2. Determine the appropriate upgrade target based on your current major version branch.
  3. 3. Review Atlassian upgrade documentation and release notes for the target version.
  4. 4. Perform a full backup of your Atlassian instance and database before upgrading.
  5. 5. Schedule a maintenance window as upgrades may require downtime.
  6. 6. Download and install the appropriate fixed version for your product:
  7. - For Bamboo: upgrade to 7.2.10, 8.0.9, 8.1.8, or 8.2.4 (or later)
  8. - For Bitbucket: upgrade to 7.6.16, 7.17.8, 7.19.5, 7.20.2, or 7.21.2 (or later)
Caveat Review Atlassian upgrade notes for your specific version jump; some upgrades may require intermediate steps or have migration considerations. Ensure compatibility with your Java version and plugins/add-ons.

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26136 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-26136 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data