Vulnerabilities
Aggregated CVE / GHSA / KEV / OSV — filter by tag and category.
| ID | Title | |
|---|---|---|
| CVE-2026-35327 |
|
Vulnerability in c (CVE-2026-35327)
vulnerability in c (CVE-2026-35327). Confidential information can be exposed externally.
|
| CVE-2026-35325 |
|
Vulnerability in c (CVE-2026-35325)
vulnerability in c (CVE-2026-35325). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35324 |
|
Vulnerability in c (CVE-2026-35324)
vulnerability in c (CVE-2026-35324). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35326 |
|
Vulnerability in c (CVE-2026-35326)
vulnerability in c (CVE-2026-35326). Successful exploitation can lead to full system takeover.
|
| CVE-2026-46769 |
|
Vulnerability in c (CVE-2026-46769)
vulnerability in c (CVE-2026-46769). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35315 |
|
Vulnerability in c (CVE-2026-35315)
vulnerability in c (CVE-2026-35315). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35314 |
|
Vulnerability in c (CVE-2026-35314)
vulnerability in c (CVE-2026-35314). Risk of unauthorized operations or information disclosure.
|
| CVE-2026-35322 |
|
Vulnerability in c (CVE-2026-35322)
vulnerability in c (CVE-2026-35322). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35318 |
|
Vulnerability in c (CVE-2026-35318)
vulnerability in c (CVE-2026-35318). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35317 |
|
Vulnerability in c (CVE-2026-35317)
vulnerability in c (CVE-2026-35317). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35302 |
|
Open Redirect in c (CVE-2026-35302)
vulnerability in c (CVE-2026-35302). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35303 |
|
Vulnerability in c (CVE-2026-35303)
vulnerability in c (CVE-2026-35303). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35311 |
|
Vulnerability in c (CVE-2026-35311)
vulnerability in c (CVE-2026-35311). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35299 |
|
Vulnerability in c (CVE-2026-35299)
vulnerability in c (CVE-2026-35299). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35288 |
|
Privilege Escalation in c (CVE-2026-35288)
vulnerability in c (CVE-2026-35288). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35295 |
|
Vulnerability in c (CVE-2026-35295)
vulnerability in c (CVE-2026-35295). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35289 |
|
Vulnerability in c (CVE-2026-35289)
vulnerability in c (CVE-2026-35289). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35275 |
|
Vulnerability in c (CVE-2026-35275)
vulnerability in c (CVE-2026-35275). Confidential information can be exposed externally.
|
| CVE-2026-35276 |
|
Vulnerability in c (CVE-2026-35276)
vulnerability in c (CVE-2026-35276). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35274 |
|
Vulnerability in c (CVE-2026-35274)
vulnerability in c (CVE-2026-35274). Confidential information can be exposed externally.
|
| CVE-2026-35279 |
|
Vulnerability in c (CVE-2026-35279)
vulnerability in c (CVE-2026-35279). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35272 |
|
Privilege Escalation in c (CVE-2026-35272)
vulnerability in c (CVE-2026-35272). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35265 |
|
Vulnerability in c (CVE-2026-35265)
vulnerability in c (CVE-2026-35265). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35262 |
|
Vulnerability in c (CVE-2026-35262)
vulnerability in c (CVE-2026-35262). Confidential information can be exposed externally.
|
| CVE-2026-35271 |
|
Vulnerability in c (CVE-2026-35271)
vulnerability in c (CVE-2026-35271). Confidential information can be exposed externally.
|
| CVE-2026-35269 |
|
Vulnerability in c (CVE-2026-35269)
vulnerability in c (CVE-2026-35269). Data can be tampered with by attackers.
|
| CVE-2026-35258 |
|
Open Redirect in c (CVE-2026-35258)
vulnerability in c (CVE-2026-35258). Confidential information can be exposed externally.
|
| CVE-2026-35259 |
|
Open Redirect in c (CVE-2026-35259)
vulnerability in c (CVE-2026-35259). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35267 |
|
Vulnerability in c (CVE-2026-35267)
vulnerability in c (CVE-2026-35267). Successful exploitation can lead to full system takeover.
|
| CVE-2026-12437 |
|
Use-After-Free in Google chrome (CVE-2026-12437)
vulnerability in Google chrome (CVE-2026-12437). Successful exploitation can lead to full system takeover.
|
| CVE-2026-54304 |
|
Information Disclosure in n8n (CVE-2026-54304)
vulnerability in n8n (CVE-2026-54304). Confidential information can be exposed externally. Exploitable via ``NODES_EXCLUDE``. Mitigation: upgrade to `2.25.7` or later.
|
| CVE-2026-54314 |
|
Vulnerability in n8n (CVE-2026-54314)
vulnerability in n8n (CVE-2026-54314). Risk of unauthorized operations or information disclosure. Exploitable via ``N8N_COMPRESSION_NODE_MAX_ZIP_ENTRIES``. Mitigation: upgrade to `2.24.0` or later.
|
| CVE-2026-54312 |
|
Vulnerability in n8n (CVE-2026-54312)
vulnerability in n8n (CVE-2026-54312). Risk of unauthorized operations or information disclosure. Exploitable via ``Object.prototype``. Mitigation: upgrade to `2.24.0` or later.
|
| CVE-2026-0156 |
|
Vulnerability in cpp (CVE-2026-0156)
vulnerability in cpp (CVE-2026-0156). Risk of unauthorized operations or information disclosure.
|
| CVE-2026-0148 |
|
Vulnerability in cpp (CVE-2026-0148)
vulnerability in cpp (CVE-2026-0148). Successful exploitation can lead to full system takeover.
|
| CVE-2026-0150 |
|
Vulnerability in google (CVE-2026-0150)
vulnerability in google (CVE-2026-0150). Successful exploitation can lead to full system takeover.
|
| CVE-2026-0147 |
|
Vulnerability in c (CVE-2026-0147)
vulnerability in c (CVE-2026-0147). Successful exploitation can lead to full system takeover.
|
| CVE-2026-0160 |
|
Vulnerability in cpp (CVE-2026-0160)
vulnerability in cpp (CVE-2026-0160). Successful exploitation can lead to full system takeover.
|
| CVE-2026-0143 |
|
Use-After-Free in c (CVE-2026-0143)
vulnerability in c (CVE-2026-0143). Successful exploitation can lead to full system takeover.
|
| CVE-2026-0153 |
|
Out-of-Bounds Write in google (CVE-2026-0153)
out-of-bounds write in google (CVE-2026-0153). Successful exploitation can lead to full system takeover.
|
| CVE-2026-0152 |
|
Buffer Overflow in c (CVE-2026-0152)
vulnerability in c (CVE-2026-0152). Successful exploitation can lead to full system takeover.
|
| CVE-2026-0146 |
|
Vulnerability in c (CVE-2026-0146)
vulnerability in c (CVE-2026-0146). Successful exploitation can lead to full system takeover.
|
| CVE-2026-0154 |
|
Vulnerability in google (CVE-2026-0154)
vulnerability in google (CVE-2026-0154). Successful exploitation can lead to full system takeover.
|
| CVE-2026-0161 |
|
Vulnerability in cpp (CVE-2026-0161)
vulnerability in cpp (CVE-2026-0161). Successful exploitation can lead to full system takeover.
|
| CVE-2026-0162 |
|
Vulnerability in cpp (CVE-2026-0162)
vulnerability in cpp (CVE-2026-0162). Successful exploitation can lead to full system takeover.
|
| CVE-2026-0164 |
|
Vulnerability in google (CVE-2026-0164)
vulnerability in google (CVE-2026-0164). Successful exploitation can lead to full system takeover.
|
| CVE-2026-0149 |
|
Vulnerability in google (CVE-2026-0149)
vulnerability in google (CVE-2026-0149). Successful exploitation can lead to full system takeover.
|
| CVE-2026-0151 |
|
Vulnerability in c (CVE-2026-0151)
vulnerability in c (CVE-2026-0151). Successful exploitation can lead to full system takeover.
|
| CVE-2026-0133 |
|
Vulnerability in c (CVE-2026-0133)
vulnerability in c (CVE-2026-0133). Successful exploitation can lead to full system takeover.
|
| CVE-2026-0125 |
|
Use-After-Free in c (CVE-2026-0125)
vulnerability in c (CVE-2026-0125). Successful exploitation can lead to full system takeover.
|