CVE Vulnerability Catalog
Translated CVE descriptions from NVD NIST - in English
CISA KEV catalog updated: (v2026.07.27)
A race condition in V8 in Google Chrome prior to 147.0.7727.55 could allow a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Medium)
Google Chrome prior to version 147.0.7727.55 has insufficient policy enforcement in PWAs, allowing a remote attacker who compromised the renderer process to install a PWA without user consent via a crafted HTML page. (Severity: Medium)
Insufficient policy enforcement in browser UI in Google Chrome prior to 147.0.7727.55 allowed a remote attacker who had compromised the renderer process to perform UI spoofing via a crafted HTML page.
Google Chrome prior to version 147.0.7727.55 contained a race condition in WebCodecs that allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page. (Severity: Medium)
A cryptographic flaw in PDFium in Google Chrome prior to 147.0.7727.55 allowed an attacker to read potentially sensitive information from encrypted PDFs via a brute-force attack.
Google Chrome prior to version 147.0.7727.55 has an uninitialized use vulnerability in WebCodecs. A remote attacker can obtain potentially sensitive information from process memory via a crafted HTML page.
Google Chrome on Windows prior to 147.0.7727.55 has insufficient validation in Downloads, allowing bypass of download restrictions via crafted HTML.
Out of bounds read in WebAudio in Google Chrome on Mac prior to 147.0.7727.55 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Medium)
Google Chrome on Windows prior to version 147.0.7727.55 has insufficient validation of untrusted input in WebML, allowing a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page. (Severity: Medium)
Google Chrome prior to 147.0.7727.55 has incorrect security UI in Fullscreen, allowing UI spoofing via crafted HTML.
Policy bypass in LocalNetworkAccess in Google Chrome prior to 147.0.7727.55 allowed a remote attacker to bypass navigation restrictions via a crafted HTML page. (Chromium security severity: Medium)
Google Chrome prior to 147.0.7727.55 has insufficient policy enforcement in browser UI, allowing an attacker with compromised renderer to spoof the Omnibox via crafted HTML.
Google Chrome prior to 147.0.7727.55 has incorrect security UI in Blink, allowing UI spoofing via crafted HTML.
Side-channel information leakage in Navigation in Google Chrome prior to 147.0.7727.55 allowed a remote attacker to leak cross-origin data via a crafted HTML page.
A policy bypass in the Blink component of Google Chrome prior to version 147.0.7727.55 allowed a remote attacker to perform UI spoofing via a crafted HTML page. The issue has a medium severity rating according to Chromium.
Google Chrome prior to version 147.0.7727.55 has a heap buffer overflow in WebML, allowing a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page. (Severity: High)
Google Chrome before 147.0.7727.55 has a heap buffer overflow in WebML, allowing a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium severity: High)
Google Chrome prior to version 147.0.7727.55 has a heap buffer overflow in WebAudio, allowing a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page. (Severity: High)
A cross-site scripting vulnerability was found in openstatusHQ openstatus up to commit 1b678e71a85961ae319cbb214a8eae634059330c in the Onboarding Endpoint component in file apps/dashboard/src/app/(dashboard)/onboarding/client.tsx via manipulation of the callbackURL argument. The attack can be launched remotely.
The Post Blocks & Tools plugin for WordPress up to version 1.3.0 inclusive contains a Stored Cross-Site Scripting vulnerability via the 'sliderStyle' attribute in the Posts Slider block, due to insufficient input sanitization and output escaping.

