VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292286 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2021-34432 | suse_vex | SUSE CVE CVE-2021-34432 | No product status | 2026-07-03T04:50:54+00:00 | Vulnerability · Source |
| CVE-2021-47381 | suse_vex | SUSE CVE CVE-2021-47381 | known affected: 269 known not affected: 152 recommended: 587 | 2026-07-03T04:49:55+00:00 | Vulnerability · Source |
| CVE-2022-3560 | suse_vex | SUSE CVE CVE-2022-3560 | known not affected: 13 recommended: 58 | 2026-07-03T04:49:20+00:00 | Vulnerability · Source |
| CVE-2022-4899 | suse_vex | SUSE CVE CVE-2022-4899 | known affected: 365 known not affected: 31 recommended: 245 | 2026-07-03T04:49:03+00:00 | Vulnerability · Source |
| CVE-2022-22749 | suse_vex | SUSE CVE CVE-2022-22749 | recommended: 9 | 2026-07-03T04:48:43+00:00 | Vulnerability · Source |
| CVE-2022-24790 | suse_vex | SUSE CVE CVE-2022-24790 | known affected: 394 known not affected: 4 recommended: 106 | 2026-07-03T04:48:15+00:00 | Vulnerability · Source |
| CVE-2022-25308 | suse_vex | SUSE CVE CVE-2022-25308 | known affected: 433 recommended: 201 | 2026-07-03T04:48:13+00:00 | Vulnerability · Source |
| CVE-2022-29910 | suse_vex | SUSE CVE CVE-2022-29910 | known not affected: 2 recommended: 9 | 2026-07-03T04:47:37+00:00 | Vulnerability · Source |
| CVE-2022-29915 | suse_vex | SUSE CVE CVE-2022-29915 | known not affected: 2 recommended: 9 | 2026-07-03T04:47:34+00:00 | Vulnerability · Source |
| CVE-2022-38475 | suse_vex | SUSE CVE CVE-2022-38475 | known affected: 2 recommended: 9 | 2026-07-03T04:46:56+00:00 | Vulnerability · Source |
| CVE-2022-41793 | suse_vex | SUSE CVE CVE-2022-41793 | recommended: 5 | 2026-07-03T04:46:40+00:00 | Vulnerability · Source |
| CVE-2022-42885 | suse_vex | SUSE CVE CVE-2022-42885 | recommended: 5 | 2026-07-03T04:46:30+00:00 | Vulnerability · Source |
| CVE-2022-43467 | suse_vex | SUSE CVE CVE-2022-43467 | recommended: 10 | 2026-07-03T04:46:20+00:00 | Vulnerability · Source |
| CVE-2022-43607 | suse_vex | SUSE CVE CVE-2022-43607 | recommended: 5 | 2026-07-03T04:46:19+00:00 | Vulnerability · Source |
| CVE-2022-44451 | suse_vex | SUSE CVE CVE-2022-44451 | recommended: 5 | 2026-07-03T04:46:17+00:00 | Vulnerability · Source |
| CVE-2022-44566 | suse_vex | SUSE CVE CVE-2022-44566 | known affected: 394 recommended: 14 | 2026-07-03T04:46:16+00:00 | Vulnerability · Source |
| CVE-2022-46280 | suse_vex | SUSE CVE CVE-2022-46280 | recommended: 10 | 2026-07-03T04:46:02+00:00 | Vulnerability · Source |
| CVE-2022-46289 | suse_vex | SUSE CVE CVE-2022-46289 | recommended: 5 | 2026-07-03T04:45:59+00:00 | Vulnerability · Source |
| CVE-2022-46290 | suse_vex | SUSE CVE CVE-2022-46290 | recommended: 5 | 2026-07-03T04:45:58+00:00 | Vulnerability · Source |
| CVE-2022-46292 | suse_vex | SUSE CVE CVE-2022-46292 | recommended: 5 | 2026-07-03T04:45:57+00:00 | Vulnerability · Source |
| CVE-2022-46294 | suse_vex | SUSE CVE CVE-2022-46294 | recommended: 5 | 2026-07-03T04:45:55+00:00 | Vulnerability · Source |
| CVE-2022-46882 | suse_vex | SUSE CVE CVE-2022-46882 | known affected: 21 recommended: 353 | 2026-07-03T04:45:49+00:00 | Vulnerability · Source |
| CVE-2022-48434 | suse_vex | SUSE CVE CVE-2022-48434 | known affected: 120 recommended: 973 | 2026-07-03T04:45:39+00:00 | Vulnerability · Source |
| CVE-2022-48671 | suse_vex | SUSE CVE CVE-2022-48671 | known affected: 270 known not affected: 219 recommended: 457 | 2026-07-03T04:45:34+00:00 | Vulnerability · Source |
| CVE-2022-49314 | suse_vex | SUSE CVE CVE-2022-49314 | known affected: 334 known not affected: 268 recommended: 293 | 2026-07-03T04:45:10+00:00 | Vulnerability · Source |
| CVE-2023-2794 | suse_vex | SUSE CVE CVE-2023-2794 | recommended: 6 | 2026-07-03T04:43:42+00:00 | Vulnerability · Source |
| CVE-2023-4232 | suse_vex | SUSE CVE CVE-2023-4232 | recommended: 6 | 2026-07-03T04:43:14+00:00 | Vulnerability · Source |
| CVE-2023-5172 | suse_vex | SUSE CVE CVE-2023-5172 | known affected: 37 recommended: 9 | 2026-07-03T04:42:46+00:00 | Vulnerability · Source |
| CVE-2023-5173 | suse_vex | SUSE CVE CVE-2023-5173 | known affected: 37 recommended: 9 | 2026-07-03T04:42:45+00:00 | Vulnerability · Source |
| CVE-2023-6213 | suse_vex | SUSE CVE CVE-2023-6213 | known affected: 38 recommended: 9 | 2026-07-03T04:42:26+00:00 | Vulnerability · Source |
| CVE-2023-6868 | suse_vex | SUSE CVE CVE-2023-6868 | known affected: 28 recommended: 9 | 2026-07-03T04:42:10+00:00 | Vulnerability · Source |
| CVE-2023-23604 | suse_vex | SUSE CVE CVE-2023-23604 | known affected: 36 recommended: 9 | 2026-07-03T04:41:58+00:00 | Vulnerability · Source |
| CVE-2023-25736 | suse_vex | SUSE CVE CVE-2023-25736 | known affected: 1 recommended: 9 | 2026-07-03T04:41:46+00:00 | Vulnerability · Source |
| CVE-2023-25737 | suse_vex | SUSE CVE CVE-2023-25737 | known affected: 1 recommended: 301 | 2026-07-03T04:41:45+00:00 | Vulnerability · Source |
| CVE-2023-27539 | suse_vex | SUSE CVE CVE-2023-27539 | known affected: 396 recommended: 32 | 2026-07-03T04:41:32+00:00 | Vulnerability · Source |
| CVE-2023-28486 | suse_vex | SUSE CVE CVE-2023-28486 | known affected: 286 known not affected: 15 recommended: 280 | 2026-07-03T04:41:25+00:00 | Vulnerability · Source |
| CVE-2023-29543 | suse_vex | SUSE CVE CVE-2023-29543 | known affected: 15 recommended: 9 | 2026-07-03T04:41:08+00:00 | Vulnerability · Source |
| CVE-2023-30581 | suse_vex | SUSE CVE CVE-2023-30581 | known not affected: 253 recommended: 380 | 2026-07-03T04:41:02+00:00 | Vulnerability · Source |
| CVE-2023-30588 | suse_vex | SUSE CVE CVE-2023-30588 | known not affected: 85 recommended: 237 | 2026-07-03T04:41:01+00:00 | Vulnerability · Source |
| CVE-2023-32003 | suse_vex | SUSE CVE CVE-2023-32003 | known not affected: 558 recommended: 5 | 2026-07-03T04:40:57+00:00 | Vulnerability · Source |
| CVE-2023-32004 | suse_vex | SUSE CVE CVE-2023-32004 | known not affected: 558 recommended: 5 | 2026-07-03T04:40:55+00:00 | Vulnerability · Source |
| CVE-2023-32559 | suse_vex | SUSE CVE CVE-2023-32559 | recommended: 384 | 2026-07-03T04:40:47+00:00 | Vulnerability · Source |
| CVE-2023-39331 | suse_vex | SUSE CVE CVE-2023-39331 | known not affected: 558 recommended: 13 | 2026-07-03T04:40:20+00:00 | Vulnerability · Source |
| CVE-2023-46122 | suse_vex | SUSE CVE CVE-2023-46122 | recommended: 730 | 2026-07-03T04:40:01+00:00 | Vulnerability · Source |
| CVE-2023-49355 | suse_vex | SUSE CVE CVE-2023-49355 | known not affected: 113 | 2026-07-03T04:39:43+00:00 | Vulnerability · Source |
| CVE-2023-52635 | suse_vex | SUSE CVE CVE-2023-52635 | known affected: 406 known not affected: 6 recommended: 712 | 2026-07-03T04:39:18+00:00 | Vulnerability · Source |
| CVE-2023-52690 | suse_vex | SUSE CVE CVE-2023-52690 | known affected: 275 known not affected: 151 recommended: 787 | 2026-07-03T04:38:54+00:00 | Vulnerability · Source |
| CVE-2023-52835 | suse_vex | SUSE CVE CVE-2023-52835 | known affected: 539 known not affected: 33 recommended: 712 | 2026-07-03T04:38:04+00:00 | Vulnerability · Source |
| CVE-2023-53063 | suse_vex | SUSE CVE CVE-2023-53063 | known affected: 394 recommended: 23 | 2026-07-03T04:37:30+00:00 | Vulnerability · Source |
| CVE-2023-53683 | suse_vex | SUSE CVE CVE-2023-53683 | known affected: 354 known not affected: 274 recommended: 219 | 2026-07-03T04:34:57+00:00 | Vulnerability · Source |