Security readout for executives and security teams
Plain-English summary
This Atlassian flaw can let a malicious website make a vulnerable Atlassian app accept cross-origin requests using a logged-in victim’s permissions. The attacker must trick a user into visiting or requesting a malicious URL. Business risk is highest where affected Jira, Confluence, Bitbucket, Bamboo, Crowd, Fisheye, or Crucible systems are reachable by browsers used by staff.
Executive priority
Treat as a high-priority patching item for affected Atlassian Server and Data Center systems. It can expose sensitive application actions or data through a victim’s session, but available evidence here does not establish active exploitation.
Technical view
CVE-2022-26137 is a CORS bypass caused by improper handling before canonicalization, allowing crafted HTTP requests to invoke additional Servlet Filters. Atlassian states the known security issue is CORS bypass. The CVSS 3.1 score is 8.8, with network attack vector, no attacker privileges, and required user interaction.
Likely exposure
Exposure is likely in Atlassian Server or Data Center deployments running the affected version ranges listed for Bamboo, Bitbucket, Confluence, Crowd, Fisheye, Crucible, Jira, or Jira Service Management. Internet-facing and widely used internal instances deserve priority because exploitation depends on a user’s browser and permissions.
Exploitation context
The bundle does not show CISA KEV listing or other evidence of active exploitation. The attack scenario requires tricking a user into requesting a malicious URL, after which the vulnerable application may be accessed with that user’s permissions through the CORS bypass.
Researcher notes
Focus validation on version fingerprinting and CORS behavior, not proof-of-concept reproduction. The source bundle identifies the known issue as CORS bypass from additional Servlet Filter invocation. Evidence is incomplete on exploit activity beyond the CVE data and KEV=false signal.
Mitigation direction
- Upgrade affected Atlassian products to the fixed versions or later listed by Atlassian.
- Prioritize internet-facing Confluence, Jira, Bitbucket, and identity-linked Crowd deployments.
- Check Atlassian issue pages for product-specific fixed versions and upgrade notes.
- Reduce unnecessary public exposure to affected Atlassian applications while patching.
- Review browser-facing integrations that depend on permissive CORS behavior.
Validation and detection
- Inventory deployed Atlassian products and exact versions across Server and Data Center estates.
- Compare versions against each affected range in the CVE description.
- Confirm the instance is upgraded beyond the fixed version for its product branch.
- Review Atlassian product issue pages for matching product identifiers and status.
- Check access logs for unusual cross-origin request patterns as supporting evidence only.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-180: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-26137 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://jira.atlassian.com/browse/BAM-21795CVE reference · x_refsource_MISC
- https://jira.atlassian.com/browse/BSERV-13370CVE reference · x_refsource_MISC
- https://jira.atlassian.com/browse/CONFSERVER-79476CVE reference · x_refsource_MISC
- https://jira.atlassian.com/browse/CWD-5815CVE reference · x_refsource_MISC
- https://jira.atlassian.com/browse/FE-7410CVE reference · x_refsource_MISC
- https://jira.atlassian.com/browse/CRUC-8541CVE reference · x_refsource_MISC
- https://jira.atlassian.com/browse/JRASERVER-73897CVE reference · x_refsource_MISC
- https://jira.atlassian.com/browse/JSDSERVER-11863CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Behavior Order: Validate Before Canonicalize
Incorrect Behavior Order: Validate Before Canonicalize represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.