CVE-2022-26137
No exploitation reported by the sources we read.
- Published2022-07-20
- Fixed in7.21.2 · 7.20.2 · 7.19.5 · 7.17.8 · 7.6.16
- WeaknessCWE-180 · CWE-346
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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.
Timeline
dates in UTC- 2022-07-2018:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2022-26137?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2022-26137?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD · CISA-ADP| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.21 | ≥ 7.21.0, < 7.21.2 | 7.21.2 | NVD · CISA-ADP |
| 7.20 | ≥ 7.20.0, < 7.20.2 | 7.20.2 | NVD |
| 7.20 | ≥ 7.20.1, < 7.20.2 | 7.20.2 | CISA-ADP |
| 7.x | ≥ 7.18.0, < 7.19.5 | 7.19.5 | NVD · CISA-ADP |
| 7.x | ≥ 7.7.0, < 7.17.8 | 7.17.8 | NVD · CISA-ADP |
| 7.6 | < 7.6.16 | 7.6.16 | NVD · CISA-ADP |
| 8.0 | = 8.0.0 | no fix published | NVD · CISA-ADP |
| 8.1 | = 8.1.0 | no fix published | NVD · CISA-ADP |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.17 | ≥ 7.17.0, < 7.17.4 | 7.17.4 | NVD · CISA-ADP |
| 7.16 | ≥ 7.16.0, < 7.16.4 | 7.16.4 | NVD · CISA-ADP |
| 7.15 | ≥ 7.15.0, < 7.15.2 | 7.15.2 | NVD · CISA-ADP |
| 7.14 | ≥ 7.14.0, < 7.14.3 | 7.14.3 | NVD · CISA-ADP |
| 7.x | ≥ 7.5.0, < 7.13.7 | 7.13.7 | NVD · CISA-ADP |
| 7.4 | < 7.4.17 | 7.4.17 | NVD · CISA-ADP |
| 7.18 | = 7.18.0 | no fix published | NVD · CISA-ADP |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.17 | ≥ 7.17.0, < 7.17.4 | 7.17.4 | NVD · CISA-ADP |
| 7.16 | ≥ 7.16.0, < 7.16.4 | 7.16.4 | NVD · CISA-ADP |
| 7.15 | ≥ 7.15.0, < 7.15.2 | 7.15.2 | NVD · CISA-ADP |
| 7.14 | ≥ 7.14.0, < 7.14.3 | 7.14.3 | NVD · CISA-ADP |
| 7.x | ≥ 7.5.0, < 7.13.7 | 7.13.7 | NVD · CISA-ADP |
| 7.4 | < 7.4.17 | 7.4.17 | NVD · CISA-ADP |
| 7.18 | = 7.18.0 | no fix published | NVD · CISA-ADP |
8 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Atlassian bitbucket to 7.21.2 · 7.20.2 · 7.19.5 · 7.17.8 · 7.6.16
Advisories and patches
- jira.atlassian.comPatch · Vendor Advisory
- jira.atlassian.comPatch · Vendor Advisory
- jira.atlassian.comPatch · Vendor Advisory
- jira.atlassian.comPatch · Vendor Advisory
- jira.atlassian.comPatch · Vendor Advisory
- jira.atlassian.comPatch · Vendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Published
- 2022-07-20
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2022-26137?
Is CVE-2022-26137 actively exploited?
What is the CVSS score for CVE-2022-26137?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.