LiveActive security incident?Get immediate response
CVE Record

CVE-2026-0905: Insufficient policy enforcement in Network in Google Chrome prior to 144.0.7559.59 allowed an attack who ob...

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)

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-0905 is a Google Chrome information-disclosure issue. If an attacker already obtains a Chrome network log file, insufficient policy enforcement could let them read potentially sensitive information. Google/Chromium lists this as Medium, while the supplied CVSS score is Critical, so urgency should be balanced against the specific prerequisite.

Executive priority

Prioritize prompt Chrome updating through normal emergency browser patch workflows. Treat this as important for data exposure risk, but not as confirmed active exploitation based on the provided evidence.

Technical view

The CVE describes CWE-200 in Chrome Network before 144.0.7559.59. The impact is potential sensitive information exposure through a network log file obtained by an attacker. The source bundle does not provide deeper technical root-cause details, exploit mechanics, or affected platform distinctions beyond Google Chrome.

Likely exposure

Exposure is most relevant for managed endpoints running Google Chrome prior to 144.0.7559.59, especially environments that generate, store, transmit, or centralize Chrome network logs for troubleshooting or support.

Exploitation context

No active exploitation is stated in the provided sources, and the CVE is not marked KEV. The described scenario requires an attacker to obtain a network log file first, making log access controls and retention practices important.

Researcher notes

There is a notable severity mismatch: Chromium security severity is Medium, while the supplied CVSS is 9.8 Critical. The record describes information disclosure via obtained network logs, not standalone remote code execution. Validate against the CVE record and Chrome release note before escalating.

Mitigation direction

  • Update Google Chrome to 144.0.7559.59 or later where applicable.
  • Review Google Chrome release guidance for platform-specific update details.
  • Restrict access to Chrome network logs and support bundles.
  • Avoid sharing network logs unless necessary and approved.
  • Reduce retention of sensitive troubleshooting logs where business permits.

Validation and detection

  • Inventory Chrome versions across managed endpoints.
  • Confirm endpoints are on 144.0.7559.59 or later.
  • Check whether Chrome network logs are centrally collected or retained.
  • Review access permissions for stored browser diagnostic logs.
  • Monitor vendor advisories for added details or revised severity.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-0905 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-0905Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleChrome144.0.7559.59Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.