VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
78859 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2021-47163 | suse_vex | SUSE CVE CVE-2021-47163 | known affected: 571 known not affected: 192 recommended: 122 | 2026-10-04T17:00:39+00:00 | Vulnerability · Source |
| CVE-2021-47173 | suse_vex | SUSE CVE CVE-2021-47173 | known affected: 535 known not affected: 200 recommended: 221 | 2026-10-04T17:00:37+00:00 | Vulnerability · Source |
| CVE-2021-47179 | suse_vex | SUSE CVE CVE-2021-47179 | known affected: 388 known not affected: 269 recommended: 207 | 2026-10-04T17:00:35+00:00 | Vulnerability · Source |
| CVE-2021-47188 | suse_vex | SUSE CVE CVE-2021-47188 | known affected: 445 known not affected: 76 recommended: 547 | 2026-10-04T17:00:33+00:00 | Vulnerability · Source |
| CVE-2021-47276 | suse_vex | SUSE CVE CVE-2021-47276 | known affected: 507 known not affected: 173 recommended: 219 | 2026-10-04T17:00:31+00:00 | Vulnerability · Source |
| CVE-2021-47399 | suse_vex | SUSE CVE CVE-2021-47399 | known affected: 303 known not affected: 139 recommended: 657 | 2026-10-04T17:00:29+00:00 | Vulnerability · Source |
| CVE-2021-47518 | suse_vex | SUSE CVE CVE-2021-47518 | known affected: 427 known not affected: 60 recommended: 627 | 2026-10-04T17:00:26+00:00 | Vulnerability · Source |
| CVE-2021-47549 | suse_vex | SUSE CVE CVE-2021-47549 | known affected: 269 known not affected: 202 recommended: 627 | 2026-10-04T17:00:24+00:00 | Vulnerability · Source |
| CVE-2021-47633 | suse_vex | SUSE CVE CVE-2021-47633 | known affected: 481 known not affected: 165 recommended: 374 | 2026-10-04T17:00:21+00:00 | Vulnerability · Source |
| CVE-2022-3239 | suse_vex | SUSE CVE CVE-2022-3239 | known affected: 253 known not affected: 2 recommended: 1480 | 2026-10-04T17:00:16+00:00 | Vulnerability · Source |
| CVE-2022-23036 | suse_vex | SUSE CVE CVE-2022-23036 | known affected: 344 known not affected: 65 recommended: 1298 | 2026-10-04T17:00:11+00:00 | Vulnerability · Source |
| CVE-2022-33741 | suse_vex | SUSE CVE CVE-2022-33741 | known affected: 249 known not affected: 227 recommended: 1546 | 2026-10-04T17:00:04+00:00 | Vulnerability · Source |
| CVE-2022-36402 | suse_vex | SUSE CVE CVE-2022-36402 | known affected: 388 known not affected: 497 recommended: 409 | 2026-10-04T17:00:02+00:00 | Vulnerability · Source |
| CVE-2022-36879 | suse_vex | SUSE CVE CVE-2022-36879 | known affected: 237 recommended: 1527 | 2026-10-04T16:59:59+00:00 | Vulnerability · Source |
| CVE-2022-40982 | suse_vex | SUSE CVE CVE-2022-40982 | known affected: 213 recommended: 1683 | 2026-10-04T16:59:56+00:00 | Vulnerability · Source |
| CVE-2022-42328 | suse_vex | SUSE CVE CVE-2022-42328 | known affected: 269 known not affected: 419 recommended: 1133 | 2026-10-04T16:59:54+00:00 | Vulnerability · Source |
| CVE-2022-48672 | suse_vex | SUSE CVE CVE-2022-48672 | known affected: 400 known not affected: 76 recommended: 618 | 2026-10-04T16:59:50+00:00 | Vulnerability · Source |
| CVE-2022-48743 | suse_vex | SUSE CVE CVE-2022-48743 | known affected: 527 known not affected: 69 recommended: 524 | 2026-10-04T16:59:48+00:00 | Vulnerability · Source |
| CVE-2022-48860 | suse_vex | SUSE CVE CVE-2022-48860 | known affected: 512 known not affected: 63 recommended: 510 | 2026-10-04T16:59:45+00:00 | Vulnerability · Source |
| CVE-2022-48905 | suse_vex | SUSE CVE CVE-2022-48905 | known affected: 440 known not affected: 96 recommended: 588 | 2026-10-04T16:59:43+00:00 | Vulnerability · Source |
| CVE-2022-48975 | suse_vex | SUSE CVE CVE-2022-48975 | known affected: 406 known not affected: 277 recommended: 449 | 2026-10-04T16:59:41+00:00 | Vulnerability · Source |
| CVE-2022-49020 | suse_vex | SUSE CVE CVE-2022-49020 | known affected: 647 known not affected: 48 recommended: 311 | 2026-10-04T16:59:38+00:00 | Vulnerability · Source |
| CVE-2022-49089 | suse_vex | SUSE CVE CVE-2022-49089 | known affected: 452 known not affected: 235 recommended: 249 | 2026-10-04T16:59:35+00:00 | Vulnerability · Source |
| CVE-2022-49395 | suse_vex | SUSE CVE CVE-2022-49395 | known affected: 664 known not affected: 144 recommended: 60 | 2026-10-04T16:59:31+00:00 | Vulnerability · Source |
| CVE-2022-49534 | suse_vex | SUSE CVE CVE-2022-49534 | known affected: 495 known not affected: 156 recommended: 361 | 2026-10-04T16:59:28+00:00 | Vulnerability · Source |
| CVE-2022-49749 | suse_vex | SUSE CVE CVE-2022-49749 | known affected: 716 known not affected: 113 recommended: 40 | 2026-10-04T16:59:24+00:00 | Vulnerability · Source |
| CVE-2022-49937 | suse_vex | SUSE CVE CVE-2022-49937 | known not affected: 324 recommended: 286 | 2026-10-04T16:59:21+00:00 | Vulnerability · Source |
| CVE-2022-49943 | suse_vex | SUSE CVE CVE-2022-49943 | known affected: 369 known not affected: 332 recommended: 235 | 2026-10-04T16:59:20+00:00 | Vulnerability · Source |
| CVE-2022-49977 | suse_vex | SUSE CVE CVE-2022-49977 | known affected: 491 known not affected: 196 recommended: 359 | 2026-10-04T16:59:18+00:00 | Vulnerability · Source |
| CVE-2022-50008 | suse_vex | SUSE CVE CVE-2022-50008 | known affected: 534 known not affected: 157 recommended: 243 | 2026-10-04T16:59:16+00:00 | Vulnerability · Source |
| CVE-2022-50067 | suse_vex | SUSE CVE CVE-2022-50067 | known not affected: 526 recommended: 286 | 2026-10-04T16:59:13+00:00 | Vulnerability · Source |
| CVE-2022-50073 | suse_vex | SUSE CVE CVE-2022-50073 | known affected: 344 known not affected: 334 recommended: 249 | 2026-10-04T16:59:10+00:00 | Vulnerability · Source |
| CVE-2022-50146 | suse_vex | SUSE CVE CVE-2022-50146 | known affected: 403 known not affected: 271 recommended: 323 | 2026-10-04T16:59:07+00:00 | Vulnerability · Source |
| CVE-2022-50312 | suse_vex | SUSE CVE CVE-2022-50312 | known affected: 491 known not affected: 176 recommended: 310 | 2026-10-04T16:59:03+00:00 | Vulnerability · Source |
| CVE-2022-50481 | suse_vex | SUSE CVE CVE-2022-50481 | known affected: 712 known not affected: 147 recommended: 23 | 2026-10-04T16:58:59+00:00 | Vulnerability · Source |
| CVE-2022-50625 | suse_vex | SUSE CVE CVE-2022-50625 | known affected: 556 known not affected: 169 recommended: 219 | 2026-10-04T16:58:55+00:00 | Vulnerability · Source |
| CVE-2022-50640 | suse_vex | SUSE CVE CVE-2022-50640 | known affected: 507 known not affected: 209 recommended: 237 | 2026-10-04T16:58:53+00:00 | Vulnerability · Source |
| CVE-2022-50716 | suse_vex | SUSE CVE CVE-2022-50716 | known affected: 518 known not affected: 212 recommended: 219 | 2026-10-04T16:58:50+00:00 | Vulnerability · Source |
| CVE-2022-50730 | suse_vex | SUSE CVE CVE-2022-50730 | known affected: 354 known not affected: 367 recommended: 270 | 2026-10-04T16:58:48+00:00 | Vulnerability · Source |
| CVE-2022-50849 | suse_vex | SUSE CVE CVE-2022-50849 | known affected: 548 known not affected: 178 recommended: 233 | 2026-10-04T16:58:46+00:00 | Vulnerability · Source |
| CVE-2022-50865 | suse_vex | SUSE CVE CVE-2022-50865 | known affected: 688 known not affected: 208 recommended: 72 | 2026-10-04T16:58:44+00:00 | Vulnerability · Source |
| CVE-2023-2176 | suse_vex | SUSE CVE CVE-2023-2176 | known affected: 290 known not affected: 26 recommended: 1423 | 2026-10-04T16:58:40+00:00 | Vulnerability · Source |
| CVE-2023-2194 | suse_vex | SUSE CVE CVE-2023-2194 | known affected: 388 known not affected: 102 recommended: 516 | 2026-10-04T16:58:38+00:00 | Vulnerability · Source |
| CVE-2023-2513 | suse_vex | SUSE CVE CVE-2023-2513 | known affected: 303 known not affected: 6 recommended: 1232 | 2026-10-04T16:58:36+00:00 | Vulnerability · Source |
| CVE-2023-6917 | suse_vex | SUSE CVE CVE-2023-6917 | known affected: 657 recommended: 1254 | 2026-10-04T16:58:31+00:00 | Vulnerability · Source |
| CVE-2023-20585 | suse_vex | SUSE CVE CVE-2023-20585 | known affected: 429 known not affected: 422 recommended: 509 | 2026-10-04T16:58:29+00:00 | Vulnerability · Source |
| CVE-2023-52476 | suse_vex | SUSE CVE CVE-2023-52476 | known affected: 388 known not affected: 59 recommended: 956 | 2026-10-04T16:58:18+00:00 | Vulnerability · Source |
| CVE-2023-52527 | suse_vex | SUSE CVE CVE-2023-52527 | known affected: 773 known not affected: 103 recommended: 272 | 2026-10-04T16:58:15+00:00 | Vulnerability · Source |
| CVE-2023-52587 | suse_vex | SUSE CVE CVE-2023-52587 | known affected: 567 known not affected: 59 recommended: 612 | 2026-10-04T16:58:13+00:00 | Vulnerability · Source |
| CVE-2023-52590 | suse_vex | SUSE CVE CVE-2023-52590 | known affected: 133 known not affected: 65 recommended: 778 | 2026-10-04T16:58:11+00:00 | Vulnerability · Source |