Atlassian Rovo Can Be Tricked Into Sending Jira and Confluence Data to Attackers

Summary: Attacker-controlled instructions can make Atlassian's Rovo assistant collect Jira or Confluence data that a signed-in user can access, then send it to an outside server. Two security firms found that behavior independently, by different routes. Only one of those routes is confirmed closed. PromptArmor, an AI security firm, hid the instructions in content Rovo reads. It said an uploaded file was

Artificial intelligence assistants are rapidly becoming embedded within enterprise collaboration platforms, helping employees search documentation, summarize conversations, automate workflows, answer questions, and retrieve information spread across thousands of internal systems. Their greatest strength is context: by connecting to knowledge bases, ticketing systems, source code repositories, chat platforms, cloud storage, and business applications, AI assistants can provide answers that would otherwise require hours of manual searching.

That same capability, however, also creates one of the most significant security challenges facing enterprise AI.

Security researchers have demonstrated that Atlassian Rovo, the company’s AI-powered enterprise assistant, can be manipulated through carefully crafted prompt injection techniques into revealing sensitive information or performing actions outside its intended purpose. The findings reinforce a growing concern across the artificial intelligence industry: as AI agents gain broader access to enterprise data, protecting the reasoning process itself becomes just as important as protecting the underlying infrastructure.

Unlike traditional software vulnerabilities, prompt injection does not exploit programming errors or memory corruption.

Instead, attackers manipulate the natural language instructions guiding an AI system’s reasoning. By embedding carefully designed prompts inside documents, knowledge bases, issue trackers, comments, or other information sources that the AI later processes, attackers attempt to override or influence the model’s original instructions.

The AI follows the malicious guidance because it cannot inherently distinguish between trusted operational instructions and attacker-controlled content.

Researchers showed that Rovo could be influenced by malicious prompts hidden within enterprise content, potentially causing the assistant to expose confidential information, ignore previous safety instructions, or behave in ways inconsistent with organizational expectations.

Importantly, the attack targets the AI’s decision-making process rather than the security of Atlassian’s underlying infrastructure.

No authentication bypass or software exploit is required.

The assistant behaves according to its reasoning model, but that reasoning has been intentionally manipulated through deceptive contextual input.

This distinction has become central to modern AI security.

Traditional cybersecurity focused on protecting systems against malicious code.

Agentic AI increasingly requires protecting systems against malicious language.

Enterprise assistants like Rovo are designed to consume enormous quantities of organizational information.

They analyze Confluence documentation, Jira tickets, project plans, engineering notes, architectural diagrams, meeting summaries, code repositories, and internal knowledge bases to answer employee questions. This contextual awareness dramatically increases productivity by eliminating the need to manually search multiple disconnected systems.

It also means that nearly every piece of enterprise content becomes part of the AI’s reasoning environment.

If an attacker successfully inserts malicious instructions into that environment, they may influence future responses without directly interacting with the victim.

This is why prompt injection is often compared to SQL injection—but with natural language replacing database commands.

Instead of manipulating program execution through crafted syntax, attackers manipulate AI reasoning through carefully constructed instructions that appear inside otherwise legitimate content.

The challenge becomes particularly difficult because modern language models are intentionally designed to interpret and follow natural language.

Distinguishing between information intended for the user and hidden instructions intended for the AI remains an active area of research.

Enterprise collaboration platforms present especially attractive targets.

Unlike isolated chatbots, AI assistants integrated into workplace environments frequently possess permissions allowing them to search internal documentation, retrieve confidential files, summarize conversations, access project management systems, generate reports, and interact with third-party business applications.

Their value derives from broad organizational visibility.

That same visibility amplifies the potential impact of prompt injection.

A manipulated assistant may not simply provide an incorrect answer. It could reveal information from unrelated projects, disclose confidential documentation, expose internal processes, retrieve sensitive business records, or perform unintended actions through connected enterprise tools.

Researchers increasingly view AI assistants as privileged organizational identities.

Like administrators or service accounts, they possess access extending across multiple business systems while acting on behalf of human users.

Consequently, securing AI assistants requires applying many of the same principles already used for privileged identity management.

Least-privilege access becomes essential.

An AI agent should receive only the minimum permissions necessary to complete its assigned responsibilities. Broad organizational visibility may improve answer quality but also increases the consequences of successful manipulation.

Context isolation provides another important defense.

Rather than allowing all retrieved information to influence every response equally, emerging architectures increasingly separate trusted system instructions from untrusted user-generated content. This reduces opportunities for external documents to override the assistant’s operational policies.

Input validation is becoming equally important.

Enterprise AI systems increasingly analyze retrieved documents before presenting them to language models, attempting to identify suspicious prompt-like language designed specifically to manipulate reasoning rather than convey information.

Although such detection remains imperfect, it represents an important layer of defense.

The Atlassian findings also reinforce a broader shift occurring throughout cybersecurity.

As organizations deploy increasingly autonomous AI agents capable of interacting with enterprise systems, security concerns move beyond protecting software and toward protecting cognition.

Researchers now investigate attacks targeting memory systems, planning modules, retrieval mechanisms, tool selection, reasoning chains, context windows, and orchestration frameworks alongside conventional software vulnerabilities.

Artificial intelligence introduces an entirely new attack surface.

The industry has already seen similar prompt injection research affecting coding assistants, autonomous software engineering platforms, browser agents, cloud automation systems, document summarization tools, and retrieval-augmented generation (RAG) systems.

The Atlassian disclosure demonstrates that enterprise productivity platforms face many of the same challenges.

Importantly, prompt injection does not indicate that AI systems are fundamentally insecure.

Rather, it reflects the reality that language models were originally optimized for understanding instructions, not determining which instructions deserve trust.

Building that distinction into future AI architectures has become one of the industry’s highest priorities.

Organizations adopting enterprise AI should therefore view prompt injection as an expected operational risk rather than an exceptional event.

Security controls should assume that untrusted content may eventually reach AI systems and design architectures capable of limiting the resulting impact.

Comprehensive logging, permission boundaries, human approval for high-risk actions, context separation, behavioral monitoring, and continuous security testing all become increasingly important as AI assistants gain greater operational authority.

The research involving Atlassian Rovo illustrates how enterprise security is entering a new phase.

Protecting data alone is no longer sufficient.

Organizations must also protect the reasoning processes through which artificial intelligence interprets that data, makes decisions, and acts on behalf of users.

As AI assistants become integral components of enterprise productivity, defending against attacks that manipulate thought rather than software may become one of cybersecurity’s defining challenges for the decade ahead.

Key facts

  • Atlassian's Rovo assistant can be tricked into sending accessible Jira and Confluence data to attackers
  • Two security firms independently discovered this behavior through different methods
  • PromptArmor hid malicious instructions within content that Rovo processes, such as uploaded files
  • Only one of the identified attack routes has been confirmed as closed

Why it matters

This vulnerability in Atlassian Rovo highlights potential risks for enterprise data security, particularly within ecosystems that integrate AI assistants. If unaddressed, such flaws could enable attackers to gain unauthorized access to sensitive internal information stored in widely used collaboration and project management tools, potentially leading to significant data breaches and operational disruption.