dbcve.org
Classic Buffer OverflowWeakness · CWE-120

CVE-2025-66287

HIGH · 8.8 CVSS v3.1 Published 2025-12-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
A flaw was found in WebKitGTK. Processing malicious web content can cause an unexpected process crash due to improper memory handling.

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 confidence

WebKitGTK contains a memory handling flaw that causes an unexpected process crash when processing malicious web content. The vulnerability stems from improper memory management during web content processing, leading to a denial-of-service condition.

MitigationUpdate WebKitGTK to the patched version once available; until then, restrict or disable processing of untrusted web content through WebKitGTK-based applications.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm WebKitGTK installation
    Check for WebKitGTK libraries on the system. On Linux, search for libwebkit files: `find /usr -name 'libwebkit*' 2>/dev/null` or check package manager: `dpkg -l | grep webkit` (Debian) / `rpm -qa | grep webkit` (RHEL)
    Affected if WebKitGTK libraries are found on the system
  2. Identify installed WebKitGTK version
    Query the package manager for the exact version installed: `dpkg -l | grep webkitgtk` or `rpm -q webkitgtk` or check the library version directly via `pkg-config --modversion webkitgtk-4.1` (or webkitgtk-4.0 for older variants)
    Affected if Version cannot be determined or is earlier than the patched release
  3. Identify WebKitGTK-based applications
    List applications that link to WebKitGTK: `ldconfig -p | grep webkit` or check running processes for applications that handle web content (browsers, email clients with HTML rendering, help viewers)
    Affected if Applications using WebKitGTK are installed and running
  4. Verify web content processing is enabled
    Examine configuration files and runtime settings of WebKitGTK-based applications to confirm whether processing of web/HTTP content is active or permitted
    Affected if Web content processing is enabled or untrusted content can be loaded

The environment is affected if WebKitGTK is installed and applications using it can process web content, as the memory handling flaw triggers during malicious web content processing.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WebKitGTK to the patched version once available; until then, restrict or disable processing of untrusted web content through WebKitGTK-based applications.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-66287 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-66287 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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