CVE-2026-113303(google / chrome)

LOWCVSS 8.8 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

Memory corruption in WebRTC in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Critical)

0.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-119

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • chrome

Threat summary

  • 1 mentions across 1 observed day

What's happening

  • 1 total mentions across 1 day

Affected systems

Vendors
Products
chrome

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-10-26: 110-26
Full discourse1 post
  • 𝐿𝑖𝑛𝑢𝑥 𝑢𝑠𝑒𝑟@linuxuser1996

    Google closed 353 vulnerabilities in Chrome 156. Six are critical, including CVE-2026-113303 in WebRTC and CVE-2026-113279 in Accessibility. The announcement came on 20-21 October 2026. Chrome now asks for permission before connecting to insecure HTTP sites. The setting is on by default for all users. Update and restart Chrome. The fixes do not take effect until the browser restarts.

    110272963
    4.5K followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Appgooglechrome---

Explore more