Rapid7 watched attackers go from Atlassian's Confluence to a cloud warehouse in four hours
Attackers turned a 9.8-rated Confluence Data Center flaw into database, warehouse and Microsoft 365 access in about twelve hours, and Rapid7 says the tooling was likely AI-generated. The fix is 9.2.28, and every enterprise that patches in fear moves one step closer to Atlassian's cloud, the engine its fiscal 2027 guidance rests on.
Richard Tangthree-minute read
On November 13, Rapid7+11.56% — Rapid7, up 11.56 percent today, a security firm whose managed detection and response team, MDR, watches customer environments around the clock, caught an intrusion running through a customer's Confluence Data Center server 1. The flaw is CVE-2026-90436, an unauthenticated remote code execution bug in the old Apache Axis library that Apache disclosed on November 6 and CISA scores 9.8 1. It is the first exploitation of this flaw Rapid7 has observed, and Rapid7 says the attacker's scripts were likely AI-generated 1.
The fix, Confluence 9.2.28, is named in Atlassian's November bulletin, published November 17-18, which lists 318 vulnerability entries, up from 176 the month before 12.
The intrusion shows where the flaw leads
The chain matters more than the score. A Confluence server with the legacy "Remote API (XML-RPC & SOAP)" setting on accepted an unauthenticated request and ran attacker code 1. Within about three minutes, the intruder was reading Confluence's own database with its stored credentials, searching page bodies and attachments with names associated with credentials, tokens, VPN configurations and private keys, and parsing Office documents for payment card numbers 1. About four hours in, they queried a production cloud data warehouse. About twelve hours in, they signed into Microsoft+0.24% — Microsoft, up 0.24 percent today 365 with an integration service account 1.
Three minutes to Confluence's database, twelve hours to Microsoft 365
Data
| Value | |
|---|---|
| Confluence database read | 3 min |
| Cloud data warehouse queried | 4 hours |
| Microsoft 365 sign-in | 12 hours |
The automation is what compresses the timeline. Rapid7 describes commands wrapped in labeled delimiters with sequential task IDs, a structure it treats as a sign of AI-assisted tooling 1. The same automation that lets a security team triage faster lets one attacker enumerate a network in minutes, and a defense team now has to buy that automation to keep pace, not just more patches.
Who pays, and who gets paid
The enterprises running Confluence Data Center 9.x pay first: upgrade to 9.2.28 outside normal patch cycles, or turn the legacy API off 12. Confluence 10.x and Atlassian−4.24% — Atlassian, down 4.24 percent today Cloud are not affected 12.
That last fact is also the business story. Atlassian guides fiscal 2027 to about 26% cloud growth against a 16% Data Center decline, a blended 13.75%, and its stock fell about 16% after its last quarter on fears that cloud growth is slowing 35. Every scare like this one moves a migration decision inside a customer, and the evidence points one way: the flaw lives in a Data Center-only feature that 10.x and Cloud removed 35.
Atlassian's cloud growth guide steps down from the quarter it just reported
- Cloud revenue growth
- Estimate
Data
| Cloud revenue growth | |
|---|---|
| Q1 FY27 actual | 31% |
| Q2 FY27 guide (estimate) | 27% |
| FY27 guide (estimate) | 26% |
The uncomfortable part is who does the work. Atlassian gets the migration revenue; the customer's security team gets the emergency patch bill. For any team still on Data Center, the move is to treat 9.2.28 as this week's work and start the 10.x or cloud plan deliberately, before the next intrusion makes the decision for them 1.
Get Security by email, free
The breaches, flaws and security vendors AI is putting to the test. In our daily email, every weekday.






Reader comments
0 comments