VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-47501 | suse_vex | SUSE CVE CVE-2026-47501 | known affected: 152 recommended: 9 | 2026-10-16T00:21:48+00:00 | Vulnerability · Source |
| CVE-2026-47502 | suse_vex | SUSE CVE CVE-2026-47502 | known affected: 152 recommended: 4 | 2026-10-16T00:21:47+00:00 | Vulnerability · Source |
| CVE-2026-47504 | suse_vex | SUSE CVE CVE-2026-47504 | known affected: 152 recommended: 9 | 2026-10-16T00:21:45+00:00 | Vulnerability · Source |
| CVE-2026-47507 | suse_vex | SUSE CVE CVE-2026-47507 | known affected: 152 recommended: 4 | 2026-10-16T00:21:43+00:00 | Vulnerability · Source |
| CVE-2026-47508 | suse_vex | SUSE CVE CVE-2026-47508 | known affected: 152 recommended: 4 | 2026-10-16T00:21:41+00:00 | Vulnerability · Source |
| CVE-2026-47509 | suse_vex | SUSE CVE CVE-2026-47509 | known affected: 152 recommended: 4 | 2026-10-16T00:21:38+00:00 | Vulnerability · Source |
| CVE-2026-47510 | suse_vex | SUSE CVE CVE-2026-47510 | known affected: 152 recommended: 9 | 2026-10-16T00:21:37+00:00 | Vulnerability · Source |
| CVE-2026-47511 | suse_vex | SUSE CVE CVE-2026-47511 | known affected: 152 recommended: 9 | 2026-10-16T00:21:35+00:00 | Vulnerability · Source |
| CVE-2026-47512 | suse_vex | SUSE CVE CVE-2026-47512 | known affected: 152 recommended: 4 | 2026-10-16T00:21:33+00:00 | Vulnerability · Source |
| CVE-2026-47513 | suse_vex | SUSE CVE CVE-2026-47513 | known affected: 152 recommended: 4 | 2026-10-16T00:21:31+00:00 | Vulnerability · Source |
| CVE-2026-47514 | suse_vex | SUSE CVE CVE-2026-47514 | known affected: 152 recommended: 9 | 2026-10-16T00:21:30+00:00 | Vulnerability · Source |
| CVE-2026-47515 | suse_vex | SUSE CVE CVE-2026-47515 | known affected: 152 recommended: 4 | 2026-10-16T00:21:28+00:00 | Vulnerability · Source |
| CVE-2026-47516 | suse_vex | SUSE CVE CVE-2026-47516 | known affected: 152 recommended: 4 | 2026-10-16T00:21:26+00:00 | Vulnerability · Source |
| CVE-2026-47517 | suse_vex | SUSE CVE CVE-2026-47517 | known affected: 152 recommended: 4 | 2026-10-16T00:21:24+00:00 | Vulnerability · Source |
| CVE-2026-47518 | suse_vex | SUSE CVE CVE-2026-47518 | known affected: 152 recommended: 4 | 2026-10-16T00:21:22+00:00 | Vulnerability · Source |
| CVE-2026-47522 | suse_vex | SUSE CVE CVE-2026-47522 | known affected: 152 recommended: 9 | 2026-10-16T00:21:20+00:00 | Vulnerability · Source |
| CVE-2026-47523 | suse_vex | SUSE CVE CVE-2026-47523 | known affected: 152 recommended: 9 | 2026-10-16T00:21:18+00:00 | Vulnerability · Source |
| CVE-2026-47524 | suse_vex | SUSE CVE CVE-2026-47524 | known affected: 152 recommended: 9 | 2026-10-16T00:21:16+00:00 | Vulnerability · Source |
| CVE-2026-47525 | suse_vex | SUSE CVE CVE-2026-47525 | known affected: 152 recommended: 9 | 2026-10-16T00:21:14+00:00 | Vulnerability · Source |
| CVE-2026-47526 | suse_vex | SUSE CVE CVE-2026-47526 | known affected: 152 recommended: 9 | 2026-10-16T00:21:12+00:00 | Vulnerability · Source |
| CVE-2026-47527 | suse_vex | SUSE CVE CVE-2026-47527 | known affected: 152 recommended: 4 | 2026-10-16T00:21:10+00:00 | Vulnerability · Source |
| CVE-2026-47528 | suse_vex | SUSE CVE CVE-2026-47528 | known affected: 152 recommended: 4 | 2026-10-16T00:21:08+00:00 | Vulnerability · Source |
| CVE-2026-47529 | suse_vex | SUSE CVE CVE-2026-47529 | known affected: 152 recommended: 4 | 2026-10-16T00:21:06+00:00 | Vulnerability · Source |
| CVE-2026-47530 | suse_vex | SUSE CVE CVE-2026-47530 | known affected: 152 recommended: 4 | 2026-10-16T00:21:04+00:00 | Vulnerability · Source |
| CVE-2026-47531 | suse_vex | SUSE CVE CVE-2026-47531 | known affected: 152 recommended: 4 | 2026-10-16T00:21:02+00:00 | Vulnerability · Source |
| CVE-2026-47532 | suse_vex | SUSE CVE CVE-2026-47532 | known affected: 152 recommended: 9 | 2026-10-16T00:20:59+00:00 | Vulnerability · Source |
| CVE-2026-47533 | suse_vex | SUSE CVE CVE-2026-47533 | known affected: 152 recommended: 4 | 2026-10-16T00:20:56+00:00 | Vulnerability · Source |
| CVE-2026-47534 | suse_vex | SUSE CVE CVE-2026-47534 | known affected: 152 recommended: 9 | 2026-10-16T00:20:54+00:00 | Vulnerability · Source |
| CVE-2026-47537 | suse_vex | SUSE CVE CVE-2026-47537 | known affected: 152 recommended: 9 | 2026-10-16T00:20:52+00:00 | Vulnerability · Source |
| CVE-2026-47538 | suse_vex | SUSE CVE CVE-2026-47538 | known affected: 152 recommended: 9 | 2026-10-16T00:20:50+00:00 | Vulnerability · Source |
| CVE-2026-47540 | suse_vex | SUSE CVE CVE-2026-47540 | known affected: 152 recommended: 9 | 2026-10-16T00:20:48+00:00 | Vulnerability · Source |
| CVE-2026-47542 | suse_vex | SUSE CVE CVE-2026-47542 | known affected: 152 recommended: 9 | 2026-10-16T00:20:47+00:00 | Vulnerability · Source |
| CVE-2026-47543 | suse_vex | SUSE CVE CVE-2026-47543 | known affected: 152 recommended: 4 | 2026-10-16T00:20:45+00:00 | Vulnerability · Source |
| CVE-2026-47545 | suse_vex | SUSE CVE CVE-2026-47545 | known affected: 152 recommended: 9 | 2026-10-16T00:20:43+00:00 | Vulnerability · Source |
| CVE-2026-47546 | suse_vex | SUSE CVE CVE-2026-47546 | known affected: 152 recommended: 4 | 2026-10-16T00:20:41+00:00 | Vulnerability · Source |
| CVE-2026-47547 | suse_vex | SUSE CVE CVE-2026-47547 | known affected: 152 recommended: 9 | 2026-10-16T00:20:39+00:00 | Vulnerability · Source |
| CVE-2026-47548 | suse_vex | SUSE CVE CVE-2026-47548 | known affected: 152 recommended: 4 | 2026-10-16T00:20:36+00:00 | Vulnerability · Source |
| CVE-2026-47549 | suse_vex | SUSE CVE CVE-2026-47549 | known affected: 152 recommended: 4 | 2026-10-16T00:20:34+00:00 | Vulnerability · Source |
| CVE-2026-47551 | suse_vex | SUSE CVE CVE-2026-47551 | known affected: 152 recommended: 4 | 2026-10-16T00:20:32+00:00 | Vulnerability · Source |
| CVE-2026-47552 | suse_vex | SUSE CVE CVE-2026-47552 | known affected: 152 recommended: 9 | 2026-10-16T00:20:29+00:00 | Vulnerability · Source |
| CVE-2026-47553 | suse_vex | SUSE CVE CVE-2026-47553 | known affected: 152 recommended: 9 | 2026-10-16T00:20:27+00:00 | Vulnerability · Source |
| CVE-2026-47554 | suse_vex | SUSE CVE CVE-2026-47554 | known affected: 152 recommended: 9 | 2026-10-16T00:20:25+00:00 | Vulnerability · Source |
| CVE-2026-47555 | suse_vex | SUSE CVE CVE-2026-47555 | known affected: 152 recommended: 4 | 2026-10-16T00:20:23+00:00 | Vulnerability · Source |
| CVE-2026-47556 | suse_vex | SUSE CVE CVE-2026-47556 | known affected: 152 recommended: 4 | 2026-10-16T00:20:22+00:00 | Vulnerability · Source |
| CVE-2026-47557 | suse_vex | SUSE CVE CVE-2026-47557 | known affected: 152 recommended: 4 | 2026-10-16T00:20:20+00:00 | Vulnerability · Source |
| CVE-2026-47558 | suse_vex | SUSE CVE CVE-2026-47558 | known affected: 152 recommended: 4 | 2026-10-16T00:20:17+00:00 | Vulnerability · Source |
| CVE-2026-47559 | suse_vex | SUSE CVE CVE-2026-47559 | known affected: 152 recommended: 9 | 2026-10-16T00:20:14+00:00 | Vulnerability · Source |
| CVE-2026-47560 | suse_vex | SUSE CVE CVE-2026-47560 | known affected: 152 recommended: 4 | 2026-10-16T00:20:12+00:00 | Vulnerability · Source |
| CVE-2026-47561 | suse_vex | SUSE CVE CVE-2026-47561 | known affected: 152 recommended: 9 | 2026-10-16T00:20:10+00:00 | Vulnerability · Source |
| CVE-2026-47562 | suse_vex | SUSE CVE CVE-2026-47562 | known affected: 152 recommended: 4 | 2026-10-16T00:20:08+00:00 | Vulnerability · Source |