VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291704 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-23603 | suse_vex | SUSE CVE CVE-2026-23603 | No product status | 2026-08-14T01:02:01+00:00 | Vulnerability · Source |
| CVE-2026-24791 | suse_vex | SUSE CVE CVE-2026-24791 | No product status | 2026-08-14T01:01:59+00:00 | Vulnerability · Source |
| CVE-2026-31669 | suse_vex | SUSE CVE CVE-2026-31669 | first fixed: 2 known affected: 411 known not affected: 98 recommended: 602 | 2026-08-14T01:01:16+00:00 | Vulnerability · Source |
| CVE-2026-32147 | suse_vex | SUSE CVE CVE-2026-32147 | known affected: 84 recommended: 58 | 2026-08-14T01:01:07+00:00 | Vulnerability · Source |
| CVE-2026-42931 | suse_vex | SUSE CVE CVE-2026-42931 | No product status | 2026-08-14T01:00:27+00:00 | Vulnerability · Source |
| CVE-2026-43027 | suse_vex | SUSE CVE CVE-2026-43027 | first fixed: 2 known affected: 437 known not affected: 65 recommended: 774 | 2026-08-14T01:00:22+00:00 | Vulnerability · Source |
| CVE-2026-43128 | suse_vex | SUSE CVE CVE-2026-43128 | first fixed: 2 known affected: 529 known not affected: 93 recommended: 360 | 2026-08-14T01:00:06+00:00 | Vulnerability · Source |
| CVE-2026-43198 | suse_vex | SUSE CVE CVE-2026-43198 | first fixed: 2 known affected: 463 recommended: 651 | 2026-08-14T01:00:00+00:00 | Vulnerability · Source |
| CVE-2026-43329 | suse_vex | SUSE CVE CVE-2026-43329 | first fixed: 2 known affected: 425 known not affected: 79 recommended: 602 | 2026-08-14T00:59:46+00:00 | Vulnerability · Source |
| CVE-2026-46176 | suse_vex | SUSE CVE CVE-2026-46176 | first fixed: 2 known affected: 441 known not affected: 181 recommended: 393 | 2026-08-14T00:58:35+00:00 | Vulnerability · Source |
| CVE-2026-46181 | suse_vex | SUSE CVE CVE-2026-46181 | first fixed: 2 known affected: 586 known not affected: 4 recommended: 421 | 2026-08-14T00:58:32+00:00 | Vulnerability · Source |
| CVE-2026-46227 | suse_vex | SUSE CVE CVE-2026-46227 | first fixed: 2 known affected: 432 known not affected: 67 recommended: 791 | 2026-08-14T00:58:28+00:00 | Vulnerability · Source |
| CVE-2026-46244 | suse_vex | SUSE CVE CVE-2026-46244 | first fixed: 2 known affected: 441 known not affected: 181 recommended: 393 | 2026-08-14T00:58:23+00:00 | Vulnerability · Source |
| CVE-2026-49820 | suse_vex | SUSE CVE CVE-2026-49820 | No product status | 2026-08-14T00:57:43+00:00 | Vulnerability · Source |
| CVE-2026-50105 | suse_vex | SUSE CVE CVE-2026-50105 | No product status | 2026-08-14T00:57:39+00:00 | Vulnerability · Source |
| CVE-2026-54481 | suse_vex | SUSE CVE CVE-2026-54481 | No product status | 2026-08-14T00:56:38+00:00 | Vulnerability · Source |
| CVE-2026-55984 | suse_vex | SUSE CVE CVE-2026-55984 | No product status | 2026-08-14T00:56:24+00:00 | Vulnerability · Source |
| CVE-2026-55987 | suse_vex | SUSE CVE CVE-2026-55987 | No product status | 2026-08-14T00:56:22+00:00 | Vulnerability · Source |
| CVE-2026-56657 | suse_vex | SUSE CVE CVE-2026-56657 | No product status | 2026-08-14T00:56:13+00:00 | Vulnerability · Source |
| CVE-2026-57886 | suse_vex | SUSE CVE CVE-2026-57886 | No product status | 2026-08-14T00:56:07+00:00 | Vulnerability · Source |
| CVE-2026-57894 | suse_vex | SUSE CVE CVE-2026-57894 | No product status | 2026-08-14T00:56:06+00:00 | Vulnerability · Source |
| CVE-2026-57897 | suse_vex | SUSE CVE CVE-2026-57897 | No product status | 2026-08-14T00:56:04+00:00 | Vulnerability · Source |
| CVE-2026-58314 | suse_vex | SUSE CVE CVE-2026-58314 | No product status | 2026-08-14T00:55:56+00:00 | Vulnerability · Source |
| CVE-2026-58416 | suse_vex | SUSE CVE CVE-2026-58416 | No product status | 2026-08-14T00:55:55+00:00 | Vulnerability · Source |
| CVE-2026-58425 | suse_vex | SUSE CVE CVE-2026-58425 | No product status | 2026-08-14T00:55:51+00:00 | Vulnerability · Source |
| CVE-2026-58428 | suse_vex | SUSE CVE CVE-2026-58428 | No product status | 2026-08-14T00:55:48+00:00 | Vulnerability · Source |
| CVE-2026-58429 | suse_vex | SUSE CVE CVE-2026-58429 | No product status | 2026-08-14T00:55:46+00:00 | Vulnerability · Source |
| CVE-2026-58431 | suse_vex | SUSE CVE CVE-2026-58431 | No product status | 2026-08-14T00:55:45+00:00 | Vulnerability · Source |
| CVE-2026-58432 | suse_vex | SUSE CVE CVE-2026-58432 | No product status | 2026-08-14T00:55:44+00:00 | Vulnerability · Source |
| CVE-2026-58435 | suse_vex | SUSE CVE CVE-2026-58435 | No product status | 2026-08-14T00:55:42+00:00 | Vulnerability · Source |
| CVE-2026-58437 | suse_vex | SUSE CVE CVE-2026-58437 | No product status | 2026-08-14T00:55:39+00:00 | Vulnerability · Source |
| CVE-2026-58439 | suse_vex | SUSE CVE CVE-2026-58439 | No product status | 2026-08-14T00:55:36+00:00 | Vulnerability · Source |
| CVE-2026-58440 | suse_vex | SUSE CVE CVE-2026-58440 | No product status | 2026-08-14T00:55:35+00:00 | Vulnerability · Source |
| CVE-2026-58441 | suse_vex | SUSE CVE CVE-2026-58441 | No product status | 2026-08-14T00:55:33+00:00 | Vulnerability · Source |
| CVE-2026-58442 | suse_vex | SUSE CVE CVE-2026-58442 | No product status | 2026-08-14T00:55:32+00:00 | Vulnerability · Source |
| CVE-2026-58443 | suse_vex | SUSE CVE CVE-2026-58443 | No product status | 2026-08-14T00:55:30+00:00 | Vulnerability · Source |
| CVE-2026-58444 | suse_vex | SUSE CVE CVE-2026-58444 | No product status | 2026-08-14T00:55:29+00:00 | Vulnerability · Source |
| CVE-2026-58445 | suse_vex | SUSE CVE CVE-2026-58445 | No product status | 2026-08-14T00:55:27+00:00 | Vulnerability · Source |
| CVE-2026-58507 | suse_vex | SUSE CVE CVE-2026-58507 | No product status | 2026-08-14T00:55:24+00:00 | Vulnerability · Source |
| CVE-2026-58510 | suse_vex | SUSE CVE CVE-2026-58510 | No product status | 2026-08-14T00:55:22+00:00 | Vulnerability · Source |
| CVE-2026-58511 | suse_vex | SUSE CVE CVE-2026-58511 | No product status | 2026-08-14T00:55:21+00:00 | Vulnerability · Source |
| CVE-2026-64173 | suse_vex | SUSE CVE CVE-2026-64173 | known affected: 243 known not affected: 53 | 2026-08-14T00:54:10+00:00 | Vulnerability · Source |
| CVE-2026-64246 | suse_vex | SUSE CVE CVE-2026-64246 | known not affected: 298 recommended: 4 | 2026-08-14T00:54:03+00:00 | Vulnerability · Source |
| CVE-2026-64248 | suse_vex | SUSE CVE CVE-2026-64248 | known not affected: 298 recommended: 4 | 2026-08-14T00:54:01+00:00 | Vulnerability · Source |
| CVE-2026-64270 | suse_vex | SUSE CVE CVE-2026-64270 | known not affected: 298 recommended: 4 | 2026-08-14T00:54:00+00:00 | Vulnerability · Source |
| CVE-2026-64271 | suse_vex | SUSE CVE CVE-2026-64271 | known affected: 4 known not affected: 294 recommended: 4 | 2026-08-14T00:53:58+00:00 | Vulnerability · Source |
| CVE-2026-64272 | suse_vex | SUSE CVE CVE-2026-64272 | known not affected: 298 recommended: 4 | 2026-08-14T00:53:57+00:00 | Vulnerability · Source |
| CVE-2026-64273 | suse_vex | SUSE CVE CVE-2026-64273 | known affected: 4 known not affected: 294 recommended: 4 | 2026-08-14T00:53:55+00:00 | Vulnerability · Source |
| CVE-2026-64624 | suse_vex | SUSE CVE CVE-2026-64624 | known affected: 140 recommended: 11 | 2026-08-14T00:53:45+00:00 | Vulnerability · Source |
| CVE-2026-67289 | suse_vex | SUSE CVE CVE-2026-67289 | known affected: 140 recommended: 11 | 2026-08-14T00:53:42+00:00 | Vulnerability · Source |