Confluence Data CenterApplication · Atlassian
CVE-2022-26134
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 · uneditedIn affected versions of Confluence Server and Data Center, an OGNL injection vulnerability exists that would allow an unauthenticated attacker to execute arbitrary code on a Confluence Server or Data Center instance. The affected versions are from 1.3.0 before 7.4.17, from 7.13.0 before 7.13.7, from 7.14.0 before 7.14.3, from 7.15.0 before 7.15.2, from 7.16.0 before 7.16.4, from 7.17.0 before 7.17.4, and from 7.18.0 before 7.18.1.
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 confidenceOGNL injection vulnerability in Atlassian Confluence Server and Data Center allows unauthenticated attackers to inject and execute arbitrary OGNL expressions, achieving remote code execution on the underlying server.
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
Confluence Data CenterApplication
>= 1.3, < 7.4.17>= 7.13.0, < 7.13.7>= 7.14.0, < 7.14.3>= 7.15.0, < 7.15.2>= 7.16.0, < 7.16.4>= 7.17.0, < 7.17.4= 7.18.0
Confluence ServerApplication
>= 1.3, < 7.4.17>= 7.13.0, < 7.13.7>= 7.14.0, < 7.14.3>= 7.15.0, < 7.15.2>= 7.16.0, < 7.16.4>= 7.17.0, < 7.17.4= 7.18.0CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Confluence version via web interfaceLog into the Confluence administration console and navigate to 'About Confluence' (usually at /admin/aboutconfluence.action) or check the footer of any Confluence page which typically displays the version numberAffected if The displayed version falls within any of these ranges: >=1.3 and <7.4.17; >=7.13.0 and <7.13.7; >=7.14.0 and <7.14.3; >=7.15.0 and <7.15.2; >=7.16.0 and <7.16.4; >=7.17.0 and <7.17.4; or equals exactly 7.18.0
-
Identify Confluence version from local configurationOn the Confluence server, locate the confluence.cfg.xml file (typically in <confluence-home>/confluence.cfg.xml or /var/atlassian/application-data/confluence/) and read the <buildNumber> or <version> elementAffected if The version number extracted from the configuration file matches any of the affected version ranges listed above
-
Identify Confluence product type (Server vs Data Center)Check the same configuration file for the <edition> element or look for Data Center-specific files such as cluster-node.properties in <confluence-home>/cluster/ which indicates Data Center deploymentAffected if The product is Confluence Server or Confluence Data Center and the version is within the affected ranges
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.4.177.13.77.14.3
Apply vendor patches for affected versions (upgrade to 7.4.17, 7.13.7, 7.14.3, 7.15.2, 7.16.4, 7.17.4, or 7.18.1 and later) or implement network-level access controls to restrict unauthenticated access to Confluence endpoints if immediate patching is not feasible.
Upgrade to the minimum fixed version for your branch: 7.4.17, 7.13.7, 7.14.3, 7.15.2, 7.16.4, 7.17.4, or 7.18.1 (or latest stable)
- 1. Identify the current Confluence version by checking the Confluence administration console or using the /about link on the Confluence login page
- 2. Determine which version branch your current installation falls into (1.3.x to 7.4.x, 7.13.x, 7.14.x, or 7.15.x)
- 3. Take a complete backup of the Confluence database and home directory
- 4. Download the appropriate fixed version from the Atlassian downloads page: 7.4.17, 7.13.7, 7.14.3, 7.15.2, 7.16.4, 7.17.4, or 7.18.1
- 5. Stop the Confluence service
- 6. Run the installer or extract the upgrade files according to Atlassian's upgrade documentation
- 7. Start the Confluence service and verify the upgrade was successful
- 8. Confirm the instance is running the patched version in the administration console
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Confluence Data Center
Exploited in the wild — priority engagement
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26134 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-26134 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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