google has 753 CVEs on record between 2021 and 2026. Disclosure cadence is accelerating: 614 in the last 90 days against 97 in the 90 before. The busiest recent month was September 2026 with 501. The median CVSS is 7.5 (high), with 91 rated critical. 1% have been exploited in the wild, in line with the corpus average. When CISA adds a google CVE to KEV it happens fast: a median of 1 day after publication (9 cases). The dominant weakness classes are CWE-416 (91) and CWE-20 (70). Most affected products: chrome (491), android (232), mcp_toolbox_for_databases (7).

CVEs per month

Last 12 months, by publish date

1025/101125/111225/120126/010226/020326/030426/040526/050626/060726/070826/080926/09

Exploited share: 1% vs 1% corpus
Median CVSS: 7.5
Publish → KEV: 1 d median(9)
Last 90 days: 614 prev 97

Weakness classes

Products

chrome 491
android 232
mcp_toolbox_for_databases 7
github.com/google/cel-go 2
github.com/google/exposure-notifications-verification-server 2
github.com/google/go-attestation 2

Follow google:RSS feed Save a search →Embed badge ↗

753

Total CVEs

Critical

CISA KEV

Exploited

Worst active — by depth score

Google vulnerabilities

CVEs affecting Google, newest first. Open any entry for full detail, references, and exploit status.

753 CVEsRSS

CVEs per month

Weakness classes

Products

Worst active — by depth score

Google vulnerabilities

An uncontrolled recursion vulnerability in the Windows SIPA event log parser of Google go-attestation versions up to and including 0.6.1 allows an attacker to cause a denial of service (DoS)

In MicroXR Blobstore, there is a possible way to access other app's files due to a missing permission check

In checkReadPermission of PermissionsManager.java, there is a possible way to monitor sensitive device state data due to a missing permission check

In multiple functions of HostEmulationManager.java, there is a possible background activity launch due to a logic error in the code

In isCallerAllowed of WalletContextualLocationsService.kt, there is a possible way to get wallet information due to a missing permission check

In onCreate of SlicePermissionActivity.java, there is a possible permission bypass due to a confused deputy

In initAppLinkTypeAndIntent of ChannelImpl.java, there is a possible launch an arbitrary intent due to improper input validation

In resolveActivity of ActivityStarter.java, there is a possible way to perform Intent Redirection attacks due to a logic error in the code

In multiple functions of NfcService.java, there is a possible silent payment session hijacking enablement due to a missing permission check

In read of MatroskaExtractor.cpp, there is a possible out-of-bounds write due to improper casting

In multiple functions in multiple locations, there is a possible background activity launch bypass due to a confused deputy

In handleBondStateChanged of AdapterService.java, there is a possible way to skip pairing due to a logic error in the code

In multiple locations, there is a possible use after free due to a race condition

In assertSafeToStartCustomActivity of AppRestrictionsFragment.java, there is a possible read/write access to private files due to a confused deputy

In setClipboardAccessNotificationsEnabledForUser of ClipboardService.java, there is a possible mult-iuser isolation due to a logic error in the code

In onCreate of PaymentDefaultDialog.java, there is a possible way to change default payment app due to a confused deputy

In addCreatorToken of ActivityManagerService.java, there is a possible Intent Redirection Bypass due to a logic error in the code

In parseInterventionFromXml of GameManagerService.java, there is a possible permanent denial of service due to resource exhaustion

In multiple locations, there is a possible use after free due to a logic error in the code

In getItemList of SettingsFragment.java, there is a possible user interaction bypass due to misleading or insufficient UI

In multiple locations, there is a possible improper encryption key validation due to a logic error in the code

In createSessionInternal of PackageInstallerService.java, there is a possible way to permanently DoS the device due to a logic error in the code

In validate_camera_metadata_structure of camera_metadata.c, there is a possible out of bounds write due to a logical error in the code

In onCreate of ConfirmDeviceCredentialActivity.java, there is a possible unauthorized access to and modification of device credentials due to a missing permission check

In onCreate of InstallLaunch.kt, there is a possible misleading UI due to a tapjacking/overlay attack

In areBackgroundActivityStartsAllowed of BackgroundLaunchProcessController.java, there is a possible unintended way to launch activities in the background due to a logic error in the code

In buildIntentSenderForUser of LauncherAppsService.java, there is a possible way to launch an activity from the background due to BAL Bypass

In getAllSessions of multiple files, there is a possible confused deputy due to a logic error in the code

In findMetaAuthUid of AccountsDb.java, there is a possible frp bypass due to a logic error in the code

In onActivityResult of AppWidgetConfigActivityProxy.java, there is a possible unauthorized URI permission grant due to a confused deputy