{"id":404706,"date":"2026-08-22T02:49:37","date_gmt":"2026-08-22T02:49:37","guid":{"rendered":"https:\/\/malwaretips.com\/blogs\/?p=404706"},"modified":"2026-08-22T02:49:37","modified_gmt":"2026-08-22T02:49:37","slug":"chrome-151-7922-173","status":"publish","type":"post","link":"https:\/\/malwaretips.com\/blogs\/chrome-151-7922-173\/","title":{"rendered":"Google Chrome 151.0.7922.173 Update Fixes Seven Serious Security Flaws"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Chrome is the tab that stays open: mail, the bank, the shop booking page. Google posted another Stable on Thursday, 20 August 2026, seven new security fixes after Tuesday&#8217;s 169 train. The Critical hole is a use-after-free in Chromoting, Chrome&#8217;s remote-desktop stack.<\/p><div id=\"mwtad1354095092\" class=\"gas_fallback-ad_309684--placement_400588\" style=\"margin-top: 30px;margin-bottom: 30px;\"><script async src=\"\/\/pagead2.googlesyndication.com\/pagead\/js\/adsbygoogle.js?client=ca-pub-7750719144850257\" crossorigin=\"anonymous\"><\/script><ins class=\"adsbygoogle\" style=\"display:block;\" data-ad-client=\"ca-pub-7750719144850257\" \ndata-ad-slot=\"3957935887\" \ndata-ad-format=\"auto\" data-full-width-responsive=\"true\"><\/ins>\n<script> \n(adsbygoogle = window.adsbygoogle || []).push({}); \n<\/script>\n<\/div>\n\n\n\n<p class=\"wp-block-paragraph\">The same installer also closes a use-after-free in the DOM, the machinery a page uses to draw itself. Open Settings, About Chrome, wait for 151.0.7922.173 or 151.0.7922.174, and Relaunch. If About still reads 169 or 170, you are not done.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1280\" height=\"800\" src=\"https:\/\/malwaretips.com\/blogs\/wp-content\/uploads\/2026\/08\/google-chrome-151-0-7922-173-official-release.png\" alt=\"Official Google Chrome release page for version 151.0.7922.173\" class=\"wp-image-404719\" title=\"\" srcset=\"https:\/\/malwaretips.com\/blogs\/wp-content\/uploads\/2026\/08\/google-chrome-151-0-7922-173-official-release.png 1280w, https:\/\/malwaretips.com\/blogs\/wp-content\/uploads\/2026\/08\/google-chrome-151-0-7922-173-official-release-300x188.png 300w, https:\/\/malwaretips.com\/blogs\/wp-content\/uploads\/2026\/08\/google-chrome-151-0-7922-173-official-release-1024x640.png 1024w\" sizes=\"auto, (max-width: 1280px) 100vw, 1280px\" \/><\/figure>\n\n\n\n<div id=\"mwtad4125683311\" class=\"gas_fallback-ad_309747-ad_309691-placement_400589\" style=\"margin-top: 30px;margin-bottom: 30px;\"><script async src=\"\/\/pagead2.googlesyndication.com\/pagead\/js\/adsbygoogle.js?client=ca-pub-7750719144850257\" crossorigin=\"anonymous\"><\/script><ins class=\"adsbygoogle\" style=\"display:block;\" data-ad-client=\"ca-pub-7750719144850257\" \ndata-ad-slot=\"9589536513\" \ndata-ad-format=\"auto\" data-full-width-responsive=\"true\"><\/ins>\n<script> \n(adsbygoogle = window.adsbygoogle || []).push({}); \n<\/script>\n<\/div><h2 class=\"wp-block-heading\">Overview<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What broke<\/h3>\n\n\n\n<div id=\"mwtad3773781513\" class=\"mwtadp1 mwtadentity-placement\" style=\"margin-top: 50px;margin-bottom: 50px;\"> \r\n<ins class=\"adsbygoogle\"\r\n     style=\"display:block; text-align:center;\"\r\n     data-ad-layout=\"in-article\"\r\n     data-ad-format=\"fluid\"\r\n     data-ad-client=\"ca-pub-7750719144850257\"\r\n     data-ad-slot=\"7312657698\"><\/ins>\r\n <\/div><p class=\"wp-block-paragraph\">On 20 August 2026 Google released a Chrome Stable desktop build with 7 security fixes. One of them is rated Critical. <a href=\"https:\/\/chromereleases.googleblog.com\/2026\/08\/stable-channel-update-for-desktop_0404570826.html\" target=\"_blank\" rel=\"noopener\">The stable channel update for desktop<\/a> names <a href=\"https:\/\/nvd.nist.gov\/vuln\/detail\/CVE-2026-76017\" target=\"_blank\" rel=\"noopener\">CVE-2026-76017<\/a> as a use after free in Chromoting. Google&#8217;s own team reported it on 11 June 2026.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bug details stay locked until most people have the fix. That is Google&#8217;s usual rule, not a hint they are already in use.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A use-after-free occurs when software accesses memory after that memory has already been released. Depending on the surrounding conditions, the flaw may cause a crash or become part of a more serious attack. Chromoting is Chrome&#8217;s remote-desktop component.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The same release also fixes <a href=\"https:\/\/nvd.nist.gov\/vuln\/detail\/CVE-2026-76021\" target=\"_blank\" rel=\"noopener\">CVE-2026-76021<\/a>, a use-after-free in the DOM reported on 2 August 2026. The DOM is the browser&#8217;s structured representation of a page&#8217;s content and elements. Google has not published detailed exploitation steps for either issue.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Five more Highs ride the same installer: CVE-2026-76018 privilege elevation in Import, CVE-2026-76019 incorrect authorization in Workers, CVE-2026-76020 a race in V8, CVE-2026-76022 a buffer overflow in Network, and CVE-2026-76023 improper resource control in Linux Toolkit Theming. One click covers the set.<\/p>\n\n\n\n<div id=\"mwtad3474846770\" class=\"gas_fallback-ad_309686-ad_309691-placement_400597\" style=\"margin-top: 30px;margin-bottom: 30px;\"><script async src=\"\/\/pagead2.googlesyndication.com\/pagead\/js\/adsbygoogle.js?client=ca-pub-7750719144850257\" crossorigin=\"anonymous\"><\/script><ins class=\"adsbygoogle\" style=\"display:block;\" data-ad-client=\"ca-pub-7750719144850257\" \ndata-ad-slot=\"6935453015\" \ndata-ad-format=\"auto\" data-full-width-responsive=\"true\"><\/ins>\n<script> \n(adsbygoogle = window.adsbygoogle || []).push({}); \n<\/script>\n<\/div><div id=\"mwtad3955370162\" class=\"mwtadp3 mwtadentity-placement\" style=\"margin-top: 30px;margin-bottom: 30px;\"><script async src=\"https:\/\/pagead2.googlesyndication.com\/pagead\/js\/adsbygoogle.js?client=ca-pub-7750719144850257\"\r\n     crossorigin=\"anonymous\"><\/script>\r\n<ins class=\"adsbygoogle\"\r\n     style=\"display:block; text-align:center;\"\r\n     data-ad-layout=\"in-article\"\r\n     data-ad-format=\"fluid\"\r\n     data-ad-client=\"ca-pub-7750719144850257\"\r\n     data-ad-slot=\"5910219726\"><\/ins>\r\n<script>\r\n     (adsbygoogle = window.adsbygoogle || []).push({});\r\n<\/script><\/div><p class=\"wp-block-paragraph\">Google has not said any of these seven are being used in the wild. CISA has not listed 76017 or 76021 on the <a href=\"https:\/\/www.cisa.gov\/known-exploited-vulnerabilities-catalog\" target=\"_blank\" rel=\"noopener\">Known Exploited Vulnerabilities catalog<\/a>. The updater is already in the three-dot menu.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/chromereleases.googleblog.com\/2026\/08\/chrome-for-android-update_0418479132.html\" target=\"_blank\" rel=\"noopener\">The Chrome for Android update<\/a> carries the same security work as desktop 173 and 174.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Who is in range<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Anyone still launching Chrome on Windows, Mac, or Linux below 151.0.7922.173, or on Android below 151.0.7922.173. On Windows and Mac, 174 is the sibling of 173. Either number closed Thursday&#8217;s seven.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If About Chrome still reads 151.0.7922.169, 170, a 150 build, or last week&#8217;s 139-class number, you are in range. Tuesday&#8217;s 169 closed a different set. It does not close 76017.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A shop PC with Chrome pinned as the company browser is in range until About shows 173 or 174. The front-desk machine and the kiosk that only opens a booking page still launch Chrome. Updating Edge does not patch Chrome. Edge-only readers: this Chrome number is not yours.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Firefox and Safari are separate clicks. Thursday&#8217;s holes sit on the Chromium desktop and Android trains.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What the vendor shipped<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Desktop Stable, 20 August 2026: 151.0.7922.173\/.174 for Windows and Mac, 151.0.7922.173 for Linux. This train closed the seven new CVEs.<\/li>\n<li>Android Stable, 20 August 2026: 151.0.7922.173, with the same security fixes as that desktop train.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The floor is 151.0.7922.173 or 151.0.7922.174. Do not stop at a 151 build from earlier in the month if the last slot is still 169 or 170. The in-app path is three dots, Settings, About Chrome.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On some builds it is Help, About Google Chrome. Same tab. Chrome downloads the build itself. You wait, then Relaunch. Phone builds come from Google Play. Stay on About until the number moves.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What this is not<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Not Tuesday&#8217;s 169 and 170 drop. That train closed a different pair. Readers who already took 169 still need 173 or 174.<\/li>\n<li>Not patched by updating Microsoft Edge. Same engine family, different installer, different version line. Edge-only readers can skip this number.<\/li>\n<li>Not on CISA KEV. Google has not said 76017 or 76021 is in the wild.<\/li>\n<li>Not an Android-only story. The Android 173 build carries the same desktop security work. Play Store is step 3, not a second brief.<\/li>\n<li>Not done if you downloaded the build and never hit Relaunch. The old process is still running until Chrome restarts.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The patch is out. About Chrome is already in the menu. That is the cheap window.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1536\" height=\"1024\" src=\"https:\/\/malwaretips.com\/blogs\/wp-content\/uploads\/2026\/08\/do-this-now-chrome173-house.png\" alt=\"Chrome 151.0.7922.173 update reminder\" class=\"wp-image-404705\" title=\"\" srcset=\"https:\/\/malwaretips.com\/blogs\/wp-content\/uploads\/2026\/08\/do-this-now-chrome173-house.png 1536w, https:\/\/malwaretips.com\/blogs\/wp-content\/uploads\/2026\/08\/do-this-now-chrome173-house-300x200.png 300w, https:\/\/malwaretips.com\/blogs\/wp-content\/uploads\/2026\/08\/do-this-now-chrome173-house-1024x683.png 1024w\" sizes=\"auto, (max-width: 1536px) 100vw, 1536px\" \/><\/figure>\n\n\n\n<div id=\"mwtad2514977481\" class=\"gas_fallback-ad_309748-ad_309691-placement_400590\" style=\"margin-top: 30px;margin-bottom: 30px;\"><script async src=\"\/\/pagead2.googlesyndication.com\/pagead\/js\/adsbygoogle.js?client=ca-pub-7750719144850257\" crossorigin=\"anonymous\"><\/script><ins class=\"adsbygoogle\" style=\"display:block;\" data-ad-client=\"ca-pub-7750719144850257\" \ndata-ad-slot=\"3906789406\" \ndata-ad-format=\"auto\" data-full-width-responsive=\"true\"><\/ins>\n<script> \n(adsbygoogle = window.adsbygoogle || []).push({}); \n<\/script>\n<\/div><h2 class=\"wp-block-heading\">Do This Now<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>In range:<\/strong> You. Chrome below 151.0.7922.173 on Windows, Mac, Linux, or Android. On Windows and Mac, 174 also counts.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Urgency:<\/strong> Today. The Critical hole is in the browser you already click. The updater is already in the three-dot menu.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Open Chrome. Three dots, Settings, About Chrome. On some builds: Help, About Google Chrome.<\/li>\n<li>Wait until it shows 151.0.7922.173 or 151.0.7922.174, then Relaunch.<\/li>\n<li>On the phone: Google Play, Chrome, Update, then swipe it away and reopen it. Confirm 151.0.7922.173.<\/li>\n<\/ol>\n\n\n\n<div id=\"mwtad3842901648\" class=\"gas_fallback-ad_309749-ad_309691-placement_400591\" style=\"margin-top: 30px;margin-bottom: 30px;\"><script async src=\"\/\/pagead2.googlesyndication.com\/pagead\/js\/adsbygoogle.js?client=ca-pub-7750719144850257\" crossorigin=\"anonymous\"><\/script><ins class=\"adsbygoogle\" style=\"display:block;\" data-ad-client=\"ca-pub-7750719144850257\" \ndata-ad-slot=\"5354318971\" \ndata-ad-format=\"auto\" data-full-width-responsive=\"true\"><\/ins>\n<script> \n(adsbygoogle = window.adsbygoogle || []).push({}); \n<\/script>\n<\/div><h2 class=\"wp-block-heading\">Who can skip<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>About Chrome already shows 151.0.7922.173 or 151.0.7922.174, and you have relaunched once.<\/li>\n<li>Android Chrome already shows 151.0.7922.173, and no desktop Chrome in the house is still below 173.<\/li>\n<li>Safari-only on iPhone, and Chrome is not installed on any PC you click.<\/li>\n<li>Firefox-only, and you have confirmed Chrome is not the handler for Mail or Start links.<\/li>\n<li>Edge-only. Edge has its own updater and its own number. Do not type 151.0.7922.173 into Edge and call it done.<\/li>\n<li>Chrome is not installed on the PCs or phones you use.<\/li>\n<\/ul>\n\n\n\n<div id=\"mwtad3658624661\" class=\"gas_fallback-ad_309750-ad_309691-placement_400592\" style=\"margin-top: 30px;margin-bottom: 30px;\"><script async src=\"\/\/pagead2.googlesyndication.com\/pagead\/js\/adsbygoogle.js?client=ca-pub-7750719144850257\" crossorigin=\"anonymous\"><\/script><ins class=\"adsbygoogle\" style=\"display:block;\" data-ad-client=\"ca-pub-7750719144850257\" \ndata-ad-slot=\"4041237300\" \ndata-ad-format=\"auto\" data-full-width-responsive=\"true\"><\/ins>\n<script> \n(adsbygoogle = window.adsbygoogle || []).push({}); \n<\/script>\n<\/div><h2 class=\"wp-block-heading\">Why it matters<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Chrome often holds active sessions for email, banking, password managers, and business dashboards. Memory-safety flaws in browser components matter because successful exploitation can sometimes lead to code execution or the loss of a security boundary. Google rates CVE-2026-76017 Critical and the other six fixes High severity.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The fixed components include Chromoting, Import, Workers, V8, the DOM, Network, and Linux Toolkit Theming. Google has not published enough technical detail to define a reliable click-by-click attack path. The practical response is still straightforward: install the Stable update that closes all seven flaws.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Google did not put an exploited flag on these CVEs. CISA has not added them to KEV. Waiting is still how a Critical Chromoting hole sits on the default browser for a week while you keep clicking through Mail.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Tuesday&#8217;s 169 and 170 are still worth having if you missed them. They are not Thursday&#8217;s floor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A shop that images PCs once a quarter is the other half of in range. The machine that &#8220;only opens one site&#8221; still launches Chrome. Edge needs its own About screen. Chrome&#8217;s 173 is not Edge&#8217;s build number.<\/p>\n\n\n\n<div id=\"mwtad1087625401\" class=\"gas_fallback-ad_309751-ad_309691-placement_400593\" style=\"margin-top: 50px;margin-bottom: 50px;\"><script async src=\"\/\/pagead2.googlesyndication.com\/pagead\/js\/adsbygoogle.js?client=ca-pub-7750719144850257\" crossorigin=\"anonymous\"><\/script><ins class=\"adsbygoogle\" style=\"display:block;\" data-ad-client=\"ca-pub-7750719144850257\" \ndata-ad-slot=\"3690286463\" \ndata-ad-format=\"auto\" data-full-width-responsive=\"true\"><\/ins>\n<script> \n(adsbygoogle = window.adsbygoogle || []).push({}); \n<\/script>\n<\/div><h2 class=\"wp-block-heading\">Common Chrome Update Mistakes<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Checking the daily browser but missing the spare computer<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The computer in front of you is only one installation. A laptop in a bag, a shared family PC, a front-desk workstation, or a rarely used shop terminal may still carry the older build. Each copy needs its own About Chrome check.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Make a quick inventory of the devices that actually launch Chrome. You do not need asset-management software for a small household or shop. Open About Chrome on each machine, record the version, and restart any device that is below the fixed release.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Stopping after the download<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Chrome can download an update while the older browser process keeps running. Until you click Relaunch or fully close every Chrome window, the vulnerable code may still be active. The download bar is progress, not proof that installation is complete.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">After the browser reopens, return to About Chrome and read the complete four-part number. This second check catches interrupted installs, background processes that never closed, and managed devices that downloaded a package but did not finish applying it.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Following a fake browser update prompt<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Malicious websites often display convincing Chrome update warnings. They may offer a ZIP file, installer, browser extension, or command to paste into a terminal. A web page cannot reliably inspect your installed Chrome build, and it should not be trusted as the updater.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Use Chrome&#8217;s own Settings or Help menu on a desktop. On Android, use Google Play. If a page tells you to disable security software, install a special codec, or run a command before updating, close the page and use the normal update path.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Assuming a managed browser will update itself<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Business and school computers may receive Chrome through Group Policy, MDM, or a software catalog. The About page can show that updates are controlled by an administrator. Repeatedly opening the page will not override a policy that holds the older version.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Report the exact current version and the required fixed version to the administrator. Ask when the deployment will reach the device, then verify after that window. A central console saying the package was assigned is useful, but the local About screen is the final check.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Confusing the Chrome channel or a different browser<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Stable, Beta, Dev, and Canary can show different build numbers. Most readers should remain on Stable and take the fixed Stable release. Do not switch channels simply to force a number unless you understand the testing and support tradeoffs.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Edge, Brave, Vivaldi, and other Chromium-based browsers use their own release schedules. A Chrome advisory may help their vendors identify shared code, but installing Chrome does not patch those products. Check the About page inside every browser you actually use.<\/p>\n\n\n\n<div id=\"deskad1\" class=\"gas_fallback-ad_174270-ad_309691-placement_400594\" style=\"margin-top: 50px;margin-bottom: 50px;\"><script async src=\"\/\/pagead2.googlesyndication.com\/pagead\/js\/adsbygoogle.js?client=ca-pub-7750719144850257\" crossorigin=\"anonymous\"><\/script><ins class=\"adsbygoogle\" style=\"display:block;\" data-ad-client=\"ca-pub-7750719144850257\" \ndata-ad-slot=\"5700081834\" \ndata-ad-format=\"auto\" data-full-width-responsive=\"true\"><\/ins>\n<script> \n(adsbygoogle = window.adsbygoogle || []).push({}); \n<\/script>\n<\/div><h2 class=\"wp-block-heading\">Complete the Chrome Update<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">On the PC<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Open Google Chrome. Any tab is fine. You do not need a special page.<\/li>\n<li>Click the three dots in the top right. That menu is Customize and control Google Chrome on some builds.<\/li>\n<li>Click Settings, then About Chrome. On some builds click Help, then About Google Chrome. The About page is a real Chrome tab. It will say Google Chrome and a version number, then start checking.<\/li>\n<li>Let it download. The line you want is 151.0.7922.173 or 151.0.7922.174. If the last slot is still 169, 170, 139, or anything below 173, stay on the page.<\/li>\n<li>Click Relaunch when the button appears. Chrome will close every window and reopen them. That is expected. If there is no Relaunch button and the number is already 173 or 174, you are done on this PC.<\/li>\n<li>Open About one more time after the restart and read the number. Do not trust the splash. Trust the About line.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">If About Chrome never moves<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Quit Chrome fully. On Windows, check the system tray and Task Manager for leftover Chrome processes, then reopen Chrome and try About again. A download that sits at 0% is often a store, proxy, or &#8220;metered connection&#8221; block. Use the network you already trust.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Do not download Chrome from a random &#8220;browser update&#8221; site. Google&#8217;s own About page is the installer.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A shop PC with Chrome managed by Group Policy, an MDM tool, or a &#8220;do not update&#8221; catalog will not self-update no matter how many times you open About. Ask whoever owns the image to push 151.0.7922.173 or 151.0.7922.174.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That is the same build. It is just delivered by the shop&#8217;s tool instead of the three-dot menu.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">On the phone and the other PC<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Android: Google Play, Chrome, Update. Swipe the app away and open it once. About should show 151.0.7922.173 or newer.<\/li>\n<li>The laptop in the bag, the shop front-desk PC, the machine that only opens Mail: same Settings, About Chrome path tonight. One stale Chrome is enough.<\/li>\n<li>Edge is a different product with a different About screen. Do not type Chrome&#8217;s 173 into Edge and call it done.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">What you should see<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">On the About tab, under the Google Chrome heading, the version is a four-part number. 151 is the major. 0.7922 is the Chromium train Google is on this month. 173 or 174 is Thursday&#8217;s security build.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you still see 169, 170, 139, or anything below 173 in that last slot, you are not on the floor. Stay on the page. The progress line is the download. The Relaunch button is the close.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">After Relaunch, the same About tab should show the new number without asking again. The official Chrome release page shown above identifies 151.0.7922.173 and 151.0.7922.174 as the fixed desktop builds. The version shown in About Chrome is the number that matters.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">When you are done<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Desktop About reads 151.0.7922.173 or 151.0.7922.174. Android About reads 151.0.7922.173 or newer. Both have been relaunched or force-closed once. Edge is a separate click with a separate number. This tab closes Chrome.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You do not need to clear history or sign out of anything. You needed a new build. You have it.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Frequently Asked Questions<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Which Chrome version fixes these flaws?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">On Windows and Mac, Chrome 151.0.7922.173 or 151.0.7922.174 includes the seven fixes. Linux and Android users should see 151.0.7922.173 or a later build.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Does updating Microsoft Edge also update Chrome?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. Edge and Chrome use separate installers and separate version numbers. Open About Chrome inside Chrome to verify the Google browser itself.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Were these Chrome flaws already exploited?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Google had not identified active exploitation in the 20 August release notice. That does not make the flaws harmless, especially because one is rated Critical.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Will the Chrome update erase passwords or browsing data?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A normal Stable update should preserve bookmarks, passwords, history, and open tabs. Save important work before Relaunch and confirm the version afterward.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How quickly should I install this Chrome update?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Install it today where practical, especially on devices used for email, banking, passwords, or business administration. The fixed Stable build is already available through Chrome&#8217;s normal updater.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What if Chrome already shows a newer build?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A later Stable build includes earlier security fixes unless Google says otherwise. Do not downgrade. Confirm the browser is on the Stable channel and allow its normal update process to continue.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The Bottom Line<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Chrome 151.0.7922.173 and 151.0.7922.174 close seven newly disclosed security flaws, including one Google rates Critical. The update is already available through the browser&#8217;s normal About page.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Update every Chrome installation you use, relaunch it, and confirm the complete version afterward. A newer fixed build is also acceptable. The version check takes a minute and removes the guesswork.<\/p>\n\n<div id=\"mwtad2191884065\" class=\"gas_fallback-ad_176819-ad_309691-placement_400595\" style=\"margin-top: 50px;margin-bottom: 50px;\"><script async src=\"\/\/pagead2.googlesyndication.com\/pagead\/js\/adsbygoogle.js?client=ca-pub-7750719144850257\" crossorigin=\"anonymous\"><\/script><ins class=\"adsbygoogle\" style=\"display:block;\" data-ad-client=\"ca-pub-7750719144850257\" \ndata-ad-slot=\"8386082122\" \ndata-ad-format=\"auto\" data-full-width-responsive=\"true\"><\/ins>\n<script> \n(adsbygoogle = window.adsbygoogle || []).push({}); \n<\/script>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Chrome is the tab that stays open: mail, the bank, the shop booking page. Google posted another Stable on Thursday, 20 August 2026, seven new security fixes after Tuesday&#8217;s 169 train. The Critical hole is &#8230; <\/p>\n<p class=\"read-more-container\"><a title=\"Google Chrome 151.0.7922.173 Update Fixes Seven Serious Security Flaws\" class=\"read-more button\" href=\"https:\/\/malwaretips.com\/blogs\/chrome-151-7922-173\/#more-404706\" aria-label=\"Read more about Google Chrome 151.0.7922.173 Update Fixes Seven Serious Security Flaws\">Read more<\/a><\/p>\n","protected":false},"author":51,"featured_media":404719,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3605],"tags":[],"class_list":["post-404706","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news","masonry-post","generate-columns","tablet-grid-50","mobile-grid-100","grid-parent","grid-50","resize-featured-image"],"_links":{"self":[{"href":"https:\/\/malwaretips.com\/blogs\/wp-json\/wp\/v2\/posts\/404706","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/malwaretips.com\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/malwaretips.com\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/malwaretips.com\/blogs\/wp-json\/wp\/v2\/users\/51"}],"replies":[{"embeddable":true,"href":"https:\/\/malwaretips.com\/blogs\/wp-json\/wp\/v2\/comments?post=404706"}],"version-history":[{"count":1,"href":"https:\/\/malwaretips.com\/blogs\/wp-json\/wp\/v2\/posts\/404706\/revisions"}],"predecessor-version":[{"id":404754,"href":"https:\/\/malwaretips.com\/blogs\/wp-json\/wp\/v2\/posts\/404706\/revisions\/404754"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/malwaretips.com\/blogs\/wp-json\/wp\/v2\/media\/404719"}],"wp:attachment":[{"href":"https:\/\/malwaretips.com\/blogs\/wp-json\/wp\/v2\/media?parent=404706"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/malwaretips.com\/blogs\/wp-json\/wp\/v2\/categories?post=404706"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/malwaretips.com\/blogs\/wp-json\/wp\/v2\/tags?post=404706"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}