Skip to main content

Google Chrome EUVDEUVD-2026-74413

| CVE-2026-87531 LOW
Information Exposure (CWE-200)
2026-09-09 Chrome GHSA-mxc8-9v73-hv36
3.1
CVSS 3.1 · Vendor: Chrome

Severity by source

Vendor (Chrome) PRIMARY
3.1 LOW
AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
vuln.today AI
3.1 LOW

Renderer compromise prerequisite drives AC:H; cross-origin data leak is confidentiality-only at low impact; no integrity or availability effect.

3.1 AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
4.0 AV:N/AC:H/AT:P/PR:N/UI:A/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Chrome).

CVSS VectorVendor: Chrome

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Lifecycle Timeline

4
Analysis Generated
Sep 09, 2026 - 16:47 vuln.today
Patch available
Sep 09, 2026 - 01:03 EUVD
CVE Published
Sep 09, 2026 - 00:09 cve.org
UNKNOWN (no severity yet)
CVE Published
Sep 09, 2026 - 00:09 cve.org
LOW 3.1

DescriptionCVE.org

Information leak in CORS in Google Chrome prior to 153.0.8010.36 allowed a remote attacker who had compromised the renderer process to obtain cross-origin data via a crafted HTML page. (Chromium security severity: Medium)

AnalysisAI

Cross-origin data exfiltration in Google Chrome's CORS implementation prior to 153.0.8010.36 is exploitable only as a second-stage technique by an attacker who has already compromised the renderer process, allowing them to read data from foreign origins the victim is authenticated to via a crafted HTML page. With a CVSS of 3.1, EPSS of 0.17% (7th percentile), no CISA KEV listing, and no public exploit code identified, this represents a low standalone risk - its relevance is as a data-harvesting primitive chained after a renderer RCE. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
technique details hidden
Delivery
technique details hidden
Exploit
technique details hidden
Execution
technique details hidden
Persist
technique details hidden
Impact
technique details hidden

Vulnerability AssessmentAI

Exploitation Two preconditions must both be met: (1) the attacker must have already compromised Chrome's renderer process via a separate vulnerability - this is explicitly a second-stage technique and not an initial access vector - and (2) the victim must visit a crafted HTML page controlled by the attacker (UI:R). … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The CVSS 3.1 score of 3.1 (AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N) accurately captures the limited impact profile of this vulnerability. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario Full exploit scenario with step-by-step reproduction available after sign-in.
Remediation Upgrade Google Chrome to version 153.0.8010.36 or later; this is the vendor-released patch documented in the Chrome Stable Channel update at https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_0808145027.html. … Detailed patch versions, workarounds, and compensating controls in full report.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

EUVD-2026-74413 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy