dbcve.org
ChromeWeb browser · Google

CVE-2026-0905

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-20
Fix available
A fix is available. Upgrade to 144.0.7559.59 / 144.0.7559.60 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Insufficient policy enforcement in Network in Google Chrome prior to 144.0.7559.59 allowed an attack who obtained a network log file to potentially obtain potentially sensitive information via a network log file. (Chromium security severity: Medium)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Insufficient policy enforcement in Chrome's Network component allows an attacker who has obtained a network log file to potentially extract sensitive information. The vulnerability exists in versions prior to 144.0.7559.59 and stems from improper handling of network log file access controls.

MitigationUpdate Google Chrome to version 144.0.7559.59 or later. In enterprise environments, review and restrict access to network log files as a defense-in-depth measure until the patch is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChromeWeb browser
Affected:< 144.0.7559.59< 144.0.7559.60

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Chrome version
    Navigate to chrome://settings/help or use 'chrome --version' from command line to determine the installed version
    Affected if Version is below 144.0.7559.59 or 144.0.7559.60 (note: two affected version ranges exist in different release channels)
  2. Verify if network logging (net-internals) is enabled
    Navigate to chrome://net-internals in the browser and check if logging is active; look for the 'Recording' status or any active capture session
    Affected if Network logging is currently enabled - the vulnerability requires an attacker to obtain a network log file, which only exists if logging was turned on
  3. Locate network log files on the system
    Search for files named 'net-internals.log', 'chrome-net-internals-log.txt', or similar patterns in Chrome's user data directory (commonly found in %LOCALAPPDATA%\Google\Chrome\User Data\ or ~/.config/google-chrome/)
    Affected if Network log files exist and are accessible - the vulnerability allows extraction of sensitive information from these log files
  4. Review file permissions on network log files
    If log files exist, inspect file permissions to determine if they could be accessed by unauthorized users or processes (on Windows, right-click > Properties > Security; on Linux/Mac use 'ls -la')
    Affected if Log files have overly permissive access controls allowing read access to users other than the owner

User is affected if Chrome version is below 144.0.7559.59 and network logging has been enabled, resulting in accessible log files that could be read by an attacker.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 144.0.7559.59 / 144.0.7559.60 or later
Fixed in 144.0.7559.59144.0.7559.60
Interim mitigation

Update Google Chrome to version 144.0.7559.59 or later. In enterprise environments, review and restrict access to network log files as a defense-in-depth measure until the patch is applied.

Recommended fix High confidence

Chrome version 144.0.7559.59 or later (stable release)

  1. Open Google Chrome browser
  2. Click the three-dot menu icon in the top-right corner
  3. Select 'Help' from the dropdown menu
  4. Click 'About Google Chrome'
  5. The browser will check for updates automatically
  6. If version 144.0.7559.59 or later is available, click 'Update Google Chrome'
  7. Restart the browser to complete the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0905 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0905 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data