VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104648 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-31770 | suse_vex | SUSE CVE CVE-2026-31770 | known affected: 420 known not affected: 300 recommended: 308 | 2026-10-17T00:41:30+00:00 | Vulnerability · Source |
| CVE-2026-31772 | suse_vex | SUSE CVE CVE-2026-31772 | known affected: 2 known not affected: 383 recommended: 286 | 2026-10-17T00:41:28+00:00 | Vulnerability · Source |
| CVE-2026-31773 | suse_vex | SUSE CVE CVE-2026-31773 | known affected: 641 known not affected: 19 recommended: 345 | 2026-10-17T00:41:26+00:00 | Vulnerability · Source |
| CVE-2026-31774 | suse_vex | SUSE CVE CVE-2026-31774 | known affected: 396 known not affected: 319 recommended: 286 | 2026-10-17T00:41:25+00:00 | Vulnerability · Source |
| CVE-2026-31776 | suse_vex | SUSE CVE CVE-2026-31776 | known affected: 396 known not affected: 322 recommended: 308 | 2026-10-17T00:41:23+00:00 | Vulnerability · Source |
| CVE-2026-31778 | suse_vex | SUSE CVE CVE-2026-31778 | known affected: 645 known not affected: 15 recommended: 345 | 2026-10-17T00:41:22+00:00 | Vulnerability · Source |
| CVE-2026-31779 | suse_vex | SUSE CVE CVE-2026-31779 | known affected: 426 known not affected: 292 recommended: 308 | 2026-10-17T00:41:20+00:00 | Vulnerability · Source |
| CVE-2026-31780 | suse_vex | SUSE CVE CVE-2026-31780 | known affected: 699 known not affected: 21 recommended: 308 | 2026-10-17T00:41:18+00:00 | Vulnerability · Source |
| CVE-2026-31781 | suse_vex | SUSE CVE CVE-2026-31781 | known affected: 641 known not affected: 19 recommended: 331 | 2026-10-17T00:41:16+00:00 | Vulnerability · Source |
| CVE-2026-31786 | suse_vex | SUSE CVE CVE-2026-31786 | known affected: 36 known not affected: 149 recommended: 107 | 2026-10-17T00:41:15+00:00 | Vulnerability · Source |
| CVE-2026-31787 | suse_vex | SUSE CVE CVE-2026-31787 | known affected: 519 known not affected: 4 recommended: 633 | 2026-10-17T00:41:14+00:00 | Vulnerability · Source |
| CVE-2026-34757 | suse_vex | SUSE CVE CVE-2026-34757 | known affected: 594 recommended: 158 | 2026-10-17T00:41:00+00:00 | Vulnerability · Source |
| CVE-2026-39245 | suse_vex | SUSE CVE CVE-2026-39245 | known affected: 95 known not affected: 428 | 2026-10-17T00:40:54+00:00 | Vulnerability · Source |
| CVE-2026-39246 | suse_vex | SUSE CVE CVE-2026-39246 | known affected: 95 known not affected: 438 | 2026-10-17T00:40:52+00:00 | Vulnerability · Source |
| CVE-2026-39881 | suse_vex | SUSE CVE CVE-2026-39881 | known affected: 526 recommended: 132 | 2026-10-17T00:40:47+00:00 | Vulnerability · Source |
| CVE-2026-40170 | suse_vex | SUSE CVE CVE-2026-40170 | known affected: 98 known not affected: 1412 recommended: 275 | 2026-10-17T00:40:44+00:00 | Vulnerability · Source |
| CVE-2026-41506 | suse_vex | SUSE CVE CVE-2026-41506 | known affected: 393 known not affected: 383 recommended: 205 | 2026-10-17T00:40:37+00:00 | Vulnerability · Source |
| CVE-2026-42039 | suse_vex | SUSE CVE CVE-2026-42039 | known affected: 195 known not affected: 313 recommended: 1 | 2026-10-17T00:40:29+00:00 | Vulnerability · Source |
| CVE-2026-42041 | suse_vex | SUSE CVE CVE-2026-42041 | known affected: 204 known not affected: 304 recommended: 1 | 2026-10-17T00:40:28+00:00 | Vulnerability · Source |
| CVE-2026-42307 | suse_vex | SUSE CVE CVE-2026-42307 | known affected: 445 known not affected: 16 recommended: 166 | 2026-10-17T00:40:26+00:00 | Vulnerability · Source |
| CVE-2026-42338 | suse_vex | SUSE CVE CVE-2026-42338 | known affected: 226 recommended: 145 | 2026-10-17T00:40:24+00:00 | Vulnerability · Source |
| CVE-2026-42506 | suse_vex | SUSE CVE CVE-2026-42506 | known affected: 191 known not affected: 613 recommended: 305 | 2026-10-17T00:40:19+00:00 | Vulnerability · Source |
| CVE-2026-43007 | suse_vex | SUSE CVE CVE-2026-43007 | known affected: 426 known not affected: 292 recommended: 308 | 2026-10-17T00:40:14+00:00 | Vulnerability · Source |
| CVE-2026-43009 | suse_vex | SUSE CVE CVE-2026-43009 | known affected: 530 known not affected: 173 recommended: 311 | 2026-10-17T00:40:13+00:00 | Vulnerability · Source |
| CVE-2026-43010 | suse_vex | SUSE CVE CVE-2026-43010 | known affected: 484 known not affected: 219 recommended: 308 | 2026-10-17T00:40:12+00:00 | Vulnerability · Source |
| CVE-2026-43013 | suse_vex | SUSE CVE CVE-2026-43013 | known affected: 484 known not affected: 219 recommended: 310 | 2026-10-17T00:40:10+00:00 | Vulnerability · Source |
| CVE-2026-43014 | suse_vex | SUSE CVE CVE-2026-43014 | known affected: 740 known not affected: 4 recommended: 286 | 2026-10-17T00:40:08+00:00 | Vulnerability · Source |
| CVE-2026-43015 | suse_vex | SUSE CVE CVE-2026-43015 | known affected: 285 known not affected: 65 recommended: 286 | 2026-10-17T00:40:07+00:00 | Vulnerability · Source |
| CVE-2026-43016 | suse_vex | SUSE CVE CVE-2026-43016 | known affected: 513 known not affected: 219 recommended: 308 | 2026-10-17T00:40:05+00:00 | Vulnerability · Source |
| CVE-2026-43017 | suse_vex | SUSE CVE CVE-2026-43017 | known affected: 426 known not affected: 292 recommended: 308 | 2026-10-17T00:40:04+00:00 | Vulnerability · Source |
| CVE-2026-43018 | suse_vex | SUSE CVE CVE-2026-43018 | known affected: 484 known not affected: 234 recommended: 308 | 2026-10-17T00:40:02+00:00 | Vulnerability · Source |
| CVE-2026-43019 | suse_vex | SUSE CVE CVE-2026-43019 | known affected: 426 known not affected: 294 recommended: 308 | 2026-10-17T00:40:01+00:00 | Vulnerability · Source |
| CVE-2026-43020 | suse_vex | SUSE CVE CVE-2026-43020 | known affected: 641 known not affected: 19 recommended: 448 | 2026-10-17T00:39:59+00:00 | Vulnerability · Source |
| CVE-2026-43023 | suse_vex | SUSE CVE CVE-2026-43023 | known affected: 396 known not affected: 294 recommended: 424 | 2026-10-17T00:39:57+00:00 | Vulnerability · Source |
| CVE-2026-43032 | suse_vex | SUSE CVE CVE-2026-43032 | known affected: 530 known not affected: 188 recommended: 308 | 2026-10-17T00:39:53+00:00 | Vulnerability · Source |
| CVE-2026-43034 | suse_vex | SUSE CVE CVE-2026-43034 | known affected: 426 known not affected: 277 recommended: 308 | 2026-10-17T00:39:51+00:00 | Vulnerability · Source |
| CVE-2026-43036 | suse_vex | SUSE CVE CVE-2026-43036 | known affected: 641 known not affected: 4 recommended: 333 | 2026-10-17T00:39:49+00:00 | Vulnerability · Source |
| CVE-2026-43037 | suse_vex | SUSE CVE CVE-2026-43037 | known affected: 497 recommended: 870 | 2026-10-17T00:39:48+00:00 | Vulnerability · Source |
| CVE-2026-43042 | suse_vex | SUSE CVE CVE-2026-43042 | known affected: 382 known not affected: 4 | 2026-10-17T00:39:46+00:00 | Vulnerability · Source |
| CVE-2026-43043 | suse_vex | SUSE CVE CVE-2026-43043 | known affected: 645 known not affected: 15 recommended: 345 | 2026-10-17T00:39:45+00:00 | Vulnerability · Source |
| CVE-2026-43044 | suse_vex | SUSE CVE CVE-2026-43044 | known affected: 396 known not affected: 292 recommended: 342 | 2026-10-17T00:39:43+00:00 | Vulnerability · Source |
| CVE-2026-43047 | suse_vex | SUSE CVE CVE-2026-43047 | known affected: 641 known not affected: 19 recommended: 345 | 2026-10-17T00:39:41+00:00 | Vulnerability · Source |
| CVE-2026-43048 | suse_vex | SUSE CVE CVE-2026-43048 | known affected: 386 | 2026-10-17T00:39:40+00:00 | Vulnerability · Source |
| CVE-2026-43049 | suse_vex | SUSE CVE CVE-2026-43049 | known affected: 580 known not affected: 138 recommended: 310 | 2026-10-17T00:39:38+00:00 | Vulnerability · Source |
| CVE-2026-43050 | suse_vex | SUSE CVE CVE-2026-43050 | known affected: 571 recommended: 503 | 2026-10-17T00:39:37+00:00 | Vulnerability · Source |
| CVE-2026-43051 | suse_vex | SUSE CVE CVE-2026-43051 | known affected: 641 known not affected: 19 recommended: 448 | 2026-10-17T00:39:35+00:00 | Vulnerability · Source |
| CVE-2026-43053 | suse_vex | SUSE CVE CVE-2026-43053 | known affected: 530 known not affected: 175 recommended: 310 | 2026-10-17T00:39:34+00:00 | Vulnerability · Source |
| CVE-2026-43054 | suse_vex | SUSE CVE CVE-2026-43054 | known affected: 530 known not affected: 173 recommended: 310 | 2026-10-17T00:39:32+00:00 | Vulnerability · Source |
| CVE-2026-43055 | suse_vex | SUSE CVE CVE-2026-43055 | known affected: 0 known not affected: 383 recommended: 58 | 2026-10-17T00:39:31+00:00 | Vulnerability · Source |
| CVE-2026-43058 | suse_vex | SUSE CVE CVE-2026-43058 | known affected: 530 known not affected: 190 recommended: 312 | 2026-10-17T00:39:28+00:00 | Vulnerability · Source |