Skip to main content
VulnerabilityPublished

CVE-2026-21593: Atlassian Crucible Data Center · OS Command Injection

Affects Atlassian Crucible Data CenterSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.7 High.

Data as of 17 Nov 2026, 18:22 UTC

CVSS 4.0 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (atlassian)CVSS 4.07.7
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
AtlassianCrucible Data CenterAffected
  • =4.9.0 to 4.9.15
Fixed in–
AtlassianCrucible ServerAffected
  • =4.9.0 to 4.9.15
Fixed in–
AtlassianFisheye Data CenterAffected
  • =4.9.0 to 4.9.15
Fixed in–
AtlassianFisheye ServerAffected
  • =4.9.0 to 4.9.15
Fixed in–

AI-suggested

Atlassian recommends upgrading affected Fisheye and Crucible Data Center and Server instances to version 4.9.16 or later. Users unable to upgrade immediately should plan to do so as soon as possible. No other mitigations or temporary fixes are indicated in the advisory.

Description

CVE-2026-21593 is a high severity OS Command Injection vulnerability affecting Atlassian Crucible Data Center and Server versions starting from 4.9.0. It allows an authenticated attacker with low privileges to execute arbitrary commands on the affected system. Atlassian recommends upgrading to version 4.9.16 or later to remediate this issue.

References

Community reviews

Loading reviews…