Google
12,443 vulnerabilities.
All published vulnerabilities with a CVE number in Google products, newest first, with severity and references.
Page 1 of 125
| CVE | Summary | Published | CVSS |
|---|---|---|---|
| CVE-2026-28615 | Google Android: In Telecomm, there is a possible way to initiate an unauthorized phone call due to a permissions bypass. This could lead to local escalation of … | 2026-06-17 | 7.8 |
| CVE-2026-28587 | Google Android: In MmsSmsProvider of MmsSmsProvider.java, there is a possible way to retrieve sensitive information due to a missing permission check. This could … | 2026-06-17 | 5.5 |
| CVE-2026-28576 | Google Android: In Contacts Provider, there is a possible way to access the contacts database due to SQL injection. This could lead to local information disclosure … | 2026-06-17 | 5.5 |
| CVE-2026-28575 | Google Android: In PackageInstaller.Session#transfer of frameworks/base/services/core/java/com/android/server/pm/PackageInstallerSession.java, there is a possible … | 2026-06-17 | 5.5 |
| CVE-2026-20418 | Google Matter: In Thread, there is a possible out of bounds write due to a missing bounds check. This could lead to remote escalation of privilege with no … | 2026-02-02 | 9.8 |
| CVE-2026-20417 | Google Android: In pcie, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege if a malicious … | 2026-02-02 | 5.3 |
| CVE-2026-20415 | Google Android: In imgsys, there is a possible memory corruption due to improper locking. This could lead to local denial of service if a malicious actor has … | 2026-02-02 | 5.5 |
| CVE-2026-20414 | Google Android: In imgsys, there is a possible escalation of privilege due to use after free. This could lead to local escalation of privilege if a malicious actor … | 2026-02-02 | 6.7 |
| CVE-2026-20413 | Google Android: In imgsys, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege if a malicious … | 2026-02-02 | 6.7 |
| CVE-2026-20412 | Google Android: In cameraisp, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege if a … | 2026-02-02 | 7.8 |
| CVE-2026-20411 | Google Android: In cameraisp, there is a possible escalation of privilege due to use after free. This could lead to local denial of service if a malicious actor … | 2026-02-02 | 7.8 |
| CVE-2026-20410 | Google Android: In imgsys, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege if a malicious … | 2026-02-02 | 6.7 |
| CVE-2026-20409 | Google Android: In imgsys, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege if a malicious … | 2026-02-02 | 7.8 |
| CVE-2026-12467 | Google Chrome: Use after free in Extensions in Google Chrome prior to 149.0.7827.155 allowed a remote attacker who had compromised the renderer process to … | 2026-06-17 | 8.3 |
| CVE-2026-12465 | Google Chrome: Object lifecycle issue in Metrics in Google Chrome prior to 149.0.7827.155 allowed a remote attacker who had compromised the renderer process to … | 2026-06-17 | 8.3 |
| CVE-2026-12464 | Google Chrome: Use after free in Browser in Google Chrome prior to 149.0.7827.155 allowed a remote attacker who had compromised the renderer process to … | 2026-06-17 | 8.3 |
| CVE-2026-12462 | Google Chrome: Use after free in Media in Google Chrome prior to 149.0.7827.155 allowed a remote attacker who had compromised the renderer process to execute … | 2026-06-17 | 7.5 |
| CVE-2026-12460 | Google Chrome: Insufficient policy enforcement in File System Access in Google Chrome prior to 149.0.7827.155 allowed a remote attacker who had compromised the … | 2026-06-17 | 4.2 |
| CVE-2026-12459 | Google Chrome: Inappropriate implementation in Serial in Google Chrome prior to 149.0.7827.155 allowed a remote attacker to inject arbitrary scripts or HTML … | 2026-06-17 | 6.1 |
| CVE-2026-12458 | Google Chrome: Inappropriate implementation in Passwords in Google Chrome prior to 149.0.7827.155 allowed a remote attacker who convinced a user to engage in … | 2026-06-17 | 3.1 |
| CVE-2026-12457 | Google Chrome: Inappropriate implementation in Extensions in Google Chrome prior to 149.0.7827.155 allowed a remote attacker who had compromised the renderer … | 2026-06-17 | 4.2 |
| CVE-2026-12456 | Google Chrome: Inappropriate implementation in Extensions in Google Chrome prior to 149.0.7827.155 allowed an attacker who convinced a user to install a malicious … | 2026-06-17 | 4.2 |
| CVE-2026-12455 | Google Chrome: Use after free in Tab Strip in Google Chrome prior to 149.0.7827.155 allowed a remote attacker who convinced a user to engage in specific UI … | 2026-06-17 | 7.5 |
| CVE-2026-12453 | Google Chrome: Insufficient validation of untrusted input in Input in Google Chrome prior to 149.0.7827.155 allowed a remote attacker who had compromised the … | 2026-06-17 | 4.2 |
| CVE-2026-12451 | Google Chrome: Use after free in DigitalCredentials in Google Chrome prior to 149.0.7827.155 allowed a remote attacker who had compromised the renderer process to … | 2026-06-17 | 8.3 |
| CVE-2026-12450 | Google Chrome: Inappropriate implementation in Media in Google Chrome prior to 149.0.7827.155 allowed a remote attacker to obtain potentially sensitive … | 2026-06-17 | 6.5 |
| CVE-2026-3910 | Google Chrome: Inappropriate implementation in V8 in Google Chrome prior to 146.0.7680.75 allowed a remote attacker to execute arbitrary code inside a sandbox via … | 2026-03-13 | 8.8 |
| CVE-2026-3909 | Google Chrome: Out of bounds write in Skia in Google Chrome prior to 146.0.7680.75 allowed a remote attacker to perform out of bounds memory access via a crafted … | 2026-03-13 | 8.8 |
| CVE-2026-1504 | Google Chrome: Inappropriate implementation in Background Fetch API in Google Chrome prior to 144.0.7559.110 allowed a remote attacker to leak cross-origin data … | 2026-01-27 | 6.5 |
| CVE-2026-1260 | Google Sentencepiece: Invalid memory access in Sentencepiece versions less than 0.2.1 when using a vulnerable model file, which is not created in the normal training … | 2026-01-22 | 7.8 |
| CVE-2026-0908 | Google Chrome: Use after free in ANGLE in Google Chrome prior to 144.0.7559.59 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML … | 2026-01-20 | 8.8 |
| CVE-2026-0907 | Google Chrome: Incorrect security UI in Split View in Google Chrome prior to 144.0.7559.59 allowed a remote attacker to perform UI spoofing via a crafted HTML … | 2026-01-20 | 9.8 |
| CVE-2026-0906 | Google Chrome: Incorrect security UI in Google Chrome on Android prior to 144.0.7559.59 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) … | 2026-01-20 | 9.8 |
| CVE-2026-0905 | Google Chrome: Insufficient policy enforcement in Network in Google Chrome prior to 144.0.7559.59 allowed an attack who obtained a network log file to potentially … | 2026-01-20 | 9.8 |
| CVE-2026-0904 | Google Chrome: Incorrect security UI in Digital Credentials in Google Chrome prior to 144.0.7559.59 allowed a remote attacker to perform domain spoofing via a … | 2026-01-20 | 5.4 |
| CVE-2026-0903 | Google Chrome: Inappropriate implementation in Downloads in Google Chrome on Windows prior to 144.0.7559.59 allowed a remote attacker to bypass dangerous file … | 2026-01-20 | 5.4 |
| CVE-2026-0902 | Google Chrome: Inappropriate implementation in V8 in Google Chrome prior to 144.0.7559.59 allowed a remote attacker to perform an out of bounds memory read via a … | 2026-01-20 | 8.8 |
| CVE-2026-0901 | Google Chrome: Inappropriate implementation in Blink in Google Chrome on Android prior to 144.0.7559.59 allowed a remote attacker to perform UI spoofing via a … | 2026-01-20 | 5.4 |
| CVE-2026-0900 | Google Chrome: Inappropriate implementation in V8 in Google Chrome prior to 144.0.7559.59 allowed a remote attacker to potentially exploit object corruption via a … | 2026-01-20 | 8.8 |
| CVE-2026-0899 | Google Chrome: Out of bounds memory access in V8 in Google Chrome prior to 144.0.7559.59 allowed a remote attacker to potentially exploit object corruption via a … | 2026-01-20 | 8.8 |
| CVE-2026-0628 | Google Chrome: Insufficient policy enforcement in WebView tag in Google Chrome prior to 143.0.7499.192 allowed an attacker who convinced a user to install a … | 2026-01-07 | 8.8 |
| CVE-2026-0106 | Google Android: In vpu_mmap of vpu_ioctl, there is a possible arbitrary address mmap due to a missing bounds check. This could lead to local escalation of … | 2026-02-05 | 9.3 |
| CVE-2026-0092 | Google Android: In Package Manager, there is a possible device lock controller bypass due to a missing permission check. This could lead to local escalation of … | 2026-06-17 | 10.0 |
| CVE-2026-0083 | Google Android: In Nfc::eventCallback() of Nfc.h, there is a possible use after free due to a race condition. This could lead to local escalation of privilege with … | 2026-06-17 | 7.0 |
| CVE-2026-0082 | Google Android: In tryStartActivity of NfcDispatcher.java, there is a possible automatic special app access permission assignment due to an insecure default value. … | 2026-06-17 | 7.8 |
| CVE-2026-0081 | Google Android: In NFC, there is a possible way to spoof an NFC event due to a missing permission check. This could lead to local escalation of privilege with no … | 2026-06-17 | 7.8 |
| CVE-2026-0071 | Google Android: In SettingsLib, there is a possible missing permission check due to a logic error in the code. This could lead to local escalation of privilege … | 2026-06-17 | 7.8 |
| CVE-2026-0068 | Google Android: In createSessionInternal of PackageInstallerService.java, there is a possible method to remove a DPC app from a managed device without DO consent … | 2026-06-17 | 7.8 |
| CVE-2026-0064 | Google Android: In multiple places, there is a possible persistent denial of service due to resource exhaustion. This could lead to local denial of service with no … | 2026-06-17 | 5.5 |
| CVE-2026-0063 | Google Android: In setAllowedCarriers of PhoneInterfaceManager.java, there is a possible way to disable carrier restrictions due to a logic error in the code. This … | 2026-06-17 | 7.8 |
| CVE-2026-0057 | Google Android: In Contacts Provider, there is a possible way to access an incoming call's phone number and associated metadata due to a missing permission check. … | 2026-06-17 | 3.3 |
| CVE-2026-0019 | Google Android: In SettingsLib, there is a possible way to disable system components due to a logic error in the code. This could lead to local escalation of … | 2026-06-17 | 7.8 |
| CVE-2025-61619 | Google Android: In nr modem, there is a possible system crash due to improper input validation. This could lead to remote denial of service with no additional … | 2025-12-01 | 7.5 |
| CVE-2025-61618 | Google Android: In nr modem, there is a possible system crash due to improper input validation. This could lead to remote denial of service with no additional … | 2025-12-01 | 7.5 |
| CVE-2025-61617 | Google Android: In nr modem, there is a possible system crash due to improper input validation. This could lead to remote denial of service with no additional … | 2025-12-01 | 7.5 |
| CVE-2025-61610 | Google Android: In nr modem, there is a possible system crash due to improper input validation. This could lead to remote denial of service with no additional … | 2025-12-01 | 7.5 |
| CVE-2025-61609 | Google Android: In modem, there is a possible system crash due to improper input validation. This could lead to remote denial of service with no additional … | 2025-12-01 | 7.5 |
| CVE-2025-61608 | Google Android: In nr modem, there is a possible system crash due to improper input validation. This could lead to remote denial of service with no additional … | 2025-12-01 | 7.5 |
| CVE-2025-61607 | Google Android: In nr modem, there is a possible system crash due to improper input validation. This could lead to remote denial of service with no additional … | 2025-12-01 | 7.5 |
| CVE-2025-55559 | Google Tensorflow: An issue was discovered TensorFlow v2.18.0. A Denial of Service (DoS) occurs when padding is set to 'valid' in tf.keras.layers.Conv2D. | 2025-09-25 | 7.5 |
| CVE-2025-55556 | Google Tensorflow: TensorFlow v2.18.0 was discovered to output random results when compiling Embedding, leading to unexpected behavior in the application. | 2025-09-25 | 6.5 |
| CVE-2025-48647 | Google Android: In cpm_fwtp_msg_handler of cpm/google/lib/tracepoint/cpm_fwtp_ipc.c, there is a possible memory overwrite due to improper input validation. This … | 2026-01-16 | 7.8 |
| CVE-2025-48643 | Google Android: In multiple locations there is a possible provisioning bypass due to improper input validation. This could lead to local escalation of privilege … | 2026-06-17 | 7.8 |
| CVE-2025-48640 | Google Android: In multiple locations, there is a possible 3rd party passkey entry pairing approval due to a missing permission check. This could lead to remote … | 2026-06-17 | 8.0 |
| CVE-2025-48639 | Google Android: In DefaultTransitionHandler.java, there is a possible way to unknowingly grant permissions to an app due to a tapjacking/overlay attack. This could … | 2025-12-08 | 7.3 |
| CVE-2025-48638 | Google Android: In __pkvm_load_tracing of trace.c, there is a possible out-of-bounds write due to improper input validation. This could lead to local escalation of … | 2025-12-08 | 7.8 |
| CVE-2025-48637 | Google Android: In multiple functions of mem_protect.c, there is a possible out of bounds write due to an integer overflow. This could lead to local escalation of … | 2025-12-08 | 7.8 |
| CVE-2025-48633 | Google Android: In hasAccountsOnAnyUser of DevicePolicyManagerService.java, there is a possible way to add a Device Owner after provisioning due to a logic error … | 2025-12-08 | 5.5 |
| CVE-2025-48632 | Google Android: In setDisplayName of AssociationRequest.java, there is a possible way to cause CDM associations to persist after the user has disassociated them … | 2025-12-08 | 7.8 |
| CVE-2025-48631 | Google Android: In onHeaderDecoded of LocalImageResolver.java, there is a possible persistent denial of service due to resource exhaustion. This could lead to … | 2025-12-08 | 7.5 |
| CVE-2025-48629 | Google Android: In findAvailRecognizer of VoiceInteractionManagerService.java, there is a possible way to become the default speech recognizer app due to an … | 2025-12-08 | 7.8 |
| CVE-2025-48628 | Google Android: In validateIconUserBoundary of PrintManagerService.java, there is a possible cross-user image leak due to a confused deputy. This could lead to … | 2025-12-08 | 7.8 |
| CVE-2025-48627 | Google Android: In startNextMatchingActivity of ActivityTaskManagerService.java, there is a possible way to launch an activity from the background due to a logic … | 2025-12-08 | 7.8 |
| CVE-2025-48626 | Google Android: In multiple locations, there is a possible way to launch an application from the background due to a precondition check failure. This could lead to … | 2025-12-08 | 9.8 |
| CVE-2025-48625 | Google Android: In multiple locations of UsbDataAdvancedProtectionHook.java, there is a possible way to access USB data when the screen is off due to a race … | 2025-12-08 | 7.0 |
| CVE-2025-48624 | Google Android: In multiple functions of arm-smmu-v3.c, there is a possible out-of-bounds write due to improper input validation. This could lead to local … | 2025-12-08 | 7.8 |
| CVE-2025-48623 | Google Android: In init_pkvm_hyp_vcpu of pkvm.c, there is a possible out of bounds write due to improper input validation. This could lead to local escalation of … | 2025-12-08 | 7.8 |
| CVE-2025-48622 | Google Android: In ProcessArea of dng_misc_opcodes.cpp, there is a possible out of bounds read due to a buffer overflow. This could lead to local information … | 2025-12-08 | 5.5 |
| CVE-2025-48621 | Google Android: In DefaultTransitionHandler.java, there is a possible way to enable a tapjacking attack due to a insecure default. This could lead to local … | 2025-12-08 | 7.3 |
| CVE-2025-48620 | Google Android: In onSomePackagesChanged of VoiceInteractionManagerService.java, there is a possible way for a third party application's component name to persist … | 2025-12-08 | 7.8 |
| CVE-2025-48618 | Google Android: In processLaunchBrowser of CommandParamsFactory.java, there is a possible browser interaction from the lockscreen due to improper locking. This … | 2025-12-08 | 6.8 |
| CVE-2025-48617 | Google Android: In overrideConfig of CarrierConfigLoader.java, there is a possible way to bypass UID check due to a permissions bypass. This could lead to local … | 2026-06-17 | 7.8 |
| CVE-2025-48615 | Google Android: In getComponentName of MediaButtonReceiverHolder.java, there is a possible desync in persistence due to resource exhaustion. This could lead to … | 2025-12-08 | 7.8 |
| CVE-2025-48614 | Google Android: In rebootWipeUserData of RecoverySystem.java, there is a possible way to factory reset the device while in DSU mode due to a missing permission … | 2025-12-08 | 4.6 |
| CVE-2025-48612 | Google Android: In multiple locations, there is a possible way for an application on a work profile to set the main user's default NFC payment setting due to … | 2025-12-08 | 7.8 |
| CVE-2025-48610 | Google Android: In __pkvm_guest_relinquish_to_host of mem_protect.c, there is a possible configuration data leak due to a logic error in the code. This could lead … | 2025-12-08 | 5.5 |
| CVE-2025-48608 | Google Android: In isValidMediaUri of SettingsProvider.java, there is a possible cross user media read due to a missing permission check. This could lead to local … | 2025-12-08 | 5.5 |
| CVE-2025-48607 | Google Android: In multiple locations, there is a possible way to create a large amount of app ops due to a logic error in the code. This could lead to local … | 2025-12-08 | 5.5 |
| CVE-2025-48606 | Google Android: In preparePackage of InstallPackageHelper.java, there is a possible way for an app to appear hidden upon installation without a mechanism to … | 2025-12-08 | 7.8 |
| CVE-2025-48604 | Google Android: In multiple locations, there is a possible way to read files from another user due to a missing permission check. This could lead to local … | 2025-12-08 | 5.5 |
| CVE-2025-48603 | Google Android: In InputMethodInfo of InputMethodInfo.java, there is a possible permanent denial of service due to resource exhaustion. This could lead to local … | 2025-12-08 | 5.5 |
| CVE-2025-48601 | Google Android: In multiple locations, there is a possible permanent denial of service due to improper input validation. This could lead to local escalation of … | 2025-12-08 | 5.5 |
| CVE-2025-48600 | Google Android: In multiple files, there is a possible way to reveal information across users due to a missing permission check. This could lead to local … | 2025-12-08 | 5.5 |
| CVE-2025-48599 | Google Android: In multiple functions of WifiScanModeActivity.java, there is a possible way to bypass a device config restriction due to a missing permission … | 2025-12-08 | 7.8 |
| CVE-2025-48598 | Google Android: In multiple locations, there is a possible way to alter the primary user's face unlock settings due to a confused deputy. This could lead to … | 2025-12-08 | 6.6 |
| CVE-2025-48597 | Google Android: In multiple locations, there is a possible way to trick a user into accepting a permission due to a tapjacking/overlay attack. This could lead to … | 2025-12-08 | 7.8 |
| CVE-2025-48596 | Google Android: In appendFrom of Parcel.cpp, there is a possible out of bounds read due to a missing bounds check. This could lead to local escalation of privilege … | 2025-12-08 | 7.8 |
| CVE-2025-48594 | Google Android: In onUidImportance of DisassociationProcessor.java, there is a possible way to retain companion application privileges after disassociation due to … | 2025-12-08 | 7.3 |
| CVE-2025-48593 | Google Android: In bta_hf_client_cb_init of bta_hf_client_main.cc, there is a possible remote code execution due to a use after free. This could lead to remote … | 2025-11-18 | 8.0 |
| CVE-2025-48592 | Google Android: In initDecoder of C2SoftDav1dDec.cpp, there is a possible out of bounds read due to a heap buffer overflow. This could lead to remote information … | 2025-12-08 | 7.5 |
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Too many to
patch at once?
Providers for vulnerability management find the affected systems in your environment, set the order and keep the patching going.