VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104648 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2021-47650 | suse_vex | SUSE CVE CVE-2021-47650 | known affected: 334 known not affected: 362 recommended: 293 | 2026-10-17T01:24:30+00:00 | Vulnerability · Source |
| CVE-2021-47654 | suse_vex | SUSE CVE CVE-2021-47654 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-17T01:24:28+00:00 | Vulnerability · Source |
| CVE-2021-47655 | suse_vex | SUSE CVE CVE-2021-47655 | known affected: 0 known not affected: 462 | 2026-10-17T01:24:27+00:00 | Vulnerability · Source |
| CVE-2021-47658 | suse_vex | SUSE CVE CVE-2021-47658 | known affected: 0 known not affected: 462 | 2026-10-17T01:24:24+00:00 | Vulnerability · Source |
| CVE-2021-47659 | suse_vex | SUSE CVE CVE-2021-47659 | known affected: 465 known not affected: 274 recommended: 319 | 2026-10-17T01:24:22+00:00 | Vulnerability · Source |
| CVE-2021-47668 | suse_vex | SUSE CVE CVE-2021-47668 | known affected: 521 known not affected: 267 recommended: 122 | 2026-10-17T01:24:21+00:00 | Vulnerability · Source |
| CVE-2021-47669 | suse_vex | SUSE CVE CVE-2021-47669 | known affected: 454 known not affected: 304 recommended: 108 | 2026-10-17T01:24:19+00:00 | Vulnerability · Source |
| CVE-2021-47671 | suse_vex | SUSE CVE CVE-2021-47671 | known affected: 339 known not affected: 343 recommended: 271 | 2026-10-17T01:24:16+00:00 | Vulnerability · Source |
| CVE-2022-0156 | suse_vex | SUSE CVE CVE-2022-0156 | known affected: 0 known not affected: 240 recommended: 33 | 2026-10-17T01:24:15+00:00 | Vulnerability · Source |
| CVE-2022-0168 | suse_vex | SUSE CVE CVE-2022-0168 | known affected: 296 known not affected: 343 recommended: 1183 | 2026-10-17T01:24:13+00:00 | Vulnerability · Source |
| CVE-2022-0171 | suse_vex | SUSE CVE CVE-2022-0171 | known affected: 219 known not affected: 247 recommended: 369 | 2026-10-17T01:24:12+00:00 | Vulnerability · Source |
| CVE-2022-0213 | suse_vex | SUSE CVE CVE-2022-0213 | known affected: 363 recommended: 389 | 2026-10-17T01:24:10+00:00 | Vulnerability · Source |
| CVE-2022-0264 | suse_vex | SUSE CVE CVE-2022-0264 | known affected: 193 known not affected: 408 recommended: 650 | 2026-10-17T01:24:09+00:00 | Vulnerability · Source |
| CVE-2022-0318 | suse_vex | SUSE CVE CVE-2022-0318 | known affected: 341 known not affected: 32 recommended: 412 | 2026-10-17T01:24:07+00:00 | Vulnerability · Source |
| CVE-2022-0319 | suse_vex | SUSE CVE CVE-2022-0319 | known affected: 341 known not affected: 25 recommended: 407 | 2026-10-17T01:24:06+00:00 | Vulnerability · Source |
| CVE-2022-0322 | suse_vex | SUSE CVE CVE-2022-0322 | known affected: 332 known not affected: 148 recommended: 1218 | 2026-10-17T01:24:04+00:00 | Vulnerability · Source |
| CVE-2022-0330 | suse_vex | SUSE CVE CVE-2022-0330 | known affected: 351 known not affected: 87 recommended: 1569 | 2026-10-17T01:24:03+00:00 | Vulnerability · Source |
| CVE-2022-0359 | suse_vex | SUSE CVE CVE-2022-0359 | known affected: 363 recommended: 394 | 2026-10-17T01:24:01+00:00 | Vulnerability · Source |
| CVE-2022-0391 | suse_vex | SUSE CVE CVE-2022-0391 | known affected: 394 known not affected: 262 recommended: 529 | 2026-10-17T01:24:00+00:00 | Vulnerability · Source |
| CVE-2022-0407 | suse_vex | SUSE CVE CVE-2022-0407 | known affected: 353 known not affected: 32 recommended: 389 | 2026-10-17T01:23:58+00:00 | Vulnerability · Source |
| CVE-2022-0408 | suse_vex | SUSE CVE CVE-2022-0408 | known affected: 0 known not affected: 271 recommended: 33 | 2026-10-17T01:23:57+00:00 | Vulnerability · Source |
| CVE-2022-0417 | suse_vex | SUSE CVE CVE-2022-0417 | known affected: 0 known not affected: 271 recommended: 33 | 2026-10-17T01:23:56+00:00 | Vulnerability · Source |
| CVE-2022-0443 | suse_vex | SUSE CVE CVE-2022-0443 | known affected: 0 known not affected: 271 recommended: 33 | 2026-10-17T01:23:54+00:00 | Vulnerability · Source |
| CVE-2022-0485 | suse_vex | SUSE CVE CVE-2022-0485 | recommended: 50 | 2026-10-17T01:23:52+00:00 | Vulnerability · Source |
| CVE-2022-0492 | suse_vex | SUSE CVE CVE-2022-0492 | known affected: 349 known not affected: 57 recommended: 1693 | 2026-10-17T01:23:50+00:00 | Vulnerability · Source |
| CVE-2022-0494 | suse_vex | SUSE CVE CVE-2022-0494 | known affected: 282 known not affected: 329 recommended: 650 | 2026-10-17T01:23:49+00:00 | Vulnerability · Source |
| CVE-2022-0516 | suse_vex | SUSE CVE CVE-2022-0516 | known affected: 350 known not affected: 321 recommended: 1174 | 2026-10-17T01:23:47+00:00 | Vulnerability · Source |
| CVE-2022-0563 | suse_vex | SUSE CVE CVE-2022-0563 | known affected: 0 known not affected: 876 recommended: 395 | 2026-10-17T01:23:46+00:00 | Vulnerability · Source |
| CVE-2022-0581 | suse_vex | SUSE CVE CVE-2022-0581 | known affected: 0 known not affected: 124 recommended: 339 | 2026-10-17T01:23:44+00:00 | Vulnerability · Source |
| CVE-2022-0582 | suse_vex | SUSE CVE CVE-2022-0582 | known affected: 0 known not affected: 124 recommended: 339 | 2026-10-17T01:23:43+00:00 | Vulnerability · Source |
| CVE-2022-0583 | suse_vex | SUSE CVE CVE-2022-0583 | known affected: 0 known not affected: 124 recommended: 339 | 2026-10-17T01:23:42+00:00 | Vulnerability · Source |
| CVE-2022-0585 | suse_vex | SUSE CVE CVE-2022-0585 | known affected: 0 known not affected: 124 recommended: 339 | 2026-10-17T01:23:40+00:00 | Vulnerability · Source |
| CVE-2022-0615 | suse_vex | SUSE CVE CVE-2022-0615 | known affected: 0 known not affected: 439 | 2026-10-17T01:23:39+00:00 | Vulnerability · Source |
| CVE-2022-0617 | suse_vex | SUSE CVE CVE-2022-0617 | known affected: 207 known not affected: 2 recommended: 1651 | 2026-10-17T01:23:37+00:00 | Vulnerability · Source |
| CVE-2022-0644 | suse_vex | SUSE CVE CVE-2022-0644 | known affected: 207 known not affected: 119 recommended: 1332 | 2026-10-17T01:23:35+00:00 | Vulnerability · Source |
| CVE-2022-0711 | suse_vex | SUSE CVE CVE-2022-0711 | known affected: 0 known not affected: 15 recommended: 12 | 2026-10-17T01:23:34+00:00 | Vulnerability · Source |
| CVE-2022-0778 | suse_vex | SUSE CVE CVE-2022-0778 | known affected: 346 known not affected: 188 recommended: 1003 | 2026-10-17T01:23:33+00:00 | Vulnerability · Source |
| CVE-2022-0943 | suse_vex | SUSE CVE CVE-2022-0943 | known affected: 0 known not affected: 293 recommended: 43 | 2026-10-17T01:23:31+00:00 | Vulnerability · Source |
| CVE-2022-1215 | suse_vex | SUSE CVE CVE-2022-1215 | known affected: 394 known not affected: 82 recommended: 241 | 2026-10-17T01:23:28+00:00 | Vulnerability · Source |
| CVE-2022-1381 | suse_vex | SUSE CVE CVE-2022-1381 | known affected: 353 known not affected: 35 recommended: 389 | 2026-10-17T01:23:26+00:00 | Vulnerability · Source |
| CVE-2022-1785 | suse_vex | SUSE CVE CVE-2022-1785 | known affected: 363 recommended: 404 | 2026-10-17T01:23:24+00:00 | Vulnerability · Source |
| CVE-2022-1972 | suse_vex | SUSE CVE CVE-2022-1972 | known affected: 222 known not affected: 296 recommended: 1120 | 2026-10-17T01:23:22+00:00 | Vulnerability · Source |
| CVE-2022-2208 | suse_vex | SUSE CVE CVE-2022-2208 | known affected: 237 known not affected: 26 recommended: 507 | 2026-10-17T01:23:19+00:00 | Vulnerability · Source |
| CVE-2022-2344 | suse_vex | SUSE CVE CVE-2022-2344 | known affected: 237 known not affected: 2 recommended: 507 | 2026-10-17T01:23:18+00:00 | Vulnerability · Source |
| CVE-2022-2819 | suse_vex | SUSE CVE CVE-2022-2819 | known affected: 237 known not affected: 2 recommended: 507 | 2026-10-17T01:23:16+00:00 | Vulnerability · Source |
| CVE-2022-2845 | suse_vex | SUSE CVE CVE-2022-2845 | known affected: 238 recommended: 507 | 2026-10-17T01:23:14+00:00 | Vulnerability · Source |
| CVE-2022-2867 | suse_vex | SUSE CVE CVE-2022-2867 | known affected: 395 known not affected: 1 recommended: 264 | 2026-10-17T01:23:13+00:00 | Vulnerability · Source |
| CVE-2022-2906 | suse_vex | SUSE CVE CVE-2022-2906 | known affected: 0 known not affected: 569 recommended: 41 | 2026-10-17T01:23:11+00:00 | Vulnerability · Source |
| CVE-2022-2963 | suse_vex | SUSE CVE CVE-2022-2963 | known affected: 461 recommended: 109 | 2026-10-17T01:23:10+00:00 | Vulnerability · Source |
| CVE-2022-3107 | suse_vex | SUSE CVE CVE-2022-3107 | known affected: 272 known not affected: 217 recommended: 1045 | 2026-10-17T01:23:08+00:00 | Vulnerability · Source |