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-16290 | suse_vex | SUSE CVE CVE-2020-16290 | known not affected: 172 recommended: 8 | 2026-07-26T23:41:32+00:00 | Vulnerability · Source |
| CVE-2020-19190 | suse_vex | SUSE CVE CVE-2020-19190 | known not affected: 635 | 2026-07-26T23:41:30+00:00 | Vulnerability · Source |
| CVE-2020-25221 | suse_vex | SUSE CVE CVE-2020-25221 | known not affected: 413 | 2026-07-26T23:41:26+00:00 | Vulnerability · Source |
| CVE-2020-25597 | suse_vex | SUSE CVE CVE-2020-25597 | known affected: 431 known not affected: 2 recommended: 517 | 2026-07-26T23:41:25+00:00 | Vulnerability · Source |
| CVE-2020-29482 | suse_vex | SUSE CVE CVE-2020-29482 | known not affected: 334 | 2026-07-26T23:41:18+00:00 | Vulnerability · Source |
| CVE-2021-0157 | suse_vex | SUSE CVE CVE-2021-0157 | known not affected: 57 | 2026-07-26T23:41:14+00:00 | Vulnerability · Source |
| CVE-2021-3595 | suse_vex | SUSE CVE CVE-2021-3595 | known affected: 412 known not affected: 596 recommended: 1062 | 2026-07-26T23:41:08+00:00 | Vulnerability · Source |
| CVE-2021-3652 | suse_vex | SUSE CVE CVE-2021-3652 | known not affected: 28 recommended: 185 | 2026-07-26T23:41:04+00:00 | Vulnerability · Source |
| CVE-2021-3872 | suse_vex | SUSE CVE CVE-2021-3872 | known affected: 351 known not affected: 15 recommended: 389 | 2026-07-26T23:41:02+00:00 | Vulnerability · Source |
| CVE-2021-4214 | suse_vex | SUSE CVE CVE-2021-4214 | known not affected: 270 | 2026-07-26T23:41:00+00:00 | Vulnerability · Source |
| CVE-2021-28702 | suse_vex | SUSE CVE CVE-2021-28702 | known affected: 330 known not affected: 206 recommended: 247 | 2026-07-26T23:40:54+00:00 | Vulnerability · Source |
| CVE-2021-29464 | suse_vex | SUSE CVE CVE-2021-29464 | known not affected: 143 recommended: 4 | 2026-07-26T23:40:52+00:00 | Vulnerability · Source |
| CVE-2021-29649 | suse_vex | SUSE CVE CVE-2021-29649 | known not affected: 355 | 2026-07-26T23:40:51+00:00 | Vulnerability · Source |
| CVE-2021-33193 | suse_vex | SUSE CVE CVE-2021-33193 | known affected: 492 known not affected: 4 recommended: 298 | 2026-07-26T23:40:45+00:00 | Vulnerability · Source |
| CVE-2021-37322 | suse_vex | SUSE CVE CVE-2021-37322 | known not affected: 257 | 2026-07-26T23:40:42+00:00 | Vulnerability · Source |
| CVE-2021-46968 | suse_vex | SUSE CVE CVE-2021-46968 | known affected: 388 known not affected: 248 recommended: 106 | 2026-07-26T23:40:36+00:00 | Vulnerability · Source |
| CVE-2021-46997 | suse_vex | SUSE CVE CVE-2021-46997 | known not affected: 292 | 2026-07-26T23:40:34+00:00 | Vulnerability · Source |
| CVE-2021-47072 | suse_vex | SUSE CVE CVE-2021-47072 | known not affected: 292 | 2026-07-26T23:40:31+00:00 | Vulnerability · Source |
| CVE-2021-47164 | suse_vex | SUSE CVE CVE-2021-47164 | known affected: 388 known not affected: 256 recommended: 91 | 2026-07-26T23:40:29+00:00 | Vulnerability · Source |
| CVE-2021-47172 | suse_vex | SUSE CVE CVE-2021-47172 | known affected: 388 known not affected: 233 recommended: 137 | 2026-07-26T23:40:27+00:00 | Vulnerability · Source |
| CVE-2021-47213 | suse_vex | SUSE CVE CVE-2021-47213 | known not affected: 299 recommended: 20 | 2026-07-26T23:40:24+00:00 | Vulnerability · Source |
| CVE-2021-47589 | suse_vex | SUSE CVE CVE-2021-47589 | known affected: 379 known not affected: 76 recommended: 641 | 2026-07-26T23:40:10+00:00 | Vulnerability · Source |
| CVE-2022-0581 | suse_vex | SUSE CVE CVE-2022-0581 | known not affected: 124 recommended: 339 | 2026-07-26T23:40:05+00:00 | Vulnerability · Source |
| CVE-2022-1328 | suse_vex | SUSE CVE CVE-2022-1328 | known affected: 437 recommended: 129 | 2026-07-26T23:39:58+00:00 | Vulnerability · Source |
| CVE-2022-1925 | suse_vex | SUSE CVE CVE-2022-1925 | known affected: 2 known not affected: 10 recommended: 166 | 2026-07-26T23:39:56+00:00 | Vulnerability · Source |
| CVE-2022-2320 | suse_vex | SUSE CVE CVE-2022-2320 | known affected: 401 recommended: 277 | 2026-07-26T23:39:52+00:00 | Vulnerability · Source |
| CVE-2022-20118 | suse_vex | SUSE CVE CVE-2022-20118 | known not affected: 390 | 2026-07-26T23:39:43+00:00 | Vulnerability · Source |
| CVE-2022-23305 | suse_vex | SUSE CVE CVE-2022-23305 | known affected: 395 known not affected: 36 recommended: 351 | 2026-07-26T23:39:38+00:00 | Vulnerability · Source |
| CVE-2022-23481 | suse_vex | SUSE CVE CVE-2022-23481 | known affected: 395 known not affected: 1 recommended: 202 | 2026-07-26T23:39:37+00:00 | Vulnerability · Source |
| CVE-2022-24349 | suse_vex | SUSE CVE CVE-2022-24349 | known affected: 21 recommended: 15 | 2026-07-26T23:39:36+00:00 | Vulnerability · Source |
| CVE-2022-28321 | suse_vex | SUSE CVE CVE-2022-28321 | known not affected: 250 | 2026-07-26T23:39:30+00:00 | Vulnerability · Source |
| CVE-2022-29824 | suse_vex | SUSE CVE CVE-2022-29824 | known affected: 216 known not affected: 60 recommended: 702 | 2026-07-26T23:39:28+00:00 | Vulnerability · Source |
| CVE-2022-36320 | suse_vex | SUSE CVE CVE-2022-36320 | known not affected: 173 recommended: 9 | 2026-07-26T23:39:22+00:00 | Vulnerability · Source |
| CVE-2022-40090 | suse_vex | SUSE CVE CVE-2022-40090 | known affected: 454 recommended: 141 | 2026-07-26T23:39:19+00:00 | Vulnerability · Source |
| CVE-2022-48649 | suse_vex | SUSE CVE CVE-2022-48649 | known not affected: 288 | 2026-07-26T23:39:15+00:00 | Vulnerability · Source |
| CVE-2022-48782 | suse_vex | SUSE CVE CVE-2022-48782 | known not affected: 318 | 2026-07-26T23:39:12+00:00 | Vulnerability · Source |
| CVE-2022-48802 | suse_vex | SUSE CVE CVE-2022-48802 | known not affected: 359 recommended: 456 | 2026-07-26T23:39:10+00:00 | Vulnerability · Source |
| CVE-2022-48965 | suse_vex | SUSE CVE CVE-2022-48965 | known not affected: 365 | 2026-07-26T23:39:02+00:00 | Vulnerability · Source |
| CVE-2022-49070 | suse_vex | SUSE CVE CVE-2022-49070 | known affected: 364 known not affected: 302 recommended: 127 | 2026-07-26T23:38:57+00:00 | Vulnerability · Source |
| CVE-2022-49284 | suse_vex | SUSE CVE CVE-2022-49284 | known not affected: 352 | 2026-07-26T23:38:46+00:00 | Vulnerability · Source |
| CVE-2022-49307 | suse_vex | SUSE CVE CVE-2022-49307 | known affected: 340 known not affected: 264 recommended: 293 | 2026-07-26T23:38:44+00:00 | Vulnerability · Source |
| CVE-2022-49461 | suse_vex | SUSE CVE CVE-2022-49461 | known not affected: 352 | 2026-07-26T23:38:36+00:00 | Vulnerability · Source |
| CVE-2022-49539 | suse_vex | SUSE CVE CVE-2022-49539 | known affected: 112 known not affected: 240 recommended: 47 | 2026-07-26T23:38:31+00:00 | Vulnerability · Source |
| CVE-2022-49574 | suse_vex | SUSE CVE CVE-2022-49574 | known not affected: 147 recommended: 27 | 2026-07-26T23:38:26+00:00 | Vulnerability · Source |
| CVE-2022-49895 | suse_vex | SUSE CVE CVE-2022-49895 | known not affected: 397 | 2026-07-26T23:38:10+00:00 | Vulnerability · Source |
| CVE-2022-49900 | suse_vex | SUSE CVE CVE-2022-49900 | known affected: 339 known not affected: 294 recommended: 214 | 2026-07-26T23:38:08+00:00 | Vulnerability · Source |
| CVE-2022-49901 | suse_vex | SUSE CVE CVE-2022-49901 | known affected: 475 known not affected: 237 recommended: 92 | 2026-07-26T23:38:06+00:00 | Vulnerability · Source |
| CVE-2022-49972 | suse_vex | SUSE CVE CVE-2022-49972 | known affected: 369 known not affected: 347 recommended: 92 | 2026-07-26T23:38:04+00:00 | Vulnerability · Source |
| CVE-2022-50017 | suse_vex | SUSE CVE CVE-2022-50017 | known not affected: 401 | 2026-07-26T23:38:02+00:00 | Vulnerability · Source |
| CVE-2022-50220 | suse_vex | SUSE CVE CVE-2022-50220 | known affected: 425 known not affected: 248 recommended: 310 | 2026-07-26T23:37:53+00:00 | Vulnerability · Source |