🛡️ CVE-2022-26137 — bamboo
Description
A vulnerability in multiple Atlassian products allows a remote, unauthenticated attacker to cause additional Servlet Filters to be invoked when the application processes requests or responses. Atlassian has confirmed and fixed the only known security issue associated with this vulnerability: Cross-origin resource sharing (CORS) bypass. Sending a specially crafted HTTP request can invoke the Servlet Filter used to respond to CORS requests, resulting in a CORS bypass. An attacker that can trick a user into requesting a malicious URL can access the vulnerable application with the victim’s permissions. 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.
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. A user must be tricked into taking some action. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability high.
Affected software
CVE-2022-26137 is recorded against 11 packages.
- bamboo (from 8.2.0 up to 8.2.4)
- bitbucket
- confluence-data-center
- confluence-server
- crowd
- crucible (fixed in 4.8.10)
- fisheye (fixed in 4.8.10)
- jira-data-center (from 8.21.0 up to 8.22.4)
- jira-server (from 8.21.0 up to 8.22.4)
- jira-service-desk (fixed in 4.13.22)
- jira-service-management (from 4.21.0 up to 4.22.4)
Timeline and source
Published on 20 July 2022 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.
References
jira.atlassian.com
jira.atlassian.com
jira.atlassian.com
jira.atlassian.com
jira.atlassian.com
jira.atlassian.com
jira.atlassian.com
jira.atlassian.com
jira.atlassian.com
jira.atlassian.com
jira.atlassian.com
jira.atlassian.com
jira.atlassian.com
jira.atlassian.com
jira.atlassian.com
Details
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| bamboo | 8.2.0 | 8.2.4 |
| bitbucket | — | — |
| confluence-data-center | — | — |
| confluence-server | — | — |
| crowd | — | — |
| crucible | — | 4.8.10 |
| fisheye | — | 4.8.10 |
| jira-data-center | 8.21.0 | 8.22.4 |
| jira-server | 8.21.0 | 8.22.4 |
| jira-service-desk | — | 4.13.22 |
| jira-service-management | 4.21.0 | 4.22.4 |
References
Similar Threats
- High CVE-2026-21571
- High CVE-2026-21570
- Unknown MAL-2025-50934
- Unknown MAL-2025-15357
- Unknown MAL-2025-15358
More CVE 2022 advisories
Browse all of CVE 2022 in the advisory index.
Site Security Check
Is bamboo part of your stack?
CVE-2022-26137 is rated CVSS 8.8 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.