VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
282018 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-42013 | suse_vex | SUSE CVE CVE-2026-42013 | known affected: 466 recommended: 238 | 2026-07-19T17:39:44+00:00 | Vulnerability · Source |
| CVE-2026-42014 | suse_vex | SUSE CVE CVE-2026-42014 | known affected: 466 recommended: 238 | 2026-07-19T17:39:43+00:00 | Vulnerability · Source |
| CVE-2026-42015 | suse_vex | SUSE CVE CVE-2026-42015 | known affected: 466 recommended: 238 | 2026-07-19T17:39:42+00:00 | Vulnerability · Source |
| CVE-2026-42502 | suse_vex | SUSE CVE CVE-2026-42502 | known affected: 372 known not affected: 351 recommended: 266 | 2026-07-19T17:39:39+00:00 | Vulnerability · Source |
| CVE-2026-42506 | suse_vex | SUSE CVE CVE-2026-42506 | known affected: 372 known not affected: 351 recommended: 255 | 2026-07-19T17:39:38+00:00 | Vulnerability · Source |
| CVE-2026-42508 | suse_vex | SUSE CVE CVE-2026-42508 | known affected: 387 known not affected: 254 recommended: 477 | 2026-07-19T17:39:37+00:00 | Vulnerability · Source |
| CVE-2026-42767 | suse_vex | SUSE CVE CVE-2026-42767 | known affected: 413 known not affected: 380 recommended: 138 | 2026-07-19T17:39:35+00:00 | Vulnerability · Source |
| CVE-2026-43009 | suse_vex | SUSE CVE CVE-2026-43009 | first fixed: 2 known affected: 529 known not affected: 89 recommended: 295 | 2026-07-19T17:39:32+00:00 | Vulnerability · Source |
| CVE-2026-43013 | suse_vex | SUSE CVE CVE-2026-43013 | first fixed: 2 known affected: 489 known not affected: 129 recommended: 294 | 2026-07-19T17:39:31+00:00 | Vulnerability · Source |
| CVE-2026-43025 | suse_vex | SUSE CVE CVE-2026-43025 | first fixed: 34 known affected: 468 known not affected: 4 recommended: 601 | 2026-07-19T17:39:29+00:00 | Vulnerability · Source |
| CVE-2026-43026 | suse_vex | SUSE CVE CVE-2026-43026 | first fixed: 2 known affected: 586 known not affected: 4 recommended: 324 | 2026-07-19T17:39:28+00:00 | Vulnerability · Source |
| CVE-2026-43027 | suse_vex | SUSE CVE CVE-2026-43027 | first fixed: 34 known affected: 437 known not affected: 63 recommended: 661 | 2026-07-19T17:39:27+00:00 | Vulnerability · Source |
| CVE-2026-43030 | suse_vex | SUSE CVE CVE-2026-43030 | first fixed: 2 known affected: 529 known not affected: 89 recommended: 294 | 2026-07-19T17:39:25+00:00 | Vulnerability · Source |
| CVE-2026-43037 | suse_vex | SUSE CVE CVE-2026-43037 | first fixed: 34 known affected: 458 recommended: 746 | 2026-07-19T17:39:23+00:00 | Vulnerability · Source |
| CVE-2026-43038 | suse_vex | SUSE CVE CVE-2026-43038 | first fixed: 2 known affected: 468 known not affected: 4 recommended: 579 | 2026-07-19T17:39:22+00:00 | Vulnerability · Source |
| CVE-2026-43040 | suse_vex | SUSE CVE CVE-2026-43040 | first fixed: 2 known affected: 590 recommended: 324 | 2026-07-19T17:39:20+00:00 | Vulnerability · Source |
| CVE-2026-43050 | suse_vex | SUSE CVE CVE-2026-43050 | first fixed: 2 known affected: 502 recommended: 487 | 2026-07-19T17:39:19+00:00 | Vulnerability · Source |
| CVE-2026-43054 | suse_vex | SUSE CVE CVE-2026-43054 | first fixed: 2 known affected: 529 known not affected: 89 recommended: 294 | 2026-07-19T17:39:18+00:00 | Vulnerability · Source |
| CVE-2026-43060 | suse_vex | SUSE CVE CVE-2026-43060 | first fixed: 2 known affected: 555 known not affected: 65 recommended: 295 | 2026-07-19T17:39:16+00:00 | Vulnerability · Source |
| CVE-2026-43065 | suse_vex | SUSE CVE CVE-2026-43065 | first fixed: 2 known affected: 441 known not affected: 179 recommended: 294 | 2026-07-19T17:39:15+00:00 | Vulnerability · Source |
| CVE-2026-43066 | suse_vex | SUSE CVE CVE-2026-43066 | first fixed: 2 known affected: 529 known not affected: 91 recommended: 294 | 2026-07-19T17:39:14+00:00 | Vulnerability · Source |
| CVE-2026-43068 | suse_vex | SUSE CVE CVE-2026-43068 | first fixed: 2 known affected: 616 known not affected: 4 recommended: 294 | 2026-07-19T17:39:13+00:00 | Vulnerability · Source |
| CVE-2026-43088 | suse_vex | SUSE CVE CVE-2026-43088 | first fixed: 2 known affected: 590 recommended: 325 | 2026-07-19T17:39:10+00:00 | Vulnerability · Source |
| CVE-2026-43109 | suse_vex | SUSE CVE CVE-2026-43109 | first fixed: 33 known affected: 424 known not affected: 179 recommended: 294 | 2026-07-19T17:39:07+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-19T17:39:06+00:00 | Vulnerability · Source |
| CVE-2026-43190 | suse_vex | SUSE CVE CVE-2026-43190 | first fixed: 34 known affected: 468 recommended: 732 | 2026-07-19T17:39:03+00:00 | Vulnerability · Source |
| CVE-2026-43205 | suse_vex | SUSE CVE CVE-2026-43205 | first fixed: 80 known affected: 202 known not affected: 91 recommended: 42 | 2026-07-19T17:39:01+00:00 | Vulnerability · Source |
| CVE-2026-43234 | suse_vex | SUSE CVE CVE-2026-43234 | first fixed: 2 known affected: 586 known not affected: 4 recommended: 324 | 2026-07-19T17:39:00+00:00 | Vulnerability · Source |
| CVE-2026-43252 | suse_vex | SUSE CVE CVE-2026-43252 | first fixed: 2 known affected: 441 known not affected: 179 recommended: 294 | 2026-07-19T17:38:58+00:00 | Vulnerability · Source |
| CVE-2026-43265 | suse_vex | SUSE CVE CVE-2026-43265 | first fixed: 2 known affected: 441 known not affected: 179 recommended: 295 | 2026-07-19T17:38:56+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-19T17:38:55+00:00 | Vulnerability · Source |
| CVE-2026-43325 | suse_vex | SUSE CVE CVE-2026-43325 | first fixed: 2 known affected: 441 known not affected: 179 recommended: 294 | 2026-07-19T17:38:53+00:00 | Vulnerability · Source |
| CVE-2026-43328 | suse_vex | SUSE CVE CVE-2026-43328 | first fixed: 2 known affected: 650 known not affected: 37 recommended: 172 | 2026-07-19T17:38:52+00:00 | Vulnerability · Source |
| CVE-2026-43329 | suse_vex | SUSE CVE CVE-2026-43329 | first fixed: 2 known affected: 425 known not affected: 77 recommended: 549 | 2026-07-19T17:38:50+00:00 | Vulnerability · Source |
| CVE-2026-43333 | suse_vex | SUSE CVE CVE-2026-43333 | first fixed: 2 known affected: 529 known not affected: 91 recommended: 294 | 2026-07-19T17:38:49+00:00 | Vulnerability · Source |
| CVE-2026-43338 | suse_vex | SUSE CVE CVE-2026-43338 | first fixed: 2 known affected: 586 known not affected: 4 recommended: 324 | 2026-07-19T17:38:48+00:00 | Vulnerability · Source |
| CVE-2026-43341 | suse_vex | SUSE CVE CVE-2026-43341 | first fixed: 2 known affected: 441 known not affected: 179 recommended: 336 | 2026-07-19T17:38:46+00:00 | Vulnerability · Source |
| CVE-2026-43359 | suse_vex | SUSE CVE CVE-2026-43359 | first fixed: 2 known affected: 586 known not affected: 4 recommended: 324 | 2026-07-19T17:38:44+00:00 | Vulnerability · Source |
| CVE-2026-43360 | suse_vex | SUSE CVE CVE-2026-43360 | first fixed: 2 known affected: 441 known not affected: 179 recommended: 294 | 2026-07-19T17:38:43+00:00 | Vulnerability · Source |
| CVE-2026-43361 | suse_vex | SUSE CVE CVE-2026-43361 | first fixed: 2 known affected: 586 known not affected: 4 recommended: 324 | 2026-07-19T17:38:42+00:00 | Vulnerability · Source |
| CVE-2026-43362 | suse_vex | SUSE CVE CVE-2026-43362 | first fixed: 2 known affected: 468 known not affected: 122 recommended: 325 | 2026-07-19T17:38:41+00:00 | Vulnerability · Source |
| CVE-2026-43365 | suse_vex | SUSE CVE CVE-2026-43365 | first fixed: 2 known affected: 411 known not affected: 91 recommended: 487 | 2026-07-19T17:38:40+00:00 | Vulnerability · Source |
| CVE-2026-43366 | suse_vex | SUSE CVE CVE-2026-43366 | first fixed: 34 known affected: 411 known not affected: 131 recommended: 454 | 2026-07-19T17:38:38+00:00 | Vulnerability · Source |
| CVE-2026-43411 | suse_vex | SUSE CVE CVE-2026-43411 | first fixed: 2 known affected: 569 known not affected: 51 recommended: 294 | 2026-07-19T17:38:36+00:00 | Vulnerability · Source |
| CVE-2026-43455 | suse_vex | SUSE CVE CVE-2026-43455 | first fixed: 2 known affected: 441 known not affected: 179 recommended: 294 | 2026-07-19T17:38:34+00:00 | Vulnerability · Source |
| CVE-2026-43501 | suse_vex | SUSE CVE CVE-2026-43501 | first fixed: 32 known affected: 415 known not affected: 77 recommended: 487 | 2026-07-19T17:38:31+00:00 | Vulnerability · Source |
| CVE-2026-44405 | suse_vex | SUSE CVE CVE-2026-44405 | known affected: 79 recommended: 32 | 2026-07-19T17:38:28+00:00 | Vulnerability · Source |
| CVE-2026-44420 | suse_vex | SUSE CVE CVE-2026-44420 | known affected: 117 recommended: 73 | 2026-07-19T17:38:27+00:00 | Vulnerability · Source |
| CVE-2026-44421 | suse_vex | SUSE CVE CVE-2026-44421 | known affected: 117 recommended: 73 | 2026-07-19T17:38:26+00:00 | Vulnerability · Source |
| CVE-2026-44891 | suse_vex | SUSE CVE CVE-2026-44891 | known affected: 3 known not affected: 42 | 2026-07-19T17:38:22+00:00 | Vulnerability · Source |