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-43328 | suse_vex | SUSE CVE CVE-2026-43328 | known affected: 667 known not affected: 67 recommended: 308 | 2026-10-17T00:35:06+00:00 | Vulnerability · Source |
| CVE-2026-43329 | suse_vex | SUSE CVE CVE-2026-43329 | known affected: 422 known not affected: 149 recommended: 618 | 2026-10-17T00:35:04+00:00 | Vulnerability · Source |
| CVE-2026-43330 | suse_vex | SUSE CVE CVE-2026-43330 | known affected: 396 known not affected: 294 recommended: 384 | 2026-10-17T00:35:02+00:00 | Vulnerability · Source |
| CVE-2026-43333 | suse_vex | SUSE CVE CVE-2026-43333 | known affected: 530 known not affected: 175 recommended: 310 | 2026-10-17T00:35:00+00:00 | Vulnerability · Source |
| CVE-2026-43334 | suse_vex | SUSE CVE CVE-2026-43334 | known affected: 507 known not affected: 19 recommended: 643 | 2026-10-17T00:34:58+00:00 | Vulnerability · Source |
| CVE-2026-43336 | suse_vex | SUSE CVE CVE-2026-43336 | known affected: 641 known not affected: 4 recommended: 345 | 2026-10-17T00:34:57+00:00 | Vulnerability · Source |
| CVE-2026-43337 | suse_vex | SUSE CVE CVE-2026-43337 | known affected: 396 known not affected: 321 recommended: 286 | 2026-10-17T00:34:55+00:00 | Vulnerability · Source |
| CVE-2026-43338 | suse_vex | SUSE CVE CVE-2026-43338 | known affected: 641 known not affected: 4 recommended: 347 | 2026-10-17T00:34:53+00:00 | Vulnerability · Source |
| CVE-2026-43339 | suse_vex | SUSE CVE CVE-2026-43339 | known affected: 641 known not affected: 6 recommended: 436 | 2026-10-17T00:34:52+00:00 | Vulnerability · Source |
| CVE-2026-43340 | suse_vex | SUSE CVE CVE-2026-43340 | known affected: 396 known not affected: 324 recommended: 308 | 2026-10-17T00:34:50+00:00 | Vulnerability · Source |
| CVE-2026-43341 | suse_vex | SUSE CVE CVE-2026-43341 | known affected: 426 known not affected: 279 recommended: 352 | 2026-10-17T00:34:48+00:00 | Vulnerability · Source |
| CVE-2026-43342 | suse_vex | SUSE CVE CVE-2026-43342 | known affected: 580 known not affected: 140 recommended: 308 | 2026-10-17T00:34:47+00:00 | Vulnerability · Source |
| CVE-2026-43343 | suse_vex | SUSE CVE CVE-2026-43343 | known affected: 701 known not affected: 21 recommended: 308 | 2026-10-17T00:34:45+00:00 | Vulnerability · Source |
| CVE-2026-43345 | suse_vex | SUSE CVE CVE-2026-43345 | known affected: 426 known not affected: 279 recommended: 310 | 2026-10-17T00:34:43+00:00 | Vulnerability · Source |
| CVE-2026-43346 | suse_vex | SUSE CVE CVE-2026-43346 | known affected: 396 known not affected: 321 recommended: 286 | 2026-10-17T00:34:42+00:00 | Vulnerability · Source |
| CVE-2026-43352 | suse_vex | SUSE CVE CVE-2026-43352 | known affected: 559 known not affected: 175 recommended: 308 | 2026-10-17T00:34:39+00:00 | Vulnerability · Source |
| CVE-2026-43353 | suse_vex | SUSE CVE CVE-2026-43353 | known affected: 530 known not affected: 175 recommended: 308 | 2026-10-17T00:34:37+00:00 | Vulnerability · Source |
| CVE-2026-43357 | suse_vex | SUSE CVE CVE-2026-43357 | known affected: 537 known not affected: 79 recommended: 308 | 2026-10-17T00:34:35+00:00 | Vulnerability · Source |
| CVE-2026-43359 | suse_vex | SUSE CVE CVE-2026-43359 | known affected: 641 known not affected: 4 recommended: 347 | 2026-10-17T00:34:33+00:00 | Vulnerability · Source |
| CVE-2026-43360 | suse_vex | SUSE CVE CVE-2026-43360 | known affected: 426 known not affected: 279 recommended: 310 | 2026-10-17T00:34:31+00:00 | Vulnerability · Source |
| CVE-2026-43361 | suse_vex | SUSE CVE CVE-2026-43361 | known affected: 641 known not affected: 4 recommended: 347 | 2026-10-17T00:34:29+00:00 | Vulnerability · Source |
| CVE-2026-43362 | suse_vex | SUSE CVE CVE-2026-43362 | known affected: 507 known not affected: 168 recommended: 341 | 2026-10-17T00:34:27+00:00 | Vulnerability · Source |
| CVE-2026-43363 | suse_vex | SUSE CVE CVE-2026-43363 | known affected: 698 recommended: 275 | 2026-10-17T00:34:26+00:00 | Vulnerability · Source |
| CVE-2026-43365 | suse_vex | SUSE CVE CVE-2026-43365 | known affected: 396 known not affected: 175 recommended: 503 | 2026-10-17T00:34:24+00:00 | Vulnerability · Source |
| CVE-2026-43366 | suse_vex | SUSE CVE CVE-2026-43366 | known affected: 396 known not affected: 221 recommended: 571 | 2026-10-17T00:34:22+00:00 | Vulnerability · Source |
| CVE-2026-43368 | suse_vex | SUSE CVE CVE-2026-43368 | known affected: 2 known not affected: 385 recommended: 286 | 2026-10-17T00:34:20+00:00 | Vulnerability · Source |
| CVE-2026-43370 | suse_vex | SUSE CVE CVE-2026-43370 | known affected: 617 known not affected: 51 recommended: 434 | 2026-10-17T00:34:19+00:00 | Vulnerability · Source |
| CVE-2026-43373 | suse_vex | SUSE CVE CVE-2026-43373 | known affected: 645 known not affected: 6 recommended: 331 | 2026-10-17T00:34:17+00:00 | Vulnerability · Source |
| CVE-2026-43374 | suse_vex | SUSE CVE CVE-2026-43374 | known affected: 2 known not affected: 370 recommended: 203 | 2026-10-17T00:34:16+00:00 | Vulnerability · Source |
| CVE-2026-43380 | suse_vex | SUSE CVE CVE-2026-43380 | known affected: 530 known not affected: 190 recommended: 308 | 2026-10-17T00:34:14+00:00 | Vulnerability · Source |
| CVE-2026-43381 | suse_vex | SUSE CVE CVE-2026-43381 | known affected: 701 known not affected: 21 recommended: 308 | 2026-10-17T00:34:12+00:00 | Vulnerability · Source |
| CVE-2026-43382 | suse_vex | SUSE CVE CVE-2026-43382 | known affected: 426 known not affected: 294 recommended: 308 | 2026-10-17T00:34:11+00:00 | Vulnerability · Source |
| CVE-2026-43383 | suse_vex | SUSE CVE CVE-2026-43383 | known affected: 651 recommended: 331 | 2026-10-17T00:34:09+00:00 | Vulnerability · Source |
| CVE-2026-43386 | suse_vex | SUSE CVE CVE-2026-43386 | known affected: 740 known not affected: 6 recommended: 286 | 2026-10-17T00:34:07+00:00 | Vulnerability · Source |
| CVE-2026-43387 | suse_vex | SUSE CVE CVE-2026-43387 | known affected: 699 known not affected: 23 recommended: 308 | 2026-10-17T00:34:05+00:00 | Vulnerability · Source |
| CVE-2026-43395 | suse_vex | SUSE CVE CVE-2026-43395 | known affected: 396 known not affected: 336 recommended: 286 | 2026-10-17T00:34:03+00:00 | Vulnerability · Source |
| CVE-2026-43397 | suse_vex | SUSE CVE CVE-2026-43397 | known affected: 426 known not affected: 294 recommended: 308 | 2026-10-17T00:34:01+00:00 | Vulnerability · Source |
| CVE-2026-43402 | suse_vex | SUSE CVE CVE-2026-43402 | known affected: 0 known not affected: 385 | 2026-10-17T00:33:59+00:00 | Vulnerability · Source |
| CVE-2026-43405 | suse_vex | SUSE CVE CVE-2026-43405 | known affected: 530 known not affected: 175 recommended: 310 | 2026-10-17T00:33:57+00:00 | Vulnerability · Source |
| CVE-2026-43406 | suse_vex | SUSE CVE CVE-2026-43406 | known affected: 530 known not affected: 175 recommended: 310 | 2026-10-17T00:33:56+00:00 | Vulnerability · Source |
| CVE-2026-43407 | suse_vex | SUSE CVE CVE-2026-43407 | known affected: 645 recommended: 347 | 2026-10-17T00:33:54+00:00 | Vulnerability · Source |
| CVE-2026-43408 | suse_vex | SUSE CVE CVE-2026-43408 | known affected: 18 known not affected: 370 | 2026-10-17T00:33:52+00:00 | Vulnerability · Source |
| CVE-2026-43411 | suse_vex | SUSE CVE CVE-2026-43411 | known affected: 608 known not affected: 97 recommended: 310 | 2026-10-17T00:33:48+00:00 | Vulnerability · Source |
| CVE-2026-43412 | suse_vex | SUSE CVE CVE-2026-43412 | known affected: 426 known not affected: 294 recommended: 308 | 2026-10-17T00:33:46+00:00 | Vulnerability · Source |
| CVE-2026-43413 | suse_vex | SUSE CVE CVE-2026-43413 | known affected: 641 known not affected: 21 recommended: 333 | 2026-10-17T00:33:44+00:00 | Vulnerability · Source |
| CVE-2026-43416 | suse_vex | SUSE CVE CVE-2026-43416 | known affected: 697 recommended: 275 | 2026-10-17T00:33:42+00:00 | Vulnerability · Source |
| CVE-2026-43419 | suse_vex | SUSE CVE CVE-2026-43419 | known affected: 106 known not affected: 221 recommended: 108 | 2026-10-17T00:33:41+00:00 | Vulnerability · Source |
| CVE-2026-43420 | suse_vex | SUSE CVE CVE-2026-43420 | known affected: 596 known not affected: 125 recommended: 105 | 2026-10-17T00:33:39+00:00 | Vulnerability · Source |
| CVE-2026-43425 | suse_vex | SUSE CVE CVE-2026-43425 | known affected: 647 known not affected: 21 recommended: 331 | 2026-10-17T00:33:37+00:00 | Vulnerability · Source |
| CVE-2026-43426 | suse_vex | SUSE CVE CVE-2026-43426 | known affected: 705 known not affected: 17 recommended: 308 | 2026-10-17T00:33:35+00:00 | Vulnerability · Source |