CVE-2026-9123

High
7.5
0.05.010.0
Year
2026
Published
May 20, 2026
Known Affected Devices
0
CVSS Score
7.5

What is CVE-2026-9123?

Heap buffer overflow in Chromecast in Google Chrome on Android, Linux, ChromeOS prior to 148.0.7778.179 allowed a local attacker to execute arbitrary code inside a sandbox via malicious network traffic. (Chromium security severity: Medium)

CVSS Vector Breakdown

CVSS 3.1
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
AV
Attack Vector
Adjacent

Exploitable from an adjacent network (e.g. same LAN, Wi-Fi segment, Bluetooth).

AC
Attack Complexity
High

Exploit requires specific conditions, timing, or configuration to succeed.

PR
Privileges Required
None

No authentication required. Any anonymous user can exploit this vulnerability.

UI
User Interaction
None

No user interaction required. Exploit runs without any victim action.

S
Scope
Unchanged

Exploiting the vulnerability only affects the vulnerable component itself.

C
Confidentiality Impact
High

Complete loss of confidentiality. All data on the component may be exposed.

I
Integrity Impact
High

Complete loss of integrity. Attacker can modify any file or data on the component.

A
Availability Impact
High

Complete denial of service. The component becomes fully unavailable.

FAQ

How severe is CVE-2026-9123?

CVE-2026-9123 has a CVSS score of 7.5/10, rated as High. This is a high severity vulnerability and should be patched as soon as possible.

What does the CVSS score mean for CVE-2026-9123?

CVSS (Common Vulnerability Scoring System) rates vulnerability severity from 0.0 to 10.0. CVE-2026-9123 scores 7.5/10 (High). Scores 9.0–10.0 are Critical, 7.0–8.9 are High, 4.0–6.9 are Medium, and below 4.0 are Low.

Which devices are affected by CVE-2026-9123?

The list of devices confirmed to be affected by CVE-2026-9123 is shown in the "Affected Devices" section above. Check your firmware version against the vendor security advisory and apply the latest patch.

How do I fix or mitigate CVE-2026-9123?

Apply the latest firmware or software update from the vendor. Check the References section above for official advisories and patch notes. If no patch is available, consider disabling the affected feature or isolating the device from untrusted networks.