Threats / Atlassian / CVE-2022-26134
CVE-2022-26134
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Atlassian Confluence Server/Data Center vulnerability
Atlassian Confluence Server and Data Center are vulnerable to unauthenticated remote code execution via expression language injection, enabling attackers to execute arbitrary code without authentication.
Verdict
Today item, not a backlog item.
This vulnerability poses critical risk due to unauthenticated exploitation, active wild exploitation, and documented ransomware campaign activity. Organizations running affected Confluence versions require immediate patching.
CISA KEV Yes · 2022-06-023Ransomware use Flagged3EPSS 0.99999 (verify live)4Exploit Weaponized · public PoC5
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
1125 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-06-02), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.99999 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Atlassian, Confluence Server/Data Center. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-917 Expression Language Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious request exploiting the expression language injection flaw to bypass authentication controls.
Business
Attackers gain initial access to internal collaboration infrastructure without valid credentials, establishing a foothold for lateral movement.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute arbitrary code on the Confluence server to establish persistence and deploy secondary payloads.
Business
Attackers achieve code execution within the network perimeter, enabling data exfiltration, system compromise, and ransomware deployment.
3
Lateral reach — past segmentation narrative 3
Attacker
I leverage server access to move laterally across connected systems and escalate privileges within the environment.
Business
Ransomware operators encrypt critical business data and systems, disrupting operations and demanding payment for decryption keys.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05