This High severity Path Traversal (Arbitrary Read/Write) vulnerability known as CVE-2026-21592 was introduced in
Source GCVE Database
Public exploit available · CVSS 7.7 High : upgrade to 4.9.16 as a priority.
Data as of 17 Nov 2026, 19:52 UTC
Thin evidence
One scorer or none| CNA (atlassian) | CVSS 4.0 | 7.7 |
|---|
- Patch
- Available – fixed in 4.9.16
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:PExploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade com.atlassian.crucible/crucible-server to 4.9.16.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AtlassianCrucible Data Center | Affected
| Fixed in– |
| AtlassianFisheye Data Center | Affected
| Fixed in– |
Mavencom.atlassian.crucible/crucible-serverpkg:maven/com.atlassian.crucible/crucible-serverOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Atlassian recommends upgrading Crucible Server to version 4.9.16 or later, where this vulnerability is fixed. If upgrading immediately is not possible, customers should plan to update as soon as feasible. No other mitigations or temporary workarounds are specified. The issue is not present in versions prior to 4.9.0. Since this is not a cloud service, remediation depends on customer action.
Description
CVE-2026-21592 is a high severity path traversal vulnerability in Crucible Server introduced in version 4.9.0. It allows unauthenticated attackers to read protected application configuration files by exploiting improper validation of path parameters in the static-resource route. This can expose sensitive files under WEB-INF and permit access to admin-area JSPs without normal authentication checks. Atlassian recommends upgrading to version 4.9.16 or later to remediate this issue.