Arbitrary code execution via malicious extension
Published Jun 11, 2024 · Updated Mar 14, 2025
Inappropriate implementation in Chrome DevTools before 126.0.6478.54 allows attackers to execute arbitrary code via a crafted extension. Google has not published the specific DevTools locus or the incorrect operation performed on extension-controlled input. Exploitation requires convincing a user to install the malicious extension, after which attacker-supplied code executes.
Summary
What happened
Inappropriate implementation in Chrome DevTools before 126.0.6478.54 allows attackers to execute arbitrary code via a crafted extension. Google has not published the specific DevTools locus or the incorrect operation performed on extension-controlled input. Exploitation requires convincing a user to install the malicious extension, after which attacker-supplied code executes.
The record
- CVE
- CVE-2024-5836
- Published
- Jun 11, 2024
- Updated
- Mar 14, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-474, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 11, 2024CVE publishedPublication date reported by the CVE source.
- Mar 14, 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=0 <126.0.6478.54
- Affected versionversion=0 <126.0.6478.56
- Affected versionversion=0 <126.0.6478.57
- Affected versionversion=126.0.6478.54 <126.0.6478.54
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.
Weakness, pattern, technique
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