VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
293841 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2021-47526 | suse_vex | SUSE CVE CVE-2021-47526 | known affected: 275 known not affected: 176 recommended: 440 | 2026-07-27T23:54:17+00:00 | Vulnerability · Source |
| CVE-2022-2590 | suse_vex | SUSE CVE CVE-2022-2590 | known not affected: 274 recommended: 6 | 2026-07-27T23:53:42+00:00 | Vulnerability · Source |
| CVE-2022-21597 | suse_vex | SUSE CVE CVE-2022-21597 | known not affected: 426 | 2026-07-27T23:53:24+00:00 | Vulnerability · Source |
| CVE-2022-23133 | suse_vex | SUSE CVE CVE-2022-23133 | known not affected: 28 | 2026-07-27T23:53:20+00:00 | Vulnerability · Source |
| CVE-2022-23493 | suse_vex | SUSE CVE CVE-2022-23493 | known affected: 375 known not affected: 45 recommended: 170 | 2026-07-27T23:53:16+00:00 | Vulnerability · Source |
| CVE-2022-34568 | suse_vex | SUSE CVE CVE-2022-34568 | known not affected: 226 recommended: 2 | 2026-07-27T23:52:53+00:00 | Vulnerability · Source |
| CVE-2022-38126 | suse_vex | SUSE CVE CVE-2022-38126 | known affected: 395 known not affected: 1 recommended: 445 | 2026-07-27T23:52:48+00:00 | Vulnerability · Source |
| CVE-2022-44268 | suse_vex | SUSE CVE CVE-2022-44268 | known affected: 45 known not affected: 12 recommended: 534 | 2026-07-27T23:52:39+00:00 | Vulnerability · Source |
| CVE-2022-48867 | suse_vex | SUSE CVE CVE-2022-48867 | known not affected: 263 | 2026-07-27T23:52:20+00:00 | Vulnerability · Source |
| CVE-2022-48876 | suse_vex | SUSE CVE CVE-2022-48876 | known not affected: 264 | 2026-07-27T23:52:15+00:00 | Vulnerability · Source |
| CVE-2022-49391 | suse_vex | SUSE CVE CVE-2022-49391 | known not affected: 279 | 2026-07-27T23:51:31+00:00 | Vulnerability · Source |
| CVE-2022-49405 | suse_vex | SUSE CVE CVE-2022-49405 | known not affected: 279 | 2026-07-27T23:51:29+00:00 | Vulnerability · Source |
| CVE-2022-49415 | suse_vex | SUSE CVE CVE-2022-49415 | known not affected: 279 | 2026-07-27T23:51:25+00:00 | Vulnerability · Source |
| CVE-2022-50168 | suse_vex | SUSE CVE CVE-2022-50168 | known affected: 47 known not affected: 298 recommended: 27 | 2026-07-27T23:50:17+00:00 | Vulnerability · Source |
| CVE-2022-50313 | suse_vex | SUSE CVE CVE-2022-50313 | known affected: 88 known not affected: 257 recommended: 29 | 2026-07-27T23:50:08+00:00 | Vulnerability · Source |
| CVE-2022-50380 | suse_vex | SUSE CVE CVE-2022-50380 | known not affected: 345 | 2026-07-27T23:49:57+00:00 | Vulnerability · Source |
| CVE-2022-50412 | suse_vex | SUSE CVE CVE-2022-50412 | known affected: 429 known not affected: 184 recommended: 198 | 2026-07-27T23:49:53+00:00 | Vulnerability · Source |
| 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-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-4208 | suse_vex | SUSE CVE CVE-2023-4208 | recommended: 62 | 2026-07-27T23:48:59+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-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-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-46047 | suse_vex | SUSE CVE CVE-2023-46047 | known affected: 125 | 2026-07-27T23:47:46+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-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-53758 | suse_vex | SUSE CVE CVE-2023-53758 | known not affected: 337 | 2026-07-27T23:46:46+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 |
| CVE-2024-11700 | suse_vex | SUSE CVE CVE-2024-11700 | known affected: 29 recommended: 5 | 2026-07-27T23:46:14+00:00 | Vulnerability · Source |
| CVE-2026-12413 | suse_vex | SUSE CVE CVE-2026-12413 | recommended: 4 | 2026-07-27T23:42:27+00:00 | Vulnerability · Source |
| CVE-2026-12892 | suse_vex | SUSE CVE CVE-2026-12892 | first fixed: 132 known affected: 181 known not affected: 83 recommended: 607 | 2026-07-27T23:42:23+00:00 | Vulnerability · Source |
| CVE-2026-23168 | suse_vex | SUSE CVE CVE-2026-23168 | first fixed: 2 known affected: 77 known not affected: 200 recommended: 337 | 2026-07-27T23:42:05+00:00 | Vulnerability · Source |
| CVE-2026-23193 | suse_vex | SUSE CVE CVE-2026-23193 | first fixed: 2 known affected: 631 known not affected: 4 recommended: 450 | 2026-07-27T23:42:03+00:00 | Vulnerability · Source |
| CVE-2026-23455 | suse_vex | SUSE CVE CVE-2026-23455 | first fixed: 2 known affected: 222 recommended: 448 | 2026-07-27T23:41:47+00:00 | Vulnerability · Source |
| CVE-2026-25547 | suse_vex | SUSE CVE CVE-2026-25547 | first fixed: 36 known affected: 552 known not affected: 255 recommended: 394 | 2026-07-27T23:41:42+00:00 | Vulnerability · Source |
| CVE-2026-26996 | suse_vex | SUSE CVE CVE-2026-26996 | first fixed: 36 known affected: 512 known not affected: 254 recommended: 214 | 2026-07-27T23:41:38+00:00 | Vulnerability · Source |
| CVE-2026-31505 | suse_vex | SUSE CVE CVE-2026-31505 | first fixed: 26 known affected: 411 known not affected: 138 recommended: 525 | 2026-07-27T23:41:17+00:00 | Vulnerability · Source |
| CVE-2026-31533 | suse_vex | SUSE CVE CVE-2026-31533 | first fixed: 26 known affected: 442 known not affected: 67 recommended: 631 | 2026-07-27T23:41:15+00:00 | Vulnerability · Source |
| CVE-2026-31586 | suse_vex | SUSE CVE CVE-2026-31586 | first fixed: 26 known affected: 507 known not affected: 4 recommended: 635 | 2026-07-27T23:41:09+00:00 | Vulnerability · Source |
| CVE-2026-50721 | suse_vex | SUSE CVE CVE-2026-50721 | recommended: 4 | 2026-07-27T23:37:16+00:00 | Vulnerability · Source |
| CVE-2026-50722 | suse_vex | SUSE CVE CVE-2026-50722 | recommended: 4 | 2026-07-27T23:37:15+00:00 | Vulnerability · Source |
| CVE-2026-52950 | suse_vex | SUSE CVE CVE-2026-52950 | known affected: 72 known not affected: 223 | 2026-07-27T23:36:56+00:00 | Vulnerability · Source |
| CVE-2026-53702 | suse_vex | SUSE CVE CVE-2026-53702 | first fixed: 274 known affected: 827 | 2026-07-27T23:36:06+00:00 | Vulnerability · Source |