Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-113303 Overview
CVE-2026-113303 is a memory corruption vulnerability in the WebRTC component of Google Chrome. The flaw affects Chrome versions prior to 156.0.8078.47 and is classified under [CWE-119] (Improper Restriction of Operations within the Bounds of a Memory Buffer). A remote attacker who serves a crafted HTML page can trigger the bug and potentially execute arbitrary code within Chrome's sandbox. Google's Chromium project rates the underlying issue as Critical severity. The vulnerability requires user interaction, specifically visiting an attacker-controlled page, but needs no authentication.
Critical Impact
Successful exploitation allows a remote attacker to execute arbitrary code inside the Chrome sandbox, compromising confidentiality, integrity, and availability of the browser process.
Affected Products
- Google Chrome Desktop versions prior to 156.0.8078.47
- Chromium-based builds incorporating the vulnerable WebRTC component
- All platforms running affected Chrome Stable channel releases (Windows, macOS, Linux)
Discovery Timeline
- 2026-10-20 - CVE-2026-113303 published to NVD
- 2026-10-21 - Last updated in NVD database
Technical Details for CVE-2026-113303
Vulnerability Analysis
The vulnerability resides in WebRTC, the real-time communication framework Chrome uses for audio, video, and data channel sessions in the browser. WebRTC parses media streams, SDP offers, and RTP packets through complex native code paths that have historically been high-value targets for exploitation. A memory corruption condition in this component allows an attacker to influence program memory beyond intended bounds. The attack vector is network-based, exploitation complexity is low, and no privileges are required. The attacker only needs the victim to load a crafted HTML page containing malicious WebRTC payloads or JavaScript that initiates a hostile peer connection.
Root Cause
The root cause is improper restriction of operations within the bounds of a memory buffer in WebRTC code paths. Memory corruption of this class typically originates from mismatched buffer sizing, incorrect length validation during media or signaling parsing, or lifetime errors on objects shared across threads. The resulting corruption can be shaped into a write primitive suitable for code execution within the renderer or associated process.
Attack Vector
An attacker hosts a crafted HTML page that initializes a WebRTC RTCPeerConnection and transmits malformed signaling or media data to the victim's browser. When the victim visits the page, WebRTC processes the crafted input and triggers the memory corruption. Because the bug is reachable without authentication and only requires a page visit, phishing links, malicious ads, and compromised sites are viable delivery channels. Code execution occurs within the Chrome sandbox, which still exposes significant renderer-reachable data and may be chained with a sandbox escape for full system compromise.
No public proof-of-concept exploit is listed for this CVE. See the Chromium issue tracker entry #574041825 for technical details once access restrictions are lifted.
Stop Remote Code Execution Before It Runs
Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.
Stop Exploit AttemptsDetection Methods for CVE-2026-113303
Indicators of Compromise
- Chrome renderer process crashes with memory access violations shortly after visiting unfamiliar sites that initiate WebRTC sessions
- Unexpected outbound STUN, TURN, or peer connection traffic from browser processes to untrusted hosts
- Browser child processes spawning unexpected shell or scripting interpreters following WebRTC activity
Detection Strategies
- Inventory Chrome versions across endpoints and flag any build earlier than 156.0.8078.47
- Monitor endpoint telemetry for anomalous child processes created by chrome.exe or Chromium renderer processes
- Correlate browser crash reports with network connections to WebRTC signaling endpoints on suspicious domains
Monitoring Recommendations
- Enable crash reporting and centralized collection to identify repeated WebRTC-related faults
- Deploy EDR behavioral rules that flag post-exploitation activity such as credential access or persistence spawned from browser processes
- Review web proxy logs for connections to newly registered domains hosting WebRTC content
How to Mitigate CVE-2026-113303
Immediate Actions Required
- Update Google Chrome to version 156.0.8078.47 or later across all managed endpoints
- Restart Chrome after updating to ensure the patched binaries are loaded into memory
- Validate that enterprise policy prevents users from downgrading or disabling automatic updates
Patch Information
Google addressed the vulnerability in the Chrome Stable channel release documented in the Chrome Releases blog. Upgrade to Chrome 156.0.8078.47 or later on Windows, macOS, and Linux. Chromium-based browsers that embed WebRTC should apply the corresponding upstream fix.
Workarounds
- Restrict access to untrusted sites through web filtering and allowlisting until patches are deployed
- Disable WebRTC via enterprise policy or extensions in environments where it is not required
- Enforce site isolation and sandbox hardening policies through Chrome Enterprise group policies
# Verify Chrome version on Linux endpoints
google-chrome --version
# Example Chrome Enterprise policy (JSON) to force automatic updates
{
"UpdateDefault": 1,
"TargetVersionPrefix": "156.",
"ChromeCleanupEnabled": true
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

