UI spoofing via crafted HTML page
Published Nov 7, 2025 · Updated Nov 7, 2025
Inappropriate implementation in Chrome's Permissions component before 140.0.7339.80 allows remote attackers to spoof UI via crafted HTML. The public advisory identifies only the Permissions component and does not disclose the specific locus or incorrect operation. A user must open the crafted page, after which the attacker can present spoofed browser UI.
Summary
What happened
Inappropriate implementation in Chrome's Permissions component before 140.0.7339.80 allows remote attackers to spoof UI via crafted HTML. The public advisory identifies only the Permissions component and does not disclose the specific locus or incorrect operation. A user must open the crafted page, after which the attacker can present spoofed browser UI.
The record
- CVE
- CVE-2025-12906
- Published
- Nov 7, 2025
- Updated
- Nov 7, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-693, T1189
- 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