How to Fix CVE-2026-5919: Chrome (Bundle Sibling)
*By Sai Kiran Pandrala*
Last verified: 2026-05-25
| Severity | CVSS 6.5, Medium |
|---|---|
| Actively exploited? | No |
| Affected | Google Chrome (147.0.7727.55 < 147.0.7727.55) |
| Fixed in | Same patched build as CVE-2026-5272 |
| Type (CWE) | CWE-20: Insufficient validation of untrusted input |
CVE-2026-5919 is a sibling vulnerability in the same Google Chrome advisory bundle as CVE-2026-5272. The same patched build closes every CVE in the bundle, so the remediation procedure for CVE-2026-5919 matches the primary write-up.
What is different about CVE-2026-5919?
Insufficient validation of untrusted input in WebSockets in Google Chrome prior to 147.0.7727.55 allowed a remote attacker who had compromised the renderer process to bypass same origin policy via a crafted HTML page. (Chromium security severity: Low)
Impact is consistent with the bundle: a security bypass on the affected component. The patched build closes every code path in the advisory in one update.
How to fix CVE-2026-5919
Apply the patched build per the primary write-up: How to Fix CVE-2026-5272.
For a quick check, confirm the running version of Chrome:
# Confirm the installed version via your package manager
dpkg -l | grep -i chrome # Debian/Ubuntu
rpm -qa | grep -i chrome # RHEL/CentOS/Rocky
Frequently asked questions
Is CVE-2026-5919 being actively exploited?
Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.
How severe is CVE-2026-5919?
CVSS rates it 6.5 (Medium). Use that score to set your patch priority alongside the other items in your queue.
Do I have to take Chrome offline to apply the patch?
It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.
What if my vulnerability scanner still flags CVE-2026-5919 after I patch?
Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.
References
- Official vendor advisory: https://chromereleases.googleblog.com/2026/04/stable-channel-update-for-desktop.html
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-5919
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Primary write-up: How to Fix CVE-2026-5272
*Written by Sai Kiran Pandrala. Last verified 2026-05-25. Part of the Google Chrome advisory bundle. Full procedure at how-to-fix-cve-2026-5272.*