본문으로 이동
ONEPRESS

GLOBAL BRIEF

Chrome security update check: make sure 149.0.7827.155 or later is installed

Global briefing

GLOBAL LANGUAGES

Briefings by language

Only translations that preserve official sources and action checks are linked.

KO 한국어 EN English JA 日本語 ZH 简体中文 ES Español VI Tiếng Việt
Informational image showing a browser update screen and security shield for checking Chrome and Chromium-based browser security updates
ONEPRESS informational image based on Google Chrome Releases, CISA KEV, and Microsoft Edge security release notes. It illustrates browser version checking and restart completion.

Check Basis

  • Checked: 2026-06-19 17:45 KST
  • Primary sources: Google Chrome Releases for June 8 and June 16, 2026 desktop Stable updates, CISA Known Exploited Vulnerabilities Catalog, Microsoft Edge security release notes, Google Chrome update help
  • Who is covered: Chrome desktop users on Windows, Mac, and Linux, plus people and organizations using Chromium-based browsers. Chrome on mobile should be checked through the Play Store or App Store update path.

The first browser check today is not a new feature. It is the installed version number and whether a restart is still pending. Google updated Chrome desktop Stable on June 16, 2026 to 149.0.7827.155/.156 for Windows and Mac and 149.0.7827.155 for Linux, with 33 security fixes. The earlier June 8 update moved Stable to 149.0.7827.102/.103 and included 74 security fixes, including CVE-2026-11645.

This matters because CISA added CVE-2026-11645 to the Known Exploited Vulnerabilities Catalog on June 9, 2026. CISA describes it as a Google Chromium V8 out-of-bounds read and write issue that could allow arbitrary code execution inside a sandbox through a crafted HTML page. CISA also notes that Chromium-based browsers, including Chrome, Edge, and Opera, may be affected.

Who Needs This

  • People who rely on Chrome but have not opened the About Chrome update screen recently
  • Teams running workstations, school PCs, kiosks, front-desk computers, or shared laptops that stay open all day
  • Microsoft Edge or other Chromium-browser users who might assume a Chrome advisory does not apply to them
  • Anyone who keeps postponing a browser relaunch after an update indicator appears

Why This Should Come First

A browser vulnerability is not isolated to one app. It sits in the route people use to open email links, shared documents, search results, banking pages, and work dashboards. V8 is the engine that runs JavaScript and WebAssembly in web pages, so a browser issue can become relevant simply because a user opens the wrong page. This does not mean every user is being targeted, but a vulnerability in CISA KEV deserves higher priority than a routine advisory.

Chrome can also download updates in the background while the old browser process keeps running. Until the browser is restarted, the new build may not be fully active. That is why the practical check is the About Chrome screen, not a vague assumption that automatic updates are enabled.

Three Common Situations

  • Personal computer: Type chrome://settings/help in the address bar or open Help, About Google Chrome. If a relaunch button appears after the update is downloaded, save open work and restart the browser.
  • Managed work or school device: If updates are hidden or controlled by policy, ask IT to confirm the June 2026 Chrome security update and CVE-2026-11645 remediation status.
  • Edge user: Microsoft says its June 9, 2026 Edge Stable Channel 149.0.4022.62 update contains a fix for CVE-2026-11645, and June 18 Stable is 149.0.4022.80. Edge users should open About Microsoft Edge and confirm the current build.

User Checklist

  1. Open chrome://settings/help on desktop Chrome.
  2. Confirm 149.0.7827.155/.156 or later on Windows and Mac, or 149.0.7827.155 or later on Linux.
  3. If Chrome asks to relaunch, finish pending work and restart the browser.
  4. Repeat the check on family PCs, shared workstations, and backup laptops that may stay open for days.
  5. If you use Edge, open About Microsoft Edge and confirm the June security update is installed.
  6. If updates fail, use Google’s official update help or your organization’s IT policy path.

Official Links To Check

FAQ

If Chrome updates automatically, is there anything else to do?
Yes. Automatic download is not the same as a completed relaunch. Open About Chrome and check whether the latest build is installed and whether a relaunch button remains.

Is 149.0.7827.102/.103 enough?
The June 8 build addressed important issues including CVE-2026-11645. But because Google released a newer June 16 Stable update, today’s practical target is 149.0.7827.155/.156 or later on desktop.

Does this matter if I use Edge or Opera?
Possibly. CISA says the vulnerability can affect multiple Chromium-based browsers. Use each browser’s official update screen rather than assuming Chrome-only language excludes you.

Bottom Line

Desktop Chrome users should open chrome://settings/help today and confirm 149.0.7827.155/.156 or later on Windows or Mac, and 149.0.7827.155 or later on Linux. If the browser has downloaded an update, finish the relaunch. Edge and other Chromium-based browser users should check their own official update screens with the same urgency.