VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
284463 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2022-45405 | suse_vex | SUSE CVE CVE-2022-45405 | known affected: 1 recommended: 405 | 2026-07-25T17:21:54+00:00 | Vulnerability · Source |
| CVE-2022-45408 | suse_vex | SUSE CVE CVE-2022-45408 | known affected: 1 recommended: 405 | 2026-07-25T17:21:52+00:00 | Vulnerability · Source |
| CVE-2022-45411 | suse_vex | SUSE CVE CVE-2022-45411 | known affected: 1 recommended: 405 | 2026-07-25T17:21:51+00:00 | Vulnerability · Source |
| CVE-2022-45412 | suse_vex | SUSE CVE CVE-2022-45412 | known affected: 1 recommended: 405 | 2026-07-25T17:21:50+00:00 | Vulnerability · Source |
| CVE-2022-45415 | suse_vex | SUSE CVE CVE-2022-45415 | known affected: 1 recommended: 9 | 2026-07-25T17:21:48+00:00 | Vulnerability · Source |
| CVE-2022-45418 | suse_vex | SUSE CVE CVE-2022-45418 | known affected: 1 recommended: 405 | 2026-07-25T17:21:47+00:00 | Vulnerability · Source |
| CVE-2022-45420 | suse_vex | SUSE CVE CVE-2022-45420 | known affected: 1 recommended: 405 | 2026-07-25T17:21:45+00:00 | Vulnerability · Source |
| CVE-2022-45703 | suse_vex | SUSE CVE CVE-2022-45703 | known affected: 442 known not affected: 11 recommended: 326 | 2026-07-25T17:21:44+00:00 | Vulnerability · Source |
| CVE-2022-45873 | suse_vex | SUSE CVE CVE-2022-45873 | known not affected: 605 recommended: 10 | 2026-07-25T17:21:42+00:00 | Vulnerability · Source |
| CVE-2022-45884 | suse_vex | SUSE CVE CVE-2022-45884 | known affected: 192 known not affected: 8 recommended: 1351 | 2026-07-25T17:21:41+00:00 | Vulnerability · Source |
| CVE-2022-45934 | suse_vex | SUSE CVE CVE-2022-45934 | known affected: 229 recommended: 1901 | 2026-07-25T17:21:39+00:00 | Vulnerability · Source |
| CVE-2022-45939 | suse_vex | SUSE CVE CVE-2022-45939 | known affected: 125 recommended: 457 | 2026-07-25T17:21:37+00:00 | Vulnerability · Source |
| CVE-2022-46285 | suse_vex | SUSE CVE CVE-2022-46285 | known affected: 394 recommended: 166 | 2026-07-25T17:21:36+00:00 | Vulnerability · Source |
| CVE-2022-46699 | suse_vex | SUSE CVE CVE-2022-46699 | known affected: 1 recommended: 883 | 2026-07-25T17:21:34+00:00 | Vulnerability · Source |
| CVE-2022-46871 | suse_vex | SUSE CVE CVE-2022-46871 | known affected: 21 recommended: 320 | 2026-07-25T17:21:32+00:00 | Vulnerability · Source |
| CVE-2022-46875 | suse_vex | SUSE CVE CVE-2022-46875 | known affected: 21 recommended: 372 | 2026-07-25T17:21:31+00:00 | Vulnerability · Source |
| CVE-2022-46877 | suse_vex | SUSE CVE CVE-2022-46877 | known affected: 21 recommended: 320 | 2026-07-25T17:21:30+00:00 | Vulnerability · Source |
| CVE-2022-46878 | suse_vex | SUSE CVE CVE-2022-46878 | known affected: 21 recommended: 378 | 2026-07-25T17:21:28+00:00 | Vulnerability · Source |
| CVE-2022-46908 | suse_vex | SUSE CVE CVE-2022-46908 | known affected: 165 known not affected: 13 recommended: 563 | 2026-07-25T17:21:27+00:00 | Vulnerability · Source |
| CVE-2022-47008 | suse_vex | SUSE CVE CVE-2022-47008 | known affected: 10 known not affected: 224 | 2026-07-25T17:21:26+00:00 | Vulnerability · Source |
| CVE-2022-47011 | suse_vex | SUSE CVE CVE-2022-47011 | known affected: 10 known not affected: 224 | 2026-07-25T17:21:24+00:00 | Vulnerability · Source |
| CVE-2022-47111 | suse_vex | SUSE CVE CVE-2022-47111 | known affected: 93 | 2026-07-25T17:21:23+00:00 | Vulnerability · Source |