VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291942 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-31452 | suse_vex | SUSE CVE CVE-2026-31452 | first fixed: 55 known affected: 458 known not affected: 154 recommended: 275 | 2026-07-27T23:41:26+00:00 | Vulnerability · Source |
| CVE-2026-31469 | suse_vex | SUSE CVE CVE-2026-31469 | first fixed: 55 known affected: 595 recommended: 275 | 2026-07-27T23:41:23+00:00 | Vulnerability · Source |
| CVE-2026-31492 | suse_vex | SUSE CVE CVE-2026-31492 | first fixed: 55 known affected: 546 known not affected: 98 recommended: 238 | 2026-07-27T23:41:21+00:00 | Vulnerability · Source |
| CVE-2026-31503 | suse_vex | SUSE CVE CVE-2026-31503 | first fixed: 2 known affected: 644 recommended: 280 | 2026-07-27T23:41:18+00:00 | Vulnerability · Source |
| CVE-2026-31505 | suse_vex | SUSE CVE CVE-2026-31505 | first fixed: 26 known affected: 411 known not affected: 138 recommended: 525 | 2026-07-27T23:41:17+00:00 | Vulnerability · Source |
| CVE-2026-31533 | suse_vex | SUSE CVE CVE-2026-31533 | first fixed: 26 known affected: 442 known not affected: 67 recommended: 631 | 2026-07-27T23:41:15+00:00 | Vulnerability · Source |
| CVE-2026-31586 | suse_vex | SUSE CVE CVE-2026-31586 | first fixed: 26 known affected: 507 known not affected: 4 recommended: 635 | 2026-07-27T23:41:09+00:00 | Vulnerability · Source |
| CVE-2026-31596 | suse_vex | SUSE CVE CVE-2026-31596 | first fixed: 55 known affected: 612 recommended: 279 | 2026-07-27T23:41:07+00:00 | Vulnerability · Source |
| CVE-2026-31665 | suse_vex | SUSE CVE CVE-2026-31665 | first fixed: 55 known affected: 577 known not affected: 67 recommended: 238 | 2026-07-27T23:41:05+00:00 | Vulnerability · Source |
| CVE-2026-43010 | suse_vex | SUSE CVE CVE-2026-43010 | first fixed: 55 known affected: 489 known not affected: 131 recommended: 209 | 2026-07-27T23:40:02+00:00 | Vulnerability · Source |
| CVE-2026-43022 | suse_vex | SUSE CVE CVE-2026-43022 | first fixed: 55 known affected: 441 known not affected: 179 recommended: 209 | 2026-07-27T23:40:00+00:00 | Vulnerability · Source |
| CVE-2026-43025 | suse_vex | SUSE CVE CVE-2026-43025 | first fixed: 26 known affected: 468 known not affected: 4 recommended: 681 | 2026-07-27T23:39:58+00:00 | Vulnerability · Source |
| CVE-2026-43034 | suse_vex | SUSE CVE CVE-2026-43034 | first fixed: 55 known affected: 441 known not affected: 179 recommended: 209 | 2026-07-27T23:39:54+00:00 | Vulnerability · Source |
| CVE-2026-43037 | suse_vex | SUSE CVE CVE-2026-43037 | first fixed: 26 known affected: 458 recommended: 826 | 2026-07-27T23:39:52+00:00 | Vulnerability · Source |
| CVE-2026-43053 | suse_vex | SUSE CVE CVE-2026-43053 | first fixed: 55 known affected: 529 known not affected: 93 recommended: 238 | 2026-07-27T23:39:50+00:00 | Vulnerability · Source |
| CVE-2026-43081 | suse_vex | SUSE CVE CVE-2026-43081 | first fixed: 55 known affected: 441 known not affected: 181 recommended: 209 | 2026-07-27T23:39:49+00:00 | Vulnerability · Source |
| CVE-2026-43085 | suse_vex | SUSE CVE CVE-2026-43085 | first fixed: 55 known affected: 622 recommended: 209 | 2026-07-27T23:39:47+00:00 | Vulnerability · Source |
| CVE-2026-43086 | suse_vex | SUSE CVE CVE-2026-43086 | first fixed: 55 known affected: 489 known not affected: 133 recommended: 209 | 2026-07-27T23:39:45+00:00 | Vulnerability · Source |
| CVE-2026-43089 | suse_vex | SUSE CVE CVE-2026-43089 | first fixed: 55 known affected: 590 recommended: 246 | 2026-07-27T23:39:44+00:00 | Vulnerability · Source |
| CVE-2026-43093 | suse_vex | SUSE CVE CVE-2026-43093 | first fixed: 55 known affected: 572 known not affected: 20 recommended: 232 | 2026-07-27T23:39:42+00:00 | Vulnerability · Source |
| CVE-2026-43167 | suse_vex | SUSE CVE CVE-2026-43167 | first fixed: 55 known affected: 616 known not affected: 6 recommended: 197 | 2026-07-27T23:39:39+00:00 | Vulnerability · Source |
| CVE-2026-43171 | suse_vex | SUSE CVE CVE-2026-43171 | first fixed: 55 known affected: 543 known not affected: 79 recommended: 238 | 2026-07-27T23:39:37+00:00 | Vulnerability · Source |
| CVE-2026-43190 | suse_vex | SUSE CVE CVE-2026-43190 | first fixed: 26 known affected: 468 recommended: 812 | 2026-07-27T23:39:35+00:00 | Vulnerability · Source |
| CVE-2026-43194 | suse_vex | SUSE CVE CVE-2026-43194 | first fixed: 55 known affected: 618 known not affected: 4 recommended: 197 | 2026-07-27T23:39:34+00:00 | Vulnerability · Source |
| CVE-2026-43199 | suse_vex | SUSE CVE CVE-2026-43199 | first fixed: 55 known affected: 441 known not affected: 181 recommended: 197 | 2026-07-27T23:39:32+00:00 | Vulnerability · Source |
| CVE-2026-43205 | suse_vex | SUSE CVE CVE-2026-43205 | first fixed: 55 known affected: 529 known not affected: 93 recommended: 239 | 2026-07-27T23:39:29+00:00 | Vulnerability · Source |
| CVE-2026-43345 | suse_vex | SUSE CVE CVE-2026-43345 | first fixed: 55 known affected: 441 known not affected: 181 recommended: 238 | 2026-07-27T23:39:24+00:00 | Vulnerability · Source |
| CVE-2026-43366 | suse_vex | SUSE CVE CVE-2026-43366 | first fixed: 26 known affected: 411 known not affected: 133 recommended: 527 | 2026-07-27T23:39:22+00:00 | Vulnerability · Source |
| CVE-2026-43406 | suse_vex | SUSE CVE CVE-2026-43406 | first fixed: 55 known affected: 529 known not affected: 93 recommended: 238 | 2026-07-27T23:39:18+00:00 | Vulnerability · Source |
| CVE-2026-43456 | suse_vex | SUSE CVE CVE-2026-43456 | first fixed: 55 known affected: 590 recommended: 273 | 2026-07-27T23:39:08+00:00 | Vulnerability · Source |
| CVE-2026-43465 | suse_vex | SUSE CVE CVE-2026-43465 | first fixed: 55 known affected: 411 known not affected: 211 recommended: 197 | 2026-07-27T23:39:06+00:00 | Vulnerability · Source |
| CVE-2026-43494 | suse_vex | SUSE CVE CVE-2026-43494 | first fixed: 26 known affected: 400 known not affected: 67 recommended: 651 | 2026-07-27T23:39:02+00:00 | Vulnerability · Source |
| CVE-2026-43896 | suse_vex | SUSE CVE CVE-2026-43896 | known affected: 85 recommended: 17 | 2026-07-27T23:38:27+00:00 | Vulnerability · Source |
| CVE-2026-44740 | suse_vex | SUSE CVE CVE-2026-44740 | known affected: 449 known not affected: 233 recommended: 179 | 2026-07-27T23:38:22+00:00 | Vulnerability · Source |
| CVE-2026-44777 | suse_vex | SUSE CVE CVE-2026-44777 | known affected: 85 recommended: 17 | 2026-07-27T23:38:21+00:00 | Vulnerability · Source |
| CVE-2026-45838 | suse_vex | SUSE CVE CVE-2026-45838 | first fixed: 55 known affected: 602 known not affected: 20 recommended: 213 | 2026-07-27T23:38:16+00:00 | Vulnerability · Source |
| CVE-2026-45970 | suse_vex | SUSE CVE CVE-2026-45970 | first fixed: 30 known affected: 463 recommended: 717 | 2026-07-27T23:38:11+00:00 | Vulnerability · Source |
| CVE-2026-45983 | suse_vex | SUSE CVE CVE-2026-45983 | first fixed: 55 known affected: 590 recommended: 275 | 2026-07-27T23:38:10+00:00 | Vulnerability · Source |
| CVE-2026-46069 | suse_vex | SUSE CVE CVE-2026-46069 | first fixed: 55 known affected: 586 known not affected: 4 recommended: 250 | 2026-07-27T23:38:03+00:00 | Vulnerability · Source |
| CVE-2026-46071 | suse_vex | SUSE CVE CVE-2026-46071 | first fixed: 55 known affected: 411 known not affected: 181 recommended: 271 | 2026-07-27T23:38:01+00:00 | Vulnerability · Source |
| CVE-2026-46124 | suse_vex | SUSE CVE CVE-2026-46124 | first fixed: 55 known affected: 441 known not affected: 149 recommended: 277 | 2026-07-27T23:37:52+00:00 | Vulnerability · Source |
| CVE-2026-46253 | suse_vex | SUSE CVE CVE-2026-46253 | first fixed: 55 known affected: 468 known not affected: 4 recommended: 438 | 2026-07-27T23:37:39+00:00 | Vulnerability · Source |
| CVE-2026-46266 | suse_vex | SUSE CVE CVE-2026-46266 | first fixed: 55 known affected: 468 recommended: 453 | 2026-07-27T23:37:38+00:00 | Vulnerability · Source |
| CVE-2026-46289 | suse_vex | SUSE CVE CVE-2026-46289 | first fixed: 55 known affected: 411 known not affected: 181 recommended: 244 | 2026-07-27T23:37:36+00:00 | Vulnerability · Source |
| CVE-2026-46291 | suse_vex | SUSE CVE CVE-2026-46291 | first fixed: 55 known affected: 618 known not affected: 4 recommended: 240 | 2026-07-27T23:37:35+00:00 | Vulnerability · Source |
| CVE-2026-49839 | suse_vex | SUSE CVE CVE-2026-49839 | known affected: 85 recommended: 14 | 2026-07-27T23:37:23+00:00 | Vulnerability · Source |
| CVE-2026-49854 | suse_vex | SUSE CVE CVE-2026-49854 | first fixed: 2 known affected: 712 known not affected: 11 recommended: 47 | 2026-07-27T23:37:20+00:00 | Vulnerability · Source |
| CVE-2026-50721 | suse_vex | SUSE CVE CVE-2026-50721 | recommended: 4 | 2026-07-27T23:37:16+00:00 | Vulnerability · Source |
| CVE-2026-50722 | suse_vex | SUSE CVE CVE-2026-50722 | recommended: 4 | 2026-07-27T23:37:15+00:00 | Vulnerability · Source |
| CVE-2026-52908 | suse_vex | SUSE CVE CVE-2026-52908 | first fixed: 55 known affected: 441 known not affected: 181 recommended: 209 | 2026-07-27T23:37:07+00:00 | Vulnerability · Source |