VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286723 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-0158 | suse_vex | SUSE CVE CVE-2022-0158 | known not affected: 230 | 2026-07-28T23:53:25+00:00 | Vulnerability · Source |
| CVE-2022-0487 | suse_vex | SUSE CVE CVE-2022-0487 | known affected: 230 known not affected: 76 recommended: 1590 | 2026-07-28T23:53:23+00:00 | Vulnerability · Source |
| CVE-2022-0854 | suse_vex | SUSE CVE CVE-2022-0854 | known affected: 149 known not affected: 244 recommended: 1266 | 2026-07-28T23:53:21+00:00 | Vulnerability · Source |
| CVE-2022-1050 | suse_vex | SUSE CVE CVE-2022-1050 | known affected: 415 known not affected: 499 recommended: 1363 | 2026-07-28T23:53:19+00:00 | Vulnerability · Source |
| CVE-2022-1205 | suse_vex | SUSE CVE CVE-2022-1205 | known affected: 216 known not affected: 280 recommended: 1020 | 2026-07-28T23:53:17+00:00 | Vulnerability · Source |
| CVE-2022-1972 | suse_vex | SUSE CVE CVE-2022-1972 | known affected: 222 known not affected: 268 recommended: 1149 | 2026-07-28T23:53:13+00:00 | Vulnerability · Source |
| CVE-2022-2127 | suse_vex | SUSE CVE CVE-2022-2127 | known affected: 394 recommended: 2237 | 2026-07-28T23:53:11+00:00 | Vulnerability · Source |
| CVE-2022-2208 | suse_vex | SUSE CVE CVE-2022-2208 | known affected: 237 known not affected: 26 recommended: 505 | 2026-07-28T23:53:10+00:00 | Vulnerability · Source |
| CVE-2022-2288 | suse_vex | SUSE CVE CVE-2022-2288 | known not affected: 257 recommended: 21 | 2026-07-28T23:53:08+00:00 | Vulnerability · Source |
| CVE-2022-2344 | suse_vex | SUSE CVE CVE-2022-2344 | known affected: 237 known not affected: 2 recommended: 505 | 2026-07-28T23:53:06+00:00 | Vulnerability · Source |
| CVE-2022-2785 | suse_vex | SUSE CVE CVE-2022-2785 | known not affected: 327 | 2026-07-28T23:53:05+00:00 | Vulnerability · Source |
| CVE-2022-3153 | suse_vex | SUSE CVE CVE-2022-3153 | known affected: 259 known not affected: 2 recommended: 485 | 2026-07-28T23:53:03+00:00 | Vulnerability · Source |
| CVE-2022-3213 | suse_vex | SUSE CVE CVE-2022-3213 | known not affected: 344 recommended: 322 | 2026-07-28T23:53:01+00:00 | Vulnerability · Source |
| CVE-2022-3256 | suse_vex | SUSE CVE CVE-2022-3256 | known not affected: 240 | 2026-07-28T23:53:00+00:00 | Vulnerability · Source |
| CVE-2022-3524 | suse_vex | SUSE CVE CVE-2022-3524 | known affected: 255 known not affected: 123 recommended: 1540 | 2026-07-28T23:52:58+00:00 | Vulnerability · Source |
| CVE-2022-3551 | suse_vex | SUSE CVE CVE-2022-3551 | known affected: 395 recommended: 288 | 2026-07-28T23:52:55+00:00 | Vulnerability · Source |
| CVE-2022-4293 | suse_vex | SUSE CVE CVE-2022-4293 | known affected: 267 known not affected: 26 recommended: 417 | 2026-07-28T23:52:49+00:00 | Vulnerability · Source |
| CVE-2022-20117 | suse_vex | SUSE CVE CVE-2022-20117 | known not affected: 390 | 2026-07-28T23:52:47+00:00 | Vulnerability · Source |
| 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-20132 | suse_vex | SUSE CVE CVE-2022-20132 | known affected: 219 recommended: 1558 | 2026-07-28T23:52:44+00:00 | Vulnerability · Source |
| CVE-2022-21299 | suse_vex | SUSE CVE CVE-2022-21299 | known affected: 406 known not affected: 32 recommended: 1099 | 2026-07-28T23:52:42+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-22628 | suse_vex | SUSE CVE CVE-2022-22628 | known affected: 24 known not affected: 374 recommended: 952 | 2026-07-28T23:52:35+00:00 | Vulnerability · Source |
| CVE-2022-22826 | suse_vex | SUSE CVE CVE-2022-22826 | known affected: 330 known not affected: 32 recommended: 384 | 2026-07-28T23:52:34+00:00 | Vulnerability · Source |
| CVE-2022-24713 | suse_vex | SUSE CVE CVE-2022-24713 | known affected: 620 known not affected: 882 recommended: 610 | 2026-07-28T23:52:31+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-27239 | suse_vex | SUSE CVE CVE-2022-27239 | known affected: 209 known not affected: 3 recommended: 350 | 2026-07-28T23:52:24+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-28893 | suse_vex | SUSE CVE CVE-2022-28893 | known affected: 357 known not affected: 278 recommended: 935 | 2026-07-28T23:52:19+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-31740 | suse_vex | SUSE CVE CVE-2022-31740 | known not affected: 1 recommended: 405 | 2026-07-28T23:52:11+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-37290 | suse_vex | SUSE CVE CVE-2022-37290 | known affected: 94 recommended: 268 | 2026-07-28T23:52:04+00:00 | Vulnerability · Source |
| CVE-2022-40768 | suse_vex | SUSE CVE CVE-2022-40768 | known affected: 255 known not affected: 123 recommended: 1493 | 2026-07-28T23:52:02+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-45063 | suse_vex | SUSE CVE CVE-2022-45063 | known affected: 401 recommended: 112 | 2026-07-28T23:51:53+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 |