Vulnerabilities
Aggregated CVE / GHSA / KEV / OSV — filter by tag and category.
| ID | Title | |
|---|---|---|
| CVE-2026-6304 |
|
Use-After-Free in google (CVE-2026-6304)
vulnerability in google (CVE-2026-6304). Successful exploitation can lead to full system takeover.
|
| CVE-2026-6306 |
|
Vulnerability in google (CVE-2026-6306)
vulnerability in google (CVE-2026-6306). Successful exploitation can lead to full system takeover.
|
| CVE-2026-6303 |
|
Use-After-Free in google (CVE-2026-6303)
vulnerability in google (CVE-2026-6303). Successful exploitation can lead to full system takeover.
|
| CVE-2026-6305 |
|
Vulnerability in google (CVE-2026-6305)
vulnerability in google (CVE-2026-6305). Successful exploitation can lead to full system takeover.
|
| CVE-2026-6296 |
|
Vulnerability in google (CVE-2026-6296)
vulnerability in google (CVE-2026-6296). Successful exploitation can lead to full system takeover.
|
| CVE-2026-6299 |
|
Use-After-Free in google (CVE-2026-6299)
vulnerability in google (CVE-2026-6299). Successful exploitation can lead to full system takeover.
|
| CVE-2026-6300 |
|
Use-After-Free in google (CVE-2026-6300)
vulnerability in google (CVE-2026-6300). Successful exploitation can lead to full system takeover.
|
| CVE-2026-6298 |
|
Vulnerability in google (CVE-2026-6298)
vulnerability in google (CVE-2026-6298). Risk of unauthorized operations or information disclosure.
|
| CVE-2026-5863 |
|
Vulnerability in google (CVE-2026-5863)
vulnerability in google (CVE-2026-5863). Successful exploitation can lead to full system takeover.
|
| CVE-2026-5911 |
|
Vulnerability in google (CVE-2026-5911)
vulnerability in google (CVE-2026-5911). Risk of unauthorized operations or information disclosure.
|
| CVE-2026-5890 |
|
Vulnerability in google (CVE-2026-5890)
vulnerability in google (CVE-2026-5890). Confidential information can be exposed externally.
|
| CVE-2026-5879 |
|
Vulnerability in google (CVE-2026-5879)
vulnerability in google (CVE-2026-5879). Successful exploitation can lead to full system takeover.
|
| CVE-2026-5883 |
|
Use-After-Free in google (CVE-2026-5883)
vulnerability in google (CVE-2026-5883). Successful exploitation can lead to full system takeover.
|
| CVE-2026-5865 |
|
Vulnerability in google (CVE-2026-5865)
vulnerability in google (CVE-2026-5865). Successful exploitation can lead to full system takeover.
|
| CVE-2026-5867 |
|
Vulnerability in google (CVE-2026-5867)
vulnerability in google (CVE-2026-5867). Risk of unauthorized operations or information disclosure.
|
| CVE-2026-5860 |
|
Use-After-Free in google (CVE-2026-5860)
vulnerability in google (CVE-2026-5860). Successful exploitation can lead to full system takeover.
|
| CVE-2026-5272 |
|
Vulnerability in google (CVE-2026-5272)
vulnerability in google (CVE-2026-5272). Successful exploitation can lead to full system takeover.
|
| CVE-2026-5273 |
|
Use-After-Free in google (CVE-2026-5273)
vulnerability in google (CVE-2026-5273). Risk of unauthorized operations or information disclosure.
|
| CVE-2026-4447 |
|
Vulnerability in google (CVE-2026-4447)
vulnerability in google (CVE-2026-4447). Successful exploitation can lead to full system takeover.
|
| CVE-2022-2160 |
|
Vulnerability in google (CVE-2022-2160)
vulnerability in google (CVE-2022-2160). Confidential information can be exposed externally.
|
| CVE-2020-16017 KEV |
|
[KEV] Use-After-Free in Google chrome (CVE-2020-16017)
vulnerability in Google chrome (CVE-2020-16017). Risk of unauthorized operations or information disclosure. Listed in CISA KEV — actively exploited.
|
| CVE-2019-13721 |
|
Use-After-Free in google (CVE-2019-13721)
vulnerability in google (CVE-2019-13721). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5103 |
|
Vulnerability in google (CVE-2017-5103)
vulnerability in google (CVE-2017-5103). Risk of unauthorized operations or information disclosure.
|
| CVE-2017-5104 |
|
Vulnerability in google (CVE-2017-5104)
vulnerability in google (CVE-2017-5104). Data can be tampered with by attackers.
|
| CVE-2017-5105 |
|
Vulnerability in google (CVE-2017-5105)
vulnerability in google (CVE-2017-5105). Data can be tampered with by attackers.
|
| CVE-2017-5106 |
|
Vulnerability in google (CVE-2017-5106)
vulnerability in google (CVE-2017-5106). Data can be tampered with by attackers.
|
| CVE-2017-5107 |
|
Vulnerability in google (CVE-2017-5107)
vulnerability in google (CVE-2017-5107). Confidential information can be exposed externally.
|
| CVE-2017-5108 |
|
Vulnerability in google (CVE-2017-5108)
vulnerability in google (CVE-2017-5108). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5109 |
|
Vulnerability in google (CVE-2017-5109)
vulnerability in google (CVE-2017-5109). Risk of unauthorized operations or information disclosure.
|
| CVE-2017-5110 |
|
Vulnerability in google (CVE-2017-5110)
vulnerability in google (CVE-2017-5110). Data can be tampered with by attackers.
|
| CVE-2017-5111 |
|
Use-After-Free in google (CVE-2017-5111)
vulnerability in google (CVE-2017-5111). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5112 |
|
Buffer Overflow in google (CVE-2017-5112)
vulnerability in google (CVE-2017-5112). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5113 |
|
Out-of-Bounds Write in google (CVE-2017-5113)
out-of-bounds write in google (CVE-2017-5113). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5114 |
|
Buffer Overflow in google (CVE-2017-5114)
vulnerability in google (CVE-2017-5114). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5115 |
|
Vulnerability in google (CVE-2017-5115)
vulnerability in google (CVE-2017-5115). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5116 |
|
Vulnerability in google (CVE-2017-5116)
vulnerability in google (CVE-2017-5116). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5117 |
|
Information Disclosure in google (CVE-2017-5117)
vulnerability in google (CVE-2017-5117). Confidential information can be exposed externally.
|
| CVE-2017-5118 |
|
Vulnerability in google (CVE-2017-5118)
vulnerability in google (CVE-2017-5118). Risk of unauthorized operations or information disclosure.
|
| CVE-2017-5119 |
|
Buffer Overflow in google (CVE-2017-5119)
vulnerability in google (CVE-2017-5119). Risk of unauthorized operations or information disclosure.
|
| CVE-2017-5120 |
|
Vulnerability in google (CVE-2017-5120)
vulnerability in google (CVE-2017-5120). Data can be tampered with by attackers.
|
| CVE-2017-5121 |
|
Vulnerability in google (CVE-2017-5121)
vulnerability in google (CVE-2017-5121). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5122 |
|
Buffer Overflow in google (CVE-2017-5122)
vulnerability in google (CVE-2017-5122). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5074 |
|
Use-After-Free in google (CVE-2017-5074)
vulnerability in google (CVE-2017-5074). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5075 |
|
Information Disclosure in google (CVE-2017-5075)
vulnerability in google (CVE-2017-5075). Risk of unauthorized operations or information disclosure.
|
| CVE-2017-5076 |
|
Vulnerability in google (CVE-2017-5076)
vulnerability in google (CVE-2017-5076). Data can be tampered with by attackers.
|
| CVE-2017-5077 |
|
Out-of-Bounds Read in google (CVE-2017-5077)
vulnerability in google (CVE-2017-5077). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5078 |
|
Vulnerability in c (CVE-2017-5078)
vulnerability in c (CVE-2017-5078). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5079 |
|
Vulnerability in google (CVE-2017-5079)
vulnerability in google (CVE-2017-5079). Risk of unauthorized operations or information disclosure.
|
| CVE-2017-5080 |
|
Use-After-Free in google (CVE-2017-5080)
vulnerability in google (CVE-2017-5080). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5081 |
|
Vulnerability in google (CVE-2017-5081)
vulnerability in google (CVE-2017-5081). Risk of unauthorized operations or information disclosure.
|