VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283830 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2021-47010 | suse_vex | SUSE CVE CVE-2021-47010 | known not affected: 292 | 2026-07-26T00:12:05+00:00 | Vulnerability · Source |
| CVE-2021-47014 | suse_vex | SUSE CVE CVE-2021-47014 | known affected: 388 known not affected: 256 recommended: 91 | 2026-07-26T00:12:03+00:00 | Vulnerability · Source |
| CVE-2021-47158 | suse_vex | SUSE CVE CVE-2021-47158 | known affected: 55 known not affected: 298 | 2026-07-26T00:12:01+00:00 | Vulnerability · Source |
| CVE-2021-47210 | suse_vex | SUSE CVE CVE-2021-47210 | known affected: 336 known not affected: 177 recommended: 462 | 2026-07-26T00:11:58+00:00 | Vulnerability · Source |
| CVE-2021-47240 | suse_vex | SUSE CVE CVE-2021-47240 | known not affected: 271 recommended: 129 | 2026-07-26T00:11:56+00:00 | Vulnerability · Source |
| CVE-2021-47241 | suse_vex | SUSE CVE CVE-2021-47241 | known affected: 388 known not affected: 294 recommended: 91 | 2026-07-26T00:11:54+00:00 | Vulnerability · Source |
| CVE-2021-47257 | suse_vex | SUSE CVE CVE-2021-47257 | known affected: 520 known not affected: 188 recommended: 104 | 2026-07-26T00:11:51+00:00 | Vulnerability · Source |
| CVE-2021-47263 | suse_vex | SUSE CVE CVE-2021-47263 | known affected: 388 known not affected: 294 recommended: 91 | 2026-07-26T00:11:49+00:00 | Vulnerability · Source |
| CVE-2021-47375 | suse_vex | SUSE CVE CVE-2021-47375 | known affected: 334 known not affected: 96 recommended: 657 | 2026-07-26T00:11:46+00:00 | Vulnerability · Source |
| CVE-2021-47428 | suse_vex | SUSE CVE CVE-2021-47428 | known affected: 292 known not affected: 158 recommended: 543 | 2026-07-26T00:11:43+00:00 | Vulnerability · Source |
| CVE-2021-47475 | suse_vex | SUSE CVE CVE-2021-47475 | known affected: 275 known not affected: 217 recommended: 452 | 2026-07-26T00:11:40+00:00 | Vulnerability · Source |
| CVE-2021-47491 | suse_vex | SUSE CVE CVE-2021-47491 | known not affected: 217 recommended: 353 | 2026-07-26T00:11:38+00:00 | Vulnerability · Source |
| CVE-2021-47635 | suse_vex | SUSE CVE CVE-2021-47635 | known affected: 334 known not affected: 255 recommended: 223 | 2026-07-26T00:11:34+00:00 | Vulnerability · Source |
| CVE-2022-1508 | suse_vex | SUSE CVE CVE-2022-1508 | known affected: 257 known not affected: 343 recommended: 615 | 2026-07-26T00:11:30+00:00 | Vulnerability · Source |
| CVE-2022-1974 | suse_vex | SUSE CVE CVE-2022-1974 | known affected: 220 known not affected: 2 recommended: 1533 | 2026-07-26T00:11:27+00:00 | Vulnerability · Source |
| CVE-2022-2308 | suse_vex | SUSE CVE CVE-2022-2308 | known not affected: 327 recommended: 6 | 2026-07-26T00:11:24+00:00 | Vulnerability · Source |
| CVE-2022-2625 | suse_vex | SUSE CVE CVE-2022-2625 | known affected: 395 recommended: 1937 | 2026-07-26T00:11:21+00:00 | Vulnerability · Source |
| CVE-2022-2977 | suse_vex | SUSE CVE CVE-2022-2977 | known affected: 207 known not affected: 30 recommended: 1697 | 2026-07-26T00:11:18+00:00 | Vulnerability · Source |
| CVE-2022-4129 | suse_vex | SUSE CVE CVE-2022-4129 | known affected: 273 known not affected: 122 recommended: 1474 | 2026-07-26T00:11:14+00:00 | Vulnerability · Source |
| CVE-2022-4203 | suse_vex | SUSE CVE CVE-2022-4203 | known not affected: 512 recommended: 142 | 2026-07-26T00:11:12+00:00 | Vulnerability · Source |
| CVE-2022-4662 | suse_vex | SUSE CVE CVE-2022-4662 | known affected: 255 known not affected: 124 recommended: 1369 | 2026-07-26T00:11:09+00:00 | Vulnerability · Source |
| CVE-2022-22740 | suse_vex | SUSE CVE CVE-2022-22740 | recommended: 413 | 2026-07-26T00:11:06+00:00 | Vulnerability · Source |
| CVE-2022-22747 | suse_vex | SUSE CVE CVE-2022-22747 | recommended: 413 | 2026-07-26T00:11:04+00:00 | Vulnerability · Source |
| CVE-2022-23037 | suse_vex | SUSE CVE CVE-2022-23037 | known affected: 344 known not affected: 61 recommended: 1327 | 2026-07-26T00:11:01+00:00 | Vulnerability · Source |
| CVE-2022-23131 | suse_vex | SUSE CVE CVE-2022-23131 | known not affected: 37 | 2026-07-26T00:10:58+00:00 | Vulnerability · Source |
| CVE-2022-23181 | suse_vex | SUSE CVE CVE-2022-23181 | known affected: 439 recommended: 539 | 2026-07-26T00:10:56+00:00 | Vulnerability · Source |
| CVE-2022-24806 | suse_vex | SUSE CVE CVE-2022-24806 | known affected: 394 known not affected: 190 recommended: 254 | 2026-07-26T00:10:53+00:00 | Vulnerability · Source |
| CVE-2022-28281 | suse_vex | SUSE CVE CVE-2022-28281 | known affected: 3 known not affected: 128 recommended: 405 | 2026-07-26T00:10:49+00:00 | Vulnerability · Source |
| CVE-2022-28391 | suse_vex | SUSE CVE CVE-2022-28391 | known affected: 5 known not affected: 63 | 2026-07-26T00:10:47+00:00 | Vulnerability · Source |
| CVE-2022-28734 | suse_vex | SUSE CVE CVE-2022-28734 | known affected: 353 recommended: 724 | 2026-07-26T00:10:45+00:00 | Vulnerability · Source |
| CVE-2022-34471 | suse_vex | SUSE CVE CVE-2022-34471 | known affected: 1 recommended: 365 | 2026-07-26T00:10:40+00:00 | Vulnerability · Source |
| CVE-2022-34473 | suse_vex | SUSE CVE CVE-2022-34473 | known affected: 1 recommended: 365 | 2026-07-26T00:10:38+00:00 | Vulnerability · Source |
| CVE-2022-38177 | suse_vex | SUSE CVE CVE-2022-38177 | known affected: 254 known not affected: 1 recommended: 1064 | 2026-07-26T00:10:35+00:00 | Vulnerability · Source |
| CVE-2022-38235 | suse_vex | SUSE CVE CVE-2022-38235 | known not affected: 330 | 2026-07-26T00:10:32+00:00 | Vulnerability · Source |
| CVE-2022-38349 | suse_vex | SUSE CVE CVE-2022-38349 | known affected: 80 known not affected: 5 recommended: 273 | 2026-07-26T00:10:31+00:00 | Vulnerability · Source |
| CVE-2022-38784 | suse_vex | SUSE CVE CVE-2022-38784 | known affected: 1 recommended: 465 | 2026-07-26T00:10:28+00:00 | Vulnerability · Source |
| CVE-2022-42310 | suse_vex | SUSE CVE CVE-2022-42310 | known affected: 253 recommended: 518 | 2026-07-26T00:10:25+00:00 | Vulnerability · Source |
| CVE-2022-42824 | suse_vex | SUSE CVE CVE-2022-42824 | known affected: 1 known not affected: 164 recommended: 976 | 2026-07-26T00:10:23+00:00 | Vulnerability · Source |
| CVE-2022-47015 | suse_vex | SUSE CVE CVE-2022-47015 | known affected: 29 known not affected: 131 recommended: 360 | 2026-07-26T00:10:20+00:00 | Vulnerability · Source |
| CVE-2022-47521 | suse_vex | SUSE CVE CVE-2022-47521 | known not affected: 362 | 2026-07-26T00:10:17+00:00 | Vulnerability · Source |
| CVE-2022-48655 | suse_vex | SUSE CVE CVE-2022-48655 | known affected: 265 known not affected: 225 recommended: 462 | 2026-07-26T00:10:15+00:00 | Vulnerability · Source |
| CVE-2022-48750 | suse_vex | SUSE CVE CVE-2022-48750 | known not affected: 318 | 2026-07-26T00:10:11+00:00 | Vulnerability · Source |
| CVE-2022-48751 | suse_vex | SUSE CVE CVE-2022-48751 | known affected: 437 known not affected: 97 recommended: 461 | 2026-07-26T00:10:09+00:00 | Vulnerability · Source |
| CVE-2022-48788 | suse_vex | SUSE CVE CVE-2022-48788 | known affected: 385 known not affected: 116 recommended: 619 | 2026-07-26T00:10:06+00:00 | Vulnerability · Source |
| CVE-2022-48857 | suse_vex | SUSE CVE CVE-2022-48857 | known affected: 377 known not affected: 98 recommended: 595 | 2026-07-26T00:10:03+00:00 | Vulnerability · Source |
| CVE-2022-48874 | suse_vex | SUSE CVE CVE-2022-48874 | known not affected: 310 | 2026-07-26T00:10:01+00:00 | Vulnerability · Source |
| CVE-2022-48887 | suse_vex | SUSE CVE CVE-2022-48887 | known affected: 389 known not affected: 142 recommended: 288 | 2026-07-26T00:09:58+00:00 | Vulnerability · Source |
| CVE-2022-48894 | suse_vex | SUSE CVE CVE-2022-48894 | known not affected: 310 | 2026-07-26T00:09:56+00:00 | Vulnerability · Source |
| CVE-2022-48899 | suse_vex | SUSE CVE CVE-2022-48899 | known affected: 425 known not affected: 78 recommended: 495 | 2026-07-26T00:09:54+00:00 | Vulnerability · Source |
| CVE-2022-48916 | suse_vex | SUSE CVE CVE-2022-48916 | known affected: 310 known not affected: 195 recommended: 411 | 2026-07-26T00:09:51+00:00 | Vulnerability · Source |