Google Fixes 52 Chrome Security Flaws: Critical Browser Risks for Nigerian Businesses

Threat Category: Vulnerability Intelligence
Severity: High Priority
Affected Platform: Google Chrome
Fixed Versions: 156.0.8078.73/.74 for Windows and macOS; 156.0.8078.73 for Linux

What Happened?

Google has released a security update for Chrome addressing 52 vulnerabilities, including four critical and 46 high-severity flaws. This release covers browser components responsible for file handling, graphics rendering, JavaScript execution and media processing. The update is rolling out gradually.

Among the critical vulnerabilities are CVE-2026-118306 (memory corruption in FileSystem), CVE-2026-118331 (improper input validation in FileAPI), CVE-2026-118348 (improper input validation in Skia) and CVE-2026-118344 (use-after-free in Layout). These flaws involve errors in how Chrome handles data and manages memory. Depending on exploit conditions, such weaknesses can undermine browser security and potentially enable code execution.

Google has not confirmed that these vulnerabilities are being actively exploited. However, the number and severity of the flaws make timely patching a priority.

Who Is Affected and What Is the Risk?

Organisations and individuals using vulnerable versions of Chrome across Windows, macOS and Linux should verify their browser versions and apply the relevant updates.

For Nigerian banks, fintechs, telecommunications providers and other organisations operating critical services, outdated browsers can expose employees to browser-based attacks. Successful exploitation could compromise browser sessions, disrupt user activity or provide an entry point for further attacks, depending on the vulnerability and surrounding security controls. This is particularly relevant for employees accessing financial platforms, corporate applications and sensitive business information through their browsers.

How Can Organisations Mitigate the Risk?

• Patch promptly: Update Chrome to the fixed versions and verify successful installation across managed endpoints. Prioritise critical and high-severity fixes.

• Verify browser exposure: Identify outdated installations, including browsers on endpoints that may not be covered by centralised patch management.

• Strengthen endpoint monitoring: Monitor available endpoint and network telemetry for suspicious browser processes, unexpected child processes, unusual outbound connections and related post-exploitation activity.

• Reduce exposure: Enforce browser update policies, restrict unnecessary extensions and maintain layered endpoint protection.