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 smmu_detach_dev of arm-smmu-v3.c, there is a possible permission bypass due to a logic error in the code

In multiple locations, there is a possible escalation of privilege due to improper input validation

In platform_msg_handler_init of default_msg_handlers.c, there is a possible confused deputy due to a confused deputy

In google_mba_recv_msg of google_mba_poll.c, there is a possible out-of-bounds write due to a race condition

In multiple functions of physmem_extmem_linux.c, there is a possible out-of-bounds read due to uninitialized data

In ARM64_TLBI of mmu.h, there is a possible memory corruption due to a race condition

In FsmReleaseKey of fsm.c, there is a possible permission bypass due to a missing permission check

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

In multiple locations, there is a possible out-of-bounds write due to a logic error in the code

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

In Cellular Modem, there is a possible out-of-bounds write due to a missing bounds check

In CPM, there is a possible information disclosure due to a confused deputy

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

In do_sss_aes_gcm_256_op of crypto-aes.c, there is a possible out-of-bounds read due to a missing bounds check

In printf of printf.c, there is a possible out-of-bounds write due to improper input validation

In gsa_sw_pk_hash_compare of image-auth-srv.c, there is a possible escalation of privilege due to a logic error in the code

In ac_init_one_sswrp of init.c, there is a possible escalation of privilege due to a logic error in the code

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

In Bootloader, there is a possible escalation of privilege due to a missing permission check

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

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

In gf_ta_test_set_config of gf_ta_test.c, there is a possible out-of-bounds write due to improper input validation

In VPU, there is a possible information dislclosure due to a logic error in the code

In addr_remap_address_map of remap.c, there is a possible escalation of privilege due to a logic error in the code

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

In Wave6VpuDecFlush of wave6.c, there is a possible out-of-bounds write due to a missing bounds check

In gf_base_update_finger_base of gf_base.c, 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 race condition

In Cellular Modem, there is a possible denial of service due to improper input validation

In decodeAmr of ImsMediaAudioPlayer.cpp, there is a possible out-of-bounds write due to a missing bounds check