CVE-2023-25360
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 · uneditedA use-after-free vulnerability in WebCore::RenderLayer::renderer in WebKitGTK before 2.36.8 allows attackers to execute code remotely.
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 confidenceA use-after-free vulnerability in WebCore::RenderLayer::renderer in WebKitGTK versions prior to 2.36.8 allows attackers to execute code remotely by freeing memory that is still being accessed.
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< 2.36.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if WebKitGTK is installedRun: pkg-config --modversion webkit2gtk-4.1 2>/dev/null || pkg-config --modversion webkit2gtk-4.0 2>/dev/null || dpkg -l | grep -i webkitgtk 2>/dev/null || rpm -qa | grep -i webkitgtk 2>/dev/nullAffected if No output means WebKitGTK is not installed and not affected
-
Identify the exact WebKitGTK versionRun: pkg-config --modversion webkit2gtk-4.1 || pkg-config --modversion webkit2gtk-4.0Affected if The command returns a version number that can be compared to the affected range
-
Compare version against affected rangeCompare the installed version to 2.36.8 - any version below 2.36.8 is affectedAffected if Installed version is less than 2.36.8 (e.g., 2.36.7, 2.36.6, 2.35.x, etc.)
You are affected if WebKitGTK is installed and its version is lower than 2.36.8.
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 · scoped2.36.8
Upgrade WebKitGTK to version 2.36.8 or later to patch the use-after-free vulnerability.
WebKitGTK 2.36.8 or later
- Check current WebKitGTK version using your package manager (e.g., `dpkg -l libwebkit2gtk-4.0-37` on Debian/Ubuntu, or `rpm -qa | grep webkit` on RHEL/Fedora)
- Update your system's package repository metadata to ensure latest packages are available
- Upgrade WebKitGTK to version 2.36.8 or later using your system's package manager (e.g., `apt-get update && apt-get upgrade libwebkit2gtk-4.0-37` for Debian/Ubuntu, or `dnf update webkit2gtk4.0` for Fedora/RHEL)
- Verify the installed version is 2.36.8 or higher using the version check command from step 1
- If applicable, restart any applications or services that depend on WebKitGTK to ensure they load the updated library
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25360 — 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-2023-25360 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