VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283120 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-26710 | suse_vex | SUSE CVE CVE-2022-26710 | known affected: 25 recommended: 952 | 2026-07-19T18:12:08+00:00 | Vulnerability · Source |
| CVE-2022-27376 | suse_vex | SUSE CVE CVE-2022-27376 | known not affected: 74 recommended: 365 | 2026-07-19T18:12:06+00:00 | Vulnerability · Source |
| CVE-2022-27377 | suse_vex | SUSE CVE CVE-2022-27377 | known not affected: 74 recommended: 469 | 2026-07-19T18:12:05+00:00 | Vulnerability · Source |
| CVE-2022-27379 | suse_vex | SUSE CVE CVE-2022-27379 | known not affected: 74 recommended: 365 | 2026-07-19T18:12:04+00:00 | Vulnerability · Source |
| CVE-2022-27387 | suse_vex | SUSE CVE CVE-2022-27387 | known not affected: 74 recommended: 469 | 2026-07-19T18:12:02+00:00 | Vulnerability · Source |
| CVE-2022-27406 | suse_vex | SUSE CVE CVE-2022-27406 | known affected: 248 known not affected: 54 recommended: 466 | 2026-07-19T18:12:01+00:00 | Vulnerability · Source |
| CVE-2022-27446 | suse_vex | SUSE CVE CVE-2022-27446 | known not affected: 190 recommended: 365 | 2026-07-19T18:12:00+00:00 | Vulnerability · Source |
| CVE-2022-27447 | suse_vex | SUSE CVE CVE-2022-27447 | known not affected: 74 recommended: 365 | 2026-07-19T18:11:59+00:00 | Vulnerability · Source |
| CVE-2022-27448 | suse_vex | SUSE CVE CVE-2022-27448 | known not affected: 190 recommended: 365 | 2026-07-19T18:11:57+00:00 | Vulnerability · Source |
| CVE-2022-27449 | suse_vex | SUSE CVE CVE-2022-27449 | known not affected: 74 recommended: 365 | 2026-07-19T18:11:56+00:00 | Vulnerability · Source |
| CVE-2022-27458 | suse_vex | SUSE CVE CVE-2022-27458 | known not affected: 74 recommended: 365 | 2026-07-19T18:11:55+00:00 | Vulnerability · Source |
| CVE-2022-27780 | suse_vex | SUSE CVE CVE-2022-27780 | known affected: 304 known not affected: 198 recommended: 174 | 2026-07-19T18:11:53+00:00 | Vulnerability · Source |
| CVE-2022-28281 | suse_vex | SUSE CVE CVE-2022-28281 | known affected: 3 known not affected: 128 recommended: 393 | 2026-07-19T18:11:52+00:00 | Vulnerability · Source |
| CVE-2022-28289 | suse_vex | SUSE CVE CVE-2022-28289 | known affected: 3 known not affected: 128 recommended: 393 | 2026-07-19T18:11:51+00:00 | Vulnerability · Source |
| CVE-2022-28347 | suse_vex | SUSE CVE CVE-2022-28347 | known not affected: 5 recommended: 17 | 2026-07-19T18:11:50+00:00 | Vulnerability · Source |
| CVE-2022-28614 | suse_vex | SUSE CVE CVE-2022-28614 | known affected: 395 recommended: 520 | 2026-07-19T18:11:49+00:00 | Vulnerability · Source |
| CVE-2022-29177 | suse_vex | SUSE CVE CVE-2022-29177 | recommended: 3 | 2026-07-19T18:11:47+00:00 | Vulnerability · Source |
| CVE-2022-29914 | suse_vex | SUSE CVE CVE-2022-29914 | known not affected: 2 recommended: 393 | 2026-07-19T18:11:46+00:00 | Vulnerability · Source |
| CVE-2022-30595 | suse_vex | SUSE CVE CVE-2022-30595 | known not affected: 5 recommended: 26 | 2026-07-19T18:11:44+00:00 | Vulnerability · Source |
| CVE-2022-30785 | suse_vex | SUSE CVE CVE-2022-30785 | recommended: 124 | 2026-07-19T18:11:43+00:00 | Vulnerability · Source |
| CVE-2022-30788 | suse_vex | SUSE CVE CVE-2022-30788 | recommended: 252 | 2026-07-19T18:11:42+00:00 | Vulnerability · Source |
| CVE-2022-31030 | suse_vex | SUSE CVE CVE-2022-31030 | known affected: 213 recommended: 538 | 2026-07-19T18:11:40+00:00 | Vulnerability · Source |
| CVE-2022-31625 | suse_vex | SUSE CVE CVE-2022-31625 | recommended: 4470 | 2026-07-19T18:11:38+00:00 | Vulnerability · Source |
| CVE-2022-31630 | suse_vex | SUSE CVE CVE-2022-31630 | known not affected: 540 recommended: 3281 | 2026-07-19T18:11:37+00:00 | Vulnerability · Source |
| CVE-2022-31739 | suse_vex | SUSE CVE CVE-2022-31739 | known not affected: 1 recommended: 387 | 2026-07-19T18:11:35+00:00 | Vulnerability · Source |
| CVE-2022-31741 | suse_vex | SUSE CVE CVE-2022-31741 | recommended: 1645 | 2026-07-19T18:11:34+00:00 | Vulnerability · Source |
| CVE-2022-31742 | suse_vex | SUSE CVE CVE-2022-31742 | known not affected: 1 recommended: 393 | 2026-07-19T18:11:33+00:00 | Vulnerability · Source |
| CVE-2022-32205 | suse_vex | SUSE CVE CVE-2022-32205 | known affected: 254 known not affected: 160 recommended: 270 | 2026-07-19T18:11:31+00:00 | Vulnerability · Source |
| CVE-2022-32206 | suse_vex | SUSE CVE CVE-2022-32206 | known affected: 216 known not affected: 29 recommended: 477 | 2026-07-19T18:11:30+00:00 | Vulnerability · Source |
| CVE-2022-32213 | suse_vex | SUSE CVE CVE-2022-32213 | recommended: 633 | 2026-07-19T18:11:29+00:00 | Vulnerability · Source |
| CVE-2022-32214 | suse_vex | SUSE CVE CVE-2022-32214 | recommended: 617 | 2026-07-19T18:11:27+00:00 | Vulnerability · Source |
| CVE-2022-32221 | suse_vex | SUSE CVE CVE-2022-32221 | known affected: 310 known not affected: 22 recommended: 458 | 2026-07-19T18:11:26+00:00 | Vulnerability · Source |
| CVE-2022-32546 | suse_vex | SUSE CVE CVE-2022-32546 | recommended: 515 | 2026-07-19T18:11:25+00:00 | Vulnerability · Source |
| CVE-2022-32547 | suse_vex | SUSE CVE CVE-2022-32547 | recommended: 515 | 2026-07-19T18:11:23+00:00 | Vulnerability · Source |
| CVE-2022-32792 | suse_vex | SUSE CVE CVE-2022-32792 | known affected: 1 recommended: 952 | 2026-07-19T18:11:22+00:00 | Vulnerability · Source |
| CVE-2022-32886 | suse_vex | SUSE CVE CVE-2022-32886 | known affected: 1 recommended: 1007 | 2026-07-19T18:11:20+00:00 | Vulnerability · Source |
| CVE-2022-32888 | suse_vex | SUSE CVE CVE-2022-32888 | known affected: 1 known not affected: 127 recommended: 947 | 2026-07-19T18:11:19+00:00 | Vulnerability · Source |
| CVE-2022-32891 | suse_vex | SUSE CVE CVE-2022-32891 | known affected: 1 recommended: 290 | 2026-07-19T18:11:18+00:00 | Vulnerability · Source |
| CVE-2022-32912 | suse_vex | SUSE CVE CVE-2022-32912 | known affected: 1 recommended: 999 | 2026-07-19T18:11:16+00:00 | Vulnerability · Source |
| CVE-2022-32923 | suse_vex | SUSE CVE CVE-2022-32923 | known affected: 1 known not affected: 127 recommended: 947 | 2026-07-19T18:11:15+00:00 | Vulnerability · Source |
| CVE-2022-33099 | suse_vex | SUSE CVE CVE-2022-33099 | known not affected: 351 recommended: 22 | 2026-07-19T18:11:14+00:00 | Vulnerability · Source |
| CVE-2022-33980 | suse_vex | SUSE CVE CVE-2022-33980 | known not affected: 27 recommended: 16 | 2026-07-19T18:11:12+00:00 | Vulnerability · Source |
| CVE-2022-34265 | suse_vex | SUSE CVE CVE-2022-34265 | recommended: 106 | 2026-07-19T18:11:11+00:00 | Vulnerability · Source |
| CVE-2022-34303 | suse_vex | SUSE CVE CVE-2022-34303 | known not affected: 56 recommended: 3 | 2026-07-19T18:11:10+00:00 | Vulnerability · Source |
| CVE-2022-34471 | suse_vex | SUSE CVE CVE-2022-34471 | known affected: 1 recommended: 349 | 2026-07-19T18:11:09+00:00 | Vulnerability · Source |
| CVE-2022-34472 | suse_vex | SUSE CVE CVE-2022-34472 | known affected: 1 recommended: 463 | 2026-07-19T18:11:08+00:00 | Vulnerability · Source |
| CVE-2022-34473 | suse_vex | SUSE CVE CVE-2022-34473 | known affected: 1 recommended: 349 | 2026-07-19T18:11:06+00:00 | Vulnerability · Source |
| CVE-2022-34477 | suse_vex | SUSE CVE CVE-2022-34477 | known affected: 1 recommended: 349 | 2026-07-19T18:11:05+00:00 | Vulnerability · Source |
| CVE-2022-34478 | suse_vex | SUSE CVE CVE-2022-34478 | known affected: 1 recommended: 457 | 2026-07-19T18:11:04+00:00 | Vulnerability · Source |
| CVE-2022-34479 | suse_vex | SUSE CVE CVE-2022-34479 | known affected: 1 recommended: 463 | 2026-07-19T18:11:03+00:00 | Vulnerability · Source |