CVE
Atlassian remote command execution via OS command injection
Affects Crucible and Fisheye Data Center or Server versions 4.9.0 through 4.9.15, where an authenticated attacker can run commands on the server. Fixed in 4.9.16.
Written by a model from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in 4.9.16
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Crucible or Fisheye Data Center or Server installs Versions 4.9.0 through 4.9.15 of the 4.9 line
- 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? →
- 17/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? →
- Specific setups only
- 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: no
- Technical impact: total
Summary
Atlassian's Fisheye and Crucible Data Center and Server products contain an OS command injection flaw that lets an authenticated attacker with low privileges run arbitrary commands. The attacker can reach it remotely over the network, and no user action is needed.
Original description
This High severity OS Command Injection vulnerability known as CVE-2026-21593 was introduced in version 4.9.0.
This OS Command Injection vulnerability, with a CVSS Score of 7.7 and a CVSS Vector of CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N allows an authenticated attacker to execute arbitrary commands.
Atlassian recommends that Fisheye and Crucible Data Center and Server customers upgrade to the latest version. If you are unable to do so, upgrade your instance to the specified supported fixed version:
Fisheye and Crucible 4.9: Upgrade to a release greater than or equal to 4.9.16
See the Fisheye release notes (https://confluence.atlassian.com/fisheye/fisheye-release-notes-965552419.html) and Crucible release notes (https://confluence.atlassian.com/crucible/crucible-releases-298977378.html). You can download the latest version of Fisheye and Crucible from the Crucible Download Archives (https://www.atlassian.com/software/crucible/download-archives).
Who should check
Teams running Crucible or Fisheye 4.9.0 through 4.9.15, Data Center or Server editions, that need to upgrade to 4.9.16 or later.
“This High severity OS Command Injection vulnerability known as CVE-2026-21593 was introduced in version 4.9.0.”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 7.7, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Crucible or Fisheye Data Center or Server installs Versions 4.9.0 through 4.9.15 of the 4.9 lineUpgrade 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-21593 (This High severity OS Command Injection vulnerability known as CVE-2026-21593 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-21593 (entry last updated 2026-11-17):
Affected:
- Atlassian Crucible Data Center: versions 4.9.0 to 4.9.15
- Atlassian Crucible Server: versions 4.9.0 to 4.9.15
- Atlassian Fisheye Data Center: versions 4.9.0 to 4.9.15
- Atlassian Fisheye Server: 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 or Fisheye Data Center or Server installs (source: https://jira.atlassian.com/browse/CRUC-8794)
- Versions 4.9.0 through 4.9.15 of the 4.9 line (source: https://jira.atlassian.com/browse/CRUC-8794)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-21593 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-21593 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-8794
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-21593
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-21593"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Atlassian Crucible Data Center
4.9.0 to 4.9.15
- Atlassian Crucible Server
4.9.0 to 4.9.15
- Atlassian Fisheye Data Center
4.9.0 to 4.9.15
- Atlassian Fisheye Server
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-21593
Is CVE-2026-21593 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?
An authenticated attacker can execute arbitrary commands on the server because of an OS command injection flaw. The issue was introduced in version 4.9.0.Source: jira.atlassian.com
Which versions are affected by CVE-2026-21593?
Crucible Data Center: version 4.9.0 to 4.9.15. Crucible Server: version 4.9.0 to 4.9.15. Fisheye Data Center: version 4.9.0 to 4.9.15. Fisheye Server: version 4.9.0 to 4.9.15.Source: cve.now feed data
Am I affected, and how do I check?
Crucible and Fisheye, in both Data Center and Server editions, are affected in the 4.9.0 through 4.9.15 range of the 4.9 line. A reader can check whether an installed version falls in that range against the product's version information.Source: jira.atlassian.com
How do I fix CVE-2026-21593?
Upgrade to version 4.9.16 or later, which is the release the advisory names as fixed.Source: jira.atlassian.com