CVE-2022-26134

In 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.

CVSS: 9.8Criticalscored by CISA
Exploited in the wild: Yes, in CISA KEV since 2 Jun 2022CISA deadline for US federal agencies: 6 Jun 2022known use in ransomware campaignspublic exploit code
EPSS: > 99.9%chance of exploitation in the next 30 daystop 0.1% of scored CVEsFIRST score of 11 Nov 2026
Fix: Patch availablesee the advisories in the references
Published: 3 Jun 2022analysed here 12 Nov 2026

Do first. Immediately block all internet traffic to and from affected products AND apply the update per vendor instructions [https://confluence.atlassian.com/doc/confluence-security-advisory-2022-06-02-1130377146.html] OR remove the affected products by the due date on the right. Note: Once the update is successfully deployed, agencies can reassess the internet blocking rules. (CISA's required action for this KEV entry)

Summary

Triage

Exploitable: At runtime
Attack vector: network
Weakness: CWE-917 Common Weakness
Can a WAF block it?: Partly. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Product	Affected versions	Vendor says fixed in
Atlassian Confluence Data Center	>= next of 1.3.0 and < unspecified< 7.4.17>= 7.13.0 and < unspecified< 7.13.7>= 7.14.0 and < unspecified< 7.14.3>= 7.15.0 and < unspecified< 7.15.2>= 7.16.0 and < unspecified< 7.16.4>= 7.17.0 and < unspecified< 7.17.4>= 7.18.0 and < unspecified< 7.18.1Vendor says fixed in: not stated	Not stated by the vendor
Atlassian Confluence Server	>= next of 1.3.0 and < unspecified< 7.4.17>= 7.13.0 and < unspecified< 7.13.7>= 7.14.0 and < unspecified< 7.14.3>= 7.15.0 and < unspecified< 7.15.2>= 7.16.0 and < unspecified< 7.16.4>= 7.17.0 and < unspecified< 7.17.4>= 7.18.0 and < unspecified< 7.18.1Vendor says fixed in: not stated	Not stated by the vendor

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

atlassian:confluence_data_center
atlassian:confluence_server

Fix and mitigation

WAF and other mitigations

Can a WAF block it? Partly. Azure WAF publishes WAF a rule written for this CVE. Such rules block the known exploit requests and buy time, but attackers can change the request to get past them, so they do not replace the patch.

Azure WAF · 1 rule
- 932130 · Critical - 5

Also consider: patch · enable the vendor rule in block mode

Based on WAF vendor rules published for this CVE. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog: Listed since 2 Jun 2022. Known use in ransomware campaigns.
CISA due date: 6 Jun 2022, the remediation deadline for US federal agencies
CISA required action: Immediately block all internet traffic to and from affected products AND apply the update per vendor instructions [https://confluence.atlassian.com/doc/confluence-security-advisory-2022-06-02-1130377146.html] OR remove the affected products by the due date on the right. Note: Once the update is successfully deployed, agencies can reassess the internet blocking rules.
Public exploit code: Yes: 1 on Exploit-DB · 1 Metasploit module · 72 GitHub proofs of concept · 1 Nuclei template
CISA SSVC: exploitation active, automatable yes, technical impact totalAssessed by CISA 4 Feb 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

and 68 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

31 May 2022First public exploit or proof of concept
2 Jun 2022Added to CISA KEV (exploited in the wild)2 days later
3 Jun 2022Published2 days later
6 Jun 2022CISA remediation due date (US federal agencies)2 days later
4 Feb 2025CISA SSVC assessment: exploitation active975 days (about 3 years) later
21 Oct 2025CVE record last updated259 days (about 9 months) later
12 Nov 2026Analysed by vulneraibility.com387 days (about 1 year) later

CVSS vector

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

Metric	Value	What it means
Attack vector	NetworkReachable over the internet or any routable network.	Reachable over the internet or any routable network.
Attack complexity	LowRepeatable attack, no special conditions.	Repeatable attack, no special conditions.
Privileges required	NoneThe attacker needs no prior access.	The attacker needs no prior access.
User interaction	NoneNo victim action needed.	No victim action needed.
Scope	UnchangedImpact stays within the vulnerable component.	Impact stays within the vulnerable component.
Confidentiality	HighTotal data disclosure possible.	Total data disclosure possible.
Integrity	HighComplete modification possible.	Complete modification possible.
Availability	HighFull outage possible.	Full outage possible.

Common questions

Is CVE-2022-26134 being exploited?

Yes. CVE-2022-26134 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2022-26134?

CVE-2022-26134 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2022-26134?

Yes. A fix has been recorded for CVE-2022-26134. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2022-26134 affect?

CVE-2022-26134 affects atlassian:confluence_data_center, atlassian:confluence_server. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVD CVE.org CVE Details Source

7 references in the CVE record, grouped by the tags the record gives them.

Where the data on this page comes from

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
CISA KEV catalog: exploitation, date added, due date
CISA Vulnrichment (ADP): SSVC decision points
FIRST EPSS: exploit probability and percentile
Exploit-DB: published exploits
Metasploit Framework: exploit and scanner modules
Nuclei templates: detection templates
PoC-in-GitHub: GitHub repositories that claim a proof of concept

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.