Google has 2,255 CVEs on record between 2011 and 2026. Disclosure cadence is accelerating: 1836 in the last 90 days against 114 in the 90 before. The busiest recent month was October 2026 with 781. The median CVSS is 7.8 (high), with 240 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 2 days after publication (12 cases). The dominant weakness classes are CWE-416 (457) and CWE-863 (223). Most affected products: Chrome (1648), Android (547), mcp_toolbox_for_databases (7).

CVEs per month

Last 12 months, by publish date

1225/120126/010226/020326/030426/040526/050626/060726/070826/080926/091026/101126/11

Exploited share: 1% vs 1% corpus
Median CVSS: 7.8
Publish → KEV: 2 d median(12)
Last 90 days: 1836 prev 114

Weakness classes

Products

Chrome 1648
Android 547
mcp_toolbox_for_databases 7
Application Integration 5
github.com/google/sam 3
Guava 2

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

2255

Total CVEs

240

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.

2255 CVEsRSS

CVE-2026-0129Medium· 4.3

4mo ago

In RtcpByePacket::decodeByePacket, there is a possible due to a missing bounds check

In RtcpByePacket::decodeByePacket, there is a possible due to a missing bounds check. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.

▾ Sunlitgoogle · androidEPSS 0.18%via NVD

CVE-2026-0156High· 7.5

4mo ago

In checkSsrcCollisionOnRcv of RtpSession.cpp, there is a possible memory safety issue due to a missing null check

In checkSsrcCollisionOnRcv of RtpSession.cpp, there is a possible memory safety issue due to a missing null check. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed…

▾ Twilightgoogle · androidEPSS 0.22%via NVD

CVE-2026-0128Medium· 6.5⚖ disputed

4mo ago

In RtcpFbPacket::decodeRtcpFbPacket, there is a possible out of bounds read due to an integer overflow

In RtcpFbPacket::decodeRtcpFbPacket, there is a possible out of bounds read due to an integer overflow. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for explo…

CVEs per month

Weakness classes

Products

Worst active — by depth score

Google vulnerabilities

In RtcpByePacket::decodeByePacket, there is a possible due to a missing bounds check

In checkSsrcCollisionOnRcv of RtpSession.cpp, there is a possible memory safety issue due to a missing null check

In RtcpFbPacket::decodeRtcpFbPacket, there is a possible out of bounds read due to an integer overflow

Go-Attestation: Hash injection into trusted measurement list via unskipped SignatureHeaderSize vendor bytes in parseEfiSignatureList()

Go-Attestation: Hash injection into trusted measurement list via unskipped SignatureHeaderSize vendor bytes in parseEfiSignatureList()

In resolveContentProvider of ComputerEngine.java, there is a possible way to access URIs across users due to a logic error in the code

In multiple functions of NotificationChannel.java, there is a possible desync in persistence due to an incorrect bounds check

In multiple functions of AppOpsService.java, there is a possible missing permission check due to a permissions bypass

In multiple locations, there is a possible way to reveal images across users due to improper input validation

In updateProvidersWhenServiceRemoved of CredentialManagerService.java, there is a possible way to override settings across users due to a permissions bypass

In multiple functions of AccessibilityManagerService.java, there is a possible persistent denial of service due to improper input validation

In fixInitiatingUserIfNecessary of CallIntentProcessor.java, there is a possible way to make an emergency call due to a logic error in the code

In multiple locations, there is a possible tapjacking due to a logic error in the code

In Load of LoadedArsc.cpp, there is a possible out of bounds write due to a heap buffer overflow

In onNullBinding of HostEmulationManager.java, there is a possible way to launch an activity from the background due to a logic error in the code

In getCallingPackageName of Shared.java, there is a possible way to bypass activity start restrictions due to a confused deputy

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 misleading or insufficient UI

In l2c_fcr_clone_buf of l2c_fcr.cc, there is a possible way to trigger controlled heap corruption within the privileged Bluetooth process due to an integer overflow

In getApplicationLabel of KeyChainActivity.java, there is a possible way to trick the user into approving access to certificates due to misleading or insufficient UI

In multiple locations, there is a possible misleading UI due to obfuscation

In multiple locations, there is a possible way to execute code in the launcher process due to an over-privileged shell user

In multiple functions of PackageInstallerService.java, there is a possible way to install unverified apps due to a missing permission check

In getCallingAppLabel of CertInstaller.java, there is a possible way to hide a sensitive security dialogue due to misleading or insufficient UI

In approvalLevelForDomainInternal of DomainVerificationService.java, there is a possible way to hijack an arbitrary app link due to a logic error in the code

In onCreate of DisableSupervisionActivity.kt, there is a possible way to delete supervision data due to a missing null check

In applySimpleFieldMaxSize of DataRowHandler.java, there is a possible way to insert a large contact name due to improper input validation

In multiple functions of ubsan_throwing_runtime.cpp, there is a possible way to cause a crash due to an integer overflow

In setGlobalProxy of DevicePolicyManagerService.java, there is a possible desync in persistence due to improper input validation

In resumeConfigurationDispatch of ActivityRecord.java, there is a possible background application launch (bal) due to a logic error in the code