dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 4 Oct 2023.
ChromeWeb browser · Google

CVE-2023-4863

HIGH · 8.8 CVSS v3.1 Published 2023-09-12
Fix available
A fix is available. Upgrade to 1.0.62681.0 / 1.6.00.26463 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Patch available

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
Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187 and libwebp 1.3.2 allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page. (Chromium security severity: Critical)

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 · high confidence

Heap buffer overflow vulnerability in libwebp's image decoding functionality allows remote attackers to perform out-of-bounds memory writes via maliciously crafted WebP images embedded in HTML pages, potentially enabling arbitrary code execution.

MitigationUpdate Google Chrome to version 116.0.5845.187 or later; update libwebp to the patched version (1.3.3 or later). Apply to all affected clients and servers processing untrusted WebP content.

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
Affected:< 116.0.5845.187
FedoraOperating system
Affected:= 37= 38= 39
Debian LinuxOperating system
Affected:= 10.0= 11.0= 12.0
FirefoxWeb browser
Affected:< 102.15.1< 117.0.1>= 115.1.0, < 115.2.1
ThunderbirdApplication
Affected:< 102.15.1>= 115.0, < 115.2.2
Edge ChromiumWeb browser
Affected:< 116.0.1938.81
TeamsApplication
Affected:< 1.6.00.26463< 1.6.00.26474
Webp Image ExtensionPlugin / extension
Affected:< 1.0.62681.0

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. Check Google Chrome version
    Navigate to chrome://settings/help or run 'google-chrome --version' in terminal
    Affected if Version is below 116.0.5845.187
  2. Check Mozilla Firefox version
    Navigate to about:support or run 'firefox --version' in terminal
    Affected if Version is below 102.15.1, below 117.0.1, or between 115.1.0 and 115.2.0 (inclusive)
  3. Check Microsoft Edge version
    Navigate to edge://settings/about or run 'msedge --version' in terminal
    Affected if Version is below 116.0.1938.81
  4. Check Mozilla Thunderbird version
    Navigate to Help > About Thunderbird or run 'thunderbird --version' in terminal
    Affected if Version is below 102.15.1, or between 115.0 and 115.2.1 (inclusive)
  5. Check Microsoft Teams version
    Open Teams, click on your profile picture > About > Version, or check Programs and Features
    Affected if Version is below 1.6.00.26463 or below 1.6.00.26474 (depending on architecture)
  6. Check libwebp library version
    Run 'dpkg -l | grep libwebp' (Debian/Ubuntu) or 'rpm -qa | grep libwebp' (RHEL/Fedora) or check file version of libwebp shared library
    Affected if Version is below 1.3.2

User is affected if any installed browser, Thunderbird, Teams, or libwebp library matches the affected version ranges AND the application processes WebP images from untrusted sources.

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.

dbcve · scoped
Upgrade available Upgrade to 1.0.62681.0 / 1.6.00.26463 / 1.6.00.26474 or later
Fixed in 1.0.62681.01.6.00.264631.6.00.26474
Vendor patch github.com →
Interim mitigation

Update Google Chrome to version 116.0.5845.187 or later; update libwebp to the patched version (1.3.3 or later). Apply to all affected clients and servers processing untrusted WebP content.

Recommended fix High confidence

Product-specific: Chrome 116.0.5845.187+; Edge 116.0.1938.81+; Firefox 102.15.1+/115.2.1+/117.0.1+; Thunderbird 102.15.1+/115.2.2+; Teams 1.6.00.26463+/1.6.00.26474+; WebP Extension 1.0.62681.0+; libwebp 1.3.3+

  1. For Google Chrome: Upgrade to version 116.0.5845.187 or later
  2. For Microsoft Edge Chromium: Upgrade to version 116.0.1938.81 or later
  3. For Mozilla Firefox: Upgrade to 102.15.1+, 117.0.1+, or 115.2.1+ depending on ESR channel
  4. For Mozilla Thunderbird: Upgrade to 102.15.1+ or 115.2.2+ depending on ESR channel
  5. For Microsoft Teams (Desktop): Upgrade to 1.6.00.26463+ or 1.6.00.27464+ depending on architecture
  6. For WebP Image Extension: Upgrade to version 1.0.62681.0 or later
  7. For Fedora Linux systems: Update libwebp package via 'dnf update libwebp' after vendor releases patch
  8. For Debian Linux: Update libwebp package via 'apt-get update && apt-get upgrade libwebp' after vendor releases patch

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-4863 — 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-2023-4863 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