VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291942 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2021-33037 | suse_vex | SUSE CVE CVE-2021-33037 | known affected: 423 recommended: 515 | 2026-07-27T23:55:59+00:00 | Vulnerability · Source |
| CVE-2021-34337 | suse_vex | SUSE CVE CVE-2021-34337 | known not affected: 16 recommended: 2 | 2026-07-27T23:55:54+00:00 | Vulnerability · Source |
| CVE-2021-34557 | suse_vex | SUSE CVE CVE-2021-34557 | known affected: 45 known not affected: 24 recommended: 38 | 2026-07-27T23:55:53+00:00 | Vulnerability · Source |
| CVE-2021-34866 | suse_vex | SUSE CVE CVE-2021-34866 | known affected: 323 known not affected: 259 recommended: 485 | 2026-07-27T23:55:51+00:00 | Vulnerability · Source |
| CVE-2021-37600 | suse_vex | SUSE CVE CVE-2021-37600 | known affected: 407 known not affected: 164 recommended: 1264 | 2026-07-27T23:55:47+00:00 | Vulnerability · Source |
| CVE-2021-37616 | suse_vex | SUSE CVE CVE-2021-37616 | known not affected: 32 | 2026-07-27T23:55:45+00:00 | Vulnerability · Source |
| CVE-2021-38201 | suse_vex | SUSE CVE CVE-2021-38201 | known not affected: 260 recommended: 20 | 2026-07-27T23:55:43+00:00 | Vulnerability · Source |
| CVE-2021-41496 | suse_vex | SUSE CVE CVE-2021-41496 | known affected: 408 known not affected: 9 recommended: 402 | 2026-07-27T23:55:36+00:00 | Vulnerability · Source |
| CVE-2021-42381 | suse_vex | SUSE CVE CVE-2021-42381 | known affected: 4 known not affected: 8 recommended: 132 | 2026-07-27T23:55:33+00:00 | Vulnerability · Source |
| CVE-2021-43813 | suse_vex | SUSE CVE CVE-2021-43813 | recommended: 329 | 2026-07-27T23:55:29+00:00 | Vulnerability · Source |
| CVE-2021-44569 | suse_vex | SUSE CVE CVE-2021-44569 | known not affected: 304 | 2026-07-27T23:55:28+00:00 | Vulnerability · Source |
| CVE-2021-44964 | suse_vex | SUSE CVE CVE-2021-44964 | known not affected: 327 recommended: 3 | 2026-07-27T23:55:26+00:00 | Vulnerability · Source |
| CVE-2021-46665 | suse_vex | SUSE CVE CVE-2021-46665 | known affected: 1 recommended: 484 | 2026-07-27T23:55:21+00:00 | Vulnerability · Source |
| CVE-2021-46666 | suse_vex | SUSE CVE CVE-2021-46666 | known not affected: 70 recommended: 16 | 2026-07-27T23:55:20+00:00 | Vulnerability · Source |
| CVE-2021-46986 | suse_vex | SUSE CVE CVE-2021-46986 | known not affected: 238 | 2026-07-27T23:55:10+00:00 | Vulnerability · Source |
| CVE-2021-47054 | suse_vex | SUSE CVE CVE-2021-47054 | known affected: 412 known not affected: 140 recommended: 208 | 2026-07-27T23:55:06+00:00 | Vulnerability · Source |
| CVE-2021-47090 | suse_vex | SUSE CVE CVE-2021-47090 | known not affected: 238 | 2026-07-27T23:55:01+00:00 | Vulnerability · Source |
| CVE-2021-47132 | suse_vex | SUSE CVE CVE-2021-47132 | known not affected: 238 | 2026-07-27T23:54:58+00:00 | Vulnerability · Source |
| CVE-2021-47140 | suse_vex | SUSE CVE CVE-2021-47140 | known not affected: 238 | 2026-07-27T23:54:57+00:00 | Vulnerability · Source |
| CVE-2021-47169 | suse_vex | SUSE CVE CVE-2021-47169 | known affected: 433 known not affected: 182 recommended: 200 | 2026-07-27T23:54:53+00:00 | Vulnerability · Source |
| CVE-2021-47230 | suse_vex | SUSE CVE CVE-2021-47230 | known affected: 385 known not affected: 238 recommended: 91 | 2026-07-27T23:54:45+00:00 | Vulnerability · Source |
| CVE-2021-47233 | suse_vex | SUSE CVE CVE-2021-47233 | known not affected: 283 | 2026-07-27T23:54:43+00:00 | Vulnerability · Source |
| CVE-2021-47251 | suse_vex | SUSE CVE CVE-2021-47251 | known not affected: 283 | 2026-07-27T23:54:40+00:00 | Vulnerability · Source |
| CVE-2021-47253 | suse_vex | SUSE CVE CVE-2021-47253 | known affected: 376 known not affected: 253 recommended: 91 | 2026-07-27T23:54:39+00:00 | Vulnerability · Source |
| CVE-2021-47278 | suse_vex | SUSE CVE CVE-2021-47278 | known not affected: 283 | 2026-07-27T23:54:37+00:00 | Vulnerability · Source |
| CVE-2021-47526 | suse_vex | SUSE CVE CVE-2021-47526 | known affected: 275 known not affected: 176 recommended: 440 | 2026-07-27T23:54:17+00:00 | Vulnerability · Source |
| CVE-2021-47543 | suse_vex | SUSE CVE CVE-2021-47543 | known not affected: 60 | 2026-07-27T23:54:12+00:00 | Vulnerability · Source |
| CVE-2022-0171 | suse_vex | SUSE CVE CVE-2022-0171 | known affected: 209 known not affected: 169 recommended: 388 | 2026-07-27T23:54:00+00:00 | Vulnerability · Source |
| CVE-2022-1587 | suse_vex | SUSE CVE CVE-2022-1587 | known affected: 242 known not affected: 402 recommended: 540 | 2026-07-27T23:53:52+00:00 | Vulnerability · Source |
| CVE-2022-1664 | suse_vex | SUSE CVE CVE-2022-1664 | known not affected: 3 recommended: 124 | 2026-07-27T23:53:51+00:00 | Vulnerability · Source |
| CVE-2022-1769 | suse_vex | SUSE CVE CVE-2022-1769 | known not affected: 227 recommended: 15 | 2026-07-27T23:53:49+00:00 | Vulnerability · Source |
| CVE-2022-2571 | suse_vex | SUSE CVE CVE-2022-2571 | known affected: 237 known not affected: 2 recommended: 489 | 2026-07-27T23:53:43+00:00 | Vulnerability · Source |
| CVE-2022-2590 | suse_vex | SUSE CVE CVE-2022-2590 | known not affected: 274 recommended: 6 | 2026-07-27T23:53:42+00:00 | Vulnerability · Source |
| CVE-2022-3854 | suse_vex | SUSE CVE CVE-2022-3854 | known not affected: 442 recommended: 657 | 2026-07-27T23:53:32+00:00 | Vulnerability · Source |
| CVE-2022-4055 | suse_vex | SUSE CVE CVE-2022-4055 | recommended: 1 | 2026-07-27T23:53:30+00:00 | Vulnerability · Source |
| CVE-2022-21293 | suse_vex | SUSE CVE CVE-2022-21293 | known affected: 406 known not affected: 32 recommended: 1020 | 2026-07-27T23:53:27+00:00 | Vulnerability · Source |
| CVE-2022-21597 | suse_vex | SUSE CVE CVE-2022-21597 | known not affected: 426 | 2026-07-27T23:53:24+00:00 | Vulnerability · Source |
| CVE-2022-23133 | suse_vex | SUSE CVE CVE-2022-23133 | known not affected: 28 | 2026-07-27T23:53:20+00:00 | Vulnerability · Source |
| CVE-2022-23493 | suse_vex | SUSE CVE CVE-2022-23493 | known affected: 375 known not affected: 45 recommended: 170 | 2026-07-27T23:53:16+00:00 | Vulnerability · Source |
| CVE-2022-28286 | suse_vex | SUSE CVE CVE-2022-28286 | known affected: 3 known not affected: 128 recommended: 393 | 2026-07-27T23:53:05+00:00 | Vulnerability · Source |
| CVE-2022-34568 | suse_vex | SUSE CVE CVE-2022-34568 | known not affected: 226 recommended: 2 | 2026-07-27T23:52:53+00:00 | Vulnerability · Source |
| CVE-2022-37416 | suse_vex | SUSE CVE CVE-2022-37416 | known not affected: 306 | 2026-07-27T23:52:50+00:00 | Vulnerability · Source |
| CVE-2022-38126 | suse_vex | SUSE CVE CVE-2022-38126 | known affected: 395 known not affected: 1 recommended: 445 | 2026-07-27T23:52:48+00:00 | Vulnerability · Source |
| CVE-2022-41861 | suse_vex | SUSE CVE CVE-2022-41861 | known affected: 1 recommended: 717 | 2026-07-27T23:52:43+00:00 | Vulnerability · Source |
| CVE-2022-42319 | suse_vex | SUSE CVE CVE-2022-42319 | known affected: 253 known not affected: 7 recommended: 481 | 2026-07-27T23:52:42+00:00 | Vulnerability · Source |
| CVE-2022-44268 | suse_vex | SUSE CVE CVE-2022-44268 | known affected: 45 known not affected: 12 recommended: 534 | 2026-07-27T23:52:39+00:00 | Vulnerability · Source |
| CVE-2022-48635 | suse_vex | SUSE CVE CVE-2022-48635 | known not affected: 241 | 2026-07-27T23:52:35+00:00 | Vulnerability · Source |
| CVE-2022-48640 | suse_vex | SUSE CVE CVE-2022-48640 | known affected: 360 known not affected: 222 recommended: 313 | 2026-07-27T23:52:33+00:00 | Vulnerability · Source |
| CVE-2022-48707 | suse_vex | SUSE CVE CVE-2022-48707 | known not affected: 283 | 2026-07-27T23:52:30+00:00 | Vulnerability · Source |
| CVE-2022-48719 | suse_vex | SUSE CVE CVE-2022-48719 | known not affected: 271 | 2026-07-27T23:52:27+00:00 | Vulnerability · Source |