CVE-2026-0905

9.8 CRITICAL

📋 TL;DR

This vulnerability in Google Chrome allows attackers who obtain network log files to potentially extract sensitive information due to insufficient policy enforcement. It affects all users running Chrome versions prior to 144.0.7559.59. The attack requires access to network logs, which could be obtained through various means including malware or compromised systems.

💻 Affected Systems

Products:
  • Google Chrome
  • Chromium-based browsers
Versions: All versions prior to 144.0.7559.59
Operating Systems: Windows, macOS, Linux, ChromeOS
Default Config Vulnerable: ⚠️ Yes
Notes: All standard Chrome installations are vulnerable. The vulnerability requires attackers to obtain network log files, which may be stored locally or on network shares.

📦 What is this software?

Chrome by Google

Google Chrome is the world's most popular web browser, used by over 3 billion users globally across Windows, macOS, Linux, Android, and iOS platforms. As a Chromium-based browser developed by Google, Chrome dominates the browser market with approximately 65% market share, making it a critical compon...

Learn more about Chrome →

Chrome by Google

Google Chrome is the world's most popular web browser, used by over 3 billion users globally across Windows, macOS, Linux, Android, and iOS platforms. As a Chromium-based browser developed by Google, Chrome dominates the browser market with approximately 65% market share, making it a critical compon...

Learn more about Chrome →

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could extract authentication tokens, session cookies, API keys, or other sensitive data from network logs, leading to account takeover, data breaches, or lateral movement within networks.

🟠

Likely Case

Attackers with access to network logs could extract some sensitive information like URLs, partial request data, or metadata that could be used for reconnaissance or targeted attacks.

🟢

If Mitigated

With proper access controls on log files and network segmentation, the impact is limited to the specific systems where logs are accessible.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: HIGH

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Exploitation requires access to network log files. No public exploit code has been identified, but the vulnerability is relatively straightforward to exploit once log files are obtained.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 144.0.7559.59 and later

Vendor Advisory: https://chromereleases.googleblog.com/2026/01/stable-channel-update-for-desktop_13.html

Restart Required: Yes

Instructions:

1. Open Chrome and click the three-dot menu. 2. Go to Help > About Google Chrome. 3. Chrome will automatically check for updates and install version 144.0.7559.59 or later. 4. Click 'Relaunch' to restart Chrome with the update.

🔧 Temporary Workarounds

Restrict access to Chrome network logs

all

Set file permissions to prevent unauthorized access to Chrome's network log files

chmod 600 ~/.config/google-chrome/Default/Network\ Logs/*
icacls "%LOCALAPPDATA%\Google\Chrome\User Data\Default\Network Logs\*" /deny Everyone:(R)

Disable network logging

all

Turn off Chrome's network logging feature to prevent log file creation

chrome://flags/#enable-network-logging - set to Disabled

🧯 If You Can't Patch

  • Implement strict access controls on directories containing Chrome log files
  • Monitor for unauthorized access attempts to Chrome log directories

🔍 How to Verify

Check if Vulnerable:

Check Chrome version by navigating to chrome://version and verifying version is below 144.0.7559.59

Check Version:

google-chrome --version

Verify Fix Applied:

Confirm Chrome version is 144.0.7559.59 or higher in chrome://version

📡 Detection & Monitoring

Log Indicators:

  • Unauthorized access to Chrome log directories
  • Abnormal file reads from Chrome network log locations

Network Indicators:

  • Unusual outbound connections following access to Chrome log files

SIEM Query:

source="*chrome*" AND (event="FileRead" OR event="FileAccess") AND (file_path="*Network Logs*" OR file_path="*chrome_debug.log*")

🔗 References

📤 Share & Export