dbcve.org
ChromeWeb browser · Google

CVE-2026-11218

MEDIUM · 6.8 CVSS v3.1 Published 2026-06-04
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
75/100
Remediation priority · High
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
Inappropriate implementation in PlatformIntegration in Google Chrome on Windows prior to 149.0.7827.53 allowed a remote attacker who convinced a user to engage in specific UI gestures to execute arbitrary code via a malicious 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 vulnerability in Google Chrome's PlatformIntegration component on Windows (versions prior to 149.0.7827.53) allows a remote attacker to execute arbitrary code via a malicious file when the user performs specific UI gestures. The attack requires user interaction (convincing the user to engage in specific UI gestures) and involves a malicious file.

MitigationUpdate Google Chrome to version 149.0.7827.53 or later. This is a client-side browser vulnerability; the fix is obtained by patching the browser, not by modifying application code.

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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/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 checks

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

  1. Check installed Chrome version on Windows
    Open Google Chrome, click the three-dot menu, select Help, then 'About Google Chrome'. The version number is displayed on that page.
    Affected if The displayed version is earlier than 149.0.7827.53 (for example, 149.0.7827.52 or any version below 149.0.7827.53)
  2. Verify Chrome version via command line
    Open Command Prompt and run: chrome --version or locate chrome.exe in Program Files and run: "C:\Program Files\Google\Chrome\Application\chrome.exe" --version
    Affected if The returned version string shows a number less than 149.0.7827.53
  3. Confirm Chrome is running on Windows
    Open Task Manager, look for Google Chrome processes under the Processes tab, or check for chrome.exe in Task Manager details
    Affected if Chrome processes are running on a Windows system with a vulnerable version
  4. Check PlatformIntegration component presence
    This is an internal Chrome component. The vulnerability exists in Chrome's PlatformIntegration on Windows. No direct external check available; version check is the primary indicator.
    Affected if Chrome is installed on Windows and the version is below 149.0.7827.53, meaning the flawed PlatformIntegration implementation is present

You are affected if Google Chrome on your Windows system is installed with any version lower than 149.0.7827.53, as that version range contains the vulnerable PlatformIntegration component.

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. This is a client-side browser vulnerability; the fix is obtained by patching the browser, not by modifying application code.

Recommended fix High confidence

Chrome 149.0.7827.53 (or later stable release)

  1. Open Google Chrome on Windows
  2. Navigate to Settings > Help > About Google Chrome
  3. Chrome will automatically check for updates
  4. If an update is available, click 'Update Google Chrome'
  5. Restart the browser after the update completes
  6. Verify the version is 149.0.7827.53 or later by returning to About Google Chrome
Caveat Chrome auto-updates typically have no breaking changes; enterprise-managed deployments may require IT policy updates

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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