dbcve.org
CrowdApplication · Atlassian

CVE-2026-21569

HIGH · 7.9 CVSS v3.0 Published 2026-01-28
Fix available
A fix is available. Upgrade to 7.1.3 or later.
See remediation →
85/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
This High severity XXE (XML External Entity Injection) vulnerability was introduced in version 7.1.0 of Crowd Data Center and Server. This XXE (XML External Entity Injection) vulnerability, with a CVSS Score of 7.9, allows an authenticated attacker to access local and remote content which has high impact to confidentiality, low impact to integrity, high impact to availability, and requires no user interaction. Atlassian recommends that Crowd Data Center and Server customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions: * Crowd Data Center and Server 7.1: Upgrade to a release greater than or equal to 7.1.3 See the release notes (https://confluence.atlassian.com/crowd/crowd-release-notes-199094.html). You can download the latest version of Crowd Data Center and Server from the download center (https://www.atlassian.com/software/crowd/download-archive). This vulnerability was reported via our Atlassian (Internal) program.

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 confidence

This is an XXE (XML External Entity Injection) vulnerability in Atlassian Crowd Data Center and Server affecting version 7.1.0. An authenticated attacker can exploit insecure XML parsing to inject malicious external entities, enabling unauthorized access to local file system resources and remote content. The vulnerability has high confidentiality and availability impact with no user interaction required.

MitigationUpgrade to Crowd Data Center/Server 7.1.3 or later, or to the latest version, to remediate this vulnerability.

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
CrowdApplication
Affected:>= 7.1.0, < 7.1.3

CVSS 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
High
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
High

CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Atlassian Crowd installation
    Locate the Crowd installation directory and identify the crowd-distribution JAR or WAR file, or check the application startup logs for 'Atlassian Crowd' branding.
    Affected if Atlassian Crowd Data Center or Server is not installed.
  2. Check Crowd version number
    Examine the 'atlassian Crowe-version' file in the Crowd home directory, or view the version in the Crowd administration console under 'General Configuration' or 'About'.
    Affected if The installed version is 7.1.0, 7.1.1, or 7.1.2 (versions >= 7.1.0 and < 7.1.3).
  3. Verify XML import or user directory sync feature is in use
    Check Crowd administration for configured user directories that use XML-based import, or look for crowd.xml, userexport.xml, or similar XML import functionality in the 'Directory Management' section.
    Affected if XML import or directory synchronization features that process XML are not configured or used.
  4. Confirm attacker has authenticated access
    Review which users or groups have permissions to access XML import, directory sync, or API endpoints that accept XML input in Crowd.
    Affected if No authenticated users have access to XML parsing endpoints.

The environment is affected if Atlassian Crowd version 7.1.0 through 7.1.2 is installed and authenticated users can access XML import or parsing features.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.1.3 or later
Fixed in 7.1.3
Interim mitigation

Upgrade to Crowd Data Center/Server 7.1.3 or later, or to the latest version, to remediate this vulnerability.

Recommended fix High confidence

Crowd 7.1.3 or later (latest available version recommended)

  1. Back up your Crowd Data Center or Server installation, including the database and configuration files
  2. Stop the Crowd server
  3. Download Crowd version 7.1.3 or later from the Atlassian download center (https://www.atlassian.com/software/crowd/download-archive)
  4. Extract and install the new version following Atlassian's upgrade documentation
  5. Migrate any necessary configuration files from the previous installation to the new version
  6. Start the Crowd server
  7. Verify the upgrade was successful and the application is functioning correctly
Caveat Minor version upgrades within the 7.x line typically do not introduce breaking changes; review release notes for any specific considerations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Crowd Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21569 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-21569 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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