CVE
Atlassian Crucible Data Center path traversal exposes WEB-INF config files
Affects Crucible and Fisheye versions 4.9.0 through 4.9.15. The advisory names 4.9.16 as the fixed release.
Written by a model from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
- Exploited
- No known exploitation
- Fix
- Fixed in 4.9.16
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.9.16.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 28/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
Atlassian Crucible Data Center and Fisheye Data Center contain a path traversal flaw that lets an attacker read protected application configuration files, including files under WEB-INF. An attacker can reach it remotely over the network without logging in.
Original description
This High severity Path Traversal (Arbitrary Read/Write) vulnerability known as CVE-2026-21592 was introduced in version 4.9.0.
This Path Traversal (Arbitrary Read/Write) vulnerability, with a CVSS Score of 7.7 and a CVSS Vector of CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P allows an unauthenticated attacker to disclose protected application configuration files, which has high impact to confidentiality, no impact to integrity, no impact to availability, and requires no user interaction.
Atlassian recommends that Crucible Server customers upgrade to the latest version. If you are unable to do so, upgrade your instance to the specified supported fixed version: Crucible Server 4.9: Upgrade to a release greater than or equal to 4.9.16
See the Crucible Server release notes ([https://confluence.atlassian.com/crucible/crucible-releases-298977378.html]). You can download the latest version of Crucible from the Crucible Download Archives ([https://www.atlassian.com/software/crucible/download-archives]).
The following description summarizes the vulnerability reported via our Penetration Testing program:
Crucible do not account for path parameters when validating protected paths requested through the static-resource route. A crafted path segment passes validation, after which Jetty removes the path parameter during dispatch and resolves the request to a protected resource. This can expose files under WEB-INF and permit direct invocation of admin-area JSPs outside the normal interceptor and administrative password checks. An ordinary authenticated user can exploit the issue, and unauthenticated exploitation is possible when anonymous access is enabled.
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.7/10CVSS 7.7
- No patch0/5No signal
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 33 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 4.9.16.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-21592 (This High severity Path Traversal (Arbitrary Read/Write) vulnerability known as CVE-2026-21592 was introduced in version 4.9.0.), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-21592 (entry last updated 2026-11-17):
Affected:
- Atlassian Crucible Data Center: versions 4.9.0 to 4.9.15
- Atlassian Fisheye Data Center: versions 4.9.0 to 4.9.15
Fixed versions: 4.9.16.
Conditions (all must be true for the bug to be hit):
- Crucible Server or Fisheye Server version 4.9.0 through 4.9.15 (affects versions listed). (source: https://jira.atlassian.com/browse/CRUC-8793)
- Requests to the static-resource route with crafted path parameters; Jetty removes the path parameter during dispatch. (source: https://jira.atlassian.com/browse/CRUC-8793)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-21592 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-21592 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://confluence.atlassian.com/pages/viewpage.action?pageId=1874690748
- https://jira.atlassian.com/browse/CRUC-8793
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-21592
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-21592"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Atlassian Crucible Data Center
4.9.0 to 4.9.15
- Atlassian Fisheye Data Center
4.9.0 to 4.9.15
Evidence 4
Vendor advisory · 2
Establishes: Affected and fixed versions.
- Link
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-21592
Is CVE-2026-21592 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A crafted path segment passes validation, and Jetty then removes the path parameter during dispatch. This can expose files under WEB-INF and allow direct invocation of admin-area JSPs outside the interceptor and administrative password checks.Source: jira.atlassian.com
Which versions are affected by CVE-2026-21592?
Crucible Data Center: version 4.9.0 to 4.9.15. Fisheye Data Center: version 4.9.0 to 4.9.15.Source: cve.now feed data
Am I affected, and how do I check?
The listed affected versions are 4.9.0 through 4.9.15 of Crucible and Fisheye. To check, compare the installed version against that range.Source: jira.atlassian.com
How do I fix CVE-2026-21592?
Upgrade to 4.9.16 or later, the release the advisory names as the fix for Crucible Server 4.9.Source: jira.atlassian.com