← Back

Google

google

14,353 CVEs • 239 products

Products (239)

Click to collapse
Toggle
Android
android
Chrome
chrome
Tensorflow
tensorflow
Chrome Os
chrome_os
V8
v8
Asylo
asylo
Blink
blink
Picasa
picasa
Sketchup
sketchup
Tunnelblick
tunnelblick
Gvisor
gvisor
Toolbar
toolbar
Web Toolkit
web_toolkit
Protobuf
protobuf
Rendertron
rendertron
Fuchsia
fuchsia
Protobuf Java
protobuf-java
Earth
earth
Fscrypt
fscrypt
Gerrit
gerrit
Android Sdk
android_sdk
Guava
guava
Monorail
monorail
Guest Oslogin
guest-oslogin
Web Designer
web_designer
Talk
talk
Desktop
desktop
Bionic
bionic
Mod Pagespeed
mod_pagespeed
Home Firmware
home_firmware
Flatbuffers
flatbuffers
Bazel
bazel
Web Stories
web_stories
Updater
updater
Nearby
nearby
Api Search
api_search
Matter
matter
Kml
kml
Google Apps
google_apps
Gears
gears
Idapython
idapython
Admob
admob
Checkout Php
checkout-php
Cityhash
cityhash
Chrome Frame
chrome_frame
Authenticator
authenticator
Glass
glass
Android Api
android_api
Email
email
Android One
android_one
Sfntly
sfntly
Skia
skia
Pdfium
pdfium
Gmail
gmail
Santa
santa
Boringssl
boringssl
Cardboard
cardboard
Snappy
snappy
Api C++ Client
api_c++_client
Voice Builder
voice_builder
Gizmo5
gizmo5
Native Client
native_client
Openthread
openthread

CVEs (14,353)

CVE
VENDORS
PRODUCTS
UPDATED
PUBLISHED
CVSS
1Google
1Chrome
Jun 17, 2026
Aug 21, 2024
N/A· v4
7.8 HIGH· v3
N/A· v2
Insufficient data validation in Installer in Google Chrome on Windows prior to 128.0.6613.84 allowed a local attacker to perform privilege escalation via a malicious file. (Chromium security severity: Medium)
1Google
1Chrome
Jun 17, 2026
Aug 21, 2024
N/A· v4
4.3 MEDIUM· v3
N/A· v2
Inappropriate implementation in FedCM in Google Chrome prior to 128.0.6613.84 allowed a remote attacker to perform UI spoofing via a crafted HTML page. (Chromium security severity: Medium)
1Google
1Chrome
Jun 17, 2026
Aug 21, 2024
N/A· v4
4.3 MEDIUM· v3
N/A· v2
Inappropriate implementation in Permissions in Google Chrome prior to 128.0.6613.84 allowed a remote attacker to perform UI spoofing via a crafted HTML page. (Chromium security severity: Medium)
1Google
1Chrome
Jun 17, 2026
Aug 21, 2024
N/A· v4
8.8 HIGH· v3
N/A· v2
Insufficient data validation in V8 API in Google Chrome prior to 128.0.6613.84 allowed a remote attacker to potentially exploit heap corruption via a crafted Chrome Extension. (Chromium security severity: Medium)
1Google
1Chrome
Jun 17, 2026
Aug 21, 2024
N/A· v4
8.8 HIGH· v3
N/A· v2
Heap buffer overflow in PDFium in Google Chrome prior to 128.0.6613.84 allowed a remote attacker to perform an out of bounds memory read via a crafted PDF file. (Chromium security severity: Medium)
1Google
1Chrome
Jun 17, 2026
Aug 21, 2024
N/A· v4
8.8 HIGH· v3
N/A· v2
Inappropriate implementation in V8 in Google Chrome prior to 128.0.6613.84 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page. (Chromium security severity: Medium)
2Google
Microsoft
2Chrome
Edge
Jun 17, 2026
Aug 21, 2024
N/A· v4
9.6 CRITICAL· v3
N/A· v2
Type confusion in V8 in Google Chrome prior to 128.0.6613.84 allowed a remote attacker to exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
1Google
1Chrome
Jun 17, 2026
Aug 21, 2024
N/A· v4
8.8 HIGH· v3
N/A· v2
Type Confusion in V8 in Google Chrome prior to 128.0.6613.113 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
1Google
1Chrome
Jun 17, 2026
Aug 21, 2024
N/A· v4
8.8 HIGH· v3
N/A· v2
Use after free in Autofill in Google Chrome prior to 128.0.6613.84 allowed a remote attacker who had convinced the user to engage in specific UI interactions to potentially exploit heap corruption via a crafted HTML page...Show more
Use after free in Autofill in Google Chrome prior to 128.0.6613.84 allowed a remote attacker who had convinced the user to engage in specific UI interactions to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)Show less
1Google
1Chrome
Jun 17, 2026
Aug 21, 2024
N/A· v4
8.8 HIGH· v3
N/A· v2
Heap buffer overflow in Fonts in Google Chrome prior to 128.0.6613.84 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
1Google
1Chrome
Jun 17, 2026
Aug 21, 2024
N/A· v4
8.8 HIGH· v3
N/A· v2
Out of bounds memory access in Skia in Google Chrome prior to 128.0.6613.84 allowed a remote attacker who had compromised the renderer process to perform out of bounds memory access via a crafted HTML page. (Chromium sec...Show more
Out of bounds memory access in Skia in Google Chrome prior to 128.0.6613.84 allowed a remote attacker who had compromised the renderer process to perform out of bounds memory access via a crafted HTML page. (Chromium security severity: High)Show less
2Google
Microsoft
2Chrome
Edge Chromium
Jun 17, 2026
Aug 21, 2024
N/A· v4
8.8 HIGH· v3
N/A· v2
Inappropriate implementation in V8 in Google Chrome prior to 128.0.6613.84 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
1Google
1Chrome
Jun 17, 2026
Aug 21, 2024
N/A· v4
8.8 HIGH· v3
N/A· v2
Use after free in Passwords in Google Chrome on Android prior to 128.0.6613.84 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
2Google
Haxx
2Libcurl
Nest Mini Firmware
Jun 17, 2026
Aug 19, 2024
N/A· v4
5.9 MEDIUM· v3
N/A· v2
The libcurl CURLOPT_SSL_VERIFYPEER option was disabled on a subset of requests made by Nest production devices which enabled a potential man-in-the-middle attack on requests to Google cloud services by any host the traff...Show more
The libcurl CURLOPT_SSL_VERIFYPEER option was disabled on a subset of requests made by Nest production devices which enabled a potential man-in-the-middle attack on requests to Google cloud services by any host the traffic was routed through.Show less
1Google
1Android
Jun 17, 2026
Aug 19, 2024
N/A· v4
7.8 HIGH· v3
N/A· v2
In sendDeviceState_1_6 of RadioExt.cpp, there is a possible use after free due to improper locking. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not...Show more
In sendDeviceState_1_6 of RadioExt.cpp, there is a possible use after free due to improper locking. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Show less
1Google
1Android
Jun 17, 2026
Aug 15, 2024
N/A· v4
7.8 HIGH· v3
N/A· v2
In setTransactionState of SurfaceFlinger.cpp, there is a possible way to perform tapjacking due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges neede...Show more
In setTransactionState of SurfaceFlinger.cpp, there is a possible way to perform tapjacking due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Show less
1Google
1Android
Jun 17, 2026
Aug 15, 2024
N/A· v4
5.5 MEDIUM· v3
N/A· v2
In shouldWrite of OwnersData.java, there is a possible edge case that prevents MDM policies from being persisted due to a logic error in the code. This could lead to local denial of service with no additional execution p...Show more
In shouldWrite of OwnersData.java, there is a possible edge case that prevents MDM policies from being persisted due to a logic error in the code. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.Show less
1Google
1Android
Jun 17, 2026
Aug 15, 2024
N/A· v4
7.8 HIGH· v3
N/A· v2
In setForceHideNonSystemOverlayWindowIfNeeded of WindowState.java, there is a possible way for message content to be visible on the screensaver while lock screen visibility settings are restricted by the user due to a lo...Show more
In setForceHideNonSystemOverlayWindowIfNeeded of WindowState.java, there is a possible way for message content to be visible on the screensaver while lock screen visibility settings are restricted by the user due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Show less
1Google
1Android
Jun 17, 2026
Aug 15, 2024
N/A· v4
7.8 HIGH· v3
N/A· v2
In attributeBytesBase64 and attributeBytesHex of BinaryXmlSerializer.java, there is a possible arbitrary XML injection due to an integer overflow. This could lead to local escalation of privilege with no additional execu...Show more
In attributeBytesBase64 and attributeBytesHex of BinaryXmlSerializer.java, there is a possible arbitrary XML injection due to an integer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Show less
1Google
1Android
Jun 17, 2026
Aug 15, 2024
N/A· v4
7.8 HIGH· v3
N/A· v2
In shouldRestrictOverlayActivities of UsbProfileGroupSettingsManager.java, there is a possible escape from SUW due to a logic error in the code. This could lead to local escalation of privilege with no additional executi...Show more
In shouldRestrictOverlayActivities of UsbProfileGroupSettingsManager.java, there is a possible escape from SUW due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.Show less