VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
100569 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-38472 | suse_vex | SUSE CVE CVE-2022-38472 | known affected: 2 recommended: 461 | 2026-10-16T14:45:00+00:00 | Vulnerability · Source |
| CVE-2022-38478 | suse_vex | SUSE CVE CVE-2022-38478 | known affected: 2 recommended: 461 | 2026-10-16T14:44:58+00:00 | Vulnerability · Source |
| CVE-2022-38528 | suse_vex | SUSE CVE CVE-2022-38528 | recommended: 6 | 2026-10-16T14:44:56+00:00 | Vulnerability · Source |
| CVE-2022-38533 | suse_vex | SUSE CVE CVE-2022-38533 | known affected: 394 recommended: 462 | 2026-10-16T14:44:54+00:00 | Vulnerability · Source |
| CVE-2022-38648 | suse_vex | SUSE CVE CVE-2022-38648 | recommended: 132 | 2026-10-16T14:44:51+00:00 | Vulnerability · Source |
| CVE-2022-38749 | suse_vex | SUSE CVE CVE-2022-38749 | known affected: 400 recommended: 51 | 2026-10-16T14:44:49+00:00 | Vulnerability · Source |
| CVE-2022-38750 | suse_vex | SUSE CVE CVE-2022-38750 | known affected: 400 recommended: 51 | 2026-10-16T14:44:47+00:00 | Vulnerability · Source |
| CVE-2022-38752 | suse_vex | SUSE CVE CVE-2022-38752 | known affected: 400 recommended: 61 | 2026-10-16T14:44:44+00:00 | Vulnerability · Source |
| CVE-2022-39188 | suse_vex | SUSE CVE CVE-2022-39188 | known affected: 237 known not affected: 308 recommended: 1825 | 2026-10-16T14:44:41+00:00 | Vulnerability · Source |
| CVE-2022-39190 | suse_vex | SUSE CVE CVE-2022-39190 | known affected: 237 known not affected: 243 recommended: 1036 | 2026-10-16T14:44:39+00:00 | Vulnerability · Source |
| CVE-2022-39253 | suse_vex | SUSE CVE CVE-2022-39253 | known affected: 88 known not affected: 135 recommended: 683 | 2026-10-16T14:44:36+00:00 | Vulnerability · Source |
| CVE-2022-39260 | suse_vex | SUSE CVE CVE-2022-39260 | known affected: 88 known not affected: 135 recommended: 674 | 2026-10-16T14:44:33+00:00 | Vulnerability · Source |
| CVE-2022-39282 | suse_vex | SUSE CVE CVE-2022-39282 | recommended: 224 | 2026-10-16T14:44:31+00:00 | Vulnerability · Source |
| CVE-2022-39318 | suse_vex | SUSE CVE CVE-2022-39318 | recommended: 214 | 2026-10-16T14:44:28+00:00 | Vulnerability · Source |
| CVE-2022-39319 | suse_vex | SUSE CVE CVE-2022-39319 | recommended: 214 | 2026-10-16T14:44:25+00:00 | Vulnerability · Source |
| CVE-2022-39377 | suse_vex | SUSE CVE CVE-2022-39377 | known affected: 394 known not affected: 110 recommended: 41 | 2026-10-16T14:44:23+00:00 | Vulnerability · Source |
| CVE-2022-39842 | suse_vex | SUSE CVE CVE-2022-39842 | known affected: 0 known not affected: 566 | 2026-10-16T14:44:20+00:00 | Vulnerability · Source |
| CVE-2022-40023 | suse_vex | SUSE CVE CVE-2022-40023 | known affected: 24 recommended: 61 | 2026-10-16T14:44:17+00:00 | Vulnerability · Source |
| CVE-2022-40303 | suse_vex | SUSE CVE CVE-2022-40303 | known affected: 254 known not affected: 97 recommended: 586 | 2026-10-16T14:44:15+00:00 | Vulnerability · Source |
| CVE-2022-40304 | suse_vex | SUSE CVE CVE-2022-40304 | known affected: 254 known not affected: 96 recommended: 590 | 2026-10-16T14:44:12+00:00 | Vulnerability · Source |
| CVE-2022-40307 | suse_vex | SUSE CVE CVE-2022-40307 | known affected: 395 known not affected: 39 recommended: 458 | 2026-10-16T14:44:09+00:00 | Vulnerability · Source |
| CVE-2022-40674 | suse_vex | SUSE CVE CVE-2022-40674 | known affected: 217 recommended: 500 | 2026-10-16T14:44:06+00:00 | Vulnerability · Source |
| CVE-2022-40755 | suse_vex | SUSE CVE CVE-2022-40755 | known affected: 0 known not affected: 160 recommended: 28 | 2026-10-16T14:44:03+00:00 | Vulnerability · Source |
| CVE-2022-40768 | suse_vex | SUSE CVE CVE-2022-40768 | known affected: 255 recommended: 1464 | 2026-10-16T14:44:01+00:00 | Vulnerability · Source |
| CVE-2022-40898 | suse_vex | SUSE CVE CVE-2022-40898 | known affected: 394 recommended: 96 | 2026-10-16T14:43:59+00:00 | Vulnerability · Source |
| CVE-2022-40958 | suse_vex | SUSE CVE CVE-2022-40958 | known affected: 1 recommended: 437 | 2026-10-16T14:43:56+00:00 | Vulnerability · Source |
| CVE-2022-41218 | suse_vex | SUSE CVE CVE-2022-41218 | known affected: 253 recommended: 352 | 2026-10-16T14:43:54+00:00 | Vulnerability · Source |
| CVE-2022-41222 | suse_vex | SUSE CVE CVE-2022-41222 | known affected: 376 known not affected: 498 recommended: 692 | 2026-10-16T14:43:51+00:00 | Vulnerability · Source |
| CVE-2022-41674 | suse_vex | SUSE CVE CVE-2022-41674 | known affected: 253 known not affected: 207 recommended: 1374 | 2026-10-16T14:43:48+00:00 | Vulnerability · Source |
| CVE-2022-41704 | suse_vex | SUSE CVE CVE-2022-41704 | recommended: 89 | 2026-10-16T14:43:46+00:00 | Vulnerability · Source |
| CVE-2022-41849 | suse_vex | SUSE CVE CVE-2022-41849 | known affected: 253 known not affected: 199 recommended: 1096 | 2026-10-16T14:43:43+00:00 | Vulnerability · Source |
| CVE-2022-41850 | suse_vex | SUSE CVE CVE-2022-41850 | known affected: 269 recommended: 1513 | 2026-10-16T14:43:40+00:00 | Vulnerability · Source |
| CVE-2022-41860 | suse_vex | SUSE CVE CVE-2022-41860 | known affected: 1 recommended: 787 | 2026-10-16T14:43:35+00:00 | Vulnerability · Source |
| CVE-2022-41966 | suse_vex | SUSE CVE CVE-2022-41966 | known affected: 399 recommended: 51 | 2026-10-16T14:43:33+00:00 | Vulnerability · Source |
| CVE-2022-41974 | suse_vex | SUSE CVE CVE-2022-41974 | known affected: 395 known not affected: 1 recommended: 420 | 2026-10-16T14:43:30+00:00 | Vulnerability · Source |
| CVE-2022-42003 | suse_vex | SUSE CVE CVE-2022-42003 | known affected: 394 recommended: 70 | 2026-10-16T14:43:28+00:00 | Vulnerability · Source |
| CVE-2022-42012 | suse_vex | SUSE CVE CVE-2022-42012 | known affected: 254 recommended: 541 | 2026-10-16T14:43:26+00:00 | Vulnerability · Source |
| CVE-2022-42328 | suse_vex | SUSE CVE CVE-2022-42328 | known affected: 269 known not affected: 419 recommended: 1133 | 2026-10-16T14:43:23+00:00 | Vulnerability · Source |
| CVE-2022-42329 | suse_vex | SUSE CVE CVE-2022-42329 | known affected: 2 known not affected: 419 recommended: 1006 | 2026-10-16T14:43:20+00:00 | Vulnerability · Source |
| CVE-2022-42432 | suse_vex | SUSE CVE CVE-2022-42432 | known affected: 0 known not affected: 199 recommended: 22 | 2026-10-16T14:43:18+00:00 | Vulnerability · Source |
| CVE-2022-42703 | suse_vex | SUSE CVE CVE-2022-42703 | known affected: 255 recommended: 1762 | 2026-10-16T14:43:15+00:00 | Vulnerability · Source |
| CVE-2022-42719 | suse_vex | SUSE CVE CVE-2022-42719 | known affected: 253 known not affected: 199 recommended: 1300 | 2026-10-16T14:43:12+00:00 | Vulnerability · Source |
| CVE-2022-42720 | suse_vex | SUSE CVE CVE-2022-42720 | known affected: 253 known not affected: 207 recommended: 1374 | 2026-10-16T14:43:10+00:00 | Vulnerability · Source |
| CVE-2022-42721 | suse_vex | SUSE CVE CVE-2022-42721 | known affected: 253 known not affected: 207 recommended: 1374 | 2026-10-16T14:43:08+00:00 | Vulnerability · Source |
| CVE-2022-42722 | suse_vex | SUSE CVE CVE-2022-42722 | known affected: 255 known not affected: 251 recommended: 1179 | 2026-10-16T14:43:06+00:00 | Vulnerability · Source |
| CVE-2022-42823 | suse_vex | SUSE CVE CVE-2022-42823 | known affected: 1 known not affected: 170 recommended: 968 | 2026-10-16T14:43:04+00:00 | Vulnerability · Source |
| CVE-2022-42824 | suse_vex | SUSE CVE CVE-2022-42824 | known affected: 1 known not affected: 170 recommended: 968 | 2026-10-16T14:43:01+00:00 | Vulnerability · Source |
| CVE-2022-42826 | suse_vex | SUSE CVE CVE-2022-42826 | known affected: 1 recommended: 851 | 2026-10-16T14:42:59+00:00 | Vulnerability · Source |
| CVE-2022-42889 | suse_vex | SUSE CVE CVE-2022-42889 | known affected: 0 known not affected: 22 recommended: 46 | 2026-10-16T14:42:57+00:00 | Vulnerability · Source |
| CVE-2022-42895 | suse_vex | SUSE CVE CVE-2022-42895 | known affected: 384 known not affected: 322 recommended: 1441 | 2026-10-16T14:42:54+00:00 | Vulnerability · Source |