Google

In display, there is a possible memory corruption due to a missing bounds check. This could lead to local escalation of

In display, there is a possible memory corruption due to use after free. This could lead to local escalation of privileg

In display, there is a possible system crash due to use after free. This could lead to local denial of service if a mali

In MAE, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr

In MAE, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr

In imgsys, there is a possible system crash due to use after free. This could lead to local denial of service if a malic

In MAE, there is a possible out of bounds write due to a race condition. This could lead to local escalation of privileg

In MAE, there is a possible system crash due to use after free. This could lead to local denial of service if a maliciou

In preloader, there is a possible read of device unique identifiers due to a logic error. This could lead to local infor

In display, there is a possible out of bounds read due to a missing bounds check. This could lead to local information d

In display, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation o

In display, there is a possible escalation of privilege due to a missing bounds check. This could lead to local escalati

In display, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation o

In display, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation o

In display, there is a possible out of bounds read due to a missing bounds check. This could lead to local information d

In pcie, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of p

Arbitrary file write & potential privilege escalation exploiting zip slip vulnerability in Google Web Designer.

Inappropriate implementation in DevTools in Google Chrome prior to 145.0.7632.116 allowed an attacker who convinced a us

Out of bounds read and write in Tint in Google Chrome on Mac prior to 145.0.7632.116 allowed a remote attacker to perfor

Out of bounds read in Media in Google Chrome prior to 145.0.7632.116 allowed a remote attacker to perform an out of boun

Heap buffer overflow in Media in Google Chrome prior to 145.0.7632.109 allowed a remote attacker to potentially exploit

Integer overflow in V8 in Google Chrome prior to 145.0.7632.109 allowed a remote attacker to potentially exploit heap co

Heap buffer overflow in PDFium in Google Chrome prior to 145.0.7632.109 allowed a remote attacker to perform an out of b

Use after free in CSS in Google Chrome prior to 145.0.7632.75 allowed a remote attacker to execute arbitrary code inside

Inappropriate implementation in Downloads in Google Chrome prior to 145.0.7632.45 allowed a remote attacker to perform U

Inappropriate implementation in File input in Google Chrome prior to 145.0.7632.45 allowed a remote attacker who convinc

Use after free in Ozone in Google Chrome prior to 145.0.7632.45 allowed a remote attacker who convinced a user to engage

Inappropriate implementation in File input in Google Chrome prior to 145.0.7632.45 allowed a remote attacker who convinc

Race in DevTools in Google Chrome prior to 145.0.7632.45 allowed a remote attacker who convinced a user to engage in spe

Inappropriate implementation in PictureInPicture in Google Chrome prior to 145.0.7632.45 allowed a remote attacker who c

Inappropriate implementation in Animation in Google Chrome prior to 145.0.7632.45 allowed a remote attacker to leak cros

Insufficient policy enforcement in Frames in Google Chrome prior to 145.0.7632.45 allowed a remote attacker to perform U

Inappropriate implementation in WebGPU in Google Chrome prior to 145.0.7632.45 allowed a remote attacker to potentially

Heap buffer overflow in Codecs in Google Chrome prior to 145.0.7632.45 allowed a remote attacker to potentially exploit

Use after free in CSS in Google Chrome prior to 145.0.7632.45 allowed a remote attacker to potentially exploit heap corr

In vpu_mmap of vpu_ioctl, there is a possible arbitrary address mmap due to a missing bounds check. This could lead to l

Type Confusion in V8 in Google Chrome prior to 144.0.7559.132 allowed a remote attacker to potentially exploit heap corr

Heap buffer overflow in libvpx in Google Chrome prior to 144.0.7559.132 allowed a remote attacker to potentially exploit

In Thread, there is a possible out of bounds write due to a missing bounds check. This could lead to remote escalation o

In pcie, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of p

In imgsys, there is a possible memory corruption due to improper locking. This could lead to local denial of service if

In imgsys, there is a possible escalation of privilege due to use after free. This could lead to local escalation of pri

In imgsys, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of

In cameraisp, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation

In cameraisp, there is a possible escalation of privilege due to use after free. This could lead to local denial of serv

In imgsys, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of

In imgsys, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of

Inappropriate implementation in Background Fetch API in Google Chrome prior to 144.0.7559.110 allowed a remote attacker

A denial-of-service (DoS) vulnerability exists in google.protobuf.json_format.ParseDict() in Python, where the max_recur

Invalid memory access in Sentencepiece versions less than 0.2.1 when using a vulnerable model file, which is not created