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-2022-49953 | suse_vex | SUSE CVE CVE-2022-49953 | known not affected: 401 | 2026-07-28T23:50:32+00:00 | Vulnerability · Source |
| CVE-2022-49974 | suse_vex | SUSE CVE CVE-2022-49974 | known not affected: 401 recommended: 27 | 2026-07-28T23:50:31+00:00 | Vulnerability · Source |
| CVE-2022-50040 | suse_vex | SUSE CVE CVE-2022-50040 | known affected: 344 known not affected: 298 recommended: 206 | 2026-07-28T23:50:27+00:00 | Vulnerability · Source |
| CVE-2022-50181 | suse_vex | SUSE CVE CVE-2022-50181 | known affected: 419 known not affected: 254 recommended: 357 | 2026-07-28T23:50:18+00:00 | Vulnerability · Source |
| CVE-2022-50291 | suse_vex | SUSE CVE CVE-2022-50291 | known affected: 604 known not affected: 176 recommended: 23 | 2026-07-28T23:50:11+00:00 | Vulnerability · Source |
| CVE-2022-50335 | suse_vex | SUSE CVE CVE-2022-50335 | known affected: 106 known not affected: 310 | 2026-07-28T23:50:10+00:00 | Vulnerability · Source |
| CVE-2022-50463 | suse_vex | SUSE CVE CVE-2022-50463 | known not affected: 416 | 2026-07-28T23:50:00+00:00 | Vulnerability · Source |
| CVE-2022-50467 | suse_vex | SUSE CVE CVE-2022-50467 | known affected: 425 known not affected: 154 recommended: 320 | 2026-07-28T23:49:58+00:00 | Vulnerability · Source |
| CVE-2022-50501 | suse_vex | SUSE CVE CVE-2022-50501 | known affected: 472 known not affected: 187 recommended: 233 | 2026-07-28T23:49:55+00:00 | Vulnerability · Source |
| CVE-2022-50555 | suse_vex | SUSE CVE CVE-2022-50555 | known affected: 106 known not affected: 310 recommended: 47 | 2026-07-28T23:49:50+00:00 | Vulnerability · Source |
| CVE-2022-50648 | suse_vex | SUSE CVE CVE-2022-50648 | known not affected: 408 | 2026-07-28T23:49:45+00:00 | Vulnerability · Source |
| CVE-2022-50854 | suse_vex | SUSE CVE CVE-2022-50854 | known affected: 112 known not affected: 341 | 2026-07-28T23:49:36+00:00 | Vulnerability · Source |
| CVE-2022-50874 | suse_vex | SUSE CVE CVE-2022-50874 | known not affected: 453 | 2026-07-28T23:49:35+00:00 | Vulnerability · Source |
| CVE-2023-0634 | suse_vex | SUSE CVE CVE-2023-0634 | known not affected: 62 | 2026-07-28T23:49:33+00:00 | Vulnerability · Source |
| CVE-2023-2602 | suse_vex | SUSE CVE CVE-2023-2602 | known affected: 166 known not affected: 217 recommended: 387 | 2026-07-28T23:49:28+00:00 | Vulnerability · Source |
| CVE-2023-3022 | suse_vex | SUSE CVE CVE-2023-3022 | known not affected: 389 | 2026-07-28T23:49:25+00:00 | Vulnerability · Source |
| CVE-2023-3153 | suse_vex | SUSE CVE CVE-2023-3153 | known affected: 1 known not affected: 55 recommended: 353 | 2026-07-28T23:49:23+00:00 | Vulnerability · Source |
| CVE-2023-3301 | suse_vex | SUSE CVE CVE-2023-3301 | known affected: 394 known not affected: 454 recommended: 1488 | 2026-07-28T23:49:21+00:00 | Vulnerability · Source |
| CVE-2023-3576 | suse_vex | SUSE CVE CVE-2023-3576 | known affected: 515 recommended: 102 | 2026-07-28T23:49:19+00:00 | Vulnerability · Source |
| CVE-2023-3648 | suse_vex | SUSE CVE CVE-2023-3648 | known affected: 1 known not affected: 91 recommended: 192 | 2026-07-28T23:49:18+00:00 | Vulnerability · Source |
| CVE-2023-4255 | suse_vex | SUSE CVE CVE-2023-4255 | known affected: 406 known not affected: 38 recommended: 5 | 2026-07-28T23:49:13+00:00 | Vulnerability · Source |
| CVE-2023-4575 | suse_vex | SUSE CVE CVE-2023-4575 | known affected: 49 recommended: 292 | 2026-07-28T23:49:11+00:00 | Vulnerability · Source |
| CVE-2023-4732 | suse_vex | SUSE CVE CVE-2023-4732 | known not affected: 363 recommended: 20 | 2026-07-28T23:49:09+00:00 | Vulnerability · Source |
| CVE-2023-6349 | suse_vex | SUSE CVE CVE-2023-6349 | known affected: 110 known not affected: 7 recommended: 96 | 2026-07-28T23:49:04+00:00 | Vulnerability · Source |
| CVE-2023-23002 | suse_vex | SUSE CVE CVE-2023-23002 | known not affected: 288 | 2026-07-28T23:48:59+00:00 | Vulnerability · Source |
| CVE-2023-25434 | suse_vex | SUSE CVE CVE-2023-25434 | known not affected: 191 | 2026-07-28T23:48:54+00:00 | Vulnerability · Source |
| CVE-2023-25743 | suse_vex | SUSE CVE CVE-2023-25743 | known affected: 1 recommended: 245 | 2026-07-28T23:48:52+00:00 | Vulnerability · Source |
| CVE-2023-26464 | suse_vex | SUSE CVE CVE-2023-26464 | known not affected: 225 | 2026-07-28T23:48:49+00:00 | Vulnerability · Source |
| CVE-2023-27478 | suse_vex | SUSE CVE CVE-2023-27478 | known not affected: 171 | 2026-07-28T23:48:48+00:00 | Vulnerability · Source |
| CVE-2023-29935 | suse_vex | SUSE CVE CVE-2023-29935 | known not affected: 1268 | 2026-07-28T23:48:43+00:00 | Vulnerability · Source |
| CVE-2023-38429 | suse_vex | SUSE CVE CVE-2023-38429 | known not affected: 361 | 2026-07-28T23:48:39+00:00 | Vulnerability · Source |
| CVE-2023-39191 | suse_vex | SUSE CVE CVE-2023-39191 | known affected: 275 known not affected: 282 recommended: 417 | 2026-07-28T23:48:37+00:00 | Vulnerability · Source |
| CVE-2023-46218 | suse_vex | SUSE CVE CVE-2023-46218 | known affected: 299 known not affected: 38 recommended: 362 | 2026-07-28T23:48:29+00:00 | Vulnerability · Source |
| CVE-2023-51767 | suse_vex | SUSE CVE CVE-2023-51767 | known affected: 84 | 2026-07-28T23:48:25+00:00 | Vulnerability · Source |
| CVE-2023-52689 | suse_vex | SUSE CVE CVE-2023-52689 | known not affected: 330 recommended: 59 | 2026-07-28T23:48:11+00:00 | Vulnerability · Source |
| CVE-2023-52895 | suse_vex | SUSE CVE CVE-2023-52895 | known not affected: 311 | 2026-07-28T23:48:03+00:00 | Vulnerability · Source |
| CVE-2023-52897 | suse_vex | SUSE CVE CVE-2023-52897 | known not affected: 310 | 2026-07-28T23:48:01+00:00 | Vulnerability · Source |
| CVE-2023-52905 | suse_vex | SUSE CVE CVE-2023-52905 | known affected: 310 known not affected: 195 recommended: 438 | 2026-07-28T23:48:00+00:00 | Vulnerability · Source |
| CVE-2023-53003 | suse_vex | SUSE CVE CVE-2023-53003 | known affected: 106 known not affected: 238 | 2026-07-28T23:47:58+00:00 | Vulnerability · Source |
| CVE-2023-53124 | suse_vex | SUSE CVE CVE-2023-53124 | known affected: 376 known not affected: 230 recommended: 300 | 2026-07-28T23:47:54+00:00 | Vulnerability · Source |
| CVE-2023-53236 | suse_vex | SUSE CVE CVE-2023-53236 | known not affected: 416 | 2026-07-28T23:47:52+00:00 | Vulnerability · Source |
| CVE-2023-53241 | suse_vex | SUSE CVE CVE-2023-53241 | known affected: 395 known not affected: 253 recommended: 255 | 2026-07-28T23:47:50+00:00 | Vulnerability · Source |
| CVE-2023-53294 | suse_vex | SUSE CVE CVE-2023-53294 | known not affected: 416 | 2026-07-28T23:47:48+00:00 | Vulnerability · Source |
| CVE-2023-53407 | suse_vex | SUSE CVE CVE-2023-53407 | known affected: 354 known not affected: 306 recommended: 196 | 2026-07-28T23:47:46+00:00 | Vulnerability · Source |
| CVE-2023-53716 | suse_vex | SUSE CVE CVE-2023-53716 | known affected: 374 known not affected: 350 recommended: 116 | 2026-07-28T23:47:42+00:00 | Vulnerability · Source |
| CVE-2023-53720 | suse_vex | SUSE CVE CVE-2023-53720 | known not affected: 407 | 2026-07-28T23:47:40+00:00 | Vulnerability · Source |
| CVE-2023-53760 | suse_vex | SUSE CVE CVE-2023-53760 | known not affected: 408 recommended: 29 | 2026-07-28T23:47:38+00:00 | Vulnerability · Source |
| CVE-2023-53788 | suse_vex | SUSE CVE CVE-2023-53788 | known affected: 476 known not affected: 187 recommended: 233 | 2026-07-28T23:47:37+00:00 | Vulnerability · Source |
| CVE-2023-53820 | suse_vex | SUSE CVE CVE-2023-53820 | known affected: 427 known not affected: 265 recommended: 196 | 2026-07-28T23:47:35+00:00 | Vulnerability · Source |
| CVE-2023-53867 | suse_vex | SUSE CVE CVE-2023-53867 | known affected: 234 known not affected: 187 recommended: 29 | 2026-07-28T23:47:33+00:00 | Vulnerability · Source |