Monday, December 9, 2024
HomeChromeChrome 131 Released with the Fix for Multiple Vulnerabilities

Chrome 131 Released with the Fix for Multiple Vulnerabilities

Published on

SIEM as a Service

The Chrome team has officially announced the release of Chrome 131 for Windows, Mac, and Linux. The new version, Chrome 131.0.6778.69 for Linux and 131.0.6778.69/.70 for Windows and Mac is set to roll out to users over the coming days and weeks.

This update includes several security fixes, performance improvements, and other enhancements, making Chrome even more secure and efficient for its global user base.

As with every version update, Chrome 131 comes with several under-the-hood improvements.

- Advertisement - SIEM as a Service

While the full list of changes can be found in the official Chrome log, users can also look forward to upcoming blog posts from Chrome and Chromium that will outline new features and significant efforts delivered in this version.

Free Ultimate Continuous Security Monitoring Guide - Download Here (PDF)

Security Fixes and Rewards

Security remains a top priority for Google, and Chrome 131 addresses multiple vulnerabilities to ensure safer browsing for users.

In total, 12 security issues have been fixed in this release, many of which were identified by external researchers.

Google will restrict access to the detailed bug reports until a majority of users have updated to the latest version to prevent potential exploitation.

If the vulnerabilities affect third-party libraries that other projects rely on, access to details may remain restricted.

Below is a detailed list of the security vulnerabilities addressed in Chrome 131, including the relevant CVE (Common Vulnerabilities and Exposures) identifiers, descriptions, severity levels, and who reported them.

CVE IDSeverityVulnerability DescriptionDate Reported
CVE-2024-11110HighInappropriate implementation in Blink2024-10-14
CVE-2024-11111MediumInappropriate implementation in Autofill2024-08-18
CVE-2024-11112MediumUse after free in Media2024-07-23
CVE-2024-11113MediumUse after free in Accessibility2024-08-16
CVE-2024-11114MediumInappropriate implementation in Views2024-10-02
CVE-2024-11115MediumInsufficient policy enforcement in Navigation2024-10-07
CVE-2024-11116MediumInappropriate implementation in Paint2023-11-14
CVE-2024-11117LowInappropriate implementation in FileSystem2023-01-06

In addition to the fixes contributed by external researchers, Google’s ongoing internal security efforts have played a crucial role in addressing various issues.

Through internal audits, fuzzing, and other initiatives, several vulnerabilities were identified and fixed before they could affect users.

Run private, Real-time Malware Analysis in both Windows & Linux VMs. Get a 14-day free trial with ANY.RUN!

Divya
Divya
Divya is a Senior Journalist at GBhackers covering Cyber Attacks, Threats, Breaches, Vulnerabilities and other happenings in the cyber world.

Latest articles

Google Announces Vanir, A Open-Source Security Patch Validation Tool

Google has officially launched Vanir, an open-source security patch validation tool designed to streamline and...

New Transaction-Relay Jamming Vulnerability Let Attackers Exploits Bitcoin Nodes

A newly disclosed transaction-relay jamming vulnerability has raised concerns about the security of Bitcoin...

Raspberry Pi 500 & Monitor, Complete Desktop Setup at $190

Raspberry Pi, a pioneer in affordable and programmable computing, has once again elevated its...

Qlik Sense for Windows Vulnerability Allows Remote Code Execution

Qlik has identified critical vulnerabilities in its Qlik Sense Enterprise for Windows software that...

API Security Webinar

72 Hours to Audit-Ready API Security

APIs present a unique challenge in this landscape, as risk assessment and mitigation are often hindered by incomplete API inventories and insufficient documentation.

Join Vivek Gopalan, VP of Products at Indusface, in this insightful webinar as he unveils a practical framework for discovering, assessing, and addressing open API vulnerabilities within just 72 hours.

Discussion points

API Discovery: Techniques to identify and map your public APIs comprehensively.
Vulnerability Scanning: Best practices for API vulnerability analysis and penetration testing.
Clean Reporting: Steps to generate a clean, audit-ready vulnerability report within 72 hours.

More like this

Google Announces Vanir, A Open-Source Security Patch Validation Tool

Google has officially launched Vanir, an open-source security patch validation tool designed to streamline and...

New Transaction-Relay Jamming Vulnerability Let Attackers Exploits Bitcoin Nodes

A newly disclosed transaction-relay jamming vulnerability has raised concerns about the security of Bitcoin...

Raspberry Pi 500 & Monitor, Complete Desktop Setup at $190

Raspberry Pi, a pioneer in affordable and programmable computing, has once again elevated its...