How severe is CVE-2021-26086?

CVE-2021-26086 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-2021-26086?

Affected package information for CVE-2021-26086 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2021-26086?

Apply the atlassian jira data center security patch or hotfix for CVE-2021-26086 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2021-26086 across my infrastructure?

Inventory every atlassian jira data center deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

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

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2021-26086?

O3 detects and blocks CVE-2021-26086 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2021-26086 actively exploited in the wild?

Yes. There are 5 known exploit references for CVE-2021-26086, including 1 documented proof-of-concept exploit on Exploit-DB and 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2021-26086?

CVE-2021-26086 has an EPSS (Exploit Prediction Scoring System) score of 100.0%, 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.

Is CVE-2021-26086 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2021-26086 (Atlassian Jira Server and Data Center Path Traversal Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2024-11-12. CISA required all US federal civilian agencies to remediate this vulnerability by 2024-12-03. The required action was: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2021-26086?

CVE-2021-26086 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2021-26086?

CVE-2021-26086 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-2021-26086?

A Nuclei detection template exists for CVE-2021-26086, 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-2021-26086 published, and has it been updated?

CVE-2021-26086 was published on August 16, 2021 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2024-11-12 — agencies required to remediate by 2024-12-03

CVE-2021-26086

MEDIUM

Affected versions of Atlassian Jira Server and Data Center allow remote attackers to read particular files via a path traversal vulnerability in the /WEB-INF/web.xml endpoint. The affected…

Published

Aug 16, 2021

Updated

Jun 17, 2026

Affected

0 pkgs

Patched

None yet

Exploits

5 known

EPSS Exploitation Probability

via FIRST.org ↗

100.0%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

Affected versions of Atlassian Jira Server and Data Center allow remote attackers to read particular files via a path traversal vulnerability in the /WEB-INF/web.xml endpoint. The affected versions are before version 8.5.14, from version 8.6.0 before 8.13.6, and from version 8.14.0 before 8.16.1.

Affected Products

2 products · 6 configurations

Application

jira data centeratlassian

≥ 8.14.0 && < 8.16.1

range

Application

jira serveratlassian

≥ 8.14.0 && < 8.16.1

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-50380webappsmultiple

Atlassian Jira Server Data Center 8.16.0 - Arbitrary File Read

by Mayank Deshmukh · Oct 6, 2021

Exploit-DB Source

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every atlassian jira data center deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Fix
Apply the atlassian jira data center security patch or hotfix for CVE-2021-26086 on the affected version, following the vendor advisory for your exact build.
Workarounds
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2021-26086 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2021-26086. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2021-26086 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2021-26086 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works