Tag: chrome

If you have installed Google Chrome on one of your devices, then you may want to start the browser’s update engine immediately to update it to the latest version.

Google released a new version of Chrome for desktop and Android to fix a 0-day vulnerability in the browser. This one is exploited in the wild, which means that there is a chance that the issue may be exploited when you run older versions of the Google browser.

The official release notes list CVE-2025-6554 as a type confusion issue in V8, the JavaScript engine that Google Chrome uses. A type confusion vulnerability exploits a flaw in software where a program mistakes a specific type of data for another. This can lead to unexpected behavior, which threat actors may exploit in attacks.

Google mentions that the issue was reported by Clément Lecigne of Google’s Threat Analysis Group on June 25th, 2025. Google says that it mitigated the issue a day later by pushing a configuration change to the stable channel of the browser across all platforms.

This suggests that most devices — all that received the configuration change — are protected from attacks targeting the vulnerability. Still, it is recommended to update the browser immediately.

Desktop users, those who run Google Chrome on Windows, Mac, or Linux devices may select Menu > Help > About Google Chrome to do so. Chrome runs a check for updates and will install the new version automatically. Note that a restart of the browser is necessary to complete the process.

Tip: Windows users may also run winget upgrade google.chrome.exe in Terminal to upgrade the browser to the new version without first starting it.

Android users are not so lucky. The update depends on Google Play in that case, and that may take a while. There is no option to speed up the installation of the mobile browser on Android, if installed via Google Play.

Windscribe is a popular VPN solution thanks to its free version, privacy features, and interesting build a plan feature. Windscribe users may install the official extension to integrate the VPN better into Google Chrome and other Chromium-based browsers, and get several privacy features on top.

The extension adds features such as ad blocking, webRTC blocking, cookie-banner hiding, and much more.

This just happened: The developers confirmed on X that Google is blocking the latest extension update from its Chrome Web Store.

The provided screenshot shows that Google claims that the extension does not comply with the “Single Use” policy for Chrome extensions.

Good to know: The Single Purpose Policy requires that extensions focus on one specific function or theme. Google says that this improves the user experience.

The posted screenshot of the Google email shows that Google claims that the “extension is providing multiple unrelated functionalities”, such as “masking physical location”, “circumventing censorship”, and “blocking ads and trackers”.

Google is asking the developers of the extension to modify it, so that it offers a “narrowly-focused single functionality”.

Windscribe appealed Google’s objection to no avail. As it stands, Windscribe is blocked from updating its extension on the Chrome Web Store.

Tip: you can check out the Windscribe extension for Firefox, which does not have any of these issues.

This is not the first time that legitimate popular extensions have issues with the update process on the Chrome Web Store. Google’s Store is the default location for most Chromium-based browsers when it comes to extensions.

Several browsers, including Brave, do not operate their own extensions store. While some do, Microsoft with Edge or Opera with its Opera Web Browser, the majority relies on extensions from the Chrome Web Store. Even the two mentioned browsers have limited extensions listed in their respective stores.

As for Windscribe, it will be interesting to see how this works out for the company. Usually, public attention is required to get Google to look deeper into the matter and change its stance on a violation.

Google released a new security update for its Chrome web browser that fixes three security issues, including one that is exploited in the wild.

The security issue affects the desktop versions of Google Chrome and the Android version. Desktop users may select Menu > Help > About Google Chrome to install the security update immediately. Google says that it may take days or even weeks before updates may be installed automatically on systems running Google Chrome.

Google reveals basic information about two of the three vulnerabilities. The vulnerability that is exploited in the wild is CVE-2025-5419. It is an out of bounds read and write vulnerability in Chrome’s JavaScript engine that is rated high.

Google reveals that it mitigated the issue on May 28th already. It released a configuration change on the day that it “pushed out to Stable across all Chrome platforms”. Many systems running Chrome should have received the update on that day or the following days already.

Google confirmed that the security issue is exploited in the wild, but did not reveal additional information at the time. The scope of the attack and the attack vector are unknown because of this. Google limits access to security information, including information about patched security issues, to avoid giving malware groups and developers additional hints about the issue.

Chrome users may display the current version of the web browser by loading chrome://settings/help on desktop systems. Google displays on the page if Chrome is up to date.

The following versions should be displayed after installation of the update.

• Chrome for Windows or Mac: 137.0.7151.68 or 137.0.7151.69
• Chrome for Linux: 137.0.7151.68
• Chrome for Android: 137.0.7151.72

Android users can’t speed up the installation of the update.

Now You: do you use Chrome or have the browser installed? Feel free to leave a comment down below.

Google released a security update for its Chrome web browser for the desktop and Android that fixes several security issue. One of the issues is rated high and already exploited on the Internet according to Google.

The details:

• The update is available for Chrome on Windows, Linux, Mac, and Android.
• It includes fixes for four security issues in total.
• The update is a point update for Chrome 136.

The security update changes the version of the Chrome web browser to the following versions:

• Windows and Mac: 136.0.7103.113 or 136.0.7103.114
• Linux: 136.0.7103.113
• Android: 136.0.7103.125

Google lists just two of the fixed security issues on the official Chrome Releases blog. One of them is CVE-2025-4664, which is rated high and described as a “insufficient policy enforcement in loader” security issue.

Malicious users may exploit the issue to “leak cross-origin data via a crafted HTML page”. Google notes that it is aware of exploits in the wild, but does not provide additional information on the scope of the attacks.

Chrome users are encouraged to update their browser immediately to protect their data against potential attacks targetting the vulnerability.

