Vulnerabilities
Aggregated CVE / GHSA / KEV / OSV — filter by tag and category.
| ID | Title | |
|---|---|---|
| CVE-2026-35314 |
|
Vulnerability in c (CVE-2026-35314)
vulnerability in c (CVE-2026-35314). Risk of unauthorized operations or information disclosure.
|
| CVE-2026-35321 |
|
Vulnerability in c (CVE-2026-35321)
vulnerability in c (CVE-2026-35321). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35316 |
|
Vulnerability in c (CVE-2026-35316)
vulnerability in c (CVE-2026-35316). Successful exploitation can lead to full system takeover.
|
| 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-35320 |
|
Vulnerability in c (CVE-2026-35320)
vulnerability in c (CVE-2026-35320). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35312 |
|
Vulnerability in c (CVE-2026-35312)
vulnerability in c (CVE-2026-35312). 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-35305 |
|
Vulnerability in c (CVE-2026-35305)
vulnerability in c (CVE-2026-35305). Confidential information can be exposed externally.
|
| CVE-2026-35307 |
|
Vulnerability in c (CVE-2026-35307)
vulnerability in c (CVE-2026-35307). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35306 |
|
Vulnerability in c (CVE-2026-35306)
vulnerability in c (CVE-2026-35306). Confidential information can be exposed externally.
|
| CVE-2026-35309 |
|
Vulnerability in c (CVE-2026-35309)
vulnerability in c (CVE-2026-35309). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35308 |
|
Vulnerability in c (CVE-2026-35308)
vulnerability in c (CVE-2026-35308). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35310 |
|
Vulnerability in c (CVE-2026-35310)
vulnerability in c (CVE-2026-35310). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35294 |
|
Vulnerability in c (CVE-2026-35294)
vulnerability in c (CVE-2026-35294). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35284 |
|
Vulnerability in c (CVE-2026-35284)
vulnerability in c (CVE-2026-35284). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35285 |
|
Vulnerability in c (CVE-2026-35285)
vulnerability in c (CVE-2026-35285). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35282 |
|
Vulnerability in c (CVE-2026-35282)
vulnerability in c (CVE-2026-35282). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35298 |
|
Vulnerability in c (CVE-2026-35298)
vulnerability in c (CVE-2026-35298). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35283 |
|
Vulnerability in c (CVE-2026-35283)
vulnerability in c (CVE-2026-35283). 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-35280 |
|
Vulnerability in c (CVE-2026-35280)
vulnerability in c (CVE-2026-35280). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35281 |
|
Vulnerability in c (CVE-2026-35281)
vulnerability in c (CVE-2026-35281). 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-35263 |
|
Vulnerability in c (CVE-2026-35263)
vulnerability in c (CVE-2026-35263). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35268 |
|
Vulnerability in c (CVE-2026-35268)
vulnerability in c (CVE-2026-35268). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35269 |
|
Vulnerability in c (CVE-2026-35269)
vulnerability in c (CVE-2026-35269). Data can be tampered with by attackers.
|
| CVE-2026-35270 |
|
Vulnerability in c (CVE-2026-35270)
vulnerability in c (CVE-2026-35270). Successful exploitation can lead to full system takeover.
|
| CVE-2026-35271 |
|
Vulnerability in c (CVE-2026-35271)
vulnerability in c (CVE-2026-35271). Confidential information can be exposed externally.
|
| CVE-2026-22555 |
|
Authorization Flaw in code.gitea.io/gitea (CVE-2026-22555)
vulnerability in code.gitea.io/gitea (CVE-2026-22555). Confidential information can be exposed externally. Exploitable via `POST /api/v1/repos/{owner}/{repo}/forks`. Mitigation: upgrade to `1.26.0` or later.
|
| CVE-2026-54015 |
|
Vulnerability in open-webui (CVE-2026-54015)
vulnerability in open-webui (CVE-2026-54015). Confidential information can be exposed externally. Exploitable via `GET /api/v1/prompts/id/{prompt_id}/history/diff`. Mitigation: upgrade to `0.9.6` or later.
|
| CVE-2026-54012 |
|
Vulnerability in open-webui (CVE-2026-54012)
vulnerability in open-webui (CVE-2026-54012). Confidential information can be exposed externally. Exploitable via `GET /api/v1/files/{id}/content`. Mitigation: upgrade to `0.9.6` or later.
|
| CVE-2026-54010 |
|
Vulnerability in open-webui (CVE-2026-54010)
vulnerability in open-webui (CVE-2026-54010). Confidential information can be exposed externally. Exploitable via `GET /api/v1/files/{id}/content`. Mitigation: upgrade to `>= 0.9.6` or later.
|
| CVE-2026-54761 |
|
Vulnerability in github.com/traefik/traefik/v3 (CVE-2026-54761)
vulnerability in github.com/traefik/traefik/v3 (CVE-2026-54761). Confidential information can be exposed externally. Mitigation: upgrade to `3.6.21, 3.7.5` or later.
|
| CVE-2026-20706 |
|
Authorization Flaw in code.gitea.io/gitea (CVE-2026-20706)
vulnerability in code.gitea.io/gitea (CVE-2026-20706). Confidential information can be exposed externally. Exploitable via `GET /{owner}/{private-repo}/archive/main.tar.gz`. Mitigation: upgrade to `1.26.2` or later.
|
| CVE-2026-28699 |
|
Vulnerability in code.gitea.io/gitea (CVE-2026-28699)
vulnerability in code.gitea.io/gitea (CVE-2026-28699). Confidential information can be exposed externally. Exploitable via `PATCH /api/v1/user/settings`. Mitigation: upgrade to `1.26.2` or later.
|
| CVE-2026-54305 |
|
Information Disclosure in n8n (CVE-2026-54305)
vulnerability in n8n (CVE-2026-54305). Confidential information can be exposed externally. Exploitable via ``N8N_ENV_FEAT_DYNAMIC_CREDENTIALS``. Mitigation: upgrade to `2.25.7` or later.
|
| CVE-2026-11890 |
|
Vulnerability in devolutions (CVE-2026-11890)
vulnerability in devolutions (CVE-2026-11890). Risk of unauthorized operations or information disclosure.
|
| CVE-2026-52844 |
|
Path Traversal in github.com/caddyserver/caddy/v2 (CVE-2026-52844)
path traversal in github.com/caddyserver/caddy/v2 (CVE-2026-52844). Confidential information can be exposed externally. Exploitable via `GET /private/secret.txt`. Mitigation: upgrade to `2.11.4` or later.
|
| CVE-2026-49411 |
|
Vulnerability in deno (CVE-2026-49411)
vulnerability in deno (CVE-2026-49411). Confidential information can be exposed externally. Exploitable via ``Host``. Mitigation: upgrade to `2.8.0` or later.
|
| CVE-2026-50891 |
|
Vulnerability in github.com/mickael-kerjean/filestash (CVE-2026-50891)
vulnerability in github.com/mickael-kerjean/filestash (CVE-2026-50891). Confidential information can be exposed externally.
|
| CVE-2026-50892 |
|
Vulnerability in nginx (CVE-2026-50892)
vulnerability in nginx (CVE-2026-50892). Confidential information can be exposed externally.
|
| CVE-2026-50881 |
|
Vulnerability in CVE-2026-50881 (CVE-2026-50881)
vulnerability in CVE-2026-50881 (CVE-2026-50881). Confidential information can be exposed externally.
|
| CVE-2026-50884 |
|
Vulnerability in github.com/statping-ng/statping-ng (CVE-2026-50884)
vulnerability in github.com/statping-ng/statping-ng (CVE-2026-50884). Successful exploitation can lead to full system takeover.
|
| CVE-2026-50885 |
|
Vulnerability in CVE-2026-50885 (CVE-2026-50885)
vulnerability in CVE-2026-50885 (CVE-2026-50885). Confidential information can be exposed externally.
|
| CVE-2026-50886 |
|
Vulnerability in grumpydictator/firefly-iii (CVE-2026-50886)
vulnerability in grumpydictator/firefly-iii (CVE-2026-50886). Confidential information can be exposed externally.
|
| CVE-2026-50875 |
|
Vulnerability in CVE-2026-50875 (CVE-2026-50875)
vulnerability in CVE-2026-50875 (CVE-2026-50875). Data can be tampered with by attackers.
|
| CVE-2026-39006 |
|
Vulnerability in org.snmp4j:snmp4j-agent (CVE-2026-39006)
vulnerability in org.snmp4j:snmp4j-agent (CVE-2026-39006). Successful exploitation can lead to full system takeover.
|
| CVE-2026-36933 |
|
Vulnerability in CVE-2026-36933 (CVE-2026-36933)
vulnerability in CVE-2026-36933 (CVE-2026-36933). Successful exploitation can lead to full system takeover.
|
| CVE-2026-5230 |
|
Vulnerability in CVE-2026-5230 (CVE-2026-5230)
vulnerability in CVE-2026-5230 (CVE-2026-5230). Confidential information can be exposed externally.
|