ChromeWeb browser · Google
CVE-2025-13639
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInappropriate implementation in WebRTC in Google Chrome prior to 143.0.7499.41 allowed a remote attacker to perform arbitrary read/write via a crafted HTML page. (Chromium security severity: Low)
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAn inappropriate implementation vulnerability in Google Chrome's WebRTC component prior to version 143.0.7499.41 allows a remote attacker to perform arbitrary read/write operations via a crafted HTML page, indicating a memory safety flaw in the WebRTC implementation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
< 143.0.7499.40CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Chrome versionNavigate to chrome://version in the Chrome address bar or open Chrome, click the three-dot menu, go to Help > About Google Chrome. The version number is displayed at the top.Affected if The displayed version number is less than 143.0.7499.40 (for example, 143.0.7499.0, 142.0.7433.x, or any earlier version).
-
Confirm WebRTC is enabledNavigate to chrome://webrtc-internals in the Chrome address bar. If the page loads and displays WebRTC statistics and peer connection data, WebRTC is enabled.Affected if WebRTC is enabled (this is the default state in Chrome). The vulnerability exists in the WebRTC implementation, so this component must be active for exploitation to be possible.
-
Compare version to affected rangeLocate the full version string shown in chrome://version (it will be in format like 143.0.7499.40). Compare the four-part version number against the threshold 143.0.7499.40.Affected if The first three numeric segments (143.0.7499) are lower than the threshold, or the fourth segment is less than 40 (for example, versions ending in .0 through .39).
You are affected if your Chrome version is below 143.0.7499.40 and WebRTC is enabled, as the vulnerability resides in the WebRTC component and can be triggered by visiting a crafted HTML page.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped143.0.7499.40
Update Google Chrome to version 143.0.7499.41 or later to patch the vulnerability.
Chrome 143.0.7499.41 or later stable release
- 1. Open Google Chrome and navigate to Settings > Help > About Google Chrome
- 2. Chrome will automatically check for updates
- 3. If version is below 143.0.7499.41, wait for the update to download and install
- 4. Restart Chrome to apply the update
- 5. Verify the version is 143.0.7499.41 or later by returning to Settings > Help > About Google Chrome
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13639 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-13639 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data