VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
284659 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2020-28941 | suse_vex | SUSE CVE CVE-2020-28941 | known affected: 300 known not affected: 282 recommended: 957 | 2026-07-25T17:47:32+00:00 | Vulnerability · Source |
| CVE-2020-29363 | suse_vex | SUSE CVE CVE-2020-29363 | known not affected: 287 recommended: 196 | 2026-07-25T17:47:30+00:00 | Vulnerability · Source |
| CVE-2020-29368 | suse_vex | SUSE CVE CVE-2020-29368 | known affected: 419 known not affected: 116 recommended: 1462 | 2026-07-25T17:47:29+00:00 | Vulnerability · Source |
| CVE-2020-29369 | suse_vex | SUSE CVE CVE-2020-29369 | known affected: 302 known not affected: 315 recommended: 968 | 2026-07-25T17:47:27+00:00 | Vulnerability · Source |
| CVE-2020-29371 | suse_vex | SUSE CVE CVE-2020-29371 | known affected: 341 known not affected: 240 recommended: 1407 | 2026-07-25T17:47:25+00:00 | Vulnerability · Source |
| CVE-2020-29372 | suse_vex | SUSE CVE CVE-2020-29372 | known not affected: 401 | 2026-07-25T17:47:24+00:00 | Vulnerability · Source |
| CVE-2020-29385 | suse_vex | SUSE CVE CVE-2020-29385 | known affected: 394 known not affected: 298 recommended: 432 | 2026-07-25T17:47:23+00:00 | Vulnerability · Source |
| CVE-2020-29483 | suse_vex | SUSE CVE CVE-2020-29483 | known affected: 405 recommended: 559 | 2026-07-25T17:47:21+00:00 | Vulnerability · Source |
| CVE-2020-29486 | suse_vex | SUSE CVE CVE-2020-29486 | known not affected: 334 | 2026-07-25T17:47:20+00:00 | Vulnerability · Source |
| CVE-2020-29534 | suse_vex | SUSE CVE CVE-2020-29534 | known not affected: 422 | 2026-07-25T17:47:19+00:00 | Vulnerability · Source |
| CVE-2020-29562 | suse_vex | SUSE CVE CVE-2020-29562 | known affected: 330 known not affected: 62 recommended: 1229 | 2026-07-25T17:47:17+00:00 | Vulnerability · Source |
| CVE-2020-29568 | suse_vex | SUSE CVE CVE-2020-29568 | known affected: 293 known not affected: 126 recommended: 1381 | 2026-07-25T17:47:16+00:00 | Vulnerability · Source |
| CVE-2020-29569 | suse_vex | SUSE CVE CVE-2020-29569 | known affected: 441 known not affected: 129 recommended: 1641 | 2026-07-25T17:47:14+00:00 | Vulnerability · Source |
| CVE-2020-29623 | suse_vex | SUSE CVE CVE-2020-29623 | known affected: 37 known not affected: 10 recommended: 1106 | 2026-07-25T17:47:13+00:00 | Vulnerability · Source |
| CVE-2020-29651 | suse_vex | SUSE CVE CVE-2020-29651 | known affected: 246 recommended: 315 | 2026-07-25T17:47:12+00:00 | Vulnerability · Source |
| CVE-2020-35112 | suse_vex | SUSE CVE CVE-2020-35112 | recommended: 459 | 2026-07-25T17:47:10+00:00 | Vulnerability · Source |
| CVE-2020-35498 | suse_vex | SUSE CVE CVE-2020-35498 | known affected: 1 known not affected: 120 recommended: 668 | 2026-07-25T17:47:09+00:00 | Vulnerability · Source |
| CVE-2020-35499 | suse_vex | SUSE CVE CVE-2020-35499 | known not affected: 384 | 2026-07-25T17:47:07+00:00 | Vulnerability · Source |
| CVE-2020-35504 | suse_vex | SUSE CVE CVE-2020-35504 | known affected: 388 known not affected: 649 recommended: 1081 | 2026-07-25T17:47:06+00:00 | Vulnerability · Source |
| CVE-2020-35519 | suse_vex | SUSE CVE CVE-2020-35519 | known affected: 300 known not affected: 59 recommended: 1525 | 2026-07-25T17:47:04+00:00 | Vulnerability · Source |
| CVE-2020-35527 | suse_vex | SUSE CVE CVE-2020-35527 | known not affected: 245 recommended: 5 | 2026-07-25T17:47:02+00:00 | Vulnerability · Source |
| CVE-2020-35536 | suse_vex | SUSE CVE CVE-2020-35536 | known not affected: 2002 | 2026-07-25T17:47:01+00:00 | Vulnerability · Source |
| CVE-2020-35538 | suse_vex | SUSE CVE CVE-2020-35538 | known affected: 539 known not affected: 67 recommended: 116 | 2026-07-25T17:47:00+00:00 | Vulnerability · Source |
| CVE-2020-36024 | suse_vex | SUSE CVE CVE-2020-36024 | known not affected: 127 recommended: 191 | 2026-07-25T17:46:58+00:00 | Vulnerability · Source |
| CVE-2020-36152 | suse_vex | SUSE CVE CVE-2020-36152 | recommended: 20 | 2026-07-25T17:46:57+00:00 | Vulnerability · Source |
| CVE-2020-36225 | suse_vex | SUSE CVE CVE-2020-36225 | known affected: 298 recommended: 854 | 2026-07-25T17:46:55+00:00 | Vulnerability · Source |
| CVE-2020-36310 | suse_vex | SUSE CVE CVE-2020-36310 | known affected: 300 known not affected: 189 recommended: 1369 | 2026-07-25T17:46:54+00:00 | Vulnerability · Source |
| CVE-2020-36313 | suse_vex | SUSE CVE CVE-2020-36313 | known not affected: 355 | 2026-07-25T17:46:53+00:00 | Vulnerability · Source |
| CVE-2020-36328 | suse_vex | SUSE CVE CVE-2020-36328 | known affected: 394 known not affected: 147 recommended: 160 | 2026-07-25T17:46:51+00:00 | Vulnerability · Source |
| CVE-2020-36385 | suse_vex | SUSE CVE CVE-2020-36385 | known affected: 299 known not affected: 150 recommended: 1772 | 2026-07-25T17:46:49+00:00 | Vulnerability · Source |
| CVE-2020-36516 | suse_vex | SUSE CVE CVE-2020-36516 | known affected: 237 known not affected: 79 recommended: 1785 | 2026-07-25T17:46:47+00:00 | Vulnerability · Source |
| CVE-2020-36557 | suse_vex | SUSE CVE CVE-2020-36557 | known affected: 368 known not affected: 63 recommended: 912 | 2026-07-25T17:46:46+00:00 | Vulnerability · Source |
| CVE-2020-36558 | suse_vex | SUSE CVE CVE-2020-36558 | known affected: 368 known not affected: 51 recommended: 938 | 2026-07-25T17:46:44+00:00 | Vulnerability · Source |
| CVE-2020-36691 | suse_vex | SUSE CVE CVE-2020-36691 | known affected: 385 known not affected: 118 recommended: 452 | 2026-07-25T17:46:43+00:00 | Vulnerability · Source |
| CVE-2020-36766 | suse_vex | SUSE CVE CVE-2020-36766 | known affected: 388 known not affected: 198 recommended: 332 | 2026-07-25T17:46:42+00:00 | Vulnerability · Source |
| CVE-2020-36776 | suse_vex | SUSE CVE CVE-2020-36776 | known not affected: 304 | 2026-07-25T17:46:40+00:00 | Vulnerability · Source |
| CVE-2020-36777 | suse_vex | SUSE CVE CVE-2020-36777 | known affected: 456 known not affected: 147 recommended: 242 | 2026-07-25T17:46:39+00:00 | Vulnerability · Source |
| CVE-2020-36781 | suse_vex | SUSE CVE CVE-2020-36781 | known affected: 388 known not affected: 239 recommended: 91 | 2026-07-25T17:46:38+00:00 | Vulnerability · Source |
| CVE-2020-36783 | suse_vex | SUSE CVE CVE-2020-36783 | known affected: 388 known not affected: 216 recommended: 137 | 2026-07-25T17:46:36+00:00 | Vulnerability · Source |
| CVE-2020-36785 | suse_vex | SUSE CVE CVE-2020-36785 | known not affected: 267 | 2026-07-25T17:46:35+00:00 | Vulnerability · Source |
| CVE-2020-36789 | suse_vex | SUSE CVE CVE-2020-36789 | known affected: 444 known not affected: 272 recommended: 122 | 2026-07-25T17:46:33+00:00 | Vulnerability · Source |
| CVE-2020-36846 | suse_vex | SUSE CVE CVE-2020-36846 | known not affected: 317 recommended: 3 | 2026-07-25T17:46:32+00:00 | Vulnerability · Source |
| CVE-2021-0129 | suse_vex | SUSE CVE CVE-2021-0129 | known affected: 305 known not affected: 110 recommended: 1778 | 2026-07-25T17:46:30+00:00 | Vulnerability · Source |
| CVE-2021-0146 | suse_vex | SUSE CVE CVE-2021-0146 | known affected: 1 recommended: 87 | 2026-07-25T17:46:29+00:00 | Vulnerability · Source |
| CVE-2021-0166 | suse_vex | SUSE CVE CVE-2021-0166 | known not affected: 71 recommended: 130 | 2026-07-25T17:46:28+00:00 | Vulnerability · Source |
| CVE-2021-0170 | suse_vex | SUSE CVE CVE-2021-0170 | known not affected: 71 recommended: 130 | 2026-07-25T17:46:27+00:00 | Vulnerability · Source |
| CVE-2021-0175 | suse_vex | SUSE CVE CVE-2021-0175 | known not affected: 71 recommended: 130 | 2026-07-25T17:46:25+00:00 | Vulnerability · Source |
| CVE-2021-0606 | suse_vex | SUSE CVE CVE-2021-0606 | known not affected: 320 | 2026-07-25T17:46:24+00:00 | Vulnerability · Source |
| CVE-2021-0707 | suse_vex | SUSE CVE CVE-2021-0707 | known affected: 356 known not affected: 331 recommended: 402 | 2026-07-25T17:46:23+00:00 | Vulnerability · Source |
| CVE-2021-0920 | suse_vex | SUSE CVE CVE-2021-0920 | known affected: 396 known not affected: 68 recommended: 1362 | 2026-07-25T17:46:21+00:00 | Vulnerability · Source |