Skip to content
[ SIGNAL VERIFIED ] INDEPENDENT CYBERCRIME JOURNALISMCLASSIFIED // THE UNDERGROUND HAS A NEWSROOM / RSS
.COM
Latest News
ALL NEWS
Newsroom

Confluence Intrusion Reached Cloud Services Through Stored Credentials, Rapid7 Reports

Updated November 19: Rapid7 traces a Confluence intrusion into cloud services; CISA now lists the underlying Apache Axis flaw as known exploited.

Confluence Intrusion Reached Cloud Services Through Stored Credentials, Rapid7 Reports
PUBLISHED UPDATED November 19, 2026 at 6:00 AM EST

Update — November 19, 2026: CISA adds the underlying Axis flaw

CISA added Apache Axis CVE-2026-90436 to its Known Exploited Vulnerabilities catalog on November 18. Read our new four-flaw roundup for vendor remediation and the Confluence dependency context.

Rapid7 has expanded its reporting on exploitation of Confluence Data Center vulnerability CVE-2026-90436. The report’s November 17 update adds incident-response findings from an intrusion detected November 13, showing why an application compromise can require an investigation of connected cloud accounts.

What investigators observed

Rapid7 says the attacker searched Confluence data and attachments and used stored credentials to reach other services. Roughly four hours after the first exploit request, the attacker was querying a production cloud data warehouse; approximately twelve hours afterward, an integration service account was used to sign in to Microsoft 365.

Those timings describe the investigated incident. They do not predict a fixed timetable for every attack, establish how many organizations were affected, or prove that every exposed Confluence installation has been compromised.

Product scope and the vendor fix

Atlassian’s advisory says the vulnerability depends on the legacy Remote API being enabled on affected Confluence installations. Confluence 10.x and later and Atlassian Cloud are not affected. The vendor identifies 9.2.28 as a fixed release and recommends a fixed or unaffected supported version.

Disabling the legacy XML-RPC and SOAP Remote API is a temporary mitigation where immediate patching is not possible. Atlassian warns that doing so may interrupt scripts, automations or add-ons, so compatibility should be checked.

Investigate beyond the application

IPCRIME analysis: A recovery checklist should connect the compromised application to the credentials it could reveal. For each exposed secret, identify the destination system, the account owner and the actions that credential permits. Replace or revoke affected access through a trusted environment, then inspect destination-system logs for its use.

Preserve the chronology before rebuilding systems. A patch addresses the entry point; it does not invalidate credentials already copied from documents or confirm that downstream sessions have ended. The distinction matters most for shared integration accounts whose activity may otherwise resemble routine automation.

Featured image: conceptual IPCRIME artwork, not a photograph or screenshot of this incident or product.

Editorial note

IPCRIME distinguishes public records and documented findings from allegations, analysis and commentary. Report corrections through our contact page.