How severe is CVE-2020-36289?

CVE-2020-36289 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which products are affected by CVE-2020-36289?

CVE-2020-36289 affects the following products: atlassian jira data center, atlassian jira server.

How do I patch CVE-2020-36289?

No patch has shipped for CVE-2020-36289 yet — track the atlassian jira data center advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2020-36289 across my infrastructure?

Inventory every atlassian jira data center deployment and check each version against the affected-products list above.

How do I mitigate CVE-2020-36289 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Is CVE-2020-36289 actively exploited in the wild?

No public exploit code has been indexed for CVE-2020-36289 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2020-36289?

CVE-2020-36289 has an EPSS (Exploit Prediction Scoring System) score of 99.2%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2020-36289?

CVE-2020-36289 is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2020-36289?

CVE-2020-36289 affects atlassian jira data center; atlassian jira server. Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2020-36289?

A Nuclei detection template exists for CVE-2020-36289, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2020-36289 published, and has it been updated?

CVE-2020-36289 was published on May 12, 2021 and was last updated on October 17, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

Not in CISA KEV

MEDIUM severity

CVE-2020-36289 — Jira Data Center

MEDIUM

CVE-2020-36289 is a medium-severity (CVSS 5.3) CWE-863 vulnerability in atlassian jira data center. EPSS puts its 30-day exploitation probability at 99.2% (100th percentile). No vendor fix is recorded yet; mitigation options are listed below.

Published

May 12, 2021

Updated

Oct 17, 2024

Affected

2 products

Patched

See advisory

Exploits

None indexed

Exploitation data as of Oct 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2020-36289.

EPSS Exploitation Probability

via FIRST.org ↗

99.2%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2020-36289 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,415 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.

Description

Affected versions of Atlassian Jira Server and Data Center allow an unauthenticated user to enumerate users via an Information Disclosure vulnerability in the QueryComponentRendererValue!Default.jspa endpoint. The affected versions are before version 8.5.13, from version 8.6.0 before 8.13.5, and from version 8.14.0 before 8.15.1.

Affected Products

2 products · 2 configurations

Application

jira data centeratlassian

all

Application

jira serveratlassian

all

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every atlassian jira data center deployment and check each version against the affected-products list above.
Remediation status
No patch has shipped for CVE-2020-36289 yet — track the atlassian jira data center advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

How to detect CVE-2020-36289

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2020-36289 -u https://target

Template: Jira Server and Data Center - Information Disclosure
Severity: medium
Impact: An attacker can gain access to sensitive information, potentially leading to further attacks.
Remediation: Apply the necessary patches or updates provided by Atlassian to fix the vulnerability.

Template by ProjectDiscovery nuclei-templates (dhiyaneshDk), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2020-36289 being exploited in your environment?

Detect and block the exploit chain at execution, on systems you cannot patch yet.

Protect my workloads How runtime protection works