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-2022-50627 | suse_vex | SUSE CVE CVE-2022-50627 | known not affected: 373 recommended: 49 | 2026-07-27T23:49:32+00:00 | Vulnerability · Source |
| CVE-2022-50706 | suse_vex | SUSE CVE CVE-2022-50706 | known not affected: 359 recommended: 30 | 2026-07-27T23:49:30+00:00 | Vulnerability · Source |
| CVE-2023-0217 | suse_vex | SUSE CVE CVE-2023-0217 | known not affected: 480 recommended: 142 | 2026-07-27T23:49:21+00:00 | Vulnerability · Source |
| CVE-2023-0458 | suse_vex | SUSE CVE CVE-2023-0458 | known affected: 2 known not affected: 276 recommended: 47 | 2026-07-27T23:49:19+00:00 | Vulnerability · Source |
| CVE-2023-1637 | suse_vex | SUSE CVE CVE-2023-1637 | known affected: 283 known not affected: 60 recommended: 1180 | 2026-07-27T23:49:15+00:00 | Vulnerability · Source |
| CVE-2023-3164 | suse_vex | SUSE CVE CVE-2023-3164 | known affected: 542 recommended: 63 | 2026-07-27T23:49:09+00:00 | Vulnerability · Source |
| CVE-2023-3745 | suse_vex | SUSE CVE CVE-2023-3745 | known not affected: 300 recommended: 88 | 2026-07-27T23:49:07+00:00 | Vulnerability · Source |
| CVE-2023-3758 | suse_vex | SUSE CVE CVE-2023-3758 | known affected: 114 known not affected: 19 recommended: 972 | 2026-07-27T23:49:06+00:00 | Vulnerability · Source |
| CVE-2023-4057 | suse_vex | SUSE CVE CVE-2023-4057 | known affected: 40 recommended: 251 | 2026-07-27T23:49:02+00:00 | Vulnerability · Source |
| CVE-2023-4208 | suse_vex | SUSE CVE CVE-2023-4208 | recommended: 62 | 2026-07-27T23:48:59+00:00 | Vulnerability · Source |
| CVE-2023-4693 | suse_vex | SUSE CVE CVE-2023-4693 | known affected: 260 recommended: 663 | 2026-07-27T23:48:57+00:00 | Vulnerability · Source |
| CVE-2023-4901 | suse_vex | SUSE CVE CVE-2023-4901 | known affected: 45 known not affected: 1172 recommended: 12 | 2026-07-27T23:48:55+00:00 | Vulnerability · Source |
| CVE-2023-4904 | suse_vex | SUSE CVE CVE-2023-4904 | known affected: 45 known not affected: 1172 recommended: 12 | 2026-07-27T23:48:53+00:00 | Vulnerability · Source |
| CVE-2023-5090 | suse_vex | SUSE CVE CVE-2023-5090 | known affected: 287 known not affected: 903 recommended: 49 | 2026-07-27T23:48:51+00:00 | Vulnerability · Source |
| CVE-2023-5217 | suse_vex | SUSE CVE CVE-2023-5217 | known affected: 446 known not affected: 1 recommended: 515 | 2026-07-27T23:48:50+00:00 | Vulnerability · Source |
| CVE-2023-6862 | suse_vex | SUSE CVE CVE-2023-6862 | known affected: 28 recommended: 245 | 2026-07-27T23:48:39+00:00 | Vulnerability · Source |
| CVE-2023-22041 | suse_vex | SUSE CVE CVE-2023-22041 | known affected: 394 known not affected: 153 recommended: 612 | 2026-07-27T23:48:33+00:00 | Vulnerability · Source |
| CVE-2023-29499 | suse_vex | SUSE CVE CVE-2023-29499 | known not affected: 511 recommended: 69 | 2026-07-27T23:48:14+00:00 | Vulnerability · Source |
| CVE-2023-29532 | suse_vex | SUSE CVE CVE-2023-29532 | known affected: 15 recommended: 286 | 2026-07-27T23:48:12+00:00 | Vulnerability · Source |
| CVE-2023-32209 | suse_vex | SUSE CVE CVE-2023-32209 | known affected: 63 recommended: 9 | 2026-07-27T23:48:10+00:00 | Vulnerability · Source |
| CVE-2023-32725 | suse_vex | SUSE CVE CVE-2023-32725 | known not affected: 14 | 2026-07-27T23:48:08+00:00 | Vulnerability · Source |
| CVE-2023-34323 | suse_vex | SUSE CVE CVE-2023-34323 | known affected: 250 recommended: 447 | 2026-07-27T23:48:06+00:00 | Vulnerability · Source |
| CVE-2023-37201 | suse_vex | SUSE CVE CVE-2023-37201 | recommended: 265 | 2026-07-27T23:48:01+00:00 | Vulnerability · Source |
| CVE-2023-38431 | suse_vex | SUSE CVE CVE-2023-38431 | known not affected: 301 | 2026-07-27T23:47:59+00:00 | Vulnerability · Source |
| CVE-2023-40791 | suse_vex | SUSE CVE CVE-2023-40791 | known not affected: 289 | 2026-07-27T23:47:55+00:00 | Vulnerability · Source |
| CVE-2023-41360 | suse_vex | SUSE CVE CVE-2023-41360 | known not affected: 481 recommended: 177 | 2026-07-27T23:47:54+00:00 | Vulnerability · Source |
| CVE-2023-45237 | suse_vex | SUSE CVE CVE-2023-45237 | known affected: 193 recommended: 111 | 2026-07-27T23:47:49+00:00 | Vulnerability · Source |
| CVE-2023-46047 | suse_vex | SUSE CVE CVE-2023-46047 | known affected: 125 | 2026-07-27T23:47:46+00:00 | Vulnerability · Source |
| CVE-2023-52562 | suse_vex | SUSE CVE CVE-2023-52562 | known not affected: 286 recommended: 199 | 2026-07-27T23:47:36+00:00 | Vulnerability · Source |
| CVE-2023-52760 | suse_vex | SUSE CVE CVE-2023-52760 | known not affected: 283 | 2026-07-27T23:47:28+00:00 | Vulnerability · Source |
| CVE-2023-52991 | suse_vex | SUSE CVE CVE-2023-52991 | known affected: 80 known not affected: 193 recommended: 49 | 2026-07-27T23:47:17+00:00 | Vulnerability · Source |
| CVE-2023-53092 | suse_vex | SUSE CVE CVE-2023-53092 | known affected: 339 known not affected: 239 recommended: 202 | 2026-07-27T23:47:13+00:00 | Vulnerability · Source |
| CVE-2023-53193 | suse_vex | SUSE CVE CVE-2023-53193 | known affected: 359 known not affected: 298 recommended: 111 | 2026-07-27T23:47:11+00:00 | Vulnerability · Source |
| CVE-2023-53253 | suse_vex | SUSE CVE CVE-2023-53253 | known not affected: 345 | 2026-07-27T23:47:09+00:00 | Vulnerability · Source |
| CVE-2023-53301 | suse_vex | SUSE CVE CVE-2023-53301 | known affected: 47 known not affected: 298 | 2026-07-27T23:47:07+00:00 | Vulnerability · Source |
| CVE-2023-53382 | suse_vex | SUSE CVE CVE-2023-53382 | known affected: 49 known not affected: 296 | 2026-07-27T23:47:04+00:00 | Vulnerability · Source |
| CVE-2023-53434 | suse_vex | SUSE CVE CVE-2023-53434 | known not affected: 345 | 2026-07-27T23:47:02+00:00 | Vulnerability · Source |
| CVE-2023-53468 | suse_vex | SUSE CVE CVE-2023-53468 | known affected: 348 known not affected: 245 recommended: 194 | 2026-07-27T23:47:00+00:00 | Vulnerability · Source |
| CVE-2023-53471 | suse_vex | SUSE CVE CVE-2023-53471 | known affected: 383 known not affected: 210 recommended: 215 | 2026-07-27T23:46:59+00:00 | Vulnerability · Source |
| CVE-2023-53482 | suse_vex | SUSE CVE CVE-2023-53482 | known affected: 474 known not affected: 167 recommended: 87 | 2026-07-27T23:46:57+00:00 | Vulnerability · Source |
| CVE-2023-53542 | suse_vex | SUSE CVE CVE-2023-53542 | known affected: 424 known not affected: 160 recommended: 214 | 2026-07-27T23:46:55+00:00 | Vulnerability · Source |
| CVE-2023-53671 | suse_vex | SUSE CVE CVE-2023-53671 | known not affected: 345 recommended: 29 | 2026-07-27T23:46:52+00:00 | Vulnerability · Source |
| CVE-2023-53678 | suse_vex | SUSE CVE CVE-2023-53678 | known not affected: 345 recommended: 49 | 2026-07-27T23:46:51+00:00 | Vulnerability · Source |
| CVE-2023-53712 | suse_vex | SUSE CVE CVE-2023-53712 | known affected: 60 known not affected: 263 | 2026-07-27T23:46:50+00:00 | Vulnerability · Source |
| CVE-2023-53756 | suse_vex | SUSE CVE CVE-2023-53756 | known affected: 165 known not affected: 210 recommended: 29 | 2026-07-27T23:46:48+00:00 | Vulnerability · Source |
| CVE-2023-53758 | suse_vex | SUSE CVE CVE-2023-53758 | known not affected: 337 | 2026-07-27T23:46:46+00:00 | Vulnerability · Source |
| CVE-2023-53993 | suse_vex | SUSE CVE CVE-2023-53993 | known not affected: 378 recommended: 29 | 2026-07-27T23:46:44+00:00 | Vulnerability · Source |
| CVE-2023-54062 | suse_vex | SUSE CVE CVE-2023-54062 | known not affected: 354 recommended: 29 | 2026-07-27T23:46:42+00:00 | Vulnerability · Source |
| CVE-2023-54068 | suse_vex | SUSE CVE CVE-2023-54068 | known affected: 96 known not affected: 258 | 2026-07-27T23:46:40+00:00 | Vulnerability · Source |
| CVE-2023-54124 | suse_vex | SUSE CVE CVE-2023-54124 | known affected: 139 known not affected: 239 | 2026-07-27T23:46:37+00:00 | Vulnerability · Source |