vulns.co
/
GKData.io MCP and API Buy me a coffee

Chromium Project

Chromium Rule of Two: input trust, memory safety and privilege

Chromium's Rule of Two says to avoid combining untrusted input, memory-unsafe code and high privilege in one component. The architecture policy covers safer parsing, separating privileges and reviewing unsafe code even when it sits behind a safe interface.

Open the referenceArchitecture GuideReviewed 2026-10-02

How to use this reference

For an owned component, map input origin, language guarantees and execution privilege. Keep semantic authorization separate from successful parsing.

Before reading

  • Basic understanding of parsing, process privileges and memory lifetime

Context and limits

  • Memory safety does not establish data trust or permission to perform an operation.
  • Chromium-specific exceptions are not blanket guarantees for other projects.

Related visual models

Sources

  1. The Rule Of 2Chromium Project · reviewed 2026-10-02

Record reviewed 2026-10-02. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software