VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283445 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-40307 | suse_vex | SUSE CVE CVE-2022-40307 | known affected: 396 known not affected: 20 recommended: 458 | 2026-07-25T17:23:07+00:00 | Vulnerability · Source |
| CVE-2022-40433 | suse_vex | SUSE CVE CVE-2022-40433 | known affected: 4 known not affected: 477 recommended: 37 | 2026-07-25T17:23:06+00:00 | Vulnerability · Source |
| CVE-2022-40476 | suse_vex | SUSE CVE CVE-2022-40476 | known affected: 271 known not affected: 276 recommended: 635 | 2026-07-25T17:23:04+00:00 | Vulnerability · Source |
| CVE-2022-40540 | suse_vex | SUSE CVE CVE-2022-40540 | known not affected: 124 | 2026-07-25T17:23:03+00:00 | Vulnerability · Source |
| CVE-2022-40626 | suse_vex | SUSE CVE CVE-2022-40626 | known not affected: 25 | 2026-07-25T17:23:01+00:00 | Vulnerability · Source |
| CVE-2022-40674 | suse_vex | SUSE CVE CVE-2022-40674 | known affected: 217 recommended: 498 | 2026-07-25T17:23:00+00:00 | Vulnerability · Source |
| CVE-2022-40957 | suse_vex | SUSE CVE CVE-2022-40957 | known affected: 1 recommended: 437 | 2026-07-25T17:22:58+00:00 | Vulnerability · Source |
| CVE-2022-40959 | suse_vex | SUSE CVE CVE-2022-40959 | known affected: 1 recommended: 437 | 2026-07-25T17:22:57+00:00 | Vulnerability · Source |
| CVE-2022-40960 | suse_vex | SUSE CVE CVE-2022-40960 | known affected: 1 recommended: 437 | 2026-07-25T17:22:56+00:00 | Vulnerability · Source |
| CVE-2022-40982 | suse_vex | SUSE CVE CVE-2022-40982 | known affected: 197 recommended: 1696 | 2026-07-25T17:22:54+00:00 | Vulnerability · Source |
| CVE-2022-41218 | suse_vex | SUSE CVE CVE-2022-41218 | known affected: 253 known not affected: 123 recommended: 381 | 2026-07-25T17:22:53+00:00 | Vulnerability · Source |
| CVE-2022-41318 | suse_vex | SUSE CVE CVE-2022-41318 | known affected: 395 recommended: 71 | 2026-07-25T17:22:51+00:00 | Vulnerability · Source |
| CVE-2022-41844 | suse_vex | SUSE CVE CVE-2022-41844 | known not affected: 330 | 2026-07-25T17:22:50+00:00 | Vulnerability · Source |
| CVE-2022-41850 | suse_vex | SUSE CVE CVE-2022-41850 | known affected: 269 recommended: 1542 | 2026-07-25T17:22:48+00:00 | Vulnerability · Source |
| CVE-2022-41859 | suse_vex | SUSE CVE CVE-2022-41859 | known affected: 1 known not affected: 1 recommended: 756 | 2026-07-25T17:22:47+00:00 | Vulnerability · Source |
| CVE-2022-41860 | suse_vex | SUSE CVE CVE-2022-41860 | known affected: 1 recommended: 761 | 2026-07-25T17:22:46+00:00 | Vulnerability · Source |
| CVE-2022-41903 | suse_vex | SUSE CVE CVE-2022-41903 | known affected: 1 known not affected: 131 recommended: 726 | 2026-07-25T17:22:44+00:00 | Vulnerability · Source |
| CVE-2022-42010 | suse_vex | SUSE CVE CVE-2022-42010 | known affected: 254 recommended: 529 | 2026-07-25T17:22:42+00:00 | Vulnerability · Source |
| CVE-2022-42252 | suse_vex | SUSE CVE CVE-2022-42252 | known affected: 395 recommended: 537 | 2026-07-25T17:22:41+00:00 | Vulnerability · Source |
| CVE-2022-42309 | suse_vex | SUSE CVE CVE-2022-42309 | known affected: 253 recommended: 518 | 2026-07-25T17:22:39+00:00 | Vulnerability · Source |
| CVE-2022-42318 | suse_vex | SUSE CVE CVE-2022-42318 | recommended: 377 | 2026-07-25T17:22:38+00:00 | Vulnerability · Source |
| CVE-2022-42320 | suse_vex | SUSE CVE CVE-2022-42320 | known affected: 253 recommended: 518 | 2026-07-25T17:22:37+00:00 | Vulnerability · Source |
| CVE-2022-42321 | suse_vex | SUSE CVE CVE-2022-42321 | known affected: 253 recommended: 518 | 2026-07-25T17:22:35+00:00 | Vulnerability · Source |
| CVE-2022-42323 | suse_vex | SUSE CVE CVE-2022-42323 | recommended: 377 | 2026-07-25T17:22:34+00:00 | Vulnerability · Source |
| CVE-2022-42332 | suse_vex | SUSE CVE CVE-2022-42332 | known affected: 287 known not affected: 28 recommended: 413 | 2026-07-25T17:22:33+00:00 | Vulnerability · Source |
| CVE-2022-42336 | suse_vex | SUSE CVE CVE-2022-42336 | known not affected: 312 recommended: 78 | 2026-07-25T17:22:31+00:00 | Vulnerability · Source |
| CVE-2022-42432 | suse_vex | SUSE CVE CVE-2022-42432 | known not affected: 175 recommended: 22 | 2026-07-25T17:22:29+00:00 | Vulnerability · Source |
| CVE-2022-42703 | suse_vex | SUSE CVE CVE-2022-42703 | known affected: 255 recommended: 1764 | 2026-07-25T17:22:28+00:00 | Vulnerability · Source |
| CVE-2022-42719 | suse_vex | SUSE CVE CVE-2022-42719 | known affected: 253 known not affected: 175 recommended: 1329 | 2026-07-25T17:22:26+00:00 | Vulnerability · Source |
| CVE-2022-42720 | suse_vex | SUSE CVE CVE-2022-42720 | known affected: 253 known not affected: 183 recommended: 1376 | 2026-07-25T17:22:24+00:00 | Vulnerability · Source |
| CVE-2022-42721 | suse_vex | SUSE CVE CVE-2022-42721 | known affected: 253 known not affected: 183 recommended: 1376 | 2026-07-25T17:22:23+00:00 | Vulnerability · Source |
| CVE-2022-42722 | suse_vex | SUSE CVE CVE-2022-42722 | known affected: 255 known not affected: 221 recommended: 1181 | 2026-07-25T17:22:21+00:00 | Vulnerability · Source |
| CVE-2022-42823 | suse_vex | SUSE CVE CVE-2022-42823 | known affected: 1 known not affected: 164 recommended: 976 | 2026-07-25T17:22:20+00:00 | Vulnerability · Source |
| CVE-2022-42856 | suse_vex | SUSE CVE CVE-2022-42856 | known affected: 1 recommended: 875 | 2026-07-25T17:22:18+00:00 | Vulnerability · Source |
| CVE-2022-42863 | suse_vex | SUSE CVE CVE-2022-42863 | known affected: 1 recommended: 883 | 2026-07-25T17:22:17+00:00 | Vulnerability · Source |
| CVE-2022-42867 | suse_vex | SUSE CVE CVE-2022-42867 | known affected: 1 recommended: 883 | 2026-07-25T17:22:15+00:00 | Vulnerability · Source |
| CVE-2022-42915 | suse_vex | SUSE CVE CVE-2022-42915 | known affected: 304 known not affected: 185 recommended: 174 | 2026-07-25T17:22:14+00:00 | Vulnerability · Source |
| CVE-2022-42916 | suse_vex | SUSE CVE CVE-2022-42916 | known affected: 271 known not affected: 151 recommended: 253 | 2026-07-25T17:22:12+00:00 | Vulnerability · Source |
| CVE-2022-42920 | suse_vex | SUSE CVE CVE-2022-42920 | known affected: 403 recommended: 53 | 2026-07-25T17:22:11+00:00 | Vulnerability · Source |
| CVE-2022-42928 | suse_vex | SUSE CVE CVE-2022-42928 | known affected: 1 recommended: 390 | 2026-07-25T17:22:09+00:00 | Vulnerability · Source |
| CVE-2022-43552 | suse_vex | SUSE CVE CVE-2022-43552 | known affected: 321 recommended: 361 | 2026-07-25T17:22:08+00:00 | Vulnerability · Source |
| CVE-2022-43995 | suse_vex | SUSE CVE CVE-2022-43995 | known affected: 254 known not affected: 1 recommended: 360 | 2026-07-25T17:22:06+00:00 | Vulnerability · Source |
| CVE-2022-44032 | suse_vex | SUSE CVE CVE-2022-44032 | known not affected: 352 recommended: 34 | 2026-07-25T17:22:05+00:00 | Vulnerability · Source |
| CVE-2022-44034 | suse_vex | SUSE CVE CVE-2022-44034 | known not affected: 333 recommended: 6 | 2026-07-25T17:22:03+00:00 | Vulnerability · Source |
| CVE-2022-44267 | suse_vex | SUSE CVE CVE-2022-44267 | known affected: 49 known not affected: 58 recommended: 550 | 2026-07-25T17:22:02+00:00 | Vulnerability · Source |
| CVE-2022-44729 | suse_vex | SUSE CVE CVE-2022-44729 | known not affected: 39 recommended: 71 | 2026-07-25T17:22:01+00:00 | Vulnerability · Source |
| CVE-2022-45142 | suse_vex | SUSE CVE CVE-2022-45142 | known not affected: 1583 recommended: 18 | 2026-07-25T17:21:59+00:00 | Vulnerability · Source |
| CVE-2022-45143 | suse_vex | SUSE CVE CVE-2022-45143 | known affected: 394 known not affected: 262 recommended: 299 | 2026-07-25T17:21:58+00:00 | Vulnerability · Source |
| CVE-2022-45154 | suse_vex | SUSE CVE CVE-2022-45154 | known affected: 206 recommended: 260 | 2026-07-25T17:21:56+00:00 | Vulnerability · Source |
| CVE-2022-45403 | suse_vex | SUSE CVE CVE-2022-45403 | known affected: 1 recommended: 405 | 2026-07-25T17:21:55+00:00 | Vulnerability · Source |