Skip to content
Noroxi
CVE-2022-0540· NVD / CVE Program· CNA atlassian

A vulnerability in Jira Seraph allows a remote, unauthenticated attacker to bypass authentication by sending a specially crafted HTTP reques

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.

CriticalCVSS 9.8 · v3.1—Proof of concept No fix recorded
Published
Apr 20, 2022
Updated
Jun 17, 2026
EPSS
88.1% · 100th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

65

This week

Don’t wait for the next maintenance window.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
26 / 30 · 88.1%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
atlassianjira data center
atlassianjira server
atlassianjira service management

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • atlassian jira data centerbefore 8.13.8
  • atlassian jira data center8.14.0 and later · before 8.20.6
  • atlassian jira data center8.21.0 and later · before 8.22.0
  • atlassian jira serverbefore 8.13.8
  • atlassian jira server8.14.0 and later · before 8.20.6
  • atlassian jira server8.21.0 and later · before 8.22.0
  • atlassian jira service managementbefore 4.13.8
  • atlassian jira service managementbefore 4.13.18
  • atlassian jira service management4.14.0 and later · before 4.20.6
  • atlassian jira service management4.21.0 and later · before 4.22.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (atlassian). Independent of NVD's CPE analysis and usually ahead of it.

  • Atlassian Jira Core Server

    • unspecified and later · before 8.13.18affected
    • 8.14.0 and later · before unspecifiedaffected
    • unspecified and later · before 8.20.6affected
    • 8.21.0 and later · before unspecifiedaffected
    • unspecified and later · before 8.22.0affected
  • Atlassian Jira Service Management Data Center

    • unspecified and later · before 4.13.18affected
    • 4.14.0 and later · before unspecifiedaffected
    • unspecified and later · before 4.20.6affected
    • 4.21.0 and later · before unspecifiedaffected
    • unspecified and later · before 4.22.0affected
  • Atlassian Jira Service Management Server

    • unspecified and later · before 4.13.18affected
    • 4.14.0 and later · before unspecifiedaffected
    • unspecified and later · before 4.20.6affected
    • 4.21.0 and later · before unspecifiedaffected
    • unspecified and later · before 4.22.0affected
  • Atlassian Jira Software Data Center

    • unspecified and later · before 8.13.18affected
    • 8.14.0 and later · before unspecifiedaffected
    • unspecified and later · before 8.20.6affected
    • 8.21.0 and later · before unspecifiedaffected
    • unspecified and later · before 8.22.0affected
  • Atlassian Jira Software Server

    • unspecified and later · before 8.13.18affected
    • 8.14.0 and later · before unspecifiedaffected
    • unspecified and later · before 8.20.6affected
    • 8.21.0 and later · before unspecifiedaffected
    • unspecified and later · before 8.22.0affected

Other highest-scoring records for the same primary product.

  • CVE-2021-26086Affected versions of Atlassian Jira Server and Data Center allow remote attackers to read particular files via a path traversal vulnerabilitKEV
    81Now
  • CVE-2020-36239Jira Data Center, Jira Core Data Center, Jira Software Data Center from version 6.3.0 before 8.5.16, from 8.6.0 before 8.13.8, from 8.14.0 b
    54Plan
  • CVE-2022-26135A vulnerability in Mobile Plugin for Jira Data Center and Server allows a remote, authenticated user (including a user who joined via the si
    47Plan
  • CVE-2022-36801Affected versions of Atlassian Jira Server and Data Center allow anonymous remote attackers to inject arbitrary HTML or JavaScript via a Ref
    44Plan
  • CVE-2020-14179Affected versions of Atlassian Jira Server and Data Center allow remote, unauthenticated attackers to view custom field names and custom SLA
    44Plan
  • CVE-2022-36799This issue exists to document that a security improvement in the way that Jira Server and Data Center use templates has been implemented.
    41Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Nuclei detection template ×1
  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Nuclei detection templateNuclei template CVE-2022-0540 —
Proof-of-concept repository on GitHubstars:712022-05-25

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+34 d
  3. TodayOct 12, 2026+1636 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

—

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

  • CVE-2022-2613571 days apartA vulnerability in Mobile Plugin for Jira Data Center and Server allows a remote, authenticated user (including a user who joined via the si
    47Plan
  • CVE-2022-36799103 days apartThis issue exists to document that a security improvement in the way that Jira Server and Data Center use templates has been implemented.
    41Plan
  • CVE-2021-4394444 days apartThis issue exists to document that a security improvement in the way that Jira Server and Data Center use templates has been implemented.
    29Monitor

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middlewareapp.post("/admin-api/config", updateConfig);

Fixed

ts
const admin = express.Router();admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);app.use("/admin", admin);

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

All records