Remote code execution via unvalidated DevTools input
Published Nov 7, 2025 · Updated Nov 7, 2025
Improper input validation in Google Chrome DevTools before 140.0.7339.80 allows remote attackers to execute arbitrary code via user action. Google identifies the locus only as DevTools and has not disclosed which input is accepted without sufficient validation or which operation consumes it. Exploitation requires a user to act in DevTools; successful exploitation executes attacker-controlled code in the browser's security context.
Summary
What happened
Improper input validation in Google Chrome DevTools before 140.0.7339.80 allows remote attackers to execute arbitrary code via user action. Google identifies the locus only as DevTools and has not disclosed which input is accepted without sufficient validation or which operation consumes it. Exploitation requires a user to act in DevTools; successful exploitation executes attacker-controlled code in the browser's security context.
The record
- CVE
- CVE-2025-12907
- Published
- Nov 7, 2025
- Updated
- Nov 7, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-20, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 7, 2025CVE publishedPublication date reported by the CVE source.
- Nov 7, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=140.0.7339.80 <140.0.7339.80
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo