16,977 known vulnerabilities
Top Products
Use after free in WebRTC in Google Chrome prior to 89.0.4389.90 allowed a remote attacker to potentially exploit heap co
In GenerateFaceMask of face.cc, there is a possible out of bounds write due to an incorrect bounds check. This could lea
In sound_trigger_event_alloc of platform.h, there is a possible out of bounds write due to a heap buffer overflow. This
In convertToHidl of convert.cpp, there is a possible out of bounds read due to uninitialized data from ReturnFrameworkMe
In the NXP NFC firmware, there is a possible insecure firmware update due to a logic error. This could lead to local esc
In iaxxx_core_sensor_change_state of iaxxx-module.c, there is a possible out of bounds write due to a missing bounds che
In the FingerTipS touch screen driver, there is a possible out of bounds read due to an integer overflow. This could lea
In fts_driver_test_write of fts_proc.c, there is a possible out of bounds read due to a missing bounds check. This could
In the FingerTipS touch screen driver, there is a possible out of bounds read due to an integer overflow. This could lea
In the FingerTipS touch screen driver, there is a possible out of bounds write due to a heap buffer overflow. This could
In the Citadel chip firmware, there is a possible out of bounds write due to a missing bounds check. This could lead to
In the Citadel chip firmware, there is a possible out of bounds write due to a missing bounds check. This could lead to
In the Citadel chip firmware, there is a possible out of bounds write due to a missing bounds check. This could lead to
In the Titan-M chip firmware, there is a possible disclosure of stack memory due to uninitialized data. This could lead
In the Titan M chip firmware, there is a possible disclosure of stack memory due to uninitialized data. This could lead
In the Titan M chip firmware, there is a possible disclosure of stack memory due to uninitialized data. This could lead
In the Titan M chip firmware, there is a possible disclosure of stack memory due to uninitialized data. This could lead
In the Titan M chip firmware, there is a possible disclosure of stack memory due to uninitialized data. This could lead
In setNightModeActivated of UiModeManagerService.java, there is a missing permission check. This could lead to local esc
In onReceive of ImsPhoneCallTracker.java, there is a possible misattribution of data usage due to an incorrect broadcast
In FindQuotaDeviceForUuid of QuotaUtils.cpp, there is a possible use-after-free due to a race condition. This could lead
In onCreate of UsbConfirmActivity, there is a possible tapjacking vector due to an insecure default value. This could le
In createConnectToAvailableNetworkNotification of ConnectToNetworkNotificationBuilder.java, there is a possible connecti
In done of CaptivePortalLoginActivity.java, there is a confused deputy. This could lead to local escalation of privilege
In checkSlicePermission of SliceManagerService.java, there is a possible resource exposure due to an incorrect permissio
In updateNotifications of DeviceStorageMonitorService.java, there is a possible permission bypass due to an unsafe Pendi
In onReceive of DcTracker.java, there is a possible way to trigger a provisioning URL and modify other telephony setting
In getUpTo17bits of pvmp3_getbits.cpp, there is a possible out of bounds read due to a heap buffer overflow. This could
In qtaguid_untag of xt_qtaguid.c, there is a possible memory corruption due to a use after free. This could lead to loca
In bindServiceLocked of ActiveServices.java, there is a possible foreground service launch due to a confused deputy. Thi
In sdp_copy_raw_data of sdp_discovery.cc, there is a possible system compromise due to a double free. This could lead to
In Builtins::Generate_ArgumentsAdaptorTrampoline of builtins-arm.cc and related files, there is a possible out of bounds
In StopServicesAndLogViolations of reboot.cpp, there is possible memory corruption due to a use after free. This could l
In android_os_Parcel_readString8 of android_os_Parcel.cpp, there is a possible out of bounds read due to a missing bound
In Scanner::LiteralBuffer::NewCapacity of scanner.cc, there is a possible out of bounds write due to an integer overflow
In main of main.cpp, there is a possible memory corruption due to a double free. This could lead to local escalation of
In onCreate() of ChooseTypeAndAccountActivity.java, there is a possible way to learn the existence of an account, withou
In various methods of WifiNetworkSuggestionsManager.java, there is a possible modification of suggested networks due to
In getNbits of pvmp3_getbits.cpp, there is a possible out of bounds read due to a heap buffer overflow. This could lead
In DeltaPerformer::Write of delta_performer.cc, there is a possible use of untrusted input due to improper input validat
In checkUriPermission and related functions of MediaProvider.java, there is a possible way to access external files due
In onPackageModified of VoiceInteractionManagerService.java, there is a possible change of default applications due to a
In BnAudioPolicyService::onTransact of IAudioPolicyService.cpp, there is a possible out of bounds read due to a missing
In getMediaOutputSliceAction of RemoteMediaSlice.java, there is a possible permission bypass due to an unsafe PendingInt
In nci_proc_rf_management_ntf of nci_hrcv.cc, there is a possible out of bounds read due to a missing bounds check. This
In Write of NxpMfcReader.cc, there is a possible out of bounds write due to a missing bounds check. This could lead to l
In CrossProfileAppsServiceImpl.java, there is the possibility of an application's INTERACT_ACROSS_PROFILES grant state n
In oggpack_look of bitwise.c, there is a possible out of bounds read due to a missing bounds check. This could lead to r
In deletePackageVersionedInternal of PackageManagerService.java, there is a possible way to exit Screen Pinning due to a
Uninitialized data in PDFium in Google Chrome prior to 89.0.4389.72 allowed a remote attacker to obtain potentially sens
Frequently Asked Questions
How many CVEs affect Google?
Google has 16,977 CVE records in our database, including 1160 critical and 8152 high severity vulnerabilities. 94 of these are listed in CISA's Known Exploited Vulnerabilities catalog.
What are the most severe Google vulnerabilities?
Google has 1160 critical severity (CVSS 9.0+) and 8152 high severity (CVSS 7.0-8.9) vulnerabilities. 94 vulnerabilities are confirmed as actively exploited in the wild.
How can I scan for Google vulnerabilities?
CyberStrike's AI-powered security agents automatically detect vulnerabilities in Google products across your infrastructure. The platform provides continuous pentesting, DAST scanning, and real-time vulnerability monitoring with actionable remediation guidance.
Detect Google Vulnerabilities
CyberStrike scans your infrastructure for Google vulnerabilities and provides real-time remediation guidance.
Get Started