VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286675 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-41848 | suse_vex | SUSE CVE CVE-2022-41848 | known affected: 253 known not affected: 20 recommended: 1493 | 2026-07-31T17:04:09+00:00 | Vulnerability · Source |
| CVE-2022-41858 | suse_vex | SUSE CVE CVE-2022-41858 | known affected: 267 known not affected: 81 recommended: 1591 | 2026-07-31T17:04:07+00:00 | Vulnerability · Source |
| CVE-2022-42890 | suse_vex | SUSE CVE CVE-2022-42890 | recommended: 71 | 2026-07-31T17:04:05+00:00 | Vulnerability · Source |
| CVE-2022-44792 | suse_vex | SUSE CVE CVE-2022-44792 | known affected: 36 known not affected: 2 recommended: 195 | 2026-07-31T17:04:03+00:00 | Vulnerability · Source |
| CVE-2022-45869 | suse_vex | SUSE CVE CVE-2022-45869 | known affected: 279 known not affected: 297 recommended: 662 | 2026-07-31T17:04:01+00:00 | Vulnerability · Source |
| CVE-2022-46344 | suse_vex | SUSE CVE CVE-2022-46344 | known affected: 395 recommended: 309 | 2026-07-31T17:03:59+00:00 | Vulnerability · Source |
| CVE-2022-48770 | suse_vex | SUSE CVE CVE-2022-48770 | known affected: 434 known not affected: 202 recommended: 298 | 2026-07-31T17:03:55+00:00 | Vulnerability · Source |
| CVE-2022-48817 | suse_vex | SUSE CVE CVE-2022-48817 | known affected: 295 known not affected: 205 recommended: 426 | 2026-07-31T17:03:53+00:00 | Vulnerability · Source |
| CVE-2022-48921 | suse_vex | SUSE CVE CVE-2022-48921 | known affected: 310 known not affected: 195 recommended: 433 | 2026-07-31T17:03:51+00:00 | Vulnerability · Source |
| CVE-2022-48948 | suse_vex | SUSE CVE CVE-2022-48948 | known affected: 451 known not affected: 149 recommended: 394 | 2026-07-31T17:03:49+00:00 | Vulnerability · Source |
| CVE-2022-48953 | suse_vex | SUSE CVE CVE-2022-48953 | known affected: 462 known not affected: 117 recommended: 434 | 2026-07-31T17:03:47+00:00 | Vulnerability · Source |
| CVE-2022-48966 | suse_vex | SUSE CVE CVE-2022-48966 | known affected: 390 known not affected: 260 recommended: 311 | 2026-07-31T17:03:45+00:00 | Vulnerability · Source |
| CVE-2022-49031 | suse_vex | SUSE CVE CVE-2022-49031 | known affected: 396 known not affected: 151 recommended: 478 | 2026-07-31T17:03:43+00:00 | Vulnerability · Source |
| CVE-2022-49032 | suse_vex | SUSE CVE CVE-2022-49032 | known affected: 422 known not affected: 125 recommended: 478 | 2026-07-31T17:03:41+00:00 | Vulnerability · Source |
| CVE-2022-49048 | suse_vex | SUSE CVE CVE-2022-49048 | known affected: 112 known not affected: 240 | 2026-07-31T17:03:39+00:00 | Vulnerability · Source |
| CVE-2022-49192 | suse_vex | SUSE CVE CVE-2022-49192 | known not affected: 302 recommended: 70 | 2026-07-31T17:03:36+00:00 | Vulnerability · Source |
| CVE-2022-49227 | suse_vex | SUSE CVE CVE-2022-49227 | known affected: 334 known not affected: 298 recommended: 265 | 2026-07-31T17:03:34+00:00 | Vulnerability · Source |
| CVE-2022-49245 | suse_vex | SUSE CVE CVE-2022-49245 | known not affected: 352 | 2026-07-31T17:03:33+00:00 | Vulnerability · Source |
| CVE-2022-49424 | suse_vex | SUSE CVE CVE-2022-49424 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-31T17:03:30+00:00 | Vulnerability · Source |
| CVE-2022-49510 | suse_vex | SUSE CVE CVE-2022-49510 | known affected: 364 known not affected: 302 recommended: 100 | 2026-07-31T17:03:28+00:00 | Vulnerability · Source |
| CVE-2022-49563 | suse_vex | SUSE CVE CVE-2022-49563 | known affected: 424 known not affected: 148 recommended: 370 | 2026-07-31T17:03:25+00:00 | Vulnerability · Source |
| CVE-2022-49694 | suse_vex | SUSE CVE CVE-2022-49694 | known affected: 364 known not affected: 302 recommended: 100 | 2026-07-31T17:03:23+00:00 | Vulnerability · Source |
| CVE-2022-49697 | suse_vex | SUSE CVE CVE-2022-49697 | known affected: 470 known not affected: 196 recommended: 142 | 2026-07-31T17:03:21+00:00 | Vulnerability · Source |
| CVE-2022-49883 | suse_vex | SUSE CVE CVE-2022-49883 | known not affected: 397 | 2026-07-31T17:03:19+00:00 | Vulnerability · Source |
| CVE-2022-49911 | suse_vex | SUSE CVE CVE-2022-49911 | known affected: 55 known not affected: 342 recommended: 27 | 2026-07-31T17:03:17+00:00 | Vulnerability · Source |
| CVE-2022-49926 | suse_vex | SUSE CVE CVE-2022-49926 | known affected: 154 known not affected: 258 | 2026-07-31T17:03:16+00:00 | Vulnerability · Source |
| CVE-2022-50039 | suse_vex | SUSE CVE CVE-2022-50039 | known affected: 344 known not affected: 298 recommended: 253 | 2026-07-31T17:03:14+00:00 | Vulnerability · Source |
| CVE-2022-50113 | suse_vex | SUSE CVE CVE-2022-50113 | known not affected: 401 recommended: 47 | 2026-07-31T17:03:12+00:00 | Vulnerability · Source |
| CVE-2022-50183 | suse_vex | SUSE CVE CVE-2022-50183 | known affected: 369 known not affected: 347 recommended: 92 | 2026-07-31T17:03:10+00:00 | Vulnerability · Source |
| CVE-2022-50639 | suse_vex | SUSE CVE CVE-2022-50639 | known not affected: 408 recommended: 29 | 2026-07-31T17:03:03+00:00 | Vulnerability · Source |
| CVE-2022-50645 | suse_vex | SUSE CVE CVE-2022-50645 | known affected: 191 known not affected: 217 recommended: 29 | 2026-07-31T17:03:01+00:00 | Vulnerability · Source |
| CVE-2022-50758 | suse_vex | SUSE CVE CVE-2022-50758 | known affected: 354 known not affected: 329 recommended: 200 | 2026-07-31T17:02:59+00:00 | Vulnerability · Source |
| CVE-2022-50763 | suse_vex | SUSE CVE CVE-2022-50763 | known affected: 354 known not affected: 309 recommended: 196 | 2026-07-31T17:02:57+00:00 | Vulnerability · Source |
| CVE-2022-50779 | suse_vex | SUSE CVE CVE-2022-50779 | known affected: 354 known not affected: 204 recommended: 219 | 2026-07-31T17:02:55+00:00 | Vulnerability · Source |
| CVE-2023-1601 | suse_vex | SUSE CVE CVE-2023-1601 | known not affected: 340 | 2026-07-31T17:02:51+00:00 | Vulnerability · Source |
| CVE-2023-1829 | suse_vex | SUSE CVE CVE-2023-1829 | known affected: 205 known not affected: 54 recommended: 1580 | 2026-07-31T17:02:50+00:00 | Vulnerability · Source |
| CVE-2023-2177 | suse_vex | SUSE CVE CVE-2023-2177 | known affected: 199 known not affected: 124 recommended: 947 | 2026-07-31T17:02:48+00:00 | Vulnerability · Source |
| CVE-2023-3341 | suse_vex | SUSE CVE CVE-2023-3341 | known affected: 236 known not affected: 11 recommended: 742 | 2026-07-31T17:02:46+00:00 | Vulnerability · Source |
| CVE-2023-4046 | suse_vex | SUSE CVE CVE-2023-4046 | known affected: 43 recommended: 271 | 2026-07-31T17:02:44+00:00 | Vulnerability · Source |
| CVE-2023-32360 | suse_vex | SUSE CVE CVE-2023-32360 | known affected: 364 recommended: 677 | 2026-07-31T17:02:33+00:00 | Vulnerability · Source |
| CVE-2023-36661 | suse_vex | SUSE CVE CVE-2023-36661 | known affected: 84 known not affected: 178 recommended: 108 | 2026-07-31T17:02:31+00:00 | Vulnerability · Source |
| CVE-2023-42465 | suse_vex | SUSE CVE CVE-2023-42465 | known affected: 302 recommended: 317 | 2026-07-31T17:02:28+00:00 | Vulnerability · Source |
| CVE-2023-47108 | suse_vex | SUSE CVE CVE-2023-47108 | known affected: 320 known not affected: 499 recommended: 326 | 2026-07-31T17:02:24+00:00 | Vulnerability · Source |
| CVE-2023-53080 | suse_vex | SUSE CVE CVE-2023-53080 | known affected: 521 known not affected: 244 recommended: 23 | 2026-07-31T17:02:12+00:00 | Vulnerability · Source |
| CVE-2024-12718 | suse_vex | SUSE CVE CVE-2024-12718 | known affected: 344 known not affected: 145 recommended: 931 | 2026-07-31T17:01:55+00:00 | Vulnerability · Source |
| CVE-2024-26801 | suse_vex | SUSE CVE CVE-2024-26801 | known affected: 557 known not affected: 70 recommended: 608 | 2026-07-31T17:01:49+00:00 | Vulnerability · Source |
| CVE-2024-26886 | suse_vex | SUSE CVE CVE-2024-26886 | known affected: 620 known not affected: 114 recommended: 385 | 2026-07-31T17:01:46+00:00 | Vulnerability · Source |
| CVE-2024-26894 | suse_vex | SUSE CVE CVE-2024-26894 | known affected: 545 known not affected: 76 recommended: 623 | 2026-07-31T17:01:45+00:00 | Vulnerability · Source |
| CVE-2024-38541 | suse_vex | SUSE CVE CVE-2024-38541 | known affected: 284 known not affected: 113 recommended: 989 | 2026-07-31T17:01:29+00:00 | Vulnerability · Source |
| CVE-2024-39689 | suse_vex | SUSE CVE CVE-2024-39689 | known not affected: 142 recommended: 27 | 2026-07-31T17:01:26+00:00 | Vulnerability · Source |