Google has 2,255 CVEs on record between 2011 and 2026. Disclosure cadence is accelerating: 1836 in the last 90 days against 115 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 115

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

CVEs per month

Weakness classes

Products

Worst active — by depth score

Google vulnerabilities

In multiple locations, there is a possible out-of-bounds write due to improper input validation

In IP Multimedia Subsystem, there is a possible out-of-bounds write due to an incorrect bounds check

In multiple functions of remap.c, there is a possible out-of-bounds write due to an incorrect bounds check

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

In VPU, there is a possible out-of-bounds write due to an integer overflow

In enable_segment of remap.c, there is a possible permission bypass due to a logic error in the code

In gmc_mb_msg_handler of gmc_mba.c, there is a possible memory corruption due to a confused deputy

In IP Multimedia Subsystem, there is a possible authentication bypass due to a logic error in the code

In ReadDataElement of common.c, there is a possible information disclosure due to an incorrect bounds check

In multiple locations, there is a possible permission bypass due to side channel information disclosure

In Cellular Modem, there is a possible information disclosure due to a logic error in the code

In VPU, there is a possible shared memory overwrite due to improper input validation

In multiple locations, there is a possible permission bypass due to an integer overflow

In s_decode_vui_param of fw_hevc_dec_header.c, there is a possible out-of-bounds write due to a logic error in the code

In bigo_worker_thread of bigo.c, there is a possible escalation of privilege due to a race condition

In multiple locations, there is a possible use-after-free due to improper locking

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

In handle_unmap_req of tipc_virtio_dev.c, there is a possible memory corruption due to a race condition

In CPM, there is a possible permission bypass due to a confused deputy

In ReadTileInfo of vp9hwd_headers.cc, there is a possible out-of-bounds write due to a missing bounds check

In multiple functions of fpc_tee_hal.c, there is a possible use-after-free due to a logic error in the code

In Trusted Execution Environment, there is a possible memory corruption due to improper input validation

In gf_algo_get_cached_dump_data of gf_algo.c, there is a possible out-of-bounds read due to a missing bounds check

In VPU, there is a possible out-of-bounds write due to a confused deputy

In Cellular Modem, there is a possible out-of-bounds write due to a heap buffer overflow

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

In validate_ns_buf of mbu_class.rs, there is a possible information disclosure due to improper input validation

In multiple locations, there is a possible escalation of privilege due to a logic error in the code

In multiple locations, there is a possible out-of-bounds write due to an incorrect bounds check

In multiple locations, there is a possible permission bypass due to a missing permission check