dbcve.org
ChromeWeb browser · Google

CVE-2026-12444

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-17
Fix available
A fix is available. Upgrade to 149.0.7827.155 or later.
See remediation →
58/100
Remediation priority · Elevated
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
Out of bounds read in Chromoting in Google Chrome on Windows prior to 149.0.7827.155 allowed a local attacker to obtain potentially sensitive information from process memory via a malicious file. (Chromium security severity: High)

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

This is an out-of-bounds read vulnerability in Chrome's Chromoting (remote desktop) component on Windows. A local attacker can exploit this by tricking a user into opening a malicious file, allowing them to read beyond allocated memory boundaries and potentially extract sensitive data from the process memory space.

MitigationUpdate Google Chrome to version 149.0.7827.155 or later. Organizations should deploy this update through their standard patch management processes and verify completion across Windows endpoints.

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.155

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/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 if Google Chrome is installed on Windows
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome, or run the command: dir "C:\Program Files\Google\Chrome\Application" /b
    Affected if The Chrome application directory or registry key exists on the Windows system
  2. Determine the installed Chrome version
    Run the command: "C:\Program Files\Google\Chrome\Application\chrome.exe" --version, or check the Version value in the registry key from step 1, or navigate to chrome://version in the Chrome browser
    Affected if A version number is returned that is less than 149.0.7827.155
  3. Verify the Chromoting component is present
    Check for the Chromoting DLL or module within the Chrome installation directory (typically in the Application folder), or verify the remote desktop feature is accessible in Chrome settings
    Affected if The Chromoting component files exist in the Chrome installation directory on Windows
  4. Confirm the vulnerability condition
    Compare the installed Chrome version against the affected range: versions prior to 149.0.7827.155 on Windows are affected if the Chromoting component is present
    Affected if The installed Chrome version is lower than 149.0.7827.155 AND the system is running Windows with the Chromoting component available

A Windows user is affected if they have Google Chrome installed with a version number lower than 149.0.7827.155 and the Chromoting component is present on their system.

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.155 or later
Fixed in 149.0.7827.155
Interim mitigation

Update Google Chrome to version 149.0.7827.155 or later. Organizations should deploy this update through their standard patch management processes and verify completion across Windows endpoints.

Recommended fix High confidence

149.0.7827.155 or later

  1. Upgrade Google Chrome to version 149.0.7827.155 or later by navigating to chrome://settings/help and clicking 'Update Google Chrome', or download the latest version from the official Chrome download page

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 / QA2.0 h
10.0 hours of engineering $1,780
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,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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