VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
288712 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-31741 | suse_vex | SUSE CVE CVE-2026-31741 | known not affected: 291 | 2026-08-03T23:47:33+00:00 | Vulnerability · Source |
| CVE-2026-31775 | suse_vex | SUSE CVE CVE-2026-31775 | known not affected: 291 | 2026-08-03T23:47:24+00:00 | Vulnerability · Source |
| CVE-2026-34933 | suse_vex | SUSE CVE CVE-2026-34933 | known affected: 716 recommended: 306 | 2026-08-03T23:47:07+00:00 | Vulnerability · Source |
| CVE-2026-38974 | suse_vex | SUSE CVE CVE-2026-38974 | recommended: 29 | 2026-08-03T23:46:57+00:00 | Vulnerability · Source |
| CVE-2026-42006 | suse_vex | SUSE CVE CVE-2026-42006 | known affected: 198 known not affected: 32 recommended: 70 | 2026-08-03T23:46:16+00:00 | Vulnerability · Source |
| CVE-2026-42492 | suse_vex | SUSE CVE CVE-2026-42492 | known not affected: 151 recommended: 7 | 2026-08-03T23:46:09+00:00 | Vulnerability · Source |
| CVE-2026-43019 | suse_vex | SUSE CVE CVE-2026-43019 | known affected: 424 known not affected: 196 recommended: 120 | 2026-08-03T23:46:00+00:00 | Vulnerability · Source |
| CVE-2026-43020 | suse_vex | SUSE CVE CVE-2026-43020 | known affected: 569 known not affected: 31 recommended: 238 | 2026-08-03T23:45:58+00:00 | Vulnerability · Source |
| CVE-2026-43023 | suse_vex | SUSE CVE CVE-2026-43023 | known affected: 394 known not affected: 196 recommended: 236 | 2026-08-03T23:45:56+00:00 | Vulnerability · Source |
| CVE-2026-43051 | suse_vex | SUSE CVE CVE-2026-43051 | known affected: 569 known not affected: 31 recommended: 238 | 2026-08-03T23:45:46+00:00 | Vulnerability · Source |
| CVE-2026-43077 | suse_vex | SUSE CVE CVE-2026-43077 | known affected: 446 known not affected: 21 recommended: 447 | 2026-08-03T23:45:37+00:00 | Vulnerability · Source |
| CVE-2026-43095 | suse_vex | SUSE CVE CVE-2026-43095 | known not affected: 293 | 2026-08-03T23:45:32+00:00 | Vulnerability · Source |
| CVE-2026-43096 | suse_vex | SUSE CVE CVE-2026-43096 | known not affected: 295 | 2026-08-03T23:45:30+00:00 | Vulnerability · Source |
| CVE-2026-43097 | suse_vex | SUSE CVE CVE-2026-43097 | known not affected: 295 | 2026-08-03T23:45:29+00:00 | Vulnerability · Source |
| CVE-2026-43108 | suse_vex | SUSE CVE CVE-2026-43108 | known not affected: 293 | 2026-08-03T23:45:26+00:00 | Vulnerability · Source |
| CVE-2026-43110 | suse_vex | SUSE CVE CVE-2026-43110 | known affected: 451 known not affected: 21 recommended: 454 | 2026-08-03T23:45:24+00:00 | Vulnerability · Source |
| CVE-2026-43138 | suse_vex | SUSE CVE CVE-2026-43138 | known not affected: 293 | 2026-08-03T23:45:17+00:00 | Vulnerability · Source |
| CVE-2026-43144 | suse_vex | SUSE CVE CVE-2026-43144 | known not affected: 293 | 2026-08-03T23:45:14+00:00 | Vulnerability · Source |
| CVE-2026-43176 | suse_vex | SUSE CVE CVE-2026-43176 | known not affected: 293 | 2026-08-03T23:45:04+00:00 | Vulnerability · Source |
| CVE-2026-43189 | suse_vex | SUSE CVE CVE-2026-43189 | known affected: 394 known not affected: 238 recommended: 98 | 2026-08-03T23:45:02+00:00 | Vulnerability · Source |
| CVE-2026-43222 | suse_vex | SUSE CVE CVE-2026-43222 | known affected: 394 known not affected: 238 recommended: 98 | 2026-08-03T23:44:53+00:00 | Vulnerability · Source |
| CVE-2026-43229 | suse_vex | SUSE CVE CVE-2026-43229 | known not affected: 293 | 2026-08-03T23:44:51+00:00 | Vulnerability · Source |
| CVE-2026-43247 | suse_vex | SUSE CVE CVE-2026-43247 | known not affected: 293 | 2026-08-03T23:44:45+00:00 | Vulnerability · Source |
| CVE-2026-43250 | suse_vex | SUSE CVE CVE-2026-43250 | known affected: 278 known not affected: 17 | 2026-08-03T23:44:43+00:00 | Vulnerability · Source |
| CVE-2026-43267 | suse_vex | SUSE CVE CVE-2026-43267 | known not affected: 293 | 2026-08-03T23:44:37+00:00 | Vulnerability · Source |
| CVE-2026-43275 | suse_vex | SUSE CVE CVE-2026-43275 | known affected: 291 known not affected: 4 | 2026-08-03T23:44:36+00:00 | Vulnerability · Source |
| CVE-2026-43279 | suse_vex | SUSE CVE CVE-2026-43279 | known affected: 569 known not affected: 31 recommended: 251 | 2026-08-03T23:44:32+00:00 | Vulnerability · Source |
| CVE-2026-43282 | suse_vex | SUSE CVE CVE-2026-43282 | known not affected: 293 | 2026-08-03T23:44:29+00:00 | Vulnerability · Source |
| CVE-2026-43290 | suse_vex | SUSE CVE CVE-2026-43290 | known not affected: 293 | 2026-08-03T23:44:27+00:00 | Vulnerability · Source |
| CVE-2026-43293 | suse_vex | SUSE CVE CVE-2026-43293 | known not affected: 293 | 2026-08-03T23:44:25+00:00 | Vulnerability · Source |
| CVE-2026-43297 | suse_vex | SUSE CVE CVE-2026-43297 | known not affected: 293 | 2026-08-03T23:44:23+00:00 | Vulnerability · Source |
| CVE-2026-43306 | suse_vex | SUSE CVE CVE-2026-43306 | known not affected: 293 | 2026-08-03T23:44:20+00:00 | Vulnerability · Source |
| CVE-2026-43307 | suse_vex | SUSE CVE CVE-2026-43307 | known not affected: 293 | 2026-08-03T23:44:19+00:00 | Vulnerability · Source |
| CVE-2026-43320 | suse_vex | SUSE CVE CVE-2026-43320 | known affected: 424 known not affected: 198 recommended: 120 | 2026-08-03T23:44:14+00:00 | Vulnerability · Source |
| CVE-2026-43323 | suse_vex | SUSE CVE CVE-2026-43323 | known not affected: 293 | 2026-08-03T23:44:13+00:00 | Vulnerability · Source |
| CVE-2026-43344 | suse_vex | SUSE CVE CVE-2026-43344 | known affected: 228 known not affected: 67 | 2026-08-03T23:44:06+00:00 | Vulnerability · Source |
| CVE-2026-43348 | suse_vex | SUSE CVE CVE-2026-43348 | known not affected: 293 recommended: 4 | 2026-08-03T23:44:03+00:00 | Vulnerability · Source |
| CVE-2026-43354 | suse_vex | SUSE CVE CVE-2026-43354 | known not affected: 293 | 2026-08-03T23:44:01+00:00 | Vulnerability · Source |
| CVE-2026-43368 | suse_vex | SUSE CVE CVE-2026-43368 | known not affected: 293 | 2026-08-03T23:43:56+00:00 | Vulnerability · Source |
| CVE-2026-43447 | suse_vex | SUSE CVE CVE-2026-43447 | known not affected: 293 | 2026-08-03T23:43:43+00:00 | Vulnerability · Source |
| CVE-2026-43464 | suse_vex | SUSE CVE CVE-2026-43464 | known not affected: 293 | 2026-08-03T23:43:39+00:00 | Vulnerability · Source |
| CVE-2026-43473 | suse_vex | SUSE CVE CVE-2026-43473 | known affected: 472 known not affected: 150 recommended: 120 | 2026-08-03T23:43:35+00:00 | Vulnerability · Source |
| CVE-2026-43476 | suse_vex | SUSE CVE CVE-2026-43476 | known affected: 512 known not affected: 127 recommended: 98 | 2026-08-03T23:43:32+00:00 | Vulnerability · Source |
| CVE-2026-43478 | suse_vex | SUSE CVE CVE-2026-43478 | known not affected: 272 | 2026-08-03T23:43:31+00:00 | Vulnerability · Source |
| CVE-2026-43480 | suse_vex | SUSE CVE CVE-2026-43480 | known affected: 526 known not affected: 113 recommended: 98 | 2026-08-03T23:43:29+00:00 | Vulnerability · Source |
| CVE-2026-43481 | suse_vex | SUSE CVE CVE-2026-43481 | known not affected: 272 | 2026-08-03T23:43:28+00:00 | Vulnerability · Source |
| CVE-2026-43486 | suse_vex | SUSE CVE CVE-2026-43486 | known not affected: 300 | 2026-08-03T23:43:25+00:00 | Vulnerability · Source |
| CVE-2026-43487 | suse_vex | SUSE CVE CVE-2026-43487 | known not affected: 300 | 2026-08-03T23:43:23+00:00 | Vulnerability · Source |
| CVE-2026-43488 | suse_vex | SUSE CVE CVE-2026-43488 | known affected: 424 known not affected: 215 recommended: 98 | 2026-08-03T23:43:22+00:00 | Vulnerability · Source |
| CVE-2026-43495 | suse_vex | SUSE CVE CVE-2026-43495 | known affected: 97 known not affected: 198 recommended: 4 | 2026-08-03T23:43:19+00:00 | Vulnerability · Source |