Desktop users may select Menu > Help > About Google Chrome to run a check for updates. This should pick up the latest version and install it on the device. Android users can’t speed up the installation of the update unfortunately.

It is possible that other Chromium-based browsers are also affected by the issue. Expect security updates for these browsers in the coming hours and days as well.

Google has been hard at work to establish Manifest V3 as the new and only set of rules for Chrome extensions. Report suggest that Google has shifted the process into a higher gear and is disabling classic extension support for more Chrome users.

The effect is the following: any extension that is not compatible with Manifest V3 will be disabled. Chrome displays “was turned off” messages to users in that case on start. A check of the extensions management page reveals a similar message: “This extension was turned off because it’s no longer supported”.

Most Chrome users will probably experience this with the popular uBlock Origin extension. It cannot be ported fully to Manifest V3, as Google changed core functionality.

In other words, the change has a very positive effect for Google, as it gets rid of what is probably the most popular content blocker for Chrome.

While there is uBlock Origin Lite by the same developer, it is limited in some regards to the classic version. It is better than no content blocking, but still inferior.

Users who really need to use Chrome can postpone the death of uBlock Origin and other Chrome extensions that are not compatible with Manifest V3 by setting a policy. This will work only until mid-2025 though, unless Google pushes the change back a bit.

Your options

In the end, it may be better to switch to a browser that is still offering support. If you prefer Chromium, you could give Brave or Opera a try. Both companies have pledged to support Manifest V2 extensions, at least some of them, even after Google ends support in Chrome.

Another option is to switch to Firefox or a Firefox fork, like Mullvad Browser. Mozilla said that it is going to support Manifest V2 extensions and V3 extensions at the same time in Firefox. Means, you can run good old uBlock Origin in Firefox without having to worry about it suddenly being turned off.

Google is apparently testing a new privacy feature in Chrome that blocks third-party cookies by default in the browsers Incognito mode.

While that is great that Google is introducing the change, most Internet users may want to take matters into their own hands instead.

Why not block third-party cookies altogether? Yes, there is a tiny-tiny chance that some services may not work correctly anymore when you make the change. Most users on the other hand should not notice any ill-effects.

Here is the main benefit: advertisers and sites can no longer use third-party cookies to track you on the Internet.

One of the biggest offenders is Google, as it operates ads and other services on the majority of websites.

While disabling third-party cookies won’t do you much good in regards to Google, as you are using Chrome and therefore likely an open book to Google anyway, it does against many other firms on the Internet that track users for financial gains.

Here is how you disable third-party cookies in Chrome:

1. Load chrome://settings/cookies in the Chrome address bar. You may also select Menu > Settings > Privacy and security > Third-party cookies to get there manually.
2. Enable “Block third-party cookies”.
3. Disable “Allow related sites to see your activity in the group”.

The change is active right away. Use the browser normally and take note of any issues that you may encounter. This can be login related issues or other issues, such as missing functionality on websites.

You may add sites to an allow list. If you notice that a site misbehaves after you switched third-party cookies off, you may add it to the list of exceptions to see if that resolves the issue.

Here is how that is done:

1. Load chrome://settings/cookies again in the address bar.
2. Click on the add button under “Sites allowed to use third-party cookies.
3. Add [*.]domainname to add an exception for the entire site. Replace “domainname” with the name of the actual domain, e.g., chipp.in.

Verify that the change has fixed the issue that you have experienced.

Clearly, you’d also want to install a content blocker to speed up web browsing and improve privacy further.

Browser extensions are great. They improve usability and functionality on the Internet. From blocking ads and tracking over creating screenshots to improving password management or games.

All extensions come with a manifest file. This file defines rights and permissions. One of these sets the websites the extension is designed to run on. This can be a single website, part of a domain, or on the entire Internet.

Chromium has a great usability feature to limit the access of extensions. You can use it for the following:

• Allow an extension to only run on sites you select.
• Block an extension from running automatically. Make it run only when you want it to.

This may sound complicated, but it can increase privacy or performance significantly. Here is how you use the feature.

Limiting extensions in Chrome and other Chromium-based browsers

Make sure you have one extension installed. This works in Chrome, Brave, and many other Chromium-based browsers.

1. Right-click on the icon of the extension in the toolbar of the browser. Some extension icons may not be displayed. You find them when you click on the general extensions icon in that case.
2. Move the cursor over “This can read and change site data”.
3. Select one of the following options:
   • When you click the extension: this prevents the extension from running automatically when the website is opened. You need to click on its icon to load it.
   • On “sitename”: this allows the extension to run on the active website.
   • On “all sites”: this allows the extension to run on all websites (it is configured for).

Some notes:

• Functionality of some extensions may be reduced or not available when you select the click to run option. A prime example for this are ad blockers, which need to run when the site loads.
• When you select the option to run an extension on a specific site, it is set to “click to run” on any other site you have not picked.
• You may modify the setting at any time.

The list of allowed sites is manageable. You find it under Chrome menu > Extensions > Details of the extensions.

There you see “site access”, which lists all allowed sites. You may also add new sites there, if you prefer that.

Closing Words

The ability to restrict extension access in Chrome can be mighty useful. While it depends on the installed extensions, it may limit extension access to sites that you want to use the extensions on.

Sometimes, you may need extension functionality on a single site only. With this feature, you can do that exactly.

Mozilla has the feature “under development” apparently, but this has been the case for more than three years. Will it ever be a part of Firefox? I do not know.

What is your take on the feature? Do you use it actively, or is it the first time you hear about it? Let everyone know in the comment section below.