CVE-2026-0905

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)

Published: 2026-01-20 Last update: 2026-01-29 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-0905 is rated Low Risk (39.4/100): CVSS Critical severity, with low exploitation likelihood (EPSS 0.01%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-0905

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-01-20 — 0.01% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-0905

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2026-0905

OS Trackers for CVE-2026-0905

vendor priority summary link
alpine — CVE-2026-0905: 1 source package rows (qt6-qtwebengine); 2 state rows across 2 repos (3.23-community, edge-community); fixed 2, open 0. https://security.alpinelinux.org/vuln/CVE-2026-0905
debian end-of-life CVE-2026-0905 end-of-life priority: Debian including 1 source packages (chromium), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2026-0905
redhat medium — https://access.redhat.com/security/cve/CVE-2026-0905
ubuntu medium CVE-2026-0905 medium priority: Ubuntu including 1 source packages (chromium-browser), 5 status rows across 5 suites (jammy, noble, plucky, questing, upstream): not-affected 4, released 1. https://ubuntu.com/security/CVE-2026-0905

Affected software / configurations for CVE-2026-0905

Vendor Product Version Raw CPE
google chrome < 144.0.7559.59 cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*
google chrome < 144.0.7559.60 cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*

References for CVE-2026-0905

cvelogic Threat Intelligence