Google says that it “is aware that an exploit for CVE-2023-3079 exists in the wild.” This means that patches need to be installed urgently. This particular vulnerability exists in Chromium’s V8 engine.
Whenever Chrome gets a security update, other browsers based on the Chromium open-source Web browser project generally require an update, too. Microsoft Edge, Brave, Vivaldi, and Opera browsers are all built upon the Chromium codebase.
Vivaldi also released an update on June 5. Microsoft Edge and Brave browsers received updates on June 6. Opera finally released a security update (labeled as a back-port of Chrome issue 1450481) on June 7. As usual, Opera took longer than other Chromium-based browsers to release a critical security update.
Mac users can update their Chrome, Edge, Brave, or Opera browsers by clicking on the application menu (e.g. “Chrome” or “Microsoft Edge,” next to the Apple logo menu), and then clicking the first item in that menu (e.g. “About Google Chrome” or “About Microsoft Edge”). The browser will check for updates, and if an update is available, it will prompt you to restart the app to complete the update.
Vivaldi for macOS has a slightly different update procedure. After clicking on the Vivaldi menu (next to the Apple menu), click on “Check for Updates…” to ensure you have the latest version installed.
Windows users can update their browsers by following the steps provided by each browser maker: Chrome, Edge, Brave, Vivaldi, Opera.
Android users should check the Google Play Store app for the latest versions of their browsers and other apps.
Mobile browsers on iOS and iPadOS use Safari’s WebKit engine, rather than Chromium’s Blink and V8 engines. Therefore, this particular vulnerability does not affect the iOS or iPadOS versions of any Web browsers. If you would like to update your iPhone and iPad browsers anyway, you can do so via the App Store. (Here’s how to manually check for and install updates.) Note that Vivaldi for iOS is still an invite-only beta and is not yet available in the App Store.
Sometime after the release of iOS 17 and iPadOS 17, third-party app stores may become a reality—at least in the EU, for compliance with the Digital Markets Act. Apple must comply with the DMA no later than March 2024. It’s possible that third-party stores may eventually distribute alternative browser versions that use their own engines, rather than the WebKit-locked App Store versions.
As we’ve noted in the past, many non-browser apps, including Electron apps, also rely on the Chromium browser codebase for rendering HTML content. These include the desktop versions of apps like 1Password, Discord, Dropbox, Figma, GitHub, Microsoft Teams, Signal, Skype, Slack, Trello, Twitch, WhatsApp, WordPress, and Zoom. Notably, the Electron framework does not get updated in tandem with Chromium, so some Electron-based apps may remain vulnerable for months.
For this and other reasons, it’s important to keep all your other apps updated as well. To update Mac App Store apps, open the App Store, then click Updates, and click on Update All. Other apps usually have their own separate in-app or separate update mechanisms. In some cases, you may need to update an app manually by downloading a new version from the developer’s site.
Chromium vulnerabilities threaten Electron app security
You can also subscribe to our e-mail newsletter and keep an eye here on The Mac Security Blog for the latest Apple security and privacy news. And don’t forget to follow Intego on your favorite social media channels: 
