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-63991 | suse_vex | SUSE CVE CVE-2026-63991 | known affected: 673 known not affected: 50 recommended: 308 | 2026-10-17T00:15:47+00:00 | Vulnerability · Source |
| CVE-2026-63995 | suse_vex | SUSE CVE CVE-2026-63995 | known affected: 442 known not affected: 296 recommended: 228 | 2026-10-17T00:15:44+00:00 | Vulnerability · Source |
| CVE-2026-63996 | suse_vex | SUSE CVE CVE-2026-63996 | known affected: 442 known not affected: 296 recommended: 228 | 2026-10-17T00:15:42+00:00 | Vulnerability · Source |
| CVE-2026-63997 | suse_vex | SUSE CVE CVE-2026-63997 | known affected: 455 known not affected: 296 recommended: 228 | 2026-10-17T00:15:41+00:00 | Vulnerability · Source |
| CVE-2026-63998 | suse_vex | SUSE CVE CVE-2026-63998 | known affected: 455 known not affected: 296 recommended: 228 | 2026-10-17T00:15:40+00:00 | Vulnerability · Source |
| CVE-2026-63999 | suse_vex | SUSE CVE CVE-2026-63999 | known affected: 485 known not affected: 251 recommended: 252 | 2026-10-17T00:15:38+00:00 | Vulnerability · Source |
| CVE-2026-64004 | suse_vex | SUSE CVE CVE-2026-64004 | known affected: 736 recommended: 252 | 2026-10-17T00:15:35+00:00 | Vulnerability · Source |
| CVE-2026-64007 | suse_vex | SUSE CVE CVE-2026-64007 | known affected: 489 known not affected: 67 recommended: 521 | 2026-10-17T00:15:32+00:00 | Vulnerability · Source |
| CVE-2026-64014 | suse_vex | SUSE CVE CVE-2026-64014 | known affected: 677 known not affected: 59 recommended: 275 | 2026-10-17T00:15:29+00:00 | Vulnerability · Source |
| CVE-2026-64017 | suse_vex | SUSE CVE CVE-2026-64017 | known affected: 171 known not affected: 193 recommended: 286 | 2026-10-17T00:15:27+00:00 | Vulnerability · Source |
| CVE-2026-64021 | suse_vex | SUSE CVE CVE-2026-64021 | known affected: 396 known not affected: 342 recommended: 286 | 2026-10-17T00:15:25+00:00 | Vulnerability · Source |
| CVE-2026-64025 | suse_vex | SUSE CVE CVE-2026-64025 | known affected: 461 known not affected: 245 recommended: 308 | 2026-10-17T00:15:23+00:00 | Vulnerability · Source |
| CVE-2026-64026 | suse_vex | SUSE CVE CVE-2026-64026 | known affected: 278 known not affected: 97 | 2026-10-17T00:15:21+00:00 | Vulnerability · Source |
| CVE-2026-64027 | suse_vex | SUSE CVE CVE-2026-64027 | known affected: 30 known not affected: 345 | 2026-10-17T00:15:20+00:00 | Vulnerability · Source |
| CVE-2026-64033 | suse_vex | SUSE CVE CVE-2026-64033 | known affected: 489 known not affected: 264 recommended: 228 | 2026-10-17T00:15:15+00:00 | Vulnerability · Source |
| CVE-2026-64035 | suse_vex | SUSE CVE CVE-2026-64035 | known affected: 0 known not affected: 376 recommended: 141 | 2026-10-17T00:15:13+00:00 | Vulnerability · Source |
| CVE-2026-64036 | suse_vex | SUSE CVE CVE-2026-64036 | known affected: 124 known not affected: 251 | 2026-10-17T00:15:11+00:00 | Vulnerability · Source |
| CVE-2026-64037 | suse_vex | SUSE CVE CVE-2026-64037 | known affected: 0 known not affected: 376 recommended: 141 | 2026-10-17T00:15:09+00:00 | Vulnerability · Source |
| CVE-2026-64039 | suse_vex | SUSE CVE CVE-2026-64039 | known affected: 396 known not affected: 339 recommended: 252 | 2026-10-17T00:15:06+00:00 | Vulnerability · Source |
| CVE-2026-64051 | suse_vex | SUSE CVE CVE-2026-64051 | known affected: 396 known not affected: 339 recommended: 294 | 2026-10-17T00:15:02+00:00 | Vulnerability · Source |
| CVE-2026-64052 | suse_vex | SUSE CVE CVE-2026-64052 | known affected: 472 known not affected: 251 recommended: 252 | 2026-10-17T00:15:00+00:00 | Vulnerability · Source |
| CVE-2026-64053 | suse_vex | SUSE CVE CVE-2026-64053 | known affected: 32 known not affected: 345 recommended: 283 | 2026-10-17T00:14:59+00:00 | Vulnerability · Source |
| CVE-2026-64055 | suse_vex | SUSE CVE CVE-2026-64055 | known affected: 624 known not affected: 97 recommended: 228 | 2026-10-17T00:14:57+00:00 | Vulnerability · Source |
| CVE-2026-64056 | suse_vex | SUSE CVE CVE-2026-64056 | known affected: 641 known not affected: 97 recommended: 228 | 2026-10-17T00:14:55+00:00 | Vulnerability · Source |
| CVE-2026-64073 | suse_vex | SUSE CVE CVE-2026-64073 | known affected: 589 known not affected: 147 recommended: 252 | 2026-10-17T00:14:53+00:00 | Vulnerability · Source |
| CVE-2026-64076 | suse_vex | SUSE CVE CVE-2026-64076 | known affected: 228 known not affected: 147 | 2026-10-17T00:14:51+00:00 | Vulnerability · Source |
| CVE-2026-64077 | suse_vex | SUSE CVE CVE-2026-64077 | known affected: 124 known not affected: 251 | 2026-10-17T00:14:49+00:00 | Vulnerability · Source |
| CVE-2026-64083 | suse_vex | SUSE CVE CVE-2026-64083 | known affected: 396 known not affected: 339 recommended: 252 | 2026-10-17T00:14:47+00:00 | Vulnerability · Source |
| CVE-2026-64084 | suse_vex | SUSE CVE CVE-2026-64084 | known affected: 396 known not affected: 339 recommended: 252 | 2026-10-17T00:14:45+00:00 | Vulnerability · Source |
| CVE-2026-64085 | suse_vex | SUSE CVE CVE-2026-64085 | known affected: 396 known not affected: 339 recommended: 252 | 2026-10-17T00:14:43+00:00 | Vulnerability · Source |
| CVE-2026-64086 | suse_vex | SUSE CVE CVE-2026-64086 | known affected: 396 known not affected: 339 recommended: 252 | 2026-10-17T00:14:41+00:00 | Vulnerability · Source |
| CVE-2026-64087 | suse_vex | SUSE CVE CVE-2026-64087 | known affected: 530 known not affected: 205 recommended: 252 | 2026-10-17T00:14:39+00:00 | Vulnerability · Source |
| CVE-2026-64088 | suse_vex | SUSE CVE CVE-2026-64088 | known affected: 649 known not affected: 33 recommended: 275 | 2026-10-17T00:14:37+00:00 | Vulnerability · Source |
| CVE-2026-64089 | suse_vex | SUSE CVE CVE-2026-64089 | known affected: 703 known not affected: 33 recommended: 250 | 2026-10-17T00:14:36+00:00 | Vulnerability · Source |
| CVE-2026-64097 | suse_vex | SUSE CVE CVE-2026-64097 | known affected: 671 known not affected: 65 recommended: 275 | 2026-10-17T00:14:34+00:00 | Vulnerability · Source |
| CVE-2026-64099 | suse_vex | SUSE CVE CVE-2026-64099 | known affected: 455 known not affected: 296 recommended: 286 | 2026-10-17T00:14:32+00:00 | Vulnerability · Source |
| CVE-2026-64102 | suse_vex | SUSE CVE CVE-2026-64102 | known affected: 626 known not affected: 97 recommended: 371 | 2026-10-17T00:14:30+00:00 | Vulnerability · Source |
| CVE-2026-64112 | suse_vex | SUSE CVE CVE-2026-64112 | known affected: 730 known not affected: 6 recommended: 252 | 2026-10-17T00:14:26+00:00 | Vulnerability · Source |
| CVE-2026-64113 | suse_vex | SUSE CVE CVE-2026-64113 | known affected: 678 known not affected: 4 recommended: 378 | 2026-10-17T00:14:24+00:00 | Vulnerability · Source |
| CVE-2026-64118 | suse_vex | SUSE CVE CVE-2026-64118 | known affected: 678 known not affected: 4 recommended: 275 | 2026-10-17T00:14:21+00:00 | Vulnerability · Source |
| CVE-2026-64125 | suse_vex | SUSE CVE CVE-2026-64125 | known affected: 732 known not affected: 4 recommended: 252 | 2026-10-17T00:14:19+00:00 | Vulnerability · Source |
| CVE-2026-64126 | suse_vex | SUSE CVE CVE-2026-64126 | known affected: 530 known not affected: 205 recommended: 252 | 2026-10-17T00:14:17+00:00 | Vulnerability · Source |
| CVE-2026-64127 | suse_vex | SUSE CVE CVE-2026-64127 | known affected: 396 known not affected: 354 recommended: 228 | 2026-10-17T00:14:15+00:00 | Vulnerability · Source |
| CVE-2026-64128 | suse_vex | SUSE CVE CVE-2026-64128 | known affected: 484 known not affected: 251 recommended: 252 | 2026-10-17T00:14:14+00:00 | Vulnerability · Source |
| CVE-2026-64131 | suse_vex | SUSE CVE CVE-2026-64131 | known affected: 485 known not affected: 251 recommended: 252 | 2026-10-17T00:14:12+00:00 | Vulnerability · Source |
| CVE-2026-64133 | suse_vex | SUSE CVE CVE-2026-64133 | known affected: 677 known not affected: 59 recommended: 252 | 2026-10-17T00:14:10+00:00 | Vulnerability · Source |
| CVE-2026-64134 | suse_vex | SUSE CVE CVE-2026-64134 | known affected: 396 known not affected: 354 recommended: 228 | 2026-10-17T00:14:09+00:00 | Vulnerability · Source |
| CVE-2026-64135 | suse_vex | SUSE CVE CVE-2026-64135 | known affected: 396 known not affected: 339 recommended: 252 | 2026-10-17T00:14:07+00:00 | Vulnerability · Source |
| CVE-2026-64136 | suse_vex | SUSE CVE CVE-2026-64136 | known affected: 423 known not affected: 326 recommended: 166 | 2026-10-17T00:14:05+00:00 | Vulnerability · Source |
| CVE-2026-64137 | suse_vex | SUSE CVE CVE-2026-64137 | known affected: 530 known not affected: 97 recommended: 393 | 2026-10-17T00:14:03+00:00 | Vulnerability · Source |