dbcve.org
ChromeWeb browser · Google

CVE-2026-11304

HIGH · 8.8 CVSS v3.1 Published 2026-06-05
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
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
Use after free in PDFium in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to potentially exploit heap corruption via a crafted PDF file. (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 · high confidence

A use-after-free vulnerability exists in PDFium, the PDF rendering library used by Google Chrome, that allows a remote attacker to potentially exploit heap corruption by serving a specially crafted PDF file. The vulnerability stems from improper memory management when processing certain PDF objects, where memory is accessed after it has been freed. This issue was addressed in Chrome version 149.0.7827.53.

MitigationUpdate Google Chrome to version 149.0.7827.53 or later. Organizations using PDFium or Chromium-based browsers should apply the corresponding security patches immediately and monitor for any updates to downstream products.

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:< 149.0.7827.53

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 if Google Chrome is installed
    On Windows: Look for Google Chrome in Start Menu or Program Files/Google/Chrome. On Mac: Look in /Applications/Google Chrome.app. On Linux: Run 'which google-chrome' or 'which chrome' in terminal.
    Affected if Google Chrome is not installed on the system, then the user is not affected by this specific Chrome vulnerability.
  2. Determine the installed Google Chrome version
    Navigate to chrome://settings/help in the Chrome browser, or run 'google-chrome --version' (Linux) or 'chrome --version' (Windows Command Prompt) in the terminal/command prompt.
    Affected if This step reveals the exact version number needed for the next comparison.
  3. Compare installed version to affected range
    Check if the installed version is less than 149.0.7827.53. Version numbers follow the format major.minor.build.patch. Any version below 149.0.7827.53 (such as 148.x.x.x or earlier) falls within the affected range.
    Affected if The installed version is less than 149.0.7827.53, meaning the environment is affected by the vulnerability.
  4. Verify PDF rendering capability is accessible
    Confirm the user can open PDF files in Chrome by dragging a PDF into a Chrome window or using File > Open. PDFium is the underlying library used by Chrome to render all PDF content.
    Affected if PDFs can be opened in the browser, confirming PDFium is active and the vulnerable code path could be triggered if a malicious PDF is opened.

A user is affected if Google Chrome is installed with a version lower than 149.0.7827.53 and the browser can be used to open PDF files.

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 149.0.7827.53 or later
Fixed in 149.0.7827.53
Interim mitigation

Update Google Chrome to version 149.0.7827.53 or later. Organizations using PDFium or Chromium-based browsers should apply the corresponding security patches immediately and monitor for any updates to downstream products.

Recommended fix High confidence

149.0.7827.53 or later

  1. Open Google Chrome
  2. Click the three-dot menu icon in the top-right corner
  3. Select 'Help' and then 'About Google Chrome'
  4. Chrome will check for updates and display the current version
  5. If a version older than 149.0.7827.53 is shown, click 'Update Google Chrome'
  6. Restart Chrome to complete the update
  7. After update, verify the version by returning to 'About Google Chrome' and confirming it shows 149.0.7827.53 or later

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

Fix this in Chrome Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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