Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› Mojo
Cyber Security

Mojo

← Back to Glossary
By NHI Mgmt Group Updated October 31, 2026 Domain: Cyber Security

Mojo is Chromium’s inter-process communication system. It lets browser components exchange predefined messages and object handles without direct access to each other’s internals. That design supports isolation, security validation, and cross-process coordination, including cases where a renderer asks the browser to perform a privileged action on its behalf.

What Mojo Is for in Chromium

Mojo is Chromium’s inter-process communication layer, so browser components can exchange predefined messages and object handles without sharing internal state directly. That separation is central to Chromium’s security model: it reduces coupling, preserves process isolation, and gives the browser a controlled way to mediate requests that originate in less-trusted code.

Mojo is not just a transport. It defines the message contracts and access patterns that let a renderer, browser process, or other component coordinate work while keeping privilege boundaries intact. In practice, that means the design helps Chromium enforce validation at the boundary rather than exposing internals for direct access.

Why Mojo Matters for Browser Isolation

Browser isolation depends on keeping each process narrowly scoped, with communication flowing through an interface that can be validated and constrained. Mojo supports that model by making component interaction explicit: a caller can ask for an action, but it cannot bypass the IPC contract to reach privileged internals directly.

This matters because browser architecture is full of trust boundaries. Rendering, parsing, network handling, and privileged browser operations do not all belong in the same trust zone. Mojo gives Chromium a way to maintain those boundaries while still allowing the browser to function as a coordinated system.

How Mojo Shapes Privileged Actions and Validation

Mojo is especially important when a less-privileged component needs the browser process to do something sensitive on its behalf, such as a renderer requesting an action that should only be performed by trusted browser code. The security value comes from mediation: the browser can inspect the request, enforce policy, and decide whether the operation is allowed.

That same structure also creates a clear place for defensive checks. Because the interface is predefined, Chromium can validate message types, limit which objects are passed across boundaries, and avoid letting one component reach into another component’s internals. The result is a narrower and more auditable attack surface than direct in-process access would provide.

Mojo, Cross-Process Coordination, and Security Boundaries

Cross-process coordination is the practical reason Mojo exists, but the security consequence is just as important. It lets Chromium split functionality across processes without making every component mutually trusted. That reduces blast radius if one process is compromised, because the attacker still has to work through the IPC surface rather than gaining unrestricted internal access.

Mojo also makes the contract between processes more explicit for developers and reviewers. When the communication model is clear, it is easier to reason about which actions are permitted, which data crosses the boundary, and where the browser must enforce policy before performing a privileged operation.

Risk and Threat Considerations

Mojo’s security value depends on the integrity of the IPC boundary. If message validation is weak, interfaces are overly broad, or privileged objects are exposed too freely, a lower-privilege component can influence higher-privilege browser behaviour in ways that increase the impact of exploitation.

Failure mechanism: An attacker that reaches a renderer or other constrained component may try to abuse its Mojo interfaces to request privileged browser actions, pass crafted messages, or exploit insufficient validation at the boundary.

Impact: The consequence can be privilege escalation, control over sensitive browser operations, or a larger compromise radius than Chromium’s process separation is meant to allow.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5SC-3 — Security Function IsolationMojo enforces separation between browser processes and privileged operations.
AC-6 — Least PrivilegeMojo limits what less-trusted components can ask privileged browser code to do.
SI-10 — Information Input ValidationMojo interfaces depend on strict validation of messages and object handles.
Recommendation — Use SC-3 to isolate browser functions and constrain cross-boundary requests. Apply AC-6 to restrict privileged browser actions to the minimum required interface. Apply SI-10 to validate IPC inputs before privileged code processes them.
NIST CSF 2.0PR.AA-01 — Identity and Access Management Policy and ProceduresMojo’s boundary model depends on defined access rules for privileged operations.
Recommendation — Define access rules for privileged browser actions and enforce them consistently.

Practitioner Guidance

Why practitioners should care: Mojo is only as strong as the message contracts and boundary checks that sit on top of it. For browser and platform teams, the key judgement is not whether IPC exists, but whether each interface exposes the smallest practical set of actions and objects needed for the feature.

What to watch for: Review any Mojo interface that bridges a trust boundary, especially where a less-trusted process can trigger privileged behaviour. The most important questions are whether the browser validates inputs at the boundary, whether the interface can be reduced, and whether the request path preserves the intended isolation model.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org