{"slug": "hacking-muse-stealing-private-chats-through-browser-use", "title": "Hacking Muse: Stealing Private Chats Through Browser Use", "summary": "NebuSec researchers demonstrated that an attacker-controlled webpage could steal Meta Muse users' conversation history and stored memories without triggering the AI assistant's network approval prompts, then escape the agent's runtime container via a shared Linux kernel vulnerability to gain root privileges in the underlying user VM. The escape exposed Muse's secure credential storage and other resources Meta had intentionally isolated from the agent, and the team also altered stored memories and chat history. The findings target Meta's layered defenses — per-user VMs, a runtime container, and the Sentinel service that monitors outbound traffic and enforces approval policies — and raise the question of whether agent sandboxes are strong enough to protect credentials against real-world attacks.", "body_md": "[Technical writeupInside Meta MuseBrowser, Sentinel and the Shared-Kernel BoundaryRead the writeup](https://nebusec.ai/research/inside-meta-muse/)\n\nThe NebuSec research team recently investigated Meta Muse, a cloud-hosted AI assistant designed to operate inside an isolated virtual machine (VM). Despite multiple layers of security, we demonstrated how an attacker-controlled webpage could lead to unauthorized access to user data, and ultimately compromise the underlying VM.\n\nAI agents are becoming deeply integrated into the applications and workflows people use every day. They can browse websites, execute code, connect to external services and access sensitive information on behalf of users. To enable these capabilities, AI platforms often give agents access to credentials, conversation histories and persistent data while relying on sandboxing and other security controls to prevent unauthorized access.\n\nThe findings raise an important question for organizations developing and deploying AI agents: **Are the security boundaries protecting user credentials and sensitive information strong enough to withstand a real-world attack?**\n\n## Key Findings\n\nOur investigation revealed several security risks with implications for AI platforms and the users who trust them with sensitive information:\n\n- **Sensitive user data could be accessed without approval.** We demonstrated how an attacker could retrieve conversation history and stored memories without triggering Muse’s network approval prompts.\n- **Persistent user information could be modified.** The attack also allowed us to alter stored memories and conversation history, creating risks beyond unauthorized data access.\n- **Container isolation didn’t prevent access to protected resources.** By exploiting a vulnerability in the shared Linux kernel, we escaped the agent’s runtime container and obtained root privileges in the underlying user VM.\n- **Credential storage became accessible.** VM-level access exposed secure credential storage and other resources that were intentionally isolated from the agent’s runtime environment.\n\nTogether, these findings demonstrate how a compromise that begins with untrusted web content can extend to sensitive resources outside an AI agent’s intended security boundaries.\n\n## Why AI Agents Create New Risks for User Credentials\n\nTraditional applications operate within defined permissions and workflows. But AI agents introduce a different security model. An agent may need to access email, documents, collaboration platforms and other services to complete tasks on behalf of a user. These integrations often require credentials or authentication tokens that allow the agent to interact with external systems.\n\nThis access makes agents useful. But it also makes them attractive targets.\n\nA compromised AI agent may provide an attacker with more than access to a single application. Depending on its permissions and integrations, it could expose sensitive information or provide a path to other connected services.\n\nThis is why protecting the execution environment matters.\n\nSecurity controls must do more than prevent unauthorized actions by the agent itself. They must also protect the credentials and information the agent can access if one of its underlying components is compromised.\n\nIn Muse’s case, Meta implemented multiple layers of protection intended to enforce those boundaries.\n\nOur research showed how those protections could be crossed.\n\n## How Muse’s Security Boundaries Were Compromised\n\nMuse was designed with a [layered security architecture](https://nebusec.ai/research/inside-meta-muse/#high-level-security-design-of-muse). Each user’s agent operated inside a dedicated VM, with an additional runtime container separating the agent from more privileged resources.\n\nThe architecture also included Sentinel, a service responsible for monitoring outbound network traffic and enforcing approval policies, and a separate credential management service intended to keep real connector credentials outside the agent’s execution environment.\n\nThese protections served three distinct purposes:\n\n1. Container isolation restricted access to the underlying system.\n2. Network enforcement controlled outbound communications.\n3. Credential separation limited direct access to authentication secrets.\n\nHowever, the effectiveness of this architecture depended on maintaining the boundaries between those components.\n\nOur investigation demonstrated how an attacker could move across them.\n\n### From a Malicious Webpage to Unauthorized Data Access\n\nThe attack began with a vulnerability in the Chromium browser used by Muse for tasks like generating PDFs and documents. By having the agent export an attacker-controlled webpage, we achieved code execution inside its runtime container.\n\nAt this stage, Muse’s security controls continued to [restrict access to external networks](https://nebusec.ai/research/inside-meta-muse/#sentinel-approval-prompt) and privileged resources. However, our analysis of Sentinel revealed weaknesses in how outbound requests were classified and inspected. We demonstrated that sensitive information, including conversation history and stored memories, could be transmitted to an external server without triggering an approval prompt.\n\nWe could also modify the agent’s stored memories and conversation history. This meant an attacker could potentially compromise both the confidentiality and integrity of information that users expected Muse to protect.\n\n### From Container Compromise to Credential Exposure\n\nThe next question was whether the attacker could move beyond the runtime container and access resources protected at the VM level.\n\nUsing NebuSec’s automated exploit generation framework, we developed Linux kernel exploits that allowed us to escape the container and obtain root privileges in the underlying user VM. The escape exposed resources that had been intentionally kept outside the agent’s runtime environment, including persistent storage, secure credential storage and Sentinel itself.\n\nIt also allowed outbound network communications that were no longer subject to Sentinel’s container-level enforcement. The significance of this result was not simply that we achieved a container escape.\n\n**The container escape undermined the isolation boundary protecting sensitive user resources, including credential storage.**\n\nFor organizations building AI agents, this is the more consequential risk: A vulnerability in the execution environment can become a path to information and privileges that the agent was never intended to access directly.\n\nThe compromise remained within the individual user’s VM. We did not demonstrate an escape into the underlying hypervisor host or other tenants’ environments.\n\nOur [separate technical research](https://nebusec.ai/research/inside-meta-muse/) provides a detailed analysis of the browser vulnerability, Sentinel enforcement and kernel exploitation techniques used in this investigation.\n\n## Why Muse’s Security Architecture Wasn’t Enough\n\nMuse’s design incorporated several established security practices, including sandboxing, privilege separation, credential isolation and network monitoring. These controls provided meaningful protection. For example, obtaining root privileges inside the runtime container didn’t immediately grant unrestricted network access or access to the underlying VM.\n\nThe browser vulnerability created an initial execution path, and weaknesses in network policy enforcement allowed unauthorized data transfers. Kernel exploitation then enabled access to resources beyond the container’s intended reach.\n\nEach stage weakened a different part of the security architecture.\n\n**Our investigation illustrates the fact that security controls can work as designed while still failing to prevent a complete attack chain.**\n\nSeparating credentials from an agent’s runtime environment reduces risk, but that protection depends on the integrity of the boundary separating those resources. Network monitoring can restrict unauthorized communications, but its effectiveness depends on where enforcement occurs and whether compromised processes can operate outside that boundary.\n\nSecurity leaders should ask: “Do my protections remain effective when an attacker has already compromised part of the system?”\n\n## What This Means for Organizations Building AI Agents\n\nThe Muse findings are relevant to any organization developing AI agents that interact with sensitive information, enterprise applications or privileged services. As agents gain more capabilities, their execution environments become important security boundaries.\n\n**Consider these best practices for protecting AI agents:**\n\n1. \n**Protect credentials beyond the agent’s runtime.**[Keeping credentials outside an agent’s immediate execution environment](https://nebusec.ai/research/inside-meta-muse/#security-services-outside-the-container) is an important safeguard, but it doesn’t eliminate the risk of credential exposure.Consider what happens if an attacker escapes the agent’s sandbox or gains access to a more privileged part of the system. Credential protections should be designed to limit the consequences of that compromise, including restricting credential scope, access and opportunities for misuse.\n2. \n**Evaluate security across the entire execution environment.** AI agent security extends beyond the model and its application-level permissions. Browsers, containers, operating systems, network enforcement services and credential management systems all contribute to the security of the platform.A vulnerability in one component can create opportunities to compromise another. Security assessments should examine how these components interact and whether their boundaries can withstand chained attacks.\n3. \n**Validate whether vulnerabilities can actually be exploited.** Identifying vulnerabilities is important, but understanding their impact is just as critical. In the Muse investigation, the kernel environment was customized and didn’t expose the target kernel image to the runtime container.Our automated exploit generation framework produced exploits that succeeded in more than 99.9% of test runs. This allowed us to demonstrate that the kernel vulnerabilities could be used to cross a meaningful security boundary and expose resources that were otherwise inaccessible. For organizations responsible for securing complex, interconnected environments, this distinction matters. Knowing that a vulnerability exists is different from knowing whether it can be used to access sensitive data, compromise credentials or escalate privileges in a deployed system.\n\n## Securing AI Agents Requires Understanding Real-World Exploitability\n\nOur Muse investigation began with a malicious webpage and ended with access to protected resources in the underlying user VM, including secure credential storage. Our findings highlight how vulnerabilities across browsers, network enforcement and the Linux kernel can be chained to undermine security controls designed to protect sensitive user information.\n\nFor organizations building AI agents, the lesson is clear: Isolating an agent is only part of the challenge. The underlying security boundaries must also withstand attacks that attempt to move beyond the agent’s intended permissions.\n\nWe reported our findings to the Muse team, and all exploits described in our research had been patched by the time of publication.\n\n**Read the full technical research:** [Inside Meta Muse: Browser, Sentinel and the Shared-Kernel Boundary](https://nebusec.ai/research/inside-meta-muse/)", "url": "https://wpnews.pro/news/hacking-muse-stealing-private-chats-through-browser-use", "canonical_source": "https://nebusec.ai/research/meta-muse-credential-exposure/", "published_at": "2026-11-22 11:39:10+00:00", "updated_at": "2026-11-22 12:11:59.212649+00:00", "lang": "en", "topics": ["ai-agents", "ai-safety", "ai-policy"], "entities": ["Meta", "Muse", "NebuSec", "Sentinel"], "also_reported_by": [], "takeaway": null, "recommendation": null, "alternates": {"html": "https://wpnews.pro/news/hacking-muse-stealing-private-chats-through-browser-use", "markdown": "https://wpnews.pro/news/hacking-muse-stealing-private-chats-through-browser-use.md", "text": "https://wpnews.pro/news/hacking-muse-stealing-private-chats-through-browser-use.txt", "jsonld": "https://wpnews.pro/news/hacking-muse-stealing-private-chats-through-browser-use.jsonld"}}