//nefariousplan

Google

Android, Chrome, Chromium, Chromium V8, Keras

The plan

The Nefarious Plan of Google. Across seven Google case files, the pattern is not the bugs. It is the habit of shipping a name and leaving the mechanism to whoever reads it. The parameter named elidable, the flag named safemode, the function EVPPKEYcmp wrapped as a bool, the CVE identifier that becomes a repository slug: the label is always present, the thing the label describes is always somewhere else.

Case files

  1. CVE-2025-4609: Chrome's Mojo Sandbox Escape Resurfaces With Five PoC Repositories. One Is A 404. Four Share The Same Git History. Their Author's Own Report Says Not To Call It A Sandbox Escape.

    CVE-2025-4609: Chrome's Mojo Sandbox Escape Resurfaces With Five PoC Repositories. One Is A 404. Four Share The Same Git History. Their Author's Own Report Says Not To Call It A Sandbox Escape.

    CVE-2025-4609 is an insufficient-permissions check in Chrome's Mojo IPC layer. Google patched the original in Stable 136.0.7103.113 in May 2025, scored it 9.6 under CVSS 3.1 with vector AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, and closed Chromium issue tracker ent…

  2. CVE-2026-125350: Chrome's XML UAF KEV Lands Two PoCs Within Twelve Hours. One Flags Patched Users Vulnerable. The Other Describes A Chrome From February 2025.

    CVE-2026-125350: Chrome's XML UAF KEV Lands Two PoCs Within Twelve Hours. One Flags Patched Users Vulnerable. The Other Describes A Chrome From February 2025.

    CVE-2026-125350 is a use-after-free in Chrome's XML component. Google patched it on November 9, 2026, in Stable 157.0.8103.50/.51 and Extended Stable 156.0.8078.96, credited an anonymous reporter who filed three days earlier, and attached a sentence to the rel…

  3. CVE-2025-1550: The safe_mode Check Is Not in the Patch

    CVE-2025-1550: The safe_mode Check Is Not in the Patch

    Keras 3's keras.saving.loadmodel(filepath) defaults to safemode=True. The function's docstring describes the flag verbatim: "Boolean, whether to disallow unsafe lambda deserialization.

  4. CVE-2026-5865: Maglev's BuildCheckSmi Took a Parameter Named `elidable` and Did Not Read It

    CVE-2026-5865: Maglev's BuildCheckSmi Took a Parameter Named `elidable` and Did Not Read It

    The patch for CVE-2026-5865 is one boolean operand. Maglev's BuildCheckSmi is the function that emits a runtime "is this value a small integer" check before code that depends on the answer.

  5. CVE-2026-2441: The Vulnerable Chrome Binary Is a 404, the Heap Leak Is Math.random()

    CVE-2026-2441: The Vulnerable Chrome Binary Is a 404, the Heap Leak Is Math.random()

    The README declares CVSS 8.8, Renderer RCE in a sandboxed Chrome, active in-the-wild exploitation. The exploit-chain diagram names NSO Pegasus, Intellexa Predator, and APT-28. The vulnerability is real.

  6. CVE-2026-0073: adbd's EVP_PKEY_cmp Was the 2020 OpenIKED Bug

    CVE-2026-0073: adbd's EVP_PKEY_cmp Was the 2020 OpenIKED Bug

    if (EVPPKEYcmp(knownevp.get(), evppkey.get())) is the gate daemon/auth.cpp uses to authenticate wireless ADB clients. EVPPKEYcmp returns 1, 0, -1, or -2. Three of those four values are truthy in C++. Two of them mean no.

  7. CVE-2026-11645: Three Public PoCs For The V8 KEV Bug. None Of Them Read Or Write Out Of Bounds.

    CVE-2026-11645: Three Public PoCs For The V8 KEV Bug. None Of Them Read Or Write Out Of Bounds.

    CVE-2026-11645 is a Chrome V8 out-of-bounds read and write. Google's advisory describes "execute arbitrary code inside a sandbox via a crafted HTML page" against Chrome before 149.0.7827.103.