VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291913 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2021-26932 | suse_vex | SUSE CVE CVE-2021-26932 | known affected: 320 known not affected: 147 recommended: 1337 | 2026-07-31T01:35:35+00:00 | Vulnerability · Source |
| CVE-2021-28375 | suse_vex | SUSE CVE CVE-2021-28375 | known affected: 306 known not affected: 366 recommended: 1047 | 2026-07-31T01:35:33+00:00 | Vulnerability · Source |
| CVE-2021-28651 | suse_vex | SUSE CVE CVE-2021-28651 | known affected: 394 known not affected: 61 recommended: 68 | 2026-07-31T01:35:31+00:00 | Vulnerability · Source |
| CVE-2021-28652 | suse_vex | SUSE CVE CVE-2021-28652 | known affected: 399 known not affected: 10 recommended: 52 | 2026-07-31T01:35:29+00:00 | Vulnerability · Source |
| CVE-2021-28711 | suse_vex | SUSE CVE CVE-2021-28711 | known affected: 332 known not affected: 448 recommended: 1330 | 2026-07-31T01:35:27+00:00 | Vulnerability · Source |
| CVE-2021-30799 | suse_vex | SUSE CVE CVE-2021-30799 | known affected: 1 known not affected: 117 recommended: 1090 | 2026-07-31T01:35:24+00:00 | Vulnerability · Source |
| CVE-2021-30889 | suse_vex | SUSE CVE CVE-2021-30889 | known affected: 1 known not affected: 10 recommended: 941 | 2026-07-31T01:35:23+00:00 | Vulnerability · Source |
| CVE-2021-32000 | suse_vex | SUSE CVE CVE-2021-32000 | known affected: 24 known not affected: 5 recommended: 36 | 2026-07-31T01:35:21+00:00 | Vulnerability · Source |
| CVE-2021-33139 | suse_vex | SUSE CVE CVE-2021-33139 | known affected: 11 known not affected: 2 recommended: 1299 | 2026-07-31T01:35:19+00:00 | Vulnerability · Source |
| CVE-2021-35550 | suse_vex | SUSE CVE CVE-2021-35550 | known affected: 397 recommended: 729 | 2026-07-31T01:35:16+00:00 | Vulnerability · Source |
| CVE-2021-36087 | suse_vex | SUSE CVE CVE-2021-36087 | known not affected: 639 recommended: 40 | 2026-07-31T01:35:14+00:00 | Vulnerability · Source |
| CVE-2021-38497 | suse_vex | SUSE CVE CVE-2021-38497 | known affected: 1 recommended: 487 | 2026-07-31T01:35:12+00:00 | Vulnerability · Source |
| CVE-2021-38505 | suse_vex | SUSE CVE CVE-2021-38505 | known affected: 1 recommended: 412 | 2026-07-31T01:35:10+00:00 | Vulnerability · Source |
| CVE-2021-42380 | suse_vex | SUSE CVE CVE-2021-42380 | known affected: 4 known not affected: 8 recommended: 149 | 2026-07-31T01:35:08+00:00 | Vulnerability · Source |
| CVE-2021-43545 | suse_vex | SUSE CVE CVE-2021-43545 | known affected: 1 recommended: 424 | 2026-07-31T01:35:05+00:00 | Vulnerability · Source |
| CVE-2021-44038 | suse_vex | SUSE CVE CVE-2021-44038 | known not affected: 304 recommended: 7 | 2026-07-31T01:35:03+00:00 | Vulnerability · Source |
| CVE-2021-44573 | suse_vex | SUSE CVE CVE-2021-44573 | known not affected: 323 | 2026-07-31T01:35:01+00:00 | Vulnerability · Source |
| CVE-2021-44832 | suse_vex | SUSE CVE CVE-2021-44832 | known not affected: 111 recommended: 104 | 2026-07-31T01:34:59+00:00 | Vulnerability · Source |
| CVE-2021-46953 | suse_vex | SUSE CVE CVE-2021-46953 | known affected: 388 known not affected: 186 recommended: 222 | 2026-07-31T01:34:54+00:00 | Vulnerability · Source |
| CVE-2021-46973 | suse_vex | SUSE CVE CVE-2021-46973 | known not affected: 292 | 2026-07-31T01:34:49+00:00 | Vulnerability · Source |
| CVE-2021-46977 | suse_vex | SUSE CVE CVE-2021-46977 | known not affected: 292 | 2026-07-31T01:34:47+00:00 | Vulnerability · Source |
| CVE-2021-47121 | suse_vex | SUSE CVE CVE-2021-47121 | known affected: 60 known not affected: 309 | 2026-07-31T01:34:41+00:00 | Vulnerability · Source |
| CVE-2021-47147 | suse_vex | SUSE CVE CVE-2021-47147 | known not affected: 292 | 2026-07-31T01:34:40+00:00 | Vulnerability · Source |
| CVE-2021-47180 | suse_vex | SUSE CVE CVE-2021-47180 | known affected: 477 known not affected: 207 recommended: 221 | 2026-07-31T01:34:36+00:00 | Vulnerability · Source |
| CVE-2021-47244 | suse_vex | SUSE CVE CVE-2021-47244 | known not affected: 330 | 2026-07-31T01:34:34+00:00 | Vulnerability · Source |
| CVE-2021-47318 | suse_vex | SUSE CVE CVE-2021-47318 | known not affected: 325 | 2026-07-31T01:34:28+00:00 | Vulnerability · Source |
| CVE-2021-47407 | suse_vex | SUSE CVE CVE-2021-47407 | known affected: 395 known not affected: 70 recommended: 522 | 2026-07-31T01:34:22+00:00 | Vulnerability · Source |
| CVE-2021-47498 | suse_vex | SUSE CVE CVE-2021-47498 | known affected: 377 known not affected: 67 recommended: 647 | 2026-07-31T01:34:10+00:00 | Vulnerability · Source |
| CVE-2021-47540 | suse_vex | SUSE CVE CVE-2021-47540 | known affected: 269 known not affected: 181 recommended: 543 | 2026-07-31T01:34:06+00:00 | Vulnerability · Source |
| CVE-2021-47546 | suse_vex | SUSE CVE CVE-2021-47546 | known affected: 357 known not affected: 181 recommended: 302 | 2026-07-31T01:34:04+00:00 | Vulnerability · Source |
| CVE-2021-47581 | suse_vex | SUSE CVE CVE-2021-47581 | known not affected: 318 | 2026-07-31T01:34:02+00:00 | Vulnerability · Source |
| CVE-2021-47659 | suse_vex | SUSE CVE CVE-2021-47659 | known affected: 407 known not affected: 270 recommended: 319 | 2026-07-31T01:33:58+00:00 | Vulnerability · Source |
| CVE-2022-0286 | suse_vex | SUSE CVE CVE-2022-0286 | known affected: 344 known not affected: 580 recommended: 433 | 2026-07-31T01:33:56+00:00 | Vulnerability · Source |
| CVE-2022-1678 | suse_vex | SUSE CVE CVE-2022-1678 | known not affected: 390 | 2026-07-31T01:33:42+00:00 | Vulnerability · Source |
| CVE-2022-2264 | suse_vex | SUSE CVE CVE-2022-2264 | known affected: 237 known not affected: 26 recommended: 505 | 2026-07-31T01:33:34+00:00 | Vulnerability · Source |
| CVE-2022-2308 | suse_vex | SUSE CVE CVE-2022-2308 | known not affected: 564 recommended: 6 | 2026-07-31T01:33:32+00:00 | Vulnerability · Source |
| CVE-2022-3624 | suse_vex | SUSE CVE CVE-2022-3624 | known not affected: 564 | 2026-07-31T01:33:17+00:00 | Vulnerability · Source |
| CVE-2022-3630 | suse_vex | SUSE CVE CVE-2022-3630 | known not affected: 564 | 2026-07-31T01:33:13+00:00 | Vulnerability · Source |
| CVE-2022-3636 | suse_vex | SUSE CVE CVE-2022-3636 | known not affected: 720 | 2026-07-31T01:33:09+00:00 | Vulnerability · Source |
| CVE-2022-21538 | suse_vex | SUSE CVE CVE-2022-21538 | recommended: 17 | 2026-07-31T01:32:58+00:00 | Vulnerability · Source |
| CVE-2022-21539 | suse_vex | SUSE CVE CVE-2022-21539 | recommended: 17 | 2026-07-31T01:32:56+00:00 | Vulnerability · Source |
| CVE-2022-22753 | suse_vex | SUSE CVE CVE-2022-22753 | recommended: 404 | 2026-07-31T01:32:53+00:00 | Vulnerability · Source |
| CVE-2022-23041 | suse_vex | SUSE CVE CVE-2022-23041 | known affected: 344 known not affected: 61 recommended: 1327 | 2026-07-31T01:32:50+00:00 | Vulnerability · Source |
| CVE-2022-23478 | suse_vex | SUSE CVE CVE-2022-23478 | known affected: 394 known not affected: 3 recommended: 171 | 2026-07-31T01:32:48+00:00 | Vulnerability · Source |
| CVE-2022-28349 | suse_vex | SUSE CVE CVE-2022-28349 | known not affected: 390 | 2026-07-31T01:32:39+00:00 | Vulnerability · Source |
| CVE-2022-31624 | suse_vex | SUSE CVE CVE-2022-31624 | known not affected: 233 recommended: 16 | 2026-07-31T01:32:34+00:00 | Vulnerability · Source |
| CVE-2022-34266 | suse_vex | SUSE CVE CVE-2022-34266 | known affected: 394 known not affected: 2 recommended: 263 | 2026-07-31T01:32:25+00:00 | Vulnerability · Source |
| CVE-2022-40897 | suse_vex | SUSE CVE CVE-2022-40897 | known affected: 272 known not affected: 95 recommended: 350 | 2026-07-31T01:32:21+00:00 | Vulnerability · Source |
| CVE-2022-42325 | suse_vex | SUSE CVE CVE-2022-42325 | known affected: 253 known not affected: 13 recommended: 499 | 2026-07-31T01:32:19+00:00 | Vulnerability · Source |
| CVE-2022-45786 | suse_vex | SUSE CVE CVE-2022-45786 | No product status | 2026-07-31T01:32:11+00:00 | Vulnerability · Source |