Vulnerabilities
Aggregated CVE / GHSA / KEV / OSV — filter by tag and category.
| ID | Title | |
|---|---|---|
| CVE-2026-9987 |
|
Vulnerability in google (CVE-2026-9987)
vulnerability in google (CVE-2026-9987). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9984 |
|
Use-After-Free in google (CVE-2026-9984)
vulnerability in google (CVE-2026-9984). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9978 |
|
Use-After-Free in google (CVE-2026-9978)
vulnerability in google (CVE-2026-9978). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9982 |
|
Vulnerability in google (CVE-2026-9982)
vulnerability in google (CVE-2026-9982). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9983 |
|
Vulnerability in google (CVE-2026-9983)
vulnerability in google (CVE-2026-9983). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9977 |
|
Vulnerability in google (CVE-2026-9977)
vulnerability in google (CVE-2026-9977). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9972 |
|
Vulnerability in google (CVE-2026-9972)
vulnerability in google (CVE-2026-9972). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9968 |
|
Vulnerability in google (CVE-2026-9968)
vulnerability in google (CVE-2026-9968). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9969 |
|
Vulnerability in google (CVE-2026-9969)
vulnerability in google (CVE-2026-9969). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9970 |
|
Use-After-Free in google (CVE-2026-9970)
vulnerability in google (CVE-2026-9970). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9973 |
|
Out-of-Bounds Write in google (CVE-2026-9973)
out-of-bounds write in google (CVE-2026-9973). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9974 |
|
Out-of-Bounds Write in google (CVE-2026-9974)
out-of-bounds write in google (CVE-2026-9974). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9975 |
|
Out-of-Bounds Read in google (CVE-2026-9975)
vulnerability in google (CVE-2026-9975). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9976 |
|
Code Injection in google (CVE-2026-9976)
code injection in google (CVE-2026-9976). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9963 |
|
Vulnerability in google (CVE-2026-9963)
vulnerability in google (CVE-2026-9963). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9964 |
|
Use-After-Free in google (CVE-2026-9964)
vulnerability in google (CVE-2026-9964). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9966 |
|
Vulnerability in google (CVE-2026-9966)
vulnerability in google (CVE-2026-9966). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9958 |
|
Use-After-Free in google (CVE-2026-9958)
vulnerability in google (CVE-2026-9958). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9960 |
|
Vulnerability in google (CVE-2026-9960)
vulnerability in google (CVE-2026-9960). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9961 |
|
Use-After-Free in google (CVE-2026-9961)
vulnerability in google (CVE-2026-9961). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9962 |
|
Use-After-Free in google (CVE-2026-9962)
vulnerability in google (CVE-2026-9962). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9965 |
|
Out-of-Bounds Write in google (CVE-2026-9965)
out-of-bounds write in google (CVE-2026-9965). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9949 |
|
Use-After-Free in google (CVE-2026-9949)
vulnerability in google (CVE-2026-9949). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9956 |
|
Use-After-Free in google (CVE-2026-9956)
vulnerability in google (CVE-2026-9956). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9954 |
|
Use-After-Free in google (CVE-2026-9954)
vulnerability in google (CVE-2026-9954). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9957 |
|
Use-After-Free in google (CVE-2026-9957)
vulnerability in google (CVE-2026-9957). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9941 |
|
Use-After-Free in google (CVE-2026-9941)
vulnerability in google (CVE-2026-9941). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9945 |
|
Use-After-Free in google (CVE-2026-9945)
vulnerability in google (CVE-2026-9945). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9939 |
|
Vulnerability in google (CVE-2026-9939)
vulnerability in google (CVE-2026-9939). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9940 |
|
Vulnerability in google (CVE-2026-9940)
vulnerability in google (CVE-2026-9940). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9936 |
|
Use-After-Free in google (CVE-2026-9936)
vulnerability in google (CVE-2026-9936). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9922 |
|
Use-After-Free in google (CVE-2026-9922)
vulnerability in google (CVE-2026-9922). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9924 |
|
Vulnerability in google (CVE-2026-9924)
vulnerability in google (CVE-2026-9924). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9914 |
|
Vulnerability in google (CVE-2026-9914)
vulnerability in google (CVE-2026-9914). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9915 |
|
Vulnerability in google (CVE-2026-9915)
vulnerability in google (CVE-2026-9915). Successful exploitation can lead to full system takeover.
|
| CVE-2026-9906 |
|
Out-of-Bounds Write in google (CVE-2026-9906)
out-of-bounds write in google (CVE-2026-9906). Successful exploitation can lead to full system takeover.
|
| CVE-2026-46827 |
|
Privilege Escalation in c (CVE-2026-46827)
vulnerability in c (CVE-2026-46827). Successful exploitation can lead to full system takeover.
|
| CVE-2026-46826 |
|
Vulnerability in c (CVE-2026-46826)
vulnerability in c (CVE-2026-46826). Successful exploitation can lead to full system takeover.
|
| CVE-2026-46823 |
|
Authorization Flaw in c (CVE-2026-46823)
vulnerability in c (CVE-2026-46823). Confidential information can be exposed externally.
|
| CVE-2026-46829 |
|
Vulnerability in c (CVE-2026-46829)
vulnerability in c (CVE-2026-46829). Risk of unauthorized operations or information disclosure.
|
| CVE-2026-46828 |
|
Vulnerability in c (CVE-2026-46828)
vulnerability in c (CVE-2026-46828). Confidential information can be exposed externally.
|
| CVE-2026-46834 |
|
Vulnerability in c (CVE-2026-46834)
vulnerability in c (CVE-2026-46834). Risk of unauthorized operations or information disclosure.
|
| CVE-2026-46835 |
|
Vulnerability in c (CVE-2026-46835)
vulnerability in c (CVE-2026-46835). Risk of unauthorized operations or information disclosure.
|
| CVE-2026-46837 |
|
Privilege Escalation in c (CVE-2026-46837)
vulnerability in c (CVE-2026-46837). Successful exploitation can lead to full system takeover.
|
| CVE-2026-46820 |
|
Vulnerability in c (CVE-2026-46820)
vulnerability in c (CVE-2026-46820). Confidential information can be exposed externally.
|
| CVE-2026-46821 |
|
Vulnerability in c (CVE-2026-46821)
vulnerability in c (CVE-2026-46821). Confidential information can be exposed externally.
|
| CVE-2026-46818 |
|
Vulnerability in c (CVE-2026-46818)
vulnerability in c (CVE-2026-46818). Confidential information can be exposed externally.
|
| CVE-2026-42398 |
|
SSRF (Server-Side Request Forgery) in elk (CVE-2026-42398)
SSRF in elk (CVE-2026-42398). Confidential information can be exposed externally. Mitigation: upgrade to `9.2.8, 9.3.2` or later.
|
| CVE-2026-35277 |
|
Vulnerability in c (CVE-2026-35277)
vulnerability in c (CVE-2026-35277). Confidential information can be exposed externally.
|
| CVE-2026-35266 |
|
Vulnerability in c (CVE-2026-35266)
vulnerability in c (CVE-2026-35266). Confidential information can be exposed externally.
|