16,977 known vulnerabilities
Top Products
In multiple locations, there is a possible way to bypass user interaction when pairing an LE device due to a logic error
In getAppLabel of ForgetDeviceDialogFragment.java, there is a possible trick the user into forgetting a device due to mi
In l2c_fcr_clone_buf of l2c_fcr.cc, there is a possible way to trigger controlled heap corruption within the privileged
In getApplicationLabel of KeyChainActivity.java, there is a possible way to trick the user into approving access to cert
In multiple locations, there is a possible misleading UI due to obfuscation. This could lead to local escalation of priv
In multiple locations, there is a possible way to execute code in the launcher process due to an over-privileged shell u
In multiple functions of PackageInstallerService.java, there is a possible way to install unverified apps due to a missi
In getCallingAppLabel of CertInstaller.java, there is a possible way to hide a sensitive security dialogue due to mislea
In approvalLevelForDomainInternal of DomainVerificationService.java, there is a possible way to hijack an arbitrary app
In onCreate of DisableSupervisionActivity.kt, there is a possible way to delete supervision data due to a missing null c
In applySimpleFieldMaxSize of DataRowHandler.java, there is a possible way to insert a large contact name due to imprope
In multiple functions of ubsan_throwing_runtime.cpp, there is a possible way to cause a crash due to an integer overflow
In multiple functions of ubsan_throwing_runtime.cpp, there is a possible persistent denial of service due to an integer
In setGlobalProxy of DevicePolicyManagerService.java, there is a possible desync in persistence due to improper input va
In resumeConfigurationDispatch of ActivityRecord.java, there is a possible background application launch (bal) due to a
In validateNode of ResourceTypes.cpp, there is a possible out of bounds read due to an incorrect bounds check. This coul
In multiple functions, there is a possible way to access the contacts database due to a SQL injection. This could lead t
In getPreferredSize of LauncherProcessImageListener.kt, there is a possible denial of service due to resource exhaustio
In multiple functions of DevicePolicyManagerService.java, there is a possible way to hide a system critical package due
In verifySignature of ApkChecksums.java, there is a possible way to cause a crash due to resource exhaustion. This could
In multiple functions of ubsan_throwing_runtime.cpp, there is a possible way to cause a permanent denial of service due
In multiple functions of WindowState.java, there is a possible way to trick a user into accepting a permission due to a
In updateState of GraphicsDriverEnableAngleAsSystemDriverController.java, there is a possible persistent dos issue due t
In multiple functions of sdp_discovery.cc, there is a possible way to achieve code execution due to a heap buffer overfl
In setTo of ResourceTypes.cpp, there is a possible read out of bounds due to an incorrect bounds check. This could lead
In createSessionInternal of PackageInstallerService.java, there is a possible to update a Device Policy Controller (DPC)
In multiple functions of ubsan_throwing_runtime.cpp, there is a possible way to cause a crash due to an integer overflow
In multiple functions of ubsan_throwing_runtime.cpp, there is a possible way to cause a system crash due to improper inp
In handleBondStateChanged of AdapterService.java, there is a possible sensitive information disclosure due to a permissi
In hide of WindowState.java, there is a possible way to trick the user into approving permissions due to a tapjacking/ov
In InputInterceptor of Letterbox.java, there is a possible way to trick a user into accepting a permission due to a tapj
In bta_jv_rfcomm_connect of bta_jv_act.cc, there is a possible bypass of bonding for a secure connection due to a logic
In multiple functions of ubsan_throwing_runtime.cpp, there is a possible way to cause the system to crash due to an inte
In multiple functions of ubsan_throwing_runtime.cpp, there is a possible persistent denial of service due to an integer
In multiple functions of ubsan_throwing_runtime.cpp, there is a possible persistent denial of service due to resource ex
In multiple functions of ubsan_throwing_runtime.cpp, there is a possible UBSan failure due to an integer overflow. This
In multiple functions of ubsan_throwing_runtime.cpp, there is a possible way to cause a crash due to an integer overflow
In multiple functions of ubsan_throwing_runtime.cpp, there is a possible persistent denial of service due to an integer
In startAnimation of StageCoordinator.java, there is a possible tapjacking issue due to a tapjacking/overlay attack. Thi
In multiple functions of AccessibilityManagerService.java, there is a possible persistent denial of service due to impro
In updateProvidersWhenServiceRemoved of CredentialManagerService.java, there is a possible way to override settings acro
In multiple locations, there is a possible tapjacking due to a logic error in the code. This could lead to local escalat
In performPreInstallChecks of InstallRepository.kt, there is a possible way to bypass MDM policy due to a logic error in
In multiple locations, there is a possible way to reset user-selected permissions selections due to a permissions bypass
In isSameApp of NotificationManagerService.java, there is a possible persistent dos due to resource exhaustion. This cou
In multiple functions of KeyguardViewMediator.java , there is a possible way to bypass lockdown mode with screen pinning
In multiple locations, there is a possible way to achieve code execution due to an integer overflow. This could lead to
In multiple functions of PipTaskOrganizer.java, there is a possible way to launch an activity from the background due to
In multiple locations, there is a possible background activity launch due to a missing permission check. This could lead
In setUserDisclaimerAcknowledged of CarDevicePolicyService.java, there is a possible way to bypass the user dialog when
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