Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2026-78938 — Root-cause analysis and working exploit for CVE-2026-78938, a V8 TurboFan type confusion leading to arbitrary read/write within the compressed heap. Includes crash PoC and runtime-addressed primitives. | Kitploit
Tools/GitHubGitHub/eddinos2/cve-2026-78938
Vulnerability AnalysisExploitationWeb SecurityBinary Exploitation
GitHubeddinos2/cve-2026-78938

CVE-2026-78938

Root-cause analysis and working exploit for CVE-2026-78938, a V8 TurboFan type confusion leading to arbitrary read/write within the compressed heap. Includes crash PoC and runtime-addressed primitives.

View Repository
1642 months agoNot yet reviewed
Share

CVE-2026-78938 — V8 TurboFan CheckMaps instance-migration type confusion

Root-cause analysis and exploit for CVE-2026-78938, a type confusion in V8's TurboFan load elimination that was fixed in Chrome 152.0.7977.64 (V8 15.2.124.18). The bug was reported as exploited in the wild.

The exploit turns the bug into an out-of-bounds Float64Array and from there into addrof / fakeobj and arbitrary read/write over the V8 compressed heap. Everything past the initial write is located at runtime — there are no hardcoded heap offsets in the R/W stage.

  • Affected: Chrome 152.0.7977.54 (V8 15.2.124.13, commit 8ec91943)
  • Fixed: Chrome 152.0.7977.64/.65 (V8 15.2.124.18, commit 6aacaf62)
  • Fix commit: 50597b0bb48a — "[compiler] Invalidate tracked fields on CheckMaps with instance migration"

Tested on macOS arm64 against a locally built d8 of both versions.

Contents

filewhat it is
pocs/crash.jsMinimal trigger. SIGBUS on the vulnerable build, clean exit on the patched one.
pocs/rw_final.jsFull exploit, stage 1: trigger + OOB array. Frozen — see "Reproducing" below.
pocs/logic_final.jsFull exploit, stage 2: addrof/fakeobj/arbitrary R\W, loaded at runtime by stage 1.
WRITEUP.mdFull root-cause analysis and exploitation notes.

Reproducing

Build the two d8 versions (see WRITEUP.md for the exact commits and GN args), then from the repo root:

# crash PoC: SIGBUS on vuln, clean on patched
out/vuln/d8    --allow-natives-syntax --homomorphic-ic --max-valid-polymorphic-map-count=4 pocs/crash.js
out/patched/d8 --allow-natives-syntax --homomorphic-ic --max-valid-polymorphic-map-count=4 pocs/crash.js

# full R/W: works on vuln, bails out cleanly on patched
out/vuln/d8 --allow-natives-syntax --homomorphic-ic --max-valid-polymorphic-map-count=4 pocs/rw_final.js

Expected output on the vulnerable build:

[+] OOB Float64Array len=0x7f000004
[+] after write: victim2.z = 2.5
[+] fakeobj(hn|1) typeof=number
[+] ALL PRIMITIVES VERIFIED

Two things matter:

  1. The flags are required. --homomorphic-ic --max-valid-polymorphic-map-count=4 shape the polymorphic map feedback so the migration path is taken in optimized code. Without them the trigger quietly does nothing.
  2. pocs/rw_final.js is byte-frozen. The single corrupting write lands at a heap-relative offset that depends on where the victim array is allocated, which in turn depends on the script's exact bytes and path. Editing the file (or renaming it) invalidates the baked offset; WRITEUP.md documents how to re-calibrate. pocs/logic_final.js is loaded after the trigger fires, so it can be edited freely.

Notes

  • The primitive demonstrated is arbitrary read/write inside the V8 sandbox (the compressed heap). Getting code execution additionally needs a sandbox exit (e.g. corrupting a Wasm instance's RWX code region), which is out of scope for this write-up.
  • All addresses in the exploit are discovered at runtime. The only baked-in value is the single write offset in pocs/rw_final.js, for the reasons above.

This repository is for educational and defensive research purposes. The bug is patched in current Chrome; details are public in the V8 source tree.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    786
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    506
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    429
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    345
  • 5

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    262
  • 6

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    256

Explore all tools

Browse our collection of tools

View all tools →