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-64286 | suse_vex | SUSE CVE CVE-2026-64286 | known affected: 485 known not affected: 251 recommended: 256 | 2026-10-17T00:12:19+00:00 | Vulnerability · Source |
| CVE-2026-64287 | suse_vex | SUSE CVE CVE-2026-64287 | known affected: 485 known not affected: 251 recommended: 339 | 2026-10-17T00:12:17+00:00 | Vulnerability · Source |
| CVE-2026-64293 | suse_vex | SUSE CVE CVE-2026-64293 | known affected: 0 known not affected: 376 recommended: 4 | 2026-10-17T00:12:15+00:00 | Vulnerability · Source |
| CVE-2026-64294 | suse_vex | SUSE CVE CVE-2026-64294 | known affected: 589 known not affected: 147 recommended: 256 | 2026-10-17T00:12:14+00:00 | Vulnerability · Source |
| CVE-2026-64296 | suse_vex | SUSE CVE CVE-2026-64296 | known affected: 639 known not affected: 97 recommended: 256 | 2026-10-17T00:12:12+00:00 | Vulnerability · Source |
| CVE-2026-64298 | suse_vex | SUSE CVE CVE-2026-64298 | known affected: 669 recommended: 380 | 2026-10-17T00:12:09+00:00 | Vulnerability · Source |
| CVE-2026-64303 | suse_vex | SUSE CVE CVE-2026-64303 | known affected: 613 known not affected: 134 recommended: 256 | 2026-10-17T00:12:05+00:00 | Vulnerability · Source |
| CVE-2026-64305 | suse_vex | SUSE CVE CVE-2026-64305 | known affected: 673 known not affected: 63 recommended: 256 | 2026-10-17T00:12:02+00:00 | Vulnerability · Source |
| CVE-2026-64306 | suse_vex | SUSE CVE CVE-2026-64306 | known affected: 619 known not affected: 63 recommended: 279 | 2026-10-17T00:12:00+00:00 | Vulnerability · Source |
| CVE-2026-64313 | suse_vex | SUSE CVE CVE-2026-64313 | known affected: 617 known not affected: 65 recommended: 279 | 2026-10-17T00:11:58+00:00 | Vulnerability · Source |
| CVE-2026-64315 | suse_vex | SUSE CVE CVE-2026-64315 | known affected: 676 known not affected: 6 recommended: 279 | 2026-10-17T00:11:56+00:00 | Vulnerability · Source |
| CVE-2026-64316 | suse_vex | SUSE CVE CVE-2026-64316 | known affected: 639 known not affected: 97 recommended: 256 | 2026-10-17T00:11:55+00:00 | Vulnerability · Source |
| CVE-2026-64322 | suse_vex | SUSE CVE CVE-2026-64322 | known affected: 682 recommended: 279 | 2026-10-17T00:11:49+00:00 | Vulnerability · Source |
| CVE-2026-64323 | suse_vex | SUSE CVE CVE-2026-64323 | known affected: 669 recommended: 279 | 2026-10-17T00:11:47+00:00 | Vulnerability · Source |
| CVE-2026-64329 | suse_vex | SUSE CVE CVE-2026-64329 | known affected: 396 known not affected: 339 recommended: 256 | 2026-10-17T00:11:44+00:00 | Vulnerability · Source |
| CVE-2026-64330 | suse_vex | SUSE CVE CVE-2026-64330 | known affected: 617 known not affected: 52 recommended: 335 | 2026-10-17T00:11:42+00:00 | Vulnerability · Source |
| CVE-2026-64331 | suse_vex | SUSE CVE CVE-2026-64331 | known affected: 671 known not affected: 65 recommended: 256 | 2026-10-17T00:11:40+00:00 | Vulnerability · Source |
| CVE-2026-64332 | suse_vex | SUSE CVE CVE-2026-64332 | known affected: 619 known not affected: 63 recommended: 279 | 2026-10-17T00:11:38+00:00 | Vulnerability · Source |
| CVE-2026-64333 | suse_vex | SUSE CVE CVE-2026-64333 | known affected: 623 known not affected: 59 recommended: 279 | 2026-10-17T00:11:37+00:00 | Vulnerability · Source |
| CVE-2026-64334 | suse_vex | SUSE CVE CVE-2026-64334 | known affected: 623 known not affected: 59 recommended: 279 | 2026-10-17T00:11:35+00:00 | Vulnerability · Source |
| CVE-2026-64335 | suse_vex | SUSE CVE CVE-2026-64335 | known affected: 677 known not affected: 71 recommended: 256 | 2026-10-17T00:11:33+00:00 | Vulnerability · Source |
| CVE-2026-64336 | suse_vex | SUSE CVE CVE-2026-64336 | known affected: 530 known not affected: 193 recommended: 312 | 2026-10-17T00:11:31+00:00 | Vulnerability · Source |
| CVE-2026-64337 | suse_vex | SUSE CVE CVE-2026-64337 | known affected: 671 known not affected: 64 recommended: 256 | 2026-10-17T00:11:29+00:00 | Vulnerability · Source |
| CVE-2026-64338 | suse_vex | SUSE CVE CVE-2026-64338 | known affected: 484 known not affected: 268 recommended: 256 | 2026-10-17T00:11:27+00:00 | Vulnerability · Source |
| CVE-2026-64340 | suse_vex | SUSE CVE CVE-2026-64340 | known affected: 530 known not affected: 168 recommended: 279 | 2026-10-17T00:11:26+00:00 | Vulnerability · Source |
| CVE-2026-64341 | suse_vex | SUSE CVE CVE-2026-64341 | known affected: 623 known not affected: 59 recommended: 279 | 2026-10-17T00:11:24+00:00 | Vulnerability · Source |
| CVE-2026-64342 | suse_vex | SUSE CVE CVE-2026-64342 | known affected: 617 known not affected: 76 recommended: 279 | 2026-10-17T00:11:22+00:00 | Vulnerability · Source |
| CVE-2026-64343 | suse_vex | SUSE CVE CVE-2026-64343 | known affected: 623 known not affected: 59 recommended: 279 | 2026-10-17T00:11:20+00:00 | Vulnerability · Source |
| CVE-2026-64345 | suse_vex | SUSE CVE CVE-2026-64345 | known affected: 671 known not affected: 52 recommended: 312 | 2026-10-17T00:11:18+00:00 | Vulnerability · Source |
| CVE-2026-64346 | suse_vex | SUSE CVE CVE-2026-64346 | known affected: 484 known not affected: 251 recommended: 256 | 2026-10-17T00:11:16+00:00 | Vulnerability · Source |
| CVE-2026-64347 | suse_vex | SUSE CVE CVE-2026-64347 | known affected: 673 known not affected: 50 recommended: 312 | 2026-10-17T00:11:15+00:00 | Vulnerability · Source |
| CVE-2026-64348 | suse_vex | SUSE CVE CVE-2026-64348 | known affected: 426 known not affected: 326 recommended: 279 | 2026-10-17T00:11:13+00:00 | Vulnerability · Source |
| CVE-2026-64350 | suse_vex | SUSE CVE CVE-2026-64350 | known affected: 530 known not affected: 205 recommended: 256 | 2026-10-17T00:11:11+00:00 | Vulnerability · Source |
| CVE-2026-64358 | suse_vex | SUSE CVE CVE-2026-64358 | known affected: 396 known not affected: 339 recommended: 256 | 2026-10-17T00:11:08+00:00 | Vulnerability · Source |
| CVE-2026-64362 | suse_vex | SUSE CVE CVE-2026-64362 | known affected: 530 known not affected: 205 recommended: 256 | 2026-10-17T00:11:07+00:00 | Vulnerability · Source |
| CVE-2026-64364 | suse_vex | SUSE CVE CVE-2026-64364 | known affected: 32 known not affected: 347 recommended: 149 | 2026-10-17T00:11:05+00:00 | Vulnerability · Source |
| CVE-2026-64365 | suse_vex | SUSE CVE CVE-2026-64365 | known affected: 426 known not affected: 309 recommended: 256 | 2026-10-17T00:11:03+00:00 | Vulnerability · Source |
| CVE-2026-64366 | suse_vex | SUSE CVE CVE-2026-64366 | known affected: 0 known not affected: 376 recommended: 4 | 2026-10-17T00:11:02+00:00 | Vulnerability · Source |
| CVE-2026-64368 | suse_vex | SUSE CVE CVE-2026-64368 | known affected: 128 known not affected: 251 recommended: 232 | 2026-10-17T00:11:00+00:00 | Vulnerability · Source |
| CVE-2026-64374 | suse_vex | SUSE CVE CVE-2026-64374 | known affected: 373 known not affected: 4 recommended: 4 | 2026-10-17T00:10:55+00:00 | Vulnerability · Source |
| CVE-2026-64375 | suse_vex | SUSE CVE CVE-2026-64375 | known affected: 736 recommended: 279 | 2026-10-17T00:10:54+00:00 | Vulnerability · Source |
| CVE-2026-64376 | suse_vex | SUSE CVE CVE-2026-64376 | known affected: 484 known not affected: 251 recommended: 256 | 2026-10-17T00:10:52+00:00 | Vulnerability · Source |
| CVE-2026-64378 | suse_vex | SUSE CVE CVE-2026-64378 | known affected: 732 known not affected: 4 recommended: 279 | 2026-10-17T00:10:51+00:00 | Vulnerability · Source |
| CVE-2026-64379 | suse_vex | SUSE CVE CVE-2026-64379 | known affected: 371 known not affected: 6 recommended: 107 | 2026-10-17T00:10:49+00:00 | Vulnerability · Source |
| CVE-2026-64380 | suse_vex | SUSE CVE CVE-2026-64380 | known affected: 700 known not affected: 6 recommended: 172 | 2026-10-17T00:10:47+00:00 | Vulnerability · Source |
| CVE-2026-64381 | suse_vex | SUSE CVE CVE-2026-64381 | known affected: 663 known not affected: 6 recommended: 279 | 2026-10-17T00:10:46+00:00 | Vulnerability · Source |
| CVE-2026-64382 | suse_vex | SUSE CVE CVE-2026-64382 | known affected: 472 known not affected: 251 recommended: 339 | 2026-10-17T00:10:44+00:00 | Vulnerability · Source |
| CVE-2026-64401 | suse_vex | SUSE CVE CVE-2026-64401 | known affected: 626 known not affected: 97 recommended: 256 | 2026-10-17T00:10:38+00:00 | Vulnerability · Source |
| CVE-2026-64403 | suse_vex | SUSE CVE CVE-2026-64403 | known affected: 617 known not affected: 136 recommended: 256 | 2026-10-17T00:10:35+00:00 | Vulnerability · Source |
| CVE-2026-64406 | suse_vex | SUSE CVE CVE-2026-64406 | known affected: 530 known not affected: 205 recommended: 256 | 2026-10-17T00:10:32+00:00 | Vulnerability · Source |