LiveActive security incident?Get immediate response
CVE Record

CVE-2026-5281: Use after free in Dawn in Google Chrome prior to 146.0.7680.178 allowed a remote attacker who had compromis...

Use after free in Dawn in Google Chrome prior to 146.0.7680.178 allowed a remote attacker who had compromised the renderer process to execute arbitrary code via a crafted HTML page. (Chromium security severity: High)

HighCVSS 8.8Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-5281 is a high-severity Google Chrome flaw in Dawn. A malicious web page could help an attacker run code if they already compromise Chrome’s renderer process. Business urgency is high because Chrome is widely deployed and browser flaws are common entry points, but the provided sources do not show active exploitation.

Executive priority

Treat this as a priority browser update, not a confirmed emergency. Patch promptly through normal expedited browser channels, especially for internet-facing workforces and privileged users. Escalate if CISA KEV or Google later reports exploitation.

Technical view

The issue is a use-after-free vulnerability, CWE-416, in Chrome’s Dawn component before version 146.0.7680.178. The CVSS 3.1 score is 8.8. The attack vector is network-based with user interaction required. The CVE states arbitrary code execution is possible via crafted HTML after renderer compromise.

Likely exposure

Organizations with desktop Google Chrome installations below 146.0.7680.178 are potentially exposed. Exposure is strongest where users browse untrusted sites or open externally supplied web content. The supplied data does not identify other affected Chromium-based products.

Exploitation context

The source bundle does not support active exploitation. CISA KEV is marked false for this CVE. Exploitation requires a crafted HTML page and a compromised renderer process, so this is serious but not described as a simple one-click full compromise in the provided evidence.

Researcher notes

Key limits: the Chromium issue link may restrict details, and the bundle provides no exploit indicators, proof-of-concept status, or detailed patch notes beyond the Chrome stable update reference. Avoid assuming impact for non-Chrome browsers unless vendors publish their own advisories.

Mitigation direction

  • Update Google Chrome to 146.0.7680.178 or later where available.
  • Prioritize managed desktop fleets and high-risk user groups.
  • Check Google Chrome release guidance for platform-specific update details.
  • Ensure browser auto-update is enabled and functioning.

Validation and detection

  • Inventory Chrome versions across managed endpoints.
  • Confirm Chrome reports version 146.0.7680.178 or later.
  • Review patch compliance dashboards for unmanaged or stale devices.
  • Monitor vendor and CISA pages for changed exploitation status.
Prepared
Confidence
high
Sources
5

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 · low confidence lookup

CWE-416: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-5281 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
High
CVSS
8.8 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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
4Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

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
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2026-5281Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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
GoogleChrome146.0.7680.178Listed
Weakness

CWE details

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

CWE-416 · source CWE mapping

Use After Free

Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.