Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
ExploitPage invokes vulnerable WebAudio API
-
ExecutionLeak cross-origin data in-browser
-
ImpactExfiltrate information to attacker
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the WebAudio API code path in Chrome versions prior to 155.0.8059.39, and the victim must actively navigate to or load an attacker-controlled crafted HTML page (UI:R) - there is no fully passive or server-side trigger. No authentication is required (PR:N) and no special non-default browser configuration is indicated; the WebAudio API is enabled by default. The principal limiting factors are the mandatory user interaction, the confidentiality-only and partial impact (a cross-origin data leak, not code execution or full data disclosure), and the need for the user to run a pre-patch Chrome build before auto-update applies the fix. |
| Impact | Signals are consistent and point to a genuine but low-to-moderate priority issue. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N, base 4.3) describes a network-reachable, low-complexity, unauthenticated flaw whose only impact is a partial loss of confidentiality (C:L) with no integrity or availability impact - matching the 'information leak' description and CWE-200. The requirement for user interaction (UI:R - the victim must open a crafted HTML page) meaningfully constrains exploitation. CISA's SSVC decision framework corroborates the low urgency: Exploitation=none, Automatable=no, Technical Impact=partial, which aligns with a cross-origin data leak rather than code execution. There is no CISA KEV listing and no public exploit code identified, and no EPSS score was provided in the input, so exploitation probability cannot be quantified numerically - however, the SSVC 'Exploitation: none' value and Chromium's self-assigned Medium severity both indicate no observed in-the-wild activity. There is no conflict among the signals: all sources agree this is a Medium-severity, confidentiality-only browser flaw. The main caveat is the missing EPSS value, so probabilistic exploitation likelihood is an inference from SSVC/KEV absence rather than a measured figure. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page that abuses the WebAudio API to read audio-processing state that reflects data from a different origin. When a victim is lured into visiting the page in a vulnerable Chrome build (prior to 155.0.8059.39), the page infers or extracts small amounts of cross-origin information (partial confidentiality impact). No public proof-of-concept exploit has been identified at the time of analysis, and success depends on the victim actively loading the attacker's page. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 06, 2026
Cross-origin data exposure in the WebAudio implementation of Google Chrome lets a remote attacker leak limited information from other origins when a victim loads a crafted HTML page in any Chrome build prior to 155.0.8059.39. Exploitation requires the target user to actively navigate to the attacker-controlled page (CVSS 3.1 AV:N/AC:L/PR:N/UI:R, confidentiality-only, partial impact, base score 4.3), so the flaw is a low-to-moderate priority information-disclosure issue rather than a code-execution or full-data-compromise primitive. There is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis, and CISA's SSVC evaluation rates the issue as not automatable with only partial technical impact.
RemediationAI
Upgrade Google Chrome to version 155.0.8059.39 or later (vendor-released patch: 155.0.8059.39), which is delivered through the stable-channel update described at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_086471744.html; after the update installs, users must fully restart the browser so the patched WebAudio code path is loaded, and enterprises that pin or defer Chrome versions via enterprise policy should raise the minimum enforced version to 155.0.8059.39. Because the flaw is exercised only when the victim opens attacker-controlled HTML, interim exposure can be reduced by restricting browsing to trusted, allow-listed sites through enterprise URL filtering or by disabling JavaScript on untrusted destinations - both carry usability trade-offs and neither is a complete substitute for patching, since WebAudio is enabled by default and has no supported enterprise kill switch. Chrome's auto-update mechanism typically applies the fix without user action, so the residual risk window is the period between disclosure and the browser relaunching on the patched build.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is the Web Audio API (WebAudio), the default-enabled browser interface that lets JavaScript build and process audio graphs - decoding media, routing cross-origin elements through MediaElementAudioSourceNode and similar nodes, and rendering buffers for inspection. CVE-2026-106392 is classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), which here manifests as a failure to properly enforce the same-origin boundary on data derived from WebAudio processing, allowing script on the attacker's page to observe cross-origin data. The CPE entry cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* uses wildcard versioning, reflecting that every Chrome channel/platform build below 155.0.8059.39 is in scope, and the ENISA EUVD record (EUVD-2026-93717) lists only the fixed threshold 155.0.8059.39 as the affected-range boundary, consistent with the Chrome release advisory. Because WebAudio is on by default, there is no non-default configuration prerequisite; the limiting factor in the assessed vector is the mandatory user interaction (UI:R) plus the confidentiality-only, partial impact (S:U/C:L/I:N/A:N).
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Remote crafted page with no auth gives AV:N/AC:L/PR:N, but a victim must open the page (UI:R); impact is a partial cross-origin read only, so C:L and I/A:N.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Information leak in WebAudio in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to potentially leak cross-origin data via a crafted HTML page. (Chromium security severity: Medium)
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-93717
GHSA-5r8c-9qc8-mfwg
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB