{"id":193,"date":"2026-06-19T17:53:25","date_gmt":"2026-06-19T08:53:25","guid":{"rendered":"https:\/\/onepress.co.kr\/index.php\/briefing\/2026-06-19-chrome-chromium-security-update-check-en\/"},"modified":"2026-06-19T17:53:25","modified_gmt":"2026-06-19T08:53:25","slug":"2026-06-19-chrome-chromium-security-update-check-en","status":"publish","type":"briefing","link":"https:\/\/onepress.co.kr\/index.php\/briefing\/2026-06-19-chrome-chromium-security-update-check-en\/","title":{"rendered":"Chrome security update check: make sure 149.0.7827.155 or later is installed"},"content":{"rendered":"<figure class=\"wp-block-image size-full\">\n  <img decoding=\"async\" src=\"https:\/\/onepress.co.kr\/wp-content\/uploads\/2026\/06\/chrome-chromium-security-update-check-en.svg\" alt=\"Informational image showing a browser update screen and security shield for checking Chrome and Chromium-based browser security updates\" \/><figcaption>ONEPRESS informational image based on Google Chrome Releases, CISA KEV, and Microsoft Edge security release notes. It illustrates browser version checking and restart completion.<\/figcaption><\/figure>\n<h2>Check Basis<\/h2>\n<ul>\n<li>Checked: 2026-06-19 17:45 KST<\/li>\n<li>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<\/li>\n<li>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.<\/li>\n<\/ul>\n<p>The first browser check today is not a new feature. It is the <strong>installed version number and whether a restart is still pending<\/strong>. Google updated Chrome desktop Stable on June 16, 2026 to <strong>149.0.7827.155\/.156 for Windows and Mac and 149.0.7827.155 for Linux<\/strong>, with <strong>33 security fixes<\/strong>. The earlier June 8 update moved Stable to <strong>149.0.7827.102\/.103<\/strong> and included <strong>74 security fixes<\/strong>, including <strong>CVE-2026-11645<\/strong>.<\/p>\n<p>This matters because CISA added CVE-2026-11645 to the <strong>Known Exploited Vulnerabilities Catalog<\/strong> 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.<\/p>\n<h2>Who Needs This<\/h2>\n<ul>\n<li>People who rely on Chrome but have not opened the About Chrome update screen recently<\/li>\n<li>Teams running workstations, school PCs, kiosks, front-desk computers, or shared laptops that stay open all day<\/li>\n<li>Microsoft Edge or other Chromium-browser users who might assume a Chrome advisory does not apply to them<\/li>\n<li>Anyone who keeps postponing a browser relaunch after an update indicator appears<\/li>\n<\/ul>\n<h2>Why This Should Come First<\/h2>\n<p>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.<\/p>\n<p>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.<\/p>\n<h2>Three Common Situations<\/h2>\n<ul>\n<li><strong>Personal computer:<\/strong> Type <code>chrome:\/\/settings\/help<\/code> 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.<\/li>\n<li><strong>Managed work or school device:<\/strong> If updates are hidden or controlled by policy, ask IT to confirm the June 2026 Chrome security update and CVE-2026-11645 remediation status.<\/li>\n<li><strong>Edge user:<\/strong> 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.<\/li>\n<\/ul>\n<h2>User Checklist<\/h2>\n<ol>\n<li>Open <code>chrome:\/\/settings\/help<\/code> on desktop Chrome.<\/li>\n<li>Confirm <strong>149.0.7827.155\/.156 or later<\/strong> on Windows and Mac, or <strong>149.0.7827.155 or later<\/strong> on Linux.<\/li>\n<li>If Chrome asks to relaunch, finish pending work and restart the browser.<\/li>\n<li>Repeat the check on family PCs, shared workstations, and backup laptops that may stay open for days.<\/li>\n<li>If you use Edge, open About Microsoft Edge and confirm the June security update is installed.<\/li>\n<li>If updates fail, use Google\u2019s official update help or your organization\u2019s IT policy path.<\/li>\n<\/ol>\n<h2>Official Links To Check<\/h2>\n<ul>\n<li><a href=\"https:\/\/chromereleases.googleblog.com\/2026\/06\/stable-channel-update-for-desktop_01750511403.html\" target=\"_blank\" rel=\"noopener noreferrer\">Google Chrome Releases, June 16, 2026<\/a>: latest desktop Stable 149.0.7827.155\/.156 update and 33 security fixes.<\/li>\n<li><a href=\"https:\/\/chromereleases.googleblog.com\/2026\/06\/stable-channel-update-for-desktop_0153744567.html\" target=\"_blank\" rel=\"noopener noreferrer\">Google Chrome Releases, June 8, 2026<\/a>: 149.0.7827.102\/.103 update, 74 security fixes, and CVE-2026-11645.<\/li>\n<li><a href=\"https:\/\/www.cisa.gov\/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-11645\" target=\"_blank\" rel=\"noopener noreferrer\">CISA KEV search for CVE-2026-11645<\/a>: date added, due date, and Chromium-based browser scope.<\/li>\n<li><a href=\"https:\/\/support.google.com\/chrome\/answer\/95414?co=GENIE.Platform%3DDesktop&amp;hl=en\" target=\"_blank\" rel=\"noopener noreferrer\">Google Chrome update help<\/a>: official steps for checking and relaunching Chrome.<\/li>\n<li><a href=\"https:\/\/learn.microsoft.com\/en-us\/deployedge\/microsoft-edge-relnotes-security\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Edge security release notes<\/a>: Edge Stable Channel security update details.<\/li>\n<\/ul>\n<h2>FAQ<\/h2>\n<p><strong>If Chrome updates automatically, is there anything else to do?<\/strong><br \/>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.<\/p>\n<p><strong>Is 149.0.7827.102\/.103 enough?<\/strong><br \/>The June 8 build addressed important issues including CVE-2026-11645. But because Google released a newer June 16 Stable update, today\u2019s practical target is 149.0.7827.155\/.156 or later on desktop.<\/p>\n<p><strong>Does this matter if I use Edge or Opera?<\/strong><br \/>Possibly. CISA says the vulnerability can affect multiple Chromium-based browsers. Use each browser\u2019s official update screen rather than assuming Chrome-only language excludes you.<\/p>\n<h2>Bottom Line<\/h2>\n<p>Desktop Chrome users should open <code>chrome:\/\/settings\/help<\/code> today and confirm <strong>149.0.7827.155\/.156 or later<\/strong> on Windows or Mac, and <strong>149.0.7827.155 or later<\/strong> 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.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Google updated Chrome desktop Stable to 149.0.7827.155\/.156 on June 16, 2026 with 33 security fixes. Because CISA added CVE-2026-11645 to its known exploited catalog on June 9, users should check the installed Chrome or Chromium-based browser version today.<\/p>\n","protected":false},"featured_media":0,"template":"","meta":[],"class_list":["post-193","briefing","type-briefing","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/onepress.co.kr\/index.php\/wp-json\/wp\/v2\/briefing\/193","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/onepress.co.kr\/index.php\/wp-json\/wp\/v2\/briefing"}],"about":[{"href":"https:\/\/onepress.co.kr\/index.php\/wp-json\/wp\/v2\/types\/briefing"}],"wp:attachment":[{"href":"https:\/\/onepress.co.kr\/index.php\/wp-json\/wp\/v2\/media?parent=193"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}