VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292076 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-50449 | suse_vex | SUSE CVE CVE-2022-50449 | known affected: 456 known not affected: 160 recommended: 206 | 2026-07-26T00:08:13+00:00 | Vulnerability · Source |
| CVE-2022-50536 | suse_vex | SUSE CVE CVE-2022-50536 | known affected: 55 known not affected: 331 recommended: 72 | 2026-07-26T00:08:10+00:00 | Vulnerability · Source |
| CVE-2022-50580 | suse_vex | SUSE CVE CVE-2022-50580 | known affected: 472 known not affected: 171 recommended: 260 | 2026-07-26T00:08:07+00:00 | Vulnerability · Source |
| CVE-2022-50667 | suse_vex | SUSE CVE CVE-2022-50667 | known affected: 374 known not affected: 351 recommended: 136 | 2026-07-26T00:08:04+00:00 | Vulnerability · Source |
| CVE-2022-50733 | suse_vex | SUSE CVE CVE-2022-50733 | known affected: 437 known not affected: 223 recommended: 272 | 2026-07-26T00:08:00+00:00 | Vulnerability · Source |
| CVE-2022-50750 | suse_vex | SUSE CVE CVE-2022-50750 | known affected: 354 known not affected: 286 recommended: 245 | 2026-07-26T00:07:55+00:00 | Vulnerability · Source |
| CVE-2022-50764 | suse_vex | SUSE CVE CVE-2022-50764 | known affected: 218 known not affected: 171 | 2026-07-26T00:07:52+00:00 | Vulnerability · Source |
| CVE-2022-50782 | suse_vex | SUSE CVE CVE-2022-50782 | known affected: 470 known not affected: 193 recommended: 262 | 2026-07-26T00:07:50+00:00 | Vulnerability · Source |
| CVE-2022-50853 | suse_vex | SUSE CVE CVE-2022-50853 | known affected: 354 known not affected: 341 recommended: 196 | 2026-07-26T00:07:48+00:00 | Vulnerability · Source |
| CVE-2023-0668 | suse_vex | SUSE CVE CVE-2023-0668 | known affected: 103 known not affected: 137 recommended: 195 | 2026-07-26T00:07:43+00:00 | Vulnerability · Source |
| CVE-2023-0803 | suse_vex | SUSE CVE CVE-2023-0803 | known affected: 494 known not affected: 1 recommended: 161 | 2026-07-26T00:07:41+00:00 | Vulnerability · Source |
| CVE-2023-6247 | suse_vex | SUSE CVE CVE-2023-6247 | known not affected: 102 | 2026-07-26T00:07:28+00:00 | Vulnerability · Source |
| CVE-2023-7207 | suse_vex | SUSE CVE CVE-2023-7207 | known affected: 279 recommended: 284 | 2026-07-26T00:07:25+00:00 | Vulnerability · Source |
| CVE-2023-23601 | suse_vex | SUSE CVE CVE-2023-23601 | known affected: 36 recommended: 320 | 2026-07-26T00:07:21+00:00 | Vulnerability · Source |
| CVE-2023-25750 | suse_vex | SUSE CVE CVE-2023-25750 | known affected: 1 recommended: 214 | 2026-07-26T00:07:18+00:00 | Vulnerability · Source |
| CVE-2023-26606 | suse_vex | SUSE CVE CVE-2023-26606 | known not affected: 284 | 2026-07-26T00:07:17+00:00 | Vulnerability · Source |
| CVE-2023-28162 | suse_vex | SUSE CVE CVE-2023-28162 | known affected: 1 recommended: 304 | 2026-07-26T00:07:15+00:00 | Vulnerability · Source |
| CVE-2023-32636 | suse_vex | SUSE CVE CVE-2023-32636 | known not affected: 598 recommended: 64 | 2026-07-26T00:07:11+00:00 | Vulnerability · Source |
| CVE-2023-32763 | suse_vex | SUSE CVE CVE-2023-32763 | known affected: 530 known not affected: 2 recommended: 2773 | 2026-07-26T00:07:09+00:00 | Vulnerability · Source |
| CVE-2023-33850 | suse_vex | SUSE CVE CVE-2023-33850 | known affected: 394 recommended: 125 | 2026-07-26T00:07:08+00:00 | Vulnerability · Source |
| CVE-2023-34981 | suse_vex | SUSE CVE CVE-2023-34981 | known not affected: 333 | 2026-07-26T00:07:06+00:00 | Vulnerability · Source |
| CVE-2023-40481 | suse_vex | SUSE CVE CVE-2023-40481 | known not affected: 79 | 2026-07-26T00:07:02+00:00 | Vulnerability · Source |
| CVE-2023-45898 | suse_vex | SUSE CVE CVE-2023-45898 | known not affected: 337 | 2026-07-26T00:07:00+00:00 | Vulnerability · Source |
| CVE-2023-46835 | suse_vex | SUSE CVE CVE-2023-46835 | known affected: 283 recommended: 426 | 2026-07-26T00:06:58+00:00 | Vulnerability · Source |
| CVE-2023-52747 | suse_vex | SUSE CVE CVE-2023-52747 | known affected: 397 known not affected: 70 recommended: 522 | 2026-07-26T00:06:45+00:00 | Vulnerability · Source |
| CVE-2023-52779 | suse_vex | SUSE CVE CVE-2023-52779 | known not affected: 330 | 2026-07-26T00:06:44+00:00 | Vulnerability · Source |
| CVE-2023-52839 | suse_vex | SUSE CVE CVE-2023-52839 | known not affected: 330 | 2026-07-26T00:06:39+00:00 | Vulnerability · Source |
| CVE-2023-52882 | suse_vex | SUSE CVE CVE-2023-52882 | known affected: 357 known not affected: 111 recommended: 660 | 2026-07-26T00:06:37+00:00 | Vulnerability · Source |
| CVE-2023-52887 | suse_vex | SUSE CVE CVE-2023-52887 | known affected: 340 known not affected: 151 recommended: 648 | 2026-07-26T00:06:36+00:00 | Vulnerability · Source |
| CVE-2023-52907 | suse_vex | SUSE CVE CVE-2023-52907 | known affected: 425 known not affected: 76 recommended: 495 | 2026-07-26T00:06:34+00:00 | Vulnerability · Source |
| CVE-2023-53025 | suse_vex | SUSE CVE CVE-2023-53025 | known not affected: 249 recommended: 191 | 2026-07-26T00:06:32+00:00 | Vulnerability · Source |
| CVE-2023-53045 | suse_vex | SUSE CVE CVE-2023-53045 | known affected: 455 known not affected: 165 recommended: 251 | 2026-07-26T00:06:31+00:00 | Vulnerability · Source |
| CVE-2023-53095 | suse_vex | SUSE CVE CVE-2023-53095 | known affected: 369 known not affected: 343 recommended: 141 | 2026-07-26T00:06:27+00:00 | Vulnerability · Source |
| CVE-2023-53153 | suse_vex | SUSE CVE CVE-2023-53153 | known affected: 468 known not affected: 181 recommended: 243 | 2026-07-26T00:06:25+00:00 | Vulnerability · Source |
| CVE-2023-53191 | suse_vex | SUSE CVE CVE-2023-53191 | known affected: 547 known not affected: 233 recommended: 23 | 2026-07-26T00:06:24+00:00 | Vulnerability · Source |
| CVE-2023-53267 | suse_vex | SUSE CVE CVE-2023-53267 | known not affected: 416 | 2026-07-26T00:06:22+00:00 | Vulnerability · Source |
| CVE-2023-53295 | suse_vex | SUSE CVE CVE-2023-53295 | known affected: 462 known not affected: 187 recommended: 243 | 2026-07-26T00:06:20+00:00 | Vulnerability · Source |
| CVE-2023-53405 | suse_vex | SUSE CVE CVE-2023-53405 | known affected: 344 known not affected: 304 recommended: 206 | 2026-07-26T00:06:18+00:00 | Vulnerability · Source |
| CVE-2023-53406 | suse_vex | SUSE CVE CVE-2023-53406 | known affected: 401 known not affected: 286 recommended: 206 | 2026-07-26T00:06:16+00:00 | Vulnerability · Source |
| CVE-2023-53445 | suse_vex | SUSE CVE CVE-2023-53445 | known affected: 55 known not affected: 361 | 2026-07-26T00:06:15+00:00 | Vulnerability · Source |
| CVE-2023-53460 | suse_vex | SUSE CVE CVE-2023-53460 | known affected: 163 known not affected: 253 | 2026-07-26T00:06:13+00:00 | Vulnerability · Source |
| CVE-2023-53661 | suse_vex | SUSE CVE CVE-2023-53661 | known not affected: 384 recommended: 49 | 2026-07-26T00:06:10+00:00 | Vulnerability · Source |
| CVE-2023-53675 | suse_vex | SUSE CVE CVE-2023-53675 | known affected: 478 known not affected: 181 recommended: 295 | 2026-07-26T00:06:09+00:00 | Vulnerability · Source |
| CVE-2023-53796 | suse_vex | SUSE CVE CVE-2023-53796 | known not affected: 448 | 2026-07-26T00:06:07+00:00 | Vulnerability · Source |
| CVE-2023-53824 | suse_vex | SUSE CVE CVE-2023-53824 | known affected: 228 known not affected: 188 | 2026-07-26T00:06:05+00:00 | Vulnerability · Source |
| CVE-2023-53833 | suse_vex | SUSE CVE CVE-2023-53833 | known affected: 374 known not affected: 351 recommended: 116 | 2026-07-26T00:06:04+00:00 | Vulnerability · Source |
| CVE-2023-54009 | suse_vex | SUSE CVE CVE-2023-54009 | known affected: 354 known not affected: 341 recommended: 196 | 2026-07-26T00:06:02+00:00 | Vulnerability · Source |
| CVE-2023-54040 | suse_vex | SUSE CVE CVE-2023-54040 | known affected: 354 known not affected: 341 recommended: 245 | 2026-07-26T00:06:00+00:00 | Vulnerability · Source |
| CVE-2023-54151 | suse_vex | SUSE CVE CVE-2023-54151 | known not affected: 453 | 2026-07-26T00:05:58+00:00 | Vulnerability · Source |
| CVE-2023-54206 | suse_vex | SUSE CVE CVE-2023-54206 | known not affected: 453 recommended: 49 | 2026-07-26T00:05:57+00:00 | Vulnerability · Source |