CVE-2022-0540

A vulnerability in Jira Seraph allows a remote, unauthenticated attacker to bypass authentication by sending a specially crafted HTTP request. This affects Atlassian Jira Server and Data Center versions before 8.13.18, versions 8.14.0 and later before 8.20.6, and versions 8.21.0 and later before 8.22.0. This also affects Atlassian Jira Service Management Server and Data Center versions before 4.13.18, versions 4.14.0 and later before 4.20.6, and versions 4.21.0 and later before 4.22.0.

Published: 2022-04-20 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-0540 is rated High Risk (69.9/100): CVSS Critical severity, with high exploitation likelihood (EPSS 88.33%, 100th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-0540

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 92.57% 88.33% -4.23%
2 2026-05-19 92.38% 92.57% +0.19%
3 2026-03-19 — 92.38% —

Full EPSS history (69 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-0540

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0
6.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 6.4 [email protected]

Weakness enumeration for CVE-2022-0540

Affected software / configurations for CVE-2022-0540

Vendor Product Version Raw CPE
atlassian jira_data_center < 8.13.8 cpe:2.3:a:atlassian:jira_data_center:*:*:*:*:*:*:*:*
atlassian jira_data_center >= 8.14.0, < 8.20.6 cpe:2.3:a:atlassian:jira_data_center:*:*:*:*:*:*:*:*
atlassian jira_data_center >= 8.21.0, < 8.22.0 cpe:2.3:a:atlassian:jira_data_center:*:*:*:*:*:*:*:*
atlassian jira_server < 8.13.8 cpe:2.3:a:atlassian:jira_server:*:*:*:*:*:*:*:*
atlassian jira_server >= 8.14.0, < 8.20.6 cpe:2.3:a:atlassian:jira_server:*:*:*:*:*:*:*:*
atlassian jira_server >= 8.21.0, < 8.22.0 cpe:2.3:a:atlassian:jira_server:*:*:*:*:*:*:*:*
atlassian jira_service_management < 4.13.8 cpe:2.3:a:atlassian:jira_service_management:*:*:*:*:server:*:*:*
atlassian jira_service_management < 4.13.18 cpe:2.3:a:atlassian:jira_service_management:*:*:*:*:data_center:*:*:*
atlassian jira_service_management >= 4.14.0, < 4.20.6 cpe:2.3:a:atlassian:jira_service_management:*:*:*:*:data_center:*:*:*
atlassian jira_service_management >= 4.14.0, < 4.20.6 cpe:2.3:a:atlassian:jira_service_management:*:*:*:*:server:*:*:*
atlassian jira_service_management >= 4.21.0, < 4.22.0 cpe:2.3:a:atlassian:jira_service_management:*:*:*:*:data_center:*:*:*
atlassian jira_service_management >= 4.21.0, < 4.22.0 cpe:2.3:a:atlassian:jira_service_management:*:*:*:*:server:*:*:*

References for CVE-2022-0540

URL Tags
https://confluence.atlassian.com/display/JIRA/Jira+Security+Advisory+2022-04-20 Issue Tracking Patch Vendor Advisory
https://jira.atlassian.com/browse/JRASERVER-73650 Issue Tracking Patch Vendor Advisory
https://jira.atlassian.com/browse/JSDSERVER-11224 Issue Tracking Patch Vendor Advisory
cvelogic Threat Intelligence