Google has 753 CVEs on record between 2021 and 2026. Disclosure cadence is accelerating: 615 in the last 90 days against 97 in the 90 before. The busiest recent month was September 2026 with 500. 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 (492), android (232), mcp_toolbox_for_databases (6).

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: 615 prev 97

Weakness classes

Products

chrome 492
android 232
mcp_toolbox_for_databases 6
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

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

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