Privileged-page script injection via malicious extension
Published Feb 23, 2026 · Updated Feb 23, 2026
Improper DevTools handling in Google Chrome before 145.0.7632.116 allows attackers to inject script or HTML into a privileged page. DevTools improperly permits extension-supplied content to enter that page, while Google keeps the lower-level implementation fault restricted. Exploitation requires persuading a user to install a malicious extension, after which injected content runs in a privileged page context.
Summary
What happened
Improper DevTools handling in Google Chrome before 145.0.7632.116 allows attackers to inject script or HTML into a privileged page. DevTools improperly permits extension-supplied content to enter that page, while Google keeps the lower-level implementation fault restricted. Exploitation requires persuading a user to install a malicious extension, after which injected content runs in a privileged page context.
The record
- CVE
- CVE-2026-3063
- Published
- Feb 23, 2026
- Updated
- Feb 23, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- T1176
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 23, 2026CVE publishedPublication date reported by the CVE source.
- Feb 23, 2026Record 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=145.0.7632.116 <145.0.7632.116
What conditions does exploitation require?
What is affected?
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