VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
282994 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-3736 | suse_vex | SUSE CVE CVE-2022-3736 | known affected: 264 known not affected: 322 recommended: 200 | 2026-07-21T13:27:04+00:00 | Vulnerability · Source |
| CVE-2022-3964 | suse_vex | SUSE CVE CVE-2022-3964 | known not affected: 533 recommended: 210 | 2026-07-21T13:27:03+00:00 | Vulnerability · Source |
| CVE-2022-4285 | suse_vex | SUSE CVE CVE-2022-4285 | known affected: 462 known not affected: 1 recommended: 320 | 2026-07-21T13:27:02+00:00 | Vulnerability · Source |
| CVE-2022-20770 | suse_vex | SUSE CVE CVE-2022-20770 | known affected: 40 recommended: 172 | 2026-07-21T13:27:00+00:00 | Vulnerability · Source |
| CVE-2022-21426 | suse_vex | SUSE CVE CVE-2022-21426 | known affected: 394 known not affected: 59 recommended: 1159 | 2026-07-21T13:26:58+00:00 | Vulnerability · Source |
| CVE-2022-21541 | suse_vex | SUSE CVE CVE-2022-21541 | known affected: 392 known not affected: 22 recommended: 1144 | 2026-07-21T13:26:57+00:00 | Vulnerability · Source |
| CVE-2022-21549 | suse_vex | SUSE CVE CVE-2022-21549 | known affected: 390 known not affected: 361 recommended: 469 | 2026-07-21T13:26:56+00:00 | Vulnerability · Source |
| CVE-2022-21624 | suse_vex | SUSE CVE CVE-2022-21624 | known affected: 386 recommended: 1105 | 2026-07-21T13:26:54+00:00 | Vulnerability · Source |
| CVE-2022-22751 | suse_vex | SUSE CVE CVE-2022-22751 | recommended: 397 | 2026-07-21T13:26:52+00:00 | Vulnerability · Source |
| CVE-2022-22753 | suse_vex | SUSE CVE CVE-2022-22753 | recommended: 388 | 2026-07-21T13:26:51+00:00 | Vulnerability · Source |
| CVE-2022-24882 | suse_vex | SUSE CVE CVE-2022-24882 | recommended: 174 | 2026-07-21T13:26:49+00:00 | Vulnerability · Source |
| CVE-2022-25235 | suse_vex | SUSE CVE CVE-2022-25235 | known affected: 282 recommended: 414 | 2026-07-21T13:26:48+00:00 | Vulnerability · Source |
| CVE-2022-25314 | suse_vex | SUSE CVE CVE-2022-25314 | known affected: 282 recommended: 424 | 2026-07-21T13:26:47+00:00 | Vulnerability · Source |
| CVE-2022-26377 | suse_vex | SUSE CVE CVE-2022-26377 | known affected: 395 recommended: 513 | 2026-07-21T13:26:45+00:00 | Vulnerability · Source |
| CVE-2022-26716 | suse_vex | SUSE CVE CVE-2022-26716 | known affected: 1 recommended: 969 | 2026-07-21T13:26:44+00:00 | Vulnerability · Source |
| CVE-2022-27384 | suse_vex | SUSE CVE CVE-2022-27384 | known not affected: 74 recommended: 462 | 2026-07-21T13:26:42+00:00 | Vulnerability · Source |
| CVE-2022-28285 | suse_vex | SUSE CVE CVE-2022-28285 | known affected: 3 known not affected: 128 recommended: 389 | 2026-07-21T13:26:41+00:00 | Vulnerability · Source |
| CVE-2022-29404 | suse_vex | SUSE CVE CVE-2022-29404 | known affected: 395 known not affected: 1 recommended: 507 | 2026-07-21T13:26:39+00:00 | Vulnerability · Source |
| CVE-2022-29909 | suse_vex | SUSE CVE CVE-2022-29909 | known not affected: 2 recommended: 389 | 2026-07-21T13:26:38+00:00 | Vulnerability · Source |
| CVE-2022-30065 | suse_vex | SUSE CVE CVE-2022-30065 | known affected: 22 recommended: 185 | 2026-07-21T13:26:37+00:00 | Vulnerability · Source |
| CVE-2022-30699 | suse_vex | SUSE CVE CVE-2022-30699 | known affected: 1 recommended: 131 | 2026-07-21T13:26:36+00:00 | Vulnerability · Source |
| CVE-2022-30784 | suse_vex | SUSE CVE CVE-2022-30784 | recommended: 242 | 2026-07-21T13:26:34+00:00 | Vulnerability · Source |
| CVE-2022-31626 | suse_vex | SUSE CVE CVE-2022-31626 | known not affected: 1 recommended: 4373 | 2026-07-21T13:26:33+00:00 | Vulnerability · Source |
| CVE-2022-31627 | suse_vex | SUSE CVE CVE-2022-31627 | known not affected: 3460 recommended: 101 | 2026-07-21T13:26:31+00:00 | Vulnerability · Source |
| CVE-2022-31799 | suse_vex | SUSE CVE CVE-2022-31799 | recommended: 98 | 2026-07-21T13:26:30+00:00 | Vulnerability · Source |
| CVE-2022-32087 | suse_vex | SUSE CVE CVE-2022-32087 | known not affected: 75 recommended: 358 | 2026-07-21T13:26:28+00:00 | Vulnerability · Source |
| CVE-2022-32742 | suse_vex | SUSE CVE CVE-2022-32742 | known affected: 221 known not affected: 330 recommended: 3052 | 2026-07-21T13:26:27+00:00 | Vulnerability · Source |
| CVE-2022-32745 | suse_vex | SUSE CVE CVE-2022-32745 | known affected: 226 known not affected: 1356 recommended: 1237 | 2026-07-21T13:26:25+00:00 | Vulnerability · Source |
| CVE-2022-32893 | suse_vex | SUSE CVE CVE-2022-32893 | known affected: 29 recommended: 856 | 2026-07-21T13:26:24+00:00 | Vulnerability · Source |
| CVE-2022-33972 | suse_vex | SUSE CVE CVE-2022-33972 | known not affected: 1 recommended: 64 | 2026-07-21T13:26:22+00:00 | Vulnerability · Source |
| CVE-2022-34266 | suse_vex | SUSE CVE CVE-2022-34266 | known affected: 394 known not affected: 2 recommended: 246 | 2026-07-21T13:26:21+00:00 | Vulnerability · Source |
| CVE-2022-34476 | suse_vex | SUSE CVE CVE-2022-34476 | known affected: 1 recommended: 345 | 2026-07-21T13:26:20+00:00 | Vulnerability · Source |
| CVE-2022-35929 | suse_vex | SUSE CVE CVE-2022-35929 | recommended: 37 | 2026-07-21T13:26:18+00:00 | Vulnerability · Source |
| CVE-2022-36055 | suse_vex | SUSE CVE CVE-2022-36055 | known affected: 382 known not affected: 1 recommended: 118 | 2026-07-21T13:26:17+00:00 | Vulnerability · Source |
| CVE-2022-38477 | suse_vex | SUSE CVE CVE-2022-38477 | known affected: 2 recommended: 441 | 2026-07-21T13:26:15+00:00 | Vulnerability · Source |
| CVE-2022-38751 | suse_vex | SUSE CVE CVE-2022-38751 | known affected: 389 recommended: 47 | 2026-07-21T13:26:14+00:00 | Vulnerability · Source |
| CVE-2022-39260 | suse_vex | SUSE CVE CVE-2022-39260 | known affected: 67 known not affected: 125 recommended: 629 | 2026-07-21T13:26:13+00:00 | Vulnerability · Source |
| CVE-2022-40956 | suse_vex | SUSE CVE CVE-2022-40956 | known affected: 1 recommended: 421 | 2026-07-21T13:26:11+00:00 | Vulnerability · Source |
| CVE-2022-42799 | suse_vex | SUSE CVE CVE-2022-42799 | known affected: 1 known not affected: 117 recommended: 929 | 2026-07-21T13:26:09+00:00 | Vulnerability · Source |
| CVE-2022-44793 | suse_vex | SUSE CVE CVE-2022-44793 | known affected: 408 recommended: 194 | 2026-07-21T13:26:08+00:00 | Vulnerability · Source |
| CVE-2022-44840 | suse_vex | SUSE CVE CVE-2022-44840 | known affected: 442 recommended: 312 | 2026-07-21T13:26:06+00:00 | Vulnerability · Source |
| CVE-2022-45063 | suse_vex | SUSE CVE CVE-2022-45063 | known affected: 401 recommended: 105 | 2026-07-21T13:26:05+00:00 | Vulnerability · Source |
| CVE-2022-45748 | suse_vex | SUSE CVE CVE-2022-45748 | recommended: 3 | 2026-07-21T13:26:04+00:00 | Vulnerability · Source |
| CVE-2022-46343 | suse_vex | SUSE CVE CVE-2022-46343 | known affected: 383 recommended: 299 | 2026-07-21T13:26:03+00:00 | Vulnerability · Source |
| CVE-2022-46344 | suse_vex | SUSE CVE CVE-2022-46344 | known affected: 383 recommended: 299 | 2026-07-21T13:26:01+00:00 | Vulnerability · Source |
| CVE-2022-47022 | suse_vex | SUSE CVE CVE-2022-47022 | known not affected: 67 recommended: 34 | 2026-07-21T13:26:00+00:00 | Vulnerability · Source |
| CVE-2022-49320 | suse_vex | SUSE CVE CVE-2022-49320 | known affected: 401 known not affected: 209 recommended: 354 | 2026-07-21T13:25:53+00:00 | Vulnerability · Source |
| CVE-2022-50253 | suse_vex | SUSE CVE CVE-2022-50253 | first fixed: 2 known affected: 615 known not affected: 22 recommended: 523 | 2026-07-21T13:25:46+00:00 | Vulnerability · Source |
| CVE-2022-50258 | suse_vex | SUSE CVE CVE-2022-50258 | known affected: 417 known not affected: 193 recommended: 359 | 2026-07-21T13:25:45+00:00 | Vulnerability · Source |
| CVE-2022-50401 | suse_vex | SUSE CVE CVE-2022-50401 | known affected: 344 known not affected: 237 recommended: 291 | 2026-07-21T13:25:43+00:00 | Vulnerability · Source |