Arbitrary memory read and write via crafted HTML
Published Dec 2, 2025 · Updated Dec 8, 2025
Inappropriate implementation in WebRTC in Google Chrome before 143.0.7499.41 allows remote attackers to read and write memory via crafted HTML. Google identifies the affected locus only as WebRTC; the restricted issue record does not disclose the incorrect operation performed on page-controlled input. A victim must load the crafted page, after which browser-process confidentiality and integrity can be compromised without a reported service interruption.
Summary
What happened
Inappropriate implementation in WebRTC in Google Chrome before 143.0.7499.41 allows remote attackers to read and write memory via crafted HTML. Google identifies the affected locus only as WebRTC; the restricted issue record does not disclose the incorrect operation performed on page-controlled input. A victim must load the crafted page, after which browser-process confidentiality and integrity can be compromised without a reported service interruption.
The record
- CVE
- CVE-2025-13639
- Published
- Dec 2, 2025
- Updated
- Dec 8, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 2, 2025CVE publishedPublication date reported by the CVE source.
- Dec 8, 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=143.0.7499.41 <143.0.7499.41
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