Security Resilience

CVE-2025-12907

Google Chrome ≤ 140.0.7339.80

Public PoC
Published
08 November 2025
Modified
07 October 2026
Patch / advisory
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0029 21th percentile
Risk Priority 63 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-12907 is a high-severity Improper Input Validation (CWE-20) vulnerability in Google Chrome. Its CVSS base score is 8.8 (High).

Operationally, ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-12907 is an insufficient validation of untrusted input vulnerability affecting the Devtools component in Google Chrome versions prior to 140.0.7339.80. It stems from CWE-20 (Improper Input Validation) and enables a remote attacker to execute arbitrary code through user actions within Devtools. The issue carries a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), though Chromium rates its security severity as Low.

A remote attacker with no privileges can exploit this vulnerability by tricking a user into performing specific actions in Chrome's Devtools interface, such as inspecting or interacting with malicious content. Successful exploitation grants high-impact arbitrary code execution with full confidentiality, integrity, and availability effects in the context of the browser, potentially leading to sandbox escape or further compromise depending on the attacker's payload.

Mitigation is addressed in the stable channel update for Chrome desktop, detailed in the Chrome Releases blog post at https://chromereleases.googleblog.com/2025/09/stable-channel-update-for-desktop.html, which includes the patch in version 140.0.7339.80. Additional technical details are available in the Chromium issue tracker at https://issues.chromium.org/issues/427367145. Users should update to the patched version promptly to prevent exploitation.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Insufficient validation of untrusted input in Devtools in Google Chrome prior to 140.0.7339.80 allowed a remote attacker to execute arbitrary code via user action in Devtools. (Chromium security severity: Low)

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-14131Same product: Google Chrome
CVE-2026-14020Same product: Google Chrome
CVE-2026-13959Same product: Google Chrome
CVE-2026-19177Same product: Google Chrome
CVE-2026-17834Same product: Google Chrome
CVE-2024-7974Same product: Google Chrome
CVE-2026-14150Same product: Google Chrome
CVE-2026-17990Same product: Google Chrome
CVE-2026-17982Same product: Google Chrome
CVE-2026-106331Same product: Google Chrome

Affected Assets

google
chrome
≤ 140.0.7339.80

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover missing input validation through analysis or test cases.

SI-10 directly requires validity checks on information inputs, structurally preventing improper or missing validation.

Requiring documented development standards and tools can embed input-validation practices into the engineering process.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Testing against a defined set of requirements and using code review plus vulnerability scanning forces validation of inputs and handling of unanticipated conditions, reducing the chance that malformed data will be accepted.

prevents

Requiring language-specific secure coding standards, peer review, SAST and documented mitigation of common programming errors forces validation of all inputs before they are trusted.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-20, a class-level weakness, and none of its children carries one either.

References