VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
303796 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-43444 | suse_vex | SUSE CVE CVE-2026-43444 | known affected: 396 known not affected: 336 recommended: 228 | 2026-10-01T01:17:36+00:00 | Vulnerability · Source |
| CVE-2026-43445 | suse_vex | SUSE CVE CVE-2026-43445 | known affected: 651 recommended: 273 | 2026-10-01T01:17:34+00:00 | Vulnerability · Source |
| CVE-2026-43447 | suse_vex | SUSE CVE CVE-2026-43447 | known not affected: 385 | 2026-10-01T01:17:32+00:00 | Vulnerability · Source |
| CVE-2026-43449 | suse_vex | SUSE CVE CVE-2026-43449 | known affected: 534 known not affected: 117 recommended: 273 | 2026-10-01T01:17:30+00:00 | Vulnerability · Source |
| CVE-2026-43450 | suse_vex | SUSE CVE CVE-2026-43450 | known affected: 647 known not affected: 4 recommended: 356 | 2026-10-01T01:17:29+00:00 | Vulnerability · Source |
| CVE-2026-43451 | suse_vex | SUSE CVE CVE-2026-43451 | known affected: 674 known not affected: 6 recommended: 273 | 2026-10-01T01:17:27+00:00 | Vulnerability · Source |
| CVE-2026-43452 | suse_vex | SUSE CVE CVE-2026-43452 | known affected: 651 recommended: 273 | 2026-10-01T01:17:25+00:00 | Vulnerability · Source |
| CVE-2026-43456 | suse_vex | SUSE CVE CVE-2026-43456 | known affected: 604 recommended: 421 | 2026-10-01T01:17:23+00:00 | Vulnerability · Source |
| CVE-2026-43457 | suse_vex | SUSE CVE CVE-2026-43457 | known affected: 93 known not affected: 279 recommended: 145 | 2026-10-01T01:17:20+00:00 | Vulnerability · Source |
| CVE-2026-43458 | suse_vex | SUSE CVE CVE-2026-43458 | known affected: 372 recommended: 145 | 2026-10-01T01:17:17+00:00 | Vulnerability · Source |
| CVE-2026-43459 | suse_vex | SUSE CVE CVE-2026-43459 | known affected: 580 known not affected: 140 recommended: 250 | 2026-10-01T01:17:15+00:00 | Vulnerability · Source |
| CVE-2026-43464 | suse_vex | SUSE CVE CVE-2026-43464 | known not affected: 385 | 2026-10-01T01:17:13+00:00 | Vulnerability · Source |
| CVE-2026-43465 | suse_vex | SUSE CVE CVE-2026-43465 | known affected: 396 known not affected: 309 recommended: 250 | 2026-10-01T01:17:10+00:00 | Vulnerability · Source |
| CVE-2026-43466 | suse_vex | SUSE CVE CVE-2026-43466 | known affected: 617 known not affected: 34 recommended: 273 | 2026-10-01T01:17:07+00:00 | Vulnerability · Source |
| CVE-2026-43467 | suse_vex | SUSE CVE CVE-2026-43467 | known affected: 396 known not affected: 324 recommended: 250 | 2026-10-01T01:17:05+00:00 | Vulnerability · Source |
| CVE-2026-43468 | suse_vex | SUSE CVE CVE-2026-43468 | known affected: 484 known not affected: 221 recommended: 250 | 2026-10-01T01:17:03+00:00 | Vulnerability · Source |
| CVE-2026-43469 | suse_vex | SUSE CVE CVE-2026-43469 | known affected: 530 known not affected: 175 recommended: 279 | 2026-10-01T01:17:01+00:00 | Vulnerability · Source |
| CVE-2026-43470 | suse_vex | SUSE CVE CVE-2026-43470 | known affected: 484 known not affected: 221 recommended: 279 | 2026-10-01T01:16:59+00:00 | Vulnerability · Source |
| CVE-2026-43471 | suse_vex | SUSE CVE CVE-2026-43471 | known affected: 2 known not affected: 370 recommended: 145 | 2026-10-01T01:16:57+00:00 | Vulnerability · Source |
| CVE-2026-43472 | suse_vex | SUSE CVE CVE-2026-43472 | known affected: 645 known not affected: 15 recommended: 287 | 2026-10-01T01:16:55+00:00 | Vulnerability · Source |
| CVE-2026-43473 | suse_vex | SUSE CVE CVE-2026-43473 | known affected: 484 known not affected: 238 recommended: 250 | 2026-10-01T01:16:53+00:00 | Vulnerability · Source |
| CVE-2026-43475 | suse_vex | SUSE CVE CVE-2026-43475 | known affected: 671 known not affected: 50 recommended: 281 | 2026-10-01T01:16:51+00:00 | Vulnerability · Source |
| CVE-2026-43476 | suse_vex | SUSE CVE CVE-2026-43476 | known affected: 530 known not affected: 192 recommended: 250 | 2026-10-01T01:16:49+00:00 | Vulnerability · Source |
| CVE-2026-43477 | suse_vex | SUSE CVE CVE-2026-43477 | known not affected: 364 | 2026-10-01T01:16:47+00:00 | Vulnerability · Source |
| CVE-2026-43478 | suse_vex | SUSE CVE CVE-2026-43478 | known not affected: 364 | 2026-10-01T01:16:45+00:00 | Vulnerability · Source |
| CVE-2026-43480 | suse_vex | SUSE CVE CVE-2026-43480 | known affected: 556 known not affected: 166 recommended: 250 | 2026-10-01T01:16:43+00:00 | Vulnerability · Source |
| CVE-2026-43481 | suse_vex | SUSE CVE CVE-2026-43481 | known affected: 2 known not affected: 364 recommended: 145 | 2026-10-01T01:16:40+00:00 | Vulnerability · Source |
| CVE-2026-43483 | suse_vex | SUSE CVE CVE-2026-43483 | known affected: 701 known not affected: 21 recommended: 252 | 2026-10-01T01:16:38+00:00 | Vulnerability · Source |
| CVE-2026-43486 | suse_vex | SUSE CVE CVE-2026-43486 | known affected: 2 known not affected: 392 recommended: 145 | 2026-10-01T01:16:35+00:00 | Vulnerability · Source |
| CVE-2026-43487 | suse_vex | SUSE CVE CVE-2026-43487 | known affected: 2 known not affected: 392 recommended: 145 | 2026-10-01T01:16:33+00:00 | Vulnerability · Source |
| CVE-2026-43488 | suse_vex | SUSE CVE CVE-2026-43488 | known affected: 426 known not affected: 296 recommended: 250 | 2026-10-01T01:16:30+00:00 | Vulnerability · Source |
| CVE-2026-43491 | suse_vex | SUSE CVE CVE-2026-43491 | known affected: 530 known not affected: 175 recommended: 283 | 2026-10-01T01:16:28+00:00 | Vulnerability · Source |
| CVE-2026-43492 | suse_vex | SUSE CVE CVE-2026-43492 | known affected: 641 known not affected: 4 recommended: 291 | 2026-10-01T01:16:26+00:00 | Vulnerability · Source |
| CVE-2026-43493 | suse_vex | SUSE CVE CVE-2026-43493 | known affected: 651 known not affected: 17 recommended: 380 | 2026-10-01T01:16:24+00:00 | Vulnerability · Source |
| CVE-2026-43495 | suse_vex | SUSE CVE CVE-2026-43495 | known affected: 93 known not affected: 296 recommended: 149 | 2026-10-01T01:16:22+00:00 | Vulnerability · Source |
| CVE-2026-43496 | suse_vex | SUSE CVE CVE-2026-43496 | known affected: 651 recommended: 277 | 2026-10-01T01:16:20+00:00 | Vulnerability · Source |
| CVE-2026-43501 | suse_vex | SUSE CVE CVE-2026-43501 | known affected: 412 known not affected: 149 recommended: 736 | 2026-10-01T01:16:18+00:00 | Vulnerability · Source |
| CVE-2026-43502 | suse_vex | SUSE CVE CVE-2026-43502 | known affected: 538 known not affected: 125 recommended: 327 | 2026-10-01T01:16:16+00:00 | Vulnerability · Source |
| CVE-2026-44662 | suse_vex | SUSE CVE CVE-2026-44662 | known affected: 1112 known not affected: 870 recommended: 217 | 2026-10-01T01:16:12+00:00 | Vulnerability · Source |
| CVE-2026-45404 | suse_vex | SUSE CVE CVE-2026-45404 | known affected: 2 known not affected: 340 | 2026-10-01T01:16:10+00:00 | Vulnerability · Source |
| CVE-2026-45784 | suse_vex | SUSE CVE CVE-2026-45784 | known affected: 997 known not affected: 974 recommended: 222 | 2026-10-01T01:16:07+00:00 | Vulnerability · Source |
| CVE-2026-45834 | suse_vex | SUSE CVE CVE-2026-45834 | known affected: 701 known not affected: 21 recommended: 254 | 2026-10-01T01:16:05+00:00 | Vulnerability · Source |
| CVE-2026-45835 | suse_vex | SUSE CVE CVE-2026-45835 | known affected: 641 known not affected: 19 recommended: 291 | 2026-10-01T01:16:03+00:00 | Vulnerability · Source |
| CVE-2026-45837 | suse_vex | SUSE CVE CVE-2026-45837 | known affected: 2 known not affected: 370 recommended: 149 | 2026-10-01T01:16:01+00:00 | Vulnerability · Source |
| CVE-2026-45838 | suse_vex | SUSE CVE CVE-2026-45838 | known affected: 671 known not affected: 34 recommended: 254 | 2026-10-01T01:15:59+00:00 | Vulnerability · Source |
| CVE-2026-45839 | suse_vex | SUSE CVE CVE-2026-45839 | known affected: 580 known not affected: 125 recommended: 254 | 2026-10-01T01:15:56+00:00 | Vulnerability · Source |
| CVE-2026-45840 | suse_vex | SUSE CVE CVE-2026-45840 | known affected: 641 known not affected: 4 recommended: 320 | 2026-10-01T01:15:53+00:00 | Vulnerability · Source |
| CVE-2026-45841 | suse_vex | SUSE CVE CVE-2026-45841 | known affected: 645 recommended: 320 | 2026-10-01T01:15:50+00:00 | Vulnerability · Source |
| CVE-2026-45845 | suse_vex | SUSE CVE CVE-2026-45845 | known affected: 2 known not affected: 370 recommended: 149 | 2026-10-01T01:15:47+00:00 | Vulnerability · Source |
| CVE-2026-45848 | suse_vex | SUSE CVE CVE-2026-45848 | known affected: 580 known not affected: 125 recommended: 277 | 2026-10-01T01:15:44+00:00 | Vulnerability · Source |