Jira Data CenterApplication · Atlassian
CVE-2021-26086
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAffected 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencePath traversal vulnerability in Atlassian Jira Server and Data Center allows remote attackers to read arbitrary files via the /WEB-INF/web.xml endpoint through improper input validation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Jira Data CenterApplication
< 8.5.14>= 8.6.0, < 8.13.6>= 8.14.0, < 8.16.1
Jira ServerApplication
< 8.5.14>= 8.6.0, < 8.13.6>= 8.14.0, < 8.16.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Jira installed versionLocate the jira-application.properties file in the <jira-install>/atlassian-jira/WEB-INF/classes/ directory and read the 'jira.version' property, or check the VERSION file in the Jira installation root directoryAffected if The installed version is less than 8.5.14, OR between 8.6.0 and 8.13.5 inclusive, OR between 8.14.0 and 8.16.0 inclusive
-
Check Jira version from UILog into Jira as an administrator and navigate to the About page (typically found under Administration > System > Troubleshooting and support > About) to view the installed version numberAffected if The displayed version falls within any of the vulnerable ranges listed above
If the installed Jira Server or Data Center version is 8.5.14, 8.13.6, 8.16.1 or later, the environment is not affected by this path traversal vulnerability; otherwise it is vulnerable.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped8.5.148.13.68.16.1
Upgrade Jira to version 8.5.14, 8.13.6, or 8.16.1 or later to patch the vulnerability.
Upgrade to 8.16.1 or later (or the current LTS version 8.13.x for stability)
- 1. Take a complete backup of your Jira database and home directory
- 2. Review Jira upgrade documentation and check compatibility with your current Java version and plugins
- 3. Test the upgrade in a staging environment before applying to production
- 4. Download the appropriate fixed version (8.5.14, 8.13.6, or 8.16.1) from the Atlassian website
- 5. Stop your Jira service
- 6. Run the installer or extract the upgrade files to your Jira installation directory
- 7. Start Jira and verify the upgrade was successful
- 8. Test critical functionality and confirm the /WEB-INF/web.xml path traversal is no longer accessible
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Jira Data Center
Exploited in the wild — priority engagement
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-26086 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-26086 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data