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 get_global_config_item_addr of gc.c, there is a possible out-of-bounds read due to a missing bounds check

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

In Start of AudioRtpPayloadEncoderNode.cpp, there is a possible out-of-bounds write due to improper input validation

In multiple files, there is a possible out-of-bounds read due to type confusion

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

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

In multiple functions of bluetooth_cco.cc, there is a possible use-after-free due to a race condition

In multiple files, there is a possible way to obtain signatures due to type confusion

In ap_pmic_poll_msg_handler of ap_pmic_ipc.c, there is a possible permission bypass due to a confused deputy

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

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

In acfw_ffa.c, there is a possible secret read due to a logic error in the code

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

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

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

In the Setup Wizard, there is a possible remote package install due to a missing permission check

In Modem, there is a possible information disclosure due to improper input validation

In gf_ta_test_set_config of gf_ta_test.c, there is a possible heap buffer overflow due to a logic error in the code

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

In multiple functions of DreamPickerReceiver.kt, there is a possible permission bypass due to a confused deputy

In trusty_dputc of generic-arm64-smcall.c, there is a possible out-of-bounds write due to a race condition

In Vp9DecEndOfStream of vp9hwd_output.cc, there is a possible out-of-bounds read due to an incorrect bounds check

In IP Multimedia Subsystem, there is a possible out-of-bounds write due to improper input validation

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

In Cellular Modem, there is a possible permission bypass due to a logic error in the code

In FsmReleaseKey of fsm.c, there is a possible permission bypass due to improper input validation

In smmu_detach_dev_nested of arm-smmu-v3.c, there is a possible escalation of privilege due to improper input validation

In multiple locations, there is a possible time-of-check to time-of-use due to a race condition

In gmc_phy_lp3_exit_restore_registers of phy_power.c, there is a possible escalation of privilege due to a missing bounds check

In multiple locations, there is a possible information disclosure due to uninitialized memory use