Security readout for executives and security teams
Plain-English summary
A memory-safety flaw in Google Chrome could let a remote attacker run code outside Chrome’s security sandbox using crafted network traffic. Successful exploitation could compromise data, alter systems, or disrupt operations. Chrome versions before 152.0.7977.75 are described as vulnerable.
Executive priority
Treat this as an urgent browser-update priority because successful exploitation crosses Chrome’s sandbox and can cause full security impact. Confirm fleet-wide deployment promptly, while recognizing that the supplied sources do not report active exploitation.
Technical view
CVE-2026-84324 is a use-after-free vulnerability in Chrome’s Proxy component. The supplied CVSS 3.1 vector scores it 9.0: network-accessible, high-complexity, requiring neither privileges nor user interaction, with changed scope and high confidentiality, integrity, and availability impact. Chromium rates it High.
Likely exposure
Organizations are likely exposed where desktop Chrome installations remain below 152.0.7977.75, including unmanaged endpoints or devices awaiting restart after updating. The bundle does not identify other affected products or platforms.
Exploitation context
The supplied record says crafted network traffic can trigger arbitrary code execution outside the sandbox. Exploitation complexity is rated high. The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation.
Researcher notes
The description establishes the vulnerable range as versions before 152.0.7977.75, although the structured affected entry lists 152.0.7977.75 ambiguously. Treat that release as the remediation threshold based on the narrative. The bundle provides no attack-chain details, public exploit evidence, or alternative mitigations.
Mitigation direction
- Update Chrome to version 152.0.7977.75 or later through approved deployment channels.
- Restart Chrome after deployment so the updated browser binaries are active.
- Prioritize internet-facing, unmanaged, privileged-user, and high-value endpoints.
- If immediate updating is impossible, review Google’s current guidance for supported mitigations.
Validation and detection
- Inventory installed Chrome versions and identify every installation below 152.0.7977.75.
- Confirm updated devices restarted Chrome and now report the remediated version.
- Verify browser-management deployment succeeded across all organizational groups and operating systems.
- Monitor Google’s advisory and authoritative exploitation catalogs for status changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupExecution 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 lookupCVE-2026-84324 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H2.26CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9CriticalVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop.htmlCVE reference, Chrome
- https://issues.chromium.org/issues/533534913CVE reference, Chrome
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.