Skip to content
VulniPulse
Critical9.8Atlassian

Critical [CVE-2022-0540] Jira Service Management: vulnerability in Jira Seraph

This critical-severity Atlassian advisory covers CVE-2022-0540 affecting Jira Service Management.

CVE-2022-0540 Published Apr 20, 2022Updated by vendor Jun 17, 2026
Affected products & platforms
AtlassianJira
Open vendor advisory

Android app · Google Play

Monitor future Atlassian CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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.

Affected product named by the advisory: Jira Service Management.

Affected versions
  • 8.13.18
  • 8.14.0
  • 8.20.6
  • 8.21.0
  • 8.22.0
  • 4.13.18
  • 4.14.0
  • 4.20.6
  • 4.21.0
  • 4.22.0

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Fixed versions
  • 8.13.18
  • 8.20.6
  • 8.22.0
  • 4.13.18
  • 4.20.6
  • 4.22.0

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Mitigation

Upgrade to a fixed release: 8.13.18, 8.20.6, 8.22.0, 4.13.18, 4.20.6, 4.22.0. That is the remediation for this advisory.

The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.