CVE-2022-0540

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 88% (99th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8EG
EchelonGraph verdictMitigate this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 88%
CISA-KEV: Not listedEPSS PROB: 88%CVSS: 9.8Exploit: Elevated riskExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
94
EG Risk 94/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation88% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
88%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

April 20, 2022

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Oct 3, 2026
Fix referenced — no release confirmed yet.
generic

Loading...

https://jira.atlassian.com/browse/JSDSERVER-11224
generic

Loading...

https://jira.atlassian.com/browse/JRASERVER-73650
generic

Jira Security Advisory 2022-04-20 | Atlassian Support | Atlassian Documentation

https://confluence.atlassian.com/display/JIRA/Jira+Security+Advisory+2022-04-20

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 1× in last 7d / 12× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-07 23:45 UTCEPSS rescore
  2. 2026-09-30 15:46 UTCEG score recompute
  3. 2026-09-26 15:54 UTCEPSS rescore
  4. 2026-09-26 00:21 UTCEPSS rescore
  5. 2026-09-24 14:00 UTCEPSS rescore
  6. 2026-09-24 14:00 UTCEPSS rescore
  7. 2026-09-22 14:44 UTCEPSS rescore
  8. 2026-09-21 20:28 UTCEPSS rescore
  9. 2026-09-20 20:13 UTCEPSS rescore
  10. 2026-09-19 15:38 UTCEPSS rescore
  11. 2026-09-17 19:23 UTCEPSS rescore
  12. 2026-09-11 14:49 UTCEPSS rescore
  13. 2026-09-06 13:45 UTCEPSS rescore
  14. 2026-09-05 15:25 UTCEPSS rescore
  15. 2026-09-04 13:57 UTCEPSS rescore
  16. 2026-08-30 19:14 UTCEPSS rescore
  17. 2026-08-28 21:38 UTCEPSS rescore
  18. 2026-08-27 14:22 UTCEPSS rescore
  19. 2026-08-26 14:43 UTCEPSS rescore
  20. 2026-08-25 13:46 UTCEPSS rescore
  21. 2026-08-24 14:13 UTCEPSS rescore
  22. 2026-08-20 22:52 UTCEPSS rescore
  23. 2026-08-19 17:01 UTCEPSS rescore
  24. 2026-08-17 13:44 UTCEPSS rescore
  25. 2026-08-16 02:11 UTCEPSS rescore
Show 46 more
  1. 2026-08-12 13:48 UTCEPSS rescore
  2. 2026-08-06 13:44 UTCEPSS rescore
  3. 2026-08-02 02:24 UTCEPSS rescore
  4. 2026-07-30 16:25 UTCEPSS rescore
  5. 2026-07-30 01:28 UTCEPSS rescore
  6. 2026-07-28 15:33 UTCEPSS rescore
  7. 2026-07-24 14:15 UTCEPSS rescore
  8. 2026-07-24 14:15 UTCEPSS rescore
  9. 2026-07-23 14:16 UTCEPSS rescore
  10. 2026-07-23 02:06 UTCEG score recompute
  11. 2026-07-22 22:53 UTCEG score recompute
  12. 2026-07-22 14:06 UTCEPSS rescore
  13. 2026-07-18 10:02 UTCEPSS rescore
  14. 2026-07-15 01:58 UTCEPSS rescore
  15. 2026-07-15 01:58 UTCEPSS rescore
  16. 2026-07-11 08:25 UTCEPSS rescore
  17. 2026-07-09 19:07 UTCEPSS rescore
  18. 2026-07-09 19:07 UTCEPSS rescore
  19. 2026-07-07 13:43 UTCEPSS rescore
  20. 2026-07-05 02:28 UTCEPSS rescore
  21. 2026-07-05 02:28 UTCEPSS rescore
  22. 2026-06-30 23:20 UTCEPSS rescore
  23. 2026-06-27 03:07 UTCEPSS rescore
  24. 2026-06-27 03:06 UTCEPSS rescore
  25. 2026-06-24 14:03 UTCEPSS rescore
  26. 2026-06-24 14:03 UTCEPSS rescore
  27. 2026-06-23 21:31 UTCEPSS rescore
  28. 2026-06-23 21:31 UTCEPSS rescore
  29. 2026-06-19 19:24 UTCEPSS rescore
  30. 2026-06-19 19:24 UTCEPSS rescore
  31. 2026-06-15 17:46 UTCEPSS rescore
  32. 2026-06-13 22:58 UTCEPSS rescore
  33. 2026-06-13 22:58 UTCEPSS rescore
  34. 2026-06-12 23:10 UTCEPSS rescore
  35. 2026-06-11 13:58 UTCEPSS rescore
  36. 2026-06-10 22:16 UTCEPSS rescore
  37. 2026-06-05 22:45 UTCEPSS rescore
  38. 2026-06-05 22:45 UTCEPSS rescore
  39. 2026-05-31 00:15 UTCEPSS rescore
  40. 2026-05-31 00:15 UTCEPSS rescore
  41. 2026-05-27 13:39 UTCEPSS rescore
  42. 2026-05-27 13:39 UTCEPSS rescore
  43. 2026-05-26 07:17 UTCEPSS rescore
  44. 2026-05-26 07:17 UTCEPSS rescore
  45. 2026-05-25 23:24 UTCEG score recompute
  46. 2026-05-25 23:24 UTCGHSA enrichment

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCPear1y/CVE-2022-0540-RCE
    First seen May 25, 2022

    Atlassian Jira Seraph Authentication Bypass RCE（CVE-2022-0540）

    Open source ↗
  • Nucleihttp/cves/2022/CVE-2022-0540.yaml
    First seen Jan 1, 2022

    Atlassian Jira Seraph - Authentication Bypass

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-0540?
CVE-2022-0540 is a critical vulnerability published on April 20, 2022. 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…
When was CVE-2022-0540 disclosed?
CVE-2022-0540 was first published on April 20, 2022, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-0540 actively exploited?
CVE-2022-0540 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 88% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-0540?
CVE-2022-0540 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2022-0540?
A fix for CVE-2022-0540 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2022-0540

Explore →

Is Your Infrastructure Affected by CVE-2022-0540?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs