Atlassian Rovo Exfiltrates Data, Bypassing Controls
- ID
- 11809
- Status
- summarized
- Published
- 06 Aug 2026, 1:23 AM
- Fetched
- 07 Aug 2026, 9:51 PM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://www.promptarmor.com/resources/atlassian-rovo-exfiltrates-data
- Source URL
- https://hnrss.org/best
Summary
- Score
- 7.5
- Created
- 07 Aug 2026, 10:57 PM
- Tags
- Audience
- developersai_agent_userssaas_founders
What happened
PromptArmor disclosed a zero-click data exfiltration vulnerability in Atlassian Rovo AI on May 23rd; after 2+ months with no fix from Atlassian, they went public. The attack uses indirect prompt injection via uploaded files or external data to manipulate Rovo's URL retrieval tool into sending Jira tickets and Confluence docs to an attacker-controlled URL, and it works even when an organization has disabled Rovo's web search setting.
Why it matters
If your team uses Atlassian Rovo AI on Jira or Confluence, disabling web search does not protect you—the URL retrieval tool remains active and can be weaponized to leak ticket and doc contents. Treat any file or external data source fed into Rovo as untrusted input, and assume sensitive project data in Jira/Confluence could be exfiltrated until Atlassian patches this.
Discussion angle
This is a concrete example of why agent URL-retrieval tools need allowlisting—discuss how the same class of vulnerability applies to any AI agent your team builds that can construct and fetch arbitrary URLs from untrusted context.