Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
HighPublic exploit

Type Confusion in Google Chrome V8

IdentifiersCVE-2025-2135CWE-843· Access of Resource Using…

CVE-2025-2135 is a type confusion vulnerability in Google Chrome's V8 JavaScript engine. According to the provided content, Google described the issue as a type confusion in V8 in Chrome prior to 134.0.6998.88 that allowed a remote attacker to potentially trigger heap corruption via a crafted HTML page. The flaw is reachable through web content rendered by Chromium-based functionality, and in the Kibana context it can be triggered during PDF or PNG report generation because Kibana uses Chromium for screenshotting/report rendering. The supplied material does not identify a specific vulnerable function or code path within V8.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can cause heap corruption in the browser process handling the crafted page, which may enable attacker-controlled memory corruption and potentially arbitrary code execution within the affected Chromium execution context. In the Kibana reporting context described in the content, exploitation is associated with critical impact during PDF/PNG report generation, and Elastic notes that on Elastic Cloud any resulting code execution would be constrained to the Kibana Docker container, with seccomp-bpf and AppArmor reducing the likelihood of further escape. The provided content does not give a more precise upstream Chrome impact statement beyond heap corruption.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, disable Kibana reporting by setting xpack.reporting.enabled: false. Restrict PDF/PNG report-generation privileges to trusted accounts only. Configure a restrictive xpack.screenshotting.networkPolicy to prevent Chromium from being redirected to attacker-controlled destinations during report generation, while still allowing required connectivity back to Kibana (for example, permitting localhost:5601 as noted in the content). CSV reporting and serverless projects are not impacted according to the provided material.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 134.0.6998.88 or later. For affected Kibana deployments that expose this Chromium issue through reporting, upgrade to the fixed Kibana releases identified in the content: 7.17.29, 8.17.8, 8.18.3, or 9.0.3, as applicable to the deployed branch.
PUBLIC EXPLOITS

Exploits

2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 2 / 2 TOTALView more in app
CVE-2025-2135MaturityPoCVerified exploit

This repository contains a proof-of-concept (POC) exploit for CVE-2025-2135, a vulnerability in Google's V8 JavaScript engine. The exploit is implemented in a single JavaScript file (poc-CVE-2025-2135.js) and is accompanied by a detailed README.md explaining the vulnerability and exploitation technique. The exploit leverages manipulation of large JavaScript arrays and V8's internal object layouts to create a 'fake' array object, which is then used to gain arbitrary address read and write capabilities within the V8 heap. This allows the attacker to read and write memory at arbitrary addresses, a powerful primitive for further exploitation. The exploit is designed for research and debugging purposes and requires a custom-built V8 engine at a specific commit, with certain flags enabled. There are no network or external endpoints; the attack vector is local, requiring the ability to execute JavaScript in the vulnerable V8 environment. The code demonstrates advanced exploitation techniques relevant to browser and JavaScript engine security research.

sangnguyenthienDisclosed Jun 17, 2025javascriptlocal
CVE-2025-2135MaturityPoCVerified exploit

This repository contains a proof-of-concept exploit for CVE-2025-2135, targeting the V8 JavaScript engine (version 13.3.415.19) as used in Chromium-based browsers. The main file, exp.js, is a standalone exploit script designed to be run in the d8 shell with the --allow-natives-syntax flag. The exploit leverages advanced JavaScript engine internals, including JIT optimization and object structure manipulation, to achieve arbitrary memory read and write capabilities. It requires a helper.js file (not included) that provides the Helper class and related low-level primitives. The exploit demonstrates the ability to create fake objects, leak addresses, and manipulate memory, which can be used as a foundation for further exploitation such as sandbox escape or remote code execution. No network endpoints or external services are targeted; the attack vector is local, requiring the ability to execute JavaScript in the vulnerable engine context. The repository structure is minimal, consisting of a README and the main exploit script.

Wa1nut4Disclosed May 19, 2025javascriptlocal
EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleChromeapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity9

Community discussion across Reddit, Mastodon, and other social sources.