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-20119 | suse_vex | SUSE CVE CVE-2022-20119 | known not affected: 390 | 2026-07-28T23:52:46+00:00 | Vulnerability · Source |
| CVE-2022-21626 | suse_vex | SUSE CVE CVE-2022-21626 | known affected: 396 recommended: 1016 | 2026-07-28T23:52:40+00:00 | Vulnerability · Source |
| CVE-2022-21713 | suse_vex | SUSE CVE CVE-2022-21713 | recommended: 164 | 2026-07-28T23:52:38+00:00 | Vulnerability · Source |
| CVE-2022-22075 | suse_vex | SUSE CVE CVE-2022-22075 | known not affected: 288 | 2026-07-28T23:52:37+00:00 | Vulnerability · Source |
| CVE-2022-25255 | suse_vex | SUSE CVE CVE-2022-25255 | known affected: 394 known not affected: 1379 recommended: 2383 | 2026-07-28T23:52:29+00:00 | Vulnerability · Source |
| CVE-2022-25883 | suse_vex | SUSE CVE CVE-2022-25883 | known not affected: 284 recommended: 33 | 2026-07-28T23:52:27+00:00 | Vulnerability · Source |
| CVE-2022-26361 | suse_vex | SUSE CVE CVE-2022-26361 | known not affected: 46 recommended: 393 | 2026-07-28T23:52:26+00:00 | Vulnerability · Source |
| CVE-2022-27950 | suse_vex | SUSE CVE CVE-2022-27950 | known not affected: 405 recommended: 20 | 2026-07-28T23:52:22+00:00 | Vulnerability · Source |
| CVE-2022-28350 | suse_vex | SUSE CVE CVE-2022-28350 | known not affected: 390 | 2026-07-28T23:52:21+00:00 | Vulnerability · Source |
| CVE-2022-29458 | suse_vex | SUSE CVE CVE-2022-29458 | known affected: 490 known not affected: 1 recommended: 734 | 2026-07-28T23:52:16+00:00 | Vulnerability · Source |
| CVE-2022-31739 | suse_vex | SUSE CVE CVE-2022-31739 | known not affected: 1 recommended: 399 | 2026-07-28T23:52:13+00:00 | Vulnerability · Source |
| CVE-2022-33108 | suse_vex | SUSE CVE CVE-2022-33108 | known not affected: 330 | 2026-07-28T23:52:10+00:00 | Vulnerability · Source |
| CVE-2022-33746 | suse_vex | SUSE CVE CVE-2022-33746 | known affected: 252 recommended: 517 | 2026-07-28T23:52:08+00:00 | Vulnerability · Source |
| CVE-2022-33967 | suse_vex | SUSE CVE CVE-2022-33967 | known not affected: 60 recommended: 344 | 2026-07-28T23:52:06+00:00 | Vulnerability · Source |
| CVE-2022-41808 | suse_vex | SUSE CVE CVE-2022-41808 | known not affected: 416 | 2026-07-28T23:52:01+00:00 | Vulnerability · Source |
| CVE-2022-42012 | suse_vex | SUSE CVE CVE-2022-42012 | known affected: 254 recommended: 529 | 2026-07-28T23:51:59+00:00 | Vulnerability · Source |
| CVE-2022-42333 | suse_vex | SUSE CVE CVE-2022-42333 | known affected: 287 known not affected: 43 recommended: 376 | 2026-07-28T23:51:57+00:00 | Vulnerability · Source |
| CVE-2022-43680 | suse_vex | SUSE CVE CVE-2022-43680 | known affected: 238 recommended: 470 | 2026-07-28T23:51:55+00:00 | Vulnerability · Source |
| CVE-2022-46343 | suse_vex | SUSE CVE CVE-2022-46343 | known affected: 395 recommended: 309 | 2026-07-28T23:51:51+00:00 | Vulnerability · Source |
| CVE-2022-47010 | suse_vex | SUSE CVE CVE-2022-47010 | known affected: 10 known not affected: 224 | 2026-07-28T23:51:50+00:00 | Vulnerability · Source |
| CVE-2022-47112 | suse_vex | SUSE CVE CVE-2022-47112 | known affected: 93 | 2026-07-28T23:51:48+00:00 | Vulnerability · Source |
| CVE-2022-47940 | suse_vex | SUSE CVE CVE-2022-47940 | known not affected: 362 | 2026-07-28T23:51:47+00:00 | Vulnerability · Source |
| CVE-2022-48832 | suse_vex | SUSE CVE CVE-2022-48832 | known not affected: 318 | 2026-07-28T23:51:39+00:00 | Vulnerability · Source |
| CVE-2022-48845 | suse_vex | SUSE CVE CVE-2022-48845 | known not affected: 318 | 2026-07-28T23:51:37+00:00 | Vulnerability · Source |
| CVE-2022-48904 | suse_vex | SUSE CVE CVE-2022-48904 | known affected: 310 known not affected: 195 recommended: 431 | 2026-07-28T23:51:35+00:00 | Vulnerability · Source |
| CVE-2022-48950 | suse_vex | SUSE CVE CVE-2022-48950 | known not affected: 402 recommended: 29 | 2026-07-28T23:51:33+00:00 | Vulnerability · Source |
| CVE-2022-49018 | suse_vex | SUSE CVE CVE-2022-49018 | known not affected: 379 | 2026-07-28T23:51:30+00:00 | Vulnerability · Source |
| CVE-2022-49172 | suse_vex | SUSE CVE CVE-2022-49172 | known not affected: 352 | 2026-07-28T23:51:20+00:00 | Vulnerability · Source |
| CVE-2022-49231 | suse_vex | SUSE CVE CVE-2022-49231 | known not affected: 352 | 2026-07-28T23:51:15+00:00 | Vulnerability · Source |
| CVE-2022-49435 | suse_vex | SUSE CVE CVE-2022-49435 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-28T23:51:09+00:00 | Vulnerability · Source |
| CVE-2022-49454 | suse_vex | SUSE CVE CVE-2022-49454 | known not affected: 352 | 2026-07-28T23:51:06+00:00 | Vulnerability · Source |
| CVE-2022-49558 | suse_vex | SUSE CVE CVE-2022-49558 | known affected: 55 known not affected: 297 | 2026-07-28T23:51:01+00:00 | Vulnerability · Source |
| CVE-2022-49612 | suse_vex | SUSE CVE CVE-2022-49612 | known not affected: 352 recommended: 27 | 2026-07-28T23:50:59+00:00 | Vulnerability · Source |
| CVE-2022-49633 | suse_vex | SUSE CVE CVE-2022-49633 | known affected: 112 known not affected: 240 | 2026-07-28T23:50:56+00:00 | Vulnerability · Source |
| CVE-2022-49669 | suse_vex | SUSE CVE CVE-2022-49669 | known not affected: 352 recommended: 42 | 2026-07-28T23:50:52+00:00 | Vulnerability · Source |
| CVE-2022-49744 | suse_vex | SUSE CVE CVE-2022-49744 | known not affected: 344 recommended: 29 | 2026-07-28T23:50:47+00:00 | Vulnerability · Source |
| CVE-2022-49805 | suse_vex | SUSE CVE CVE-2022-49805 | known not affected: 397 | 2026-07-28T23:50:45+00:00 | Vulnerability · Source |
| CVE-2022-49920 | suse_vex | SUSE CVE CVE-2022-49920 | known affected: 55 known not affected: 342 recommended: 27 | 2026-07-28T23:50:35+00:00 | Vulnerability · Source |
| 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 |