VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-27904 | suse_vex | SUSE CVE CVE-2026-27904 | known affected: 531 known not affected: 310 recommended: 170 | 2026-07-28T17:19:33+00:00 | Vulnerability · Source |
| CVE-2026-28780 | suse_vex | SUSE CVE CVE-2026-28780 | known affected: 442 recommended: 202 | 2026-07-28T17:19:31+00:00 | Vulnerability · Source |
| CVE-2026-31402 | suse_vex | SUSE CVE CVE-2026-31402 | first fixed: 2 known affected: 477 recommended: 852 | 2026-07-28T17:19:28+00:00 | Vulnerability · Source |
| CVE-2026-31414 | suse_vex | SUSE CVE CVE-2026-31414 | first fixed: 2 known affected: 648 recommended: 294 | 2026-07-28T17:19:26+00:00 | Vulnerability · Source |
| CVE-2026-31466 | suse_vex | SUSE CVE CVE-2026-31466 | first fixed: 2 known affected: 621 known not affected: 6 recommended: 265 | 2026-07-28T17:19:19+00:00 | Vulnerability · Source |
| CVE-2026-31495 | suse_vex | SUSE CVE CVE-2026-31495 | first fixed: 2 known affected: 649 recommended: 294 | 2026-07-28T17:19:15+00:00 | Vulnerability · Source |
| CVE-2026-31499 | suse_vex | SUSE CVE CVE-2026-31499 | first fixed: 2 known affected: 459 known not affected: 154 recommended: 331 | 2026-07-28T17:19:14+00:00 | Vulnerability · Source |
| CVE-2026-31502 | suse_vex | SUSE CVE CVE-2026-31502 | first fixed: 2 known affected: 613 known not affected: 4 recommended: 329 | 2026-07-28T17:19:12+00:00 | Vulnerability · Source |
| CVE-2026-31555 | suse_vex | SUSE CVE CVE-2026-31555 | first fixed: 2 known affected: 531 known not affected: 98 recommended: 294 | 2026-07-28T17:19:06+00:00 | Vulnerability · Source |
| CVE-2026-31613 | suse_vex | SUSE CVE CVE-2026-31613 | first fixed: 2 known affected: 411 known not affected: 98 recommended: 593 | 2026-07-28T17:19:02+00:00 | Vulnerability · Source |
| CVE-2026-31673 | suse_vex | SUSE CVE CVE-2026-31673 | first fixed: 2 known affected: 608 known not affected: 4 recommended: 331 | 2026-07-28T17:18:58+00:00 | Vulnerability · Source |
| CVE-2026-31674 | suse_vex | SUSE CVE CVE-2026-31674 | first fixed: 2 known affected: 612 recommended: 331 | 2026-07-28T17:18:56+00:00 | Vulnerability · Source |
| CVE-2026-31680 | suse_vex | SUSE CVE CVE-2026-31680 | first fixed: 2 known affected: 608 known not affected: 4 recommended: 331 | 2026-07-28T17:18:54+00:00 | Vulnerability · Source |
| CVE-2026-31684 | suse_vex | SUSE CVE CVE-2026-31684 | first fixed: 2 known affected: 577 known not affected: 67 recommended: 411 | 2026-07-28T17:18:52+00:00 | Vulnerability · Source |
| CVE-2026-31693 | suse_vex | SUSE CVE CVE-2026-31693 | first fixed: 2 known affected: 441 known not affected: 186 recommended: 294 | 2026-07-28T17:18:50+00:00 | Vulnerability · Source |
| CVE-2026-31752 | suse_vex | SUSE CVE CVE-2026-31752 | first fixed: 2 known affected: 555 known not affected: 65 recommended: 294 | 2026-07-28T17:18:47+00:00 | Vulnerability · Source |
| CVE-2026-31771 | suse_vex | SUSE CVE CVE-2026-31771 | first fixed: 2 known affected: 411 known not affected: 93 recommended: 486 | 2026-07-28T17:18:46+00:00 | Vulnerability · Source |
| CVE-2026-34355 | suse_vex | SUSE CVE CVE-2026-34355 | known affected: 445 recommended: 205 | 2026-07-28T17:18:37+00:00 | Vulnerability · Source |
| CVE-2026-35480 | suse_vex | SUSE CVE CVE-2026-35480 | recommended: 2 | 2026-07-28T17:18:32+00:00 | Vulnerability · Source |
| CVE-2026-41608 | suse_vex | SUSE CVE CVE-2026-41608 | No product status | 2026-07-28T17:18:12+00:00 | Vulnerability · Source |
| CVE-2026-42039 | suse_vex | SUSE CVE CVE-2026-42039 | known affected: 126 known not affected: 267 recommended: 1 | 2026-07-28T17:17:56+00:00 | Vulnerability · Source |
| CVE-2026-42536 | suse_vex | SUSE CVE CVE-2026-42536 | known affected: 445 recommended: 205 | 2026-07-28T17:17:46+00:00 | Vulnerability · Source |
| CVE-2026-43024 | suse_vex | SUSE CVE CVE-2026-43024 | first fixed: 2 known affected: 586 known not affected: 4 recommended: 317 | 2026-07-28T17:17:41+00:00 | Vulnerability · Source |
| CVE-2026-43028 | suse_vex | SUSE CVE CVE-2026-43028 | first fixed: 2 known affected: 586 known not affected: 4 recommended: 317 | 2026-07-28T17:17:39+00:00 | Vulnerability · Source |
| CVE-2026-43035 | suse_vex | SUSE CVE CVE-2026-43035 | first fixed: 2 known affected: 572 known not affected: 18 recommended: 317 | 2026-07-28T17:17:37+00:00 | Vulnerability · Source |
| CVE-2026-43036 | suse_vex | SUSE CVE CVE-2026-43036 | first fixed: 2 known affected: 586 known not affected: 4 recommended: 317 | 2026-07-28T17:17:36+00:00 | Vulnerability · Source |
| CVE-2026-43057 | suse_vex | SUSE CVE CVE-2026-43057 | first fixed: 2 known affected: 441 known not affected: 179 recommended: 265 | 2026-07-28T17:17:31+00:00 | Vulnerability · Source |
| CVE-2026-43074 | suse_vex | SUSE CVE CVE-2026-43074 | first fixed: 2 known affected: 411 known not affected: 181 recommended: 408 | 2026-07-28T17:17:29+00:00 | Vulnerability · Source |
| CVE-2026-43080 | suse_vex | SUSE CVE CVE-2026-43080 | first fixed: 2 known affected: 590 recommended: 302 | 2026-07-28T17:17:27+00:00 | Vulnerability · Source |
| CVE-2026-43083 | suse_vex | SUSE CVE CVE-2026-43083 | first fixed: 2 known affected: 441 known not affected: 181 recommended: 294 | 2026-07-28T17:17:26+00:00 | Vulnerability · Source |
| CVE-2026-43092 | suse_vex | SUSE CVE CVE-2026-43092 | first fixed: 2 known affected: 441 known not affected: 181 recommended: 265 | 2026-07-28T17:17:23+00:00 | Vulnerability · Source |
| CVE-2026-43101 | suse_vex | SUSE CVE CVE-2026-43101 | first fixed: 2 known affected: 441 known not affected: 181 recommended: 294 | 2026-07-28T17:17:21+00:00 | Vulnerability · Source |
| CVE-2026-43107 | suse_vex | SUSE CVE CVE-2026-43107 | first fixed: 2 known affected: 555 known not affected: 67 recommended: 265 | 2026-07-28T17:17:20+00:00 | Vulnerability · Source |
| CVE-2026-43112 | suse_vex | SUSE CVE CVE-2026-43112 | first fixed: 2 known affected: 529 known not affected: 63 recommended: 420 | 2026-07-28T17:17:19+00:00 | Vulnerability · Source |
| CVE-2026-43139 | suse_vex | SUSE CVE CVE-2026-43139 | first fixed: 2 known affected: 590 recommended: 302 | 2026-07-28T17:17:14+00:00 | Vulnerability · Source |
| CVE-2026-43157 | suse_vex | SUSE CVE CVE-2026-43157 | first fixed: 2 known affected: 529 known not affected: 93 recommended: 265 | 2026-07-28T17:17:12+00:00 | Vulnerability · Source |
| CVE-2026-43191 | suse_vex | SUSE CVE CVE-2026-43191 | first fixed: 2 known affected: 441 known not affected: 181 recommended: 265 | 2026-07-28T17:17:09+00:00 | Vulnerability · Source |
| CVE-2026-43238 | suse_vex | SUSE CVE CVE-2026-43238 | first fixed: 2 known affected: 441 known not affected: 181 recommended: 265 | 2026-07-28T17:17:04+00:00 | Vulnerability · Source |
| CVE-2026-43248 | suse_vex | SUSE CVE CVE-2026-43248 | first fixed: 2 known affected: 441 known not affected: 181 recommended: 265 | 2026-07-28T17:17:01+00:00 | Vulnerability · Source |
| CVE-2026-43284 | suse_vex | SUSE CVE CVE-2026-43284 | first fixed: 2 known affected: 468 known not affected: 6 recommended: 872 | 2026-07-28T17:16:59+00:00 | Vulnerability · Source |
| CVE-2026-43303 | suse_vex | SUSE CVE CVE-2026-43303 | first fixed: 2 known affected: 489 known not affected: 133 recommended: 348 | 2026-07-28T17:16:56+00:00 | Vulnerability · Source |
| CVE-2026-43336 | suse_vex | SUSE CVE CVE-2026-43336 | first fixed: 2 known affected: 586 known not affected: 4 recommended: 302 | 2026-07-28T17:16:50+00:00 | Vulnerability · Source |
| CVE-2026-43339 | suse_vex | SUSE CVE CVE-2026-43339 | first fixed: 2 known affected: 586 known not affected: 6 recommended: 317 | 2026-07-28T17:16:48+00:00 | Vulnerability · Source |
| CVE-2026-43341 | suse_vex | SUSE CVE CVE-2026-43341 | first fixed: 2 known affected: 441 known not affected: 181 recommended: 336 | 2026-07-28T17:16:46+00:00 | Vulnerability · Source |
| CVE-2026-43405 | suse_vex | SUSE CVE CVE-2026-43405 | first fixed: 2 known affected: 529 known not affected: 93 recommended: 294 | 2026-07-28T17:16:40+00:00 | Vulnerability · Source |
| CVE-2026-43407 | suse_vex | SUSE CVE CVE-2026-43407 | first fixed: 2 known affected: 590 recommended: 331 | 2026-07-28T17:16:39+00:00 | Vulnerability · Source |
| CVE-2026-43468 | suse_vex | SUSE CVE CVE-2026-43468 | first fixed: 2 known affected: 489 known not affected: 133 recommended: 265 | 2026-07-28T17:16:34+00:00 | Vulnerability · Source |
| CVE-2026-43469 | suse_vex | SUSE CVE CVE-2026-43469 | first fixed: 2 known affected: 529 known not affected: 93 recommended: 294 | 2026-07-28T17:16:32+00:00 | Vulnerability · Source |
| CVE-2026-43871 | suse_vex | SUSE CVE CVE-2026-43871 | No product status | 2026-07-28T17:15:57+00:00 | Vulnerability · Source |
| CVE-2026-44172 | suse_vex | SUSE CVE CVE-2026-44172 | known affected: 552 known not affected: 23 recommended: 247 | 2026-07-28T17:15:55+00:00 | Vulnerability · Source |