UI spoofing via undisclosed Autofill flaw
Published Apr 2, 2025 · Updated Apr 15, 2025
Inappropriate Autofill implementation in Google Chrome before 135.0.7049.52 allows remote attackers to spoof browser UI via crafted HTML. Google has not publicly disclosed the faulty Autofill operation; the linked Chromium issue remains restricted and the release note identifies only the affected component. Exploitation requires specific user gestures on the attacker's page, and the resulting false browser presentation can deceive the user but does not interrupt service.
Summary
What happened
Inappropriate Autofill implementation in Google Chrome before 135.0.7049.52 allows remote attackers to spoof browser UI via crafted HTML. Google has not publicly disclosed the faulty Autofill operation; the linked Chromium issue remains restricted and the release note identifies only the affected component. Exploitation requires specific user gestures on the attacker's page, and the resulting false browser presentation can deceive the user but does not interrupt service.
The record
- CVE
- CVE-2025-3073
- Published
- Apr 2, 2025
- Updated
- Apr 15, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-451
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 2, 2025CVE publishedPublication date reported by the CVE source.
- Apr 15, 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=135.0.7049.52 <135.0.7049.52
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