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-49571 | suse_vex | SUSE CVE CVE-2022-49571 | known not affected: 137 | 2026-07-27T23:51:18+00:00 | Vulnerability · Source |
| CVE-2022-49588 | suse_vex | SUSE CVE CVE-2022-49588 | known affected: 49 known not affected: 230 recommended: 27 | 2026-07-27T23:51:16+00:00 | Vulnerability · Source |
| CVE-2022-49593 | suse_vex | SUSE CVE CVE-2022-49593 | known not affected: 137 recommended: 27 | 2026-07-27T23:51:15+00:00 | Vulnerability · Source |
| CVE-2022-49698 | suse_vex | SUSE CVE CVE-2022-49698 | known not affected: 275 recommended: 42 | 2026-07-27T23:51:06+00:00 | Vulnerability · Source |
| CVE-2022-49728 | suse_vex | SUSE CVE CVE-2022-49728 | known affected: 564 known not affected: 112 recommended: 33 | 2026-07-27T23:51:01+00:00 | Vulnerability · Source |
| CVE-2022-49824 | suse_vex | SUSE CVE CVE-2022-49824 | known affected: 339 known not affected: 232 recommended: 269 | 2026-07-27T23:50:52+00:00 | Vulnerability · Source |
| CVE-2022-49829 | suse_vex | SUSE CVE CVE-2022-49829 | known affected: 517 known not affected: 178 recommended: 23 | 2026-07-27T23:50:51+00:00 | Vulnerability · Source |
| CVE-2022-49848 | suse_vex | SUSE CVE CVE-2022-49848 | known not affected: 326 recommended: 27 | 2026-07-27T23:50:49+00:00 | Vulnerability · Source |
| CVE-2022-49856 | suse_vex | SUSE CVE CVE-2022-49856 | known not affected: 326 | 2026-07-27T23:50:47+00:00 | Vulnerability · Source |
| CVE-2022-49876 | suse_vex | SUSE CVE CVE-2022-49876 | known not affected: 326 | 2026-07-27T23:50:46+00:00 | Vulnerability · Source |
| CVE-2022-49914 | suse_vex | SUSE CVE CVE-2022-49914 | known affected: 575 known not affected: 198 recommended: 30 | 2026-07-27T23:50:41+00:00 | Vulnerability · Source |
| CVE-2022-49982 | suse_vex | SUSE CVE CVE-2022-49982 | known affected: 344 known not affected: 311 recommended: 253 | 2026-07-27T23:50:34+00:00 | Vulnerability · Source |
| CVE-2022-49991 | suse_vex | SUSE CVE CVE-2022-49991 | known affected: 49 known not affected: 281 recommended: 27 | 2026-07-27T23:50:33+00:00 | Vulnerability · Source |
| CVE-2022-50001 | suse_vex | SUSE CVE CVE-2022-50001 | known affected: 88 known not affected: 242 recommended: 42 | 2026-07-27T23:50:31+00:00 | Vulnerability · Source |
| CVE-2022-50007 | suse_vex | SUSE CVE CVE-2022-50007 | known affected: 524 known not affected: 224 recommended: 77 | 2026-07-27T23:50:30+00:00 | Vulnerability · Source |
| CVE-2022-50056 | suse_vex | SUSE CVE CVE-2022-50056 | known not affected: 330 | 2026-07-27T23:50:28+00:00 | Vulnerability · Source |
| CVE-2022-50058 | suse_vex | SUSE CVE CVE-2022-50058 | known not affected: 330 recommended: 27 | 2026-07-27T23:50:26+00:00 | Vulnerability · Source |
| CVE-2022-50063 | suse_vex | SUSE CVE CVE-2022-50063 | known not affected: 330 | 2026-07-27T23:50:25+00:00 | Vulnerability · Source |
| CVE-2022-50104 | suse_vex | SUSE CVE CVE-2022-50104 | known affected: 376 known not affected: 194 recommended: 284 | 2026-07-27T23:50:23+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-50326 | suse_vex | SUSE CVE CVE-2022-50326 | known not affected: 345 recommended: 27 | 2026-07-27T23:50:06+00:00 | Vulnerability · Source |
| CVE-2022-50363 | suse_vex | SUSE CVE CVE-2022-50363 | known not affected: 345 recommended: 27 | 2026-07-27T23:50:04+00:00 | Vulnerability · Source |
| CVE-2022-50366 | suse_vex | SUSE CVE CVE-2022-50366 | known affected: 166 known not affected: 160 | 2026-07-27T23:50:02+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-50519 | suse_vex | SUSE CVE CVE-2022-50519 | known affected: 397 known not affected: 259 recommended: 191 | 2026-07-27T23:49:45+00:00 | Vulnerability · Source |
| CVE-2022-50554 | suse_vex | SUSE CVE CVE-2022-50554 | known affected: 135 known not affected: 191 recommended: 47 | 2026-07-27T23:49:40+00:00 | Vulnerability · Source |
| CVE-2022-50558 | suse_vex | SUSE CVE CVE-2022-50558 | known not affected: 336 recommended: 29 | 2026-07-27T23:49:38+00:00 | Vulnerability · Source |
| CVE-2022-50620 | suse_vex | SUSE CVE CVE-2022-50620 | known not affected: 337 | 2026-07-27T23:49:35+00:00 | Vulnerability · Source |
| CVE-2022-50621 | suse_vex | SUSE CVE CVE-2022-50621 | known affected: 374 known not affected: 349 recommended: 87 | 2026-07-27T23:49:34+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-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 |