# CVE-2022-26137: Security feature bypass in Bamboo Data Center > Remote attackers can bypass CORS restrictions via crafted requests, allowing unauthorized access to Atlassian applications using victim permissions. - **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 20 Jul 2022 - **Updated:** 3 Oct 2024 - **Also known as:** GHSA-fpj5-pcgc-34g7 ## What is CVE-2022-26137? CVE-2022-26137 is a high-severity vulnerability in Atlassian Crucible, published on 20 Jul 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official 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. Weakness: CWE-346 (Origin Validation Error), CWE-180 (Incorrect Behavior Order: Validate Before Canonicalize) ## Which versions are affected by CVE-2022-26137? It affects 11 products. Products: Atlassian Bamboo, Atlassian Bitbucket, Atlassian Confluence Data Center, Atlassian Confluence Server, Atlassian Crowd, Atlassian Crucible, Atlassian Fisheye, Atlassian Jira Data Center, Atlassian Jira Server, Atlassian Jira Service Desk, Atlassian Jira Service Management. ## How do I fix CVE-2022-26137? No fix has been published for CVE-2022-26137 yet. Limit exposure of the affected software until one is available. ## Is CVE-2022-26137 being exploited? There is no known exploitation of CVE-2022-26137 in the wild and no public exploit code. ## Other vulnerabilities in Atlassian Crucible - [CVE-2026-21589](https://insights.sbomify.com/CVE-2026-21589/): Atlassian Multiple Products Files or Directories Accessible to External Parties (critical 9.3, exploited in the wild) - [CVE-2022-26136](https://insights.sbomify.com/CVE-2022-26136/): Auth bypass in Bamboo Data Center (critical 9.8) - [CVE-2016-5229](https://insights.sbomify.com/CVE-2016-5229/): Deserialization in n/a (critical 9.8) - [CVE-2014-9757](https://insights.sbomify.com/CVE-2014-9757/): Deserialization in n/a (critical 9.8) - [CVE-2015-8360](https://insights.sbomify.com/CVE-2015-8360/): Deserialization in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-26137 and fix it if it is affected. What it is: CVE-2022-26137 is a high-severity vulnerability in Atlassian Crucible, published on 20 Jul 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2022-26137 in the wild and no public exploit code. Affected product: Atlassian Crucible. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-26137/ (Markdown: https://insights.sbomify.com/CVE-2022-26137/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-26137 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-26137 - OSV: https://osv.dev/vulnerability/CVE-2022-26137 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-26137/ Summaries are generated and may contain mistakes; the official description above is the record.