VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2020-27837 | suse_vex | SUSE CVE CVE-2020-27837 | known affected: 239 known not affected: 315 recommended: 213 | 2026-07-26T16:53:55+00:00 | Vulnerability · Source |
| CVE-2020-35506 | suse_vex | SUSE CVE CVE-2020-35506 | known affected: 388 known not affected: 649 recommended: 1081 | 2026-07-26T16:53:52+00:00 | Vulnerability · Source |
| CVE-2020-35513 | suse_vex | SUSE CVE CVE-2020-35513 | known not affected: 409 recommended: 13 | 2026-07-26T16:53:48+00:00 | Vulnerability · Source |
| CVE-2020-35517 | suse_vex | SUSE CVE CVE-2020-35517 | known not affected: 1180 | 2026-07-26T16:53:47+00:00 | Vulnerability · Source |
| CVE-2020-36221 | suse_vex | SUSE CVE CVE-2020-36221 | known affected: 298 recommended: 854 | 2026-07-26T16:53:45+00:00 | Vulnerability · Source |
| CVE-2020-36775 | suse_vex | SUSE CVE CVE-2020-36775 | known not affected: 304 | 2026-07-26T16:53:43+00:00 | Vulnerability · Source |
| CVE-2020-37127 | suse_vex | SUSE CVE CVE-2020-37127 | known not affected: 36 | 2026-07-26T16:53:42+00:00 | Vulnerability · Source |
| CVE-2021-0938 | suse_vex | SUSE CVE CVE-2021-0938 | known not affected: 316 | 2026-07-26T16:53:39+00:00 | Vulnerability · Source |
| CVE-2021-3658 | suse_vex | SUSE CVE CVE-2021-3658 | known affected: 6 known not affected: 42 recommended: 109 | 2026-07-26T16:53:31+00:00 | Vulnerability · Source |
| CVE-2021-4166 | suse_vex | SUSE CVE CVE-2021-4166 | known affected: 363 known not affected: 7 recommended: 366 | 2026-07-26T16:53:27+00:00 | Vulnerability · Source |
| CVE-2021-26376 | suse_vex | SUSE CVE CVE-2021-26376 | known affected: 11 known not affected: 1 recommended: 1292 | 2026-07-26T16:53:16+00:00 | Vulnerability · Source |
| CVE-2021-28662 | suse_vex | SUSE CVE CVE-2021-28662 | known affected: 394 known not affected: 72 recommended: 52 | 2026-07-26T16:53:14+00:00 | Vulnerability · Source |
| CVE-2021-28703 | suse_vex | SUSE CVE CVE-2021-28703 | known not affected: 357 recommended: 8 | 2026-07-26T16:53:12+00:00 | Vulnerability · Source |
| CVE-2021-29964 | suse_vex | SUSE CVE CVE-2021-29964 | known affected: 46 recommended: 438 | 2026-07-26T16:53:10+00:00 | Vulnerability · Source |
| CVE-2021-29967 | suse_vex | SUSE CVE CVE-2021-29967 | known affected: 46 recommended: 442 | 2026-07-26T16:53:09+00:00 | Vulnerability · Source |
| CVE-2021-29989 | suse_vex | SUSE CVE CVE-2021-29989 | known affected: 1 known not affected: 24 recommended: 522 | 2026-07-26T16:53:07+00:00 | Vulnerability · Source |
| CVE-2021-31440 | suse_vex | SUSE CVE CVE-2021-31440 | known affected: 2 known not affected: 328 recommended: 29 | 2026-07-26T16:53:03+00:00 | Vulnerability · Source |
| CVE-2021-34403 | suse_vex | SUSE CVE CVE-2021-34403 | known not affected: 419 | 2026-07-26T16:52:59+00:00 | Vulnerability · Source |
| CVE-2021-35331 | suse_vex | SUSE CVE CVE-2021-35331 | recommended: 216 | 2026-07-26T16:52:58+00:00 | Vulnerability · Source |
| CVE-2021-35465 | suse_vex | SUSE CVE CVE-2021-35465 | known affected: 2 known not affected: 2537 | 2026-07-26T16:52:56+00:00 | Vulnerability · Source |
| CVE-2021-35604 | suse_vex | SUSE CVE CVE-2021-35604 | known not affected: 86 recommended: 446 | 2026-07-26T16:52:54+00:00 | Vulnerability · Source |
| CVE-2021-38604 | suse_vex | SUSE CVE CVE-2021-38604 | known not affected: 651 | 2026-07-26T16:52:52+00:00 | Vulnerability · Source |
| CVE-2021-39921 | suse_vex | SUSE CVE CVE-2021-39921 | known affected: 20 recommended: 288 | 2026-07-26T16:52:50+00:00 | Vulnerability · Source |
| CVE-2021-43535 | suse_vex | SUSE CVE CVE-2021-43535 | known not affected: 156 recommended: 2 | 2026-07-26T16:52:47+00:00 | Vulnerability · Source |
| CVE-2021-45046 | suse_vex | SUSE CVE CVE-2021-45046 | known not affected: 201 recommended: 134 | 2026-07-26T16:52:46+00:00 | Vulnerability · Source |
| CVE-2021-46101 | suse_vex | SUSE CVE CVE-2021-46101 | known not affected: 573 | 2026-07-26T16:52:42+00:00 | Vulnerability · Source |
| CVE-2021-46935 | suse_vex | SUSE CVE CVE-2021-46935 | known not affected: 312 | 2026-07-26T16:52:39+00:00 | Vulnerability · Source |
| CVE-2021-47634 | suse_vex | SUSE CVE CVE-2021-47634 | known affected: 649 known not affected: 152 recommended: 40 | 2026-07-26T16:52:14+00:00 | Vulnerability · Source |
| CVE-2022-0392 | suse_vex | SUSE CVE CVE-2022-0392 | known affected: 353 known not affected: 32 recommended: 392 | 2026-07-26T16:52:05+00:00 | Vulnerability · Source |
| CVE-2022-2526 | suse_vex | SUSE CVE CVE-2022-2526 | known not affected: 598 recommended: 18 | 2026-07-26T16:51:52+00:00 | Vulnerability · Source |
| CVE-2022-4127 | suse_vex | SUSE CVE CVE-2022-4127 | known not affected: 333 | 2026-07-26T16:51:45+00:00 | Vulnerability · Source |
| CVE-2022-20008 | suse_vex | SUSE CVE CVE-2022-20008 | known affected: 222 known not affected: 155 recommended: 1074 | 2026-07-26T16:51:43+00:00 | Vulnerability · Source |
| CVE-2022-21131 | suse_vex | SUSE CVE CVE-2022-21131 | known not affected: 87 | 2026-07-26T16:51:42+00:00 | Vulnerability · Source |
| CVE-2022-23033 | suse_vex | SUSE CVE CVE-2022-23033 | known affected: 340 known not affected: 238 recommended: 333 | 2026-07-26T16:51:39+00:00 | Vulnerability · Source |
| CVE-2022-23218 | suse_vex | SUSE CVE CVE-2022-23218 | known affected: 339 recommended: 1452 | 2026-07-26T16:51:37+00:00 | Vulnerability · Source |
| CVE-2022-26125 | suse_vex | SUSE CVE CVE-2022-26125 | recommended: 255 | 2026-07-26T16:51:32+00:00 | Vulnerability · Source |
| CVE-2022-31737 | suse_vex | SUSE CVE CVE-2022-31737 | known not affected: 1 recommended: 405 | 2026-07-26T16:51:24+00:00 | Vulnerability · Source |
| CVE-2022-32087 | suse_vex | SUSE CVE CVE-2022-32087 | known not affected: 94 recommended: 378 | 2026-07-26T16:51:21+00:00 | Vulnerability · Source |
| CVE-2022-38229 | suse_vex | SUSE CVE CVE-2022-38229 | known not affected: 330 | 2026-07-26T16:51:15+00:00 | Vulnerability · Source |
| CVE-2022-45404 | suse_vex | SUSE CVE CVE-2022-45404 | known affected: 1 recommended: 405 | 2026-07-26T16:51:11+00:00 | Vulnerability · Source |
| CVE-2022-47939 | suse_vex | SUSE CVE CVE-2022-47939 | known not affected: 362 | 2026-07-26T16:51:09+00:00 | Vulnerability · Source |
| CVE-2022-48560 | suse_vex | SUSE CVE CVE-2022-48560 | known affected: 394 known not affected: 698 recommended: 209 | 2026-07-26T16:51:06+00:00 | Vulnerability · Source |
| CVE-2022-48670 | suse_vex | SUSE CVE CVE-2022-48670 | known not affected: 554 | 2026-07-26T16:51:03+00:00 | Vulnerability · Source |
| CVE-2022-48740 | suse_vex | SUSE CVE CVE-2022-48740 | known affected: 330 known not affected: 198 recommended: 475 | 2026-07-26T16:50:59+00:00 | Vulnerability · Source |
| CVE-2022-48745 | suse_vex | SUSE CVE CVE-2022-48745 | known affected: 330 known not affected: 205 recommended: 391 | 2026-07-26T16:50:57+00:00 | Vulnerability · Source |
| CVE-2022-48811 | suse_vex | SUSE CVE CVE-2022-48811 | known affected: 385 known not affected: 121 recommended: 581 | 2026-07-26T16:50:52+00:00 | Vulnerability · Source |
| CVE-2022-48920 | suse_vex | SUSE CVE CVE-2022-48920 | known affected: 512 known not affected: 86 recommended: 358 | 2026-07-26T16:50:45+00:00 | Vulnerability · Source |
| CVE-2022-48998 | suse_vex | SUSE CVE CVE-2022-48998 | known not affected: 379 | 2026-07-26T16:50:33+00:00 | Vulnerability · Source |
| CVE-2022-49043 | suse_vex | SUSE CVE CVE-2022-49043 | known affected: 396 known not affected: 397 recommended: 243 | 2026-07-26T16:50:32+00:00 | Vulnerability · Source |
| CVE-2022-49297 | suse_vex | SUSE CVE CVE-2022-49297 | known affected: 395 known not affected: 179 recommended: 341 | 2026-07-26T16:50:22+00:00 | Vulnerability · Source |