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-0554 | suse_vex | SUSE CVE CVE-2022-0554 | known not affected: 242 recommended: 26 | 2026-07-19T18:14:20+00:00 | Vulnerability · Source |
| CVE-2022-0563 | suse_vex | SUSE CVE CVE-2022-0563 | known not affected: 772 recommended: 387 | 2026-07-19T18:14:19+00:00 | Vulnerability · Source |
| CVE-2022-0582 | suse_vex | SUSE CVE CVE-2022-0582 | known not affected: 101 recommended: 339 | 2026-07-19T18:14:18+00:00 | Vulnerability · Source |
| CVE-2022-0714 | suse_vex | SUSE CVE CVE-2022-0714 | known not affected: 256 recommended: 21 | 2026-07-19T18:14:17+00:00 | Vulnerability · Source |
| CVE-2022-0856 | suse_vex | SUSE CVE CVE-2022-0856 | known affected: 39 recommended: 149 | 2026-07-19T18:14:15+00:00 | Vulnerability · Source |
| CVE-2022-0907 | suse_vex | SUSE CVE CVE-2022-0907 | known not affected: 206 recommended: 45 | 2026-07-19T18:14:14+00:00 | Vulnerability · Source |
| CVE-2022-0909 | suse_vex | SUSE CVE CVE-2022-0909 | known affected: 433 known not affected: 13 recommended: 232 | 2026-07-19T18:14:13+00:00 | Vulnerability · Source |
| CVE-2022-0934 | suse_vex | SUSE CVE CVE-2022-0934 | recommended: 98 | 2026-07-19T18:14:12+00:00 | Vulnerability · Source |
| CVE-2022-0943 | suse_vex | SUSE CVE CVE-2022-0943 | known not affected: 256 recommended: 26 | 2026-07-19T18:14:10+00:00 | Vulnerability · Source |
| CVE-2022-1097 | suse_vex | SUSE CVE CVE-2022-1097 | known affected: 391 known not affected: 128 recommended: 1519 | 2026-07-19T18:14:09+00:00 | Vulnerability · Source |
| CVE-2022-1215 | suse_vex | SUSE CVE CVE-2022-1215 | known affected: 394 known not affected: 75 recommended: 238 | 2026-07-19T18:14:07+00:00 | Vulnerability · Source |
| CVE-2022-1620 | suse_vex | SUSE CVE CVE-2022-1620 | known affected: 363 recommended: 371 | 2026-07-19T18:14:06+00:00 | Vulnerability · Source |
| CVE-2022-1796 | suse_vex | SUSE CVE CVE-2022-1796 | known affected: 363 recommended: 371 | 2026-07-19T18:14:04+00:00 | Vulnerability · Source |
| CVE-2022-1897 | suse_vex | SUSE CVE CVE-2022-1897 | known affected: 363 recommended: 381 | 2026-07-19T18:14:03+00:00 | Vulnerability · Source |
| CVE-2022-1898 | suse_vex | SUSE CVE CVE-2022-1898 | known affected: 363 recommended: 371 | 2026-07-19T18:14:01+00:00 | Vulnerability · Source |
| CVE-2022-1920 | suse_vex | SUSE CVE CVE-2022-1920 | known affected: 2 known not affected: 10 recommended: 167 | 2026-07-19T18:14:00+00:00 | Vulnerability · Source |
| CVE-2022-1922 | suse_vex | SUSE CVE CVE-2022-1922 | known affected: 2 known not affected: 10 recommended: 167 | 2026-07-19T18:13:59+00:00 | Vulnerability · Source |
| CVE-2022-1923 | suse_vex | SUSE CVE CVE-2022-1923 | known affected: 2 known not affected: 10 recommended: 158 | 2026-07-19T18:13:58+00:00 | Vulnerability · Source |
| CVE-2022-1925 | suse_vex | SUSE CVE CVE-2022-1925 | known affected: 2 known not affected: 10 recommended: 158 | 2026-07-19T18:13:57+00:00 | Vulnerability · Source |
| CVE-2022-1968 | suse_vex | SUSE CVE CVE-2022-1968 | known affected: 247 recommended: 489 | 2026-07-19T18:13:56+00:00 | Vulnerability · Source |
| CVE-2022-2000 | suse_vex | SUSE CVE CVE-2022-2000 | known not affected: 241 recommended: 21 | 2026-07-19T18:13:54+00:00 | Vulnerability · Source |
| CVE-2022-2042 | suse_vex | SUSE CVE CVE-2022-2042 | known not affected: 241 recommended: 21 | 2026-07-19T18:13:53+00:00 | Vulnerability · Source |
| CVE-2022-2084 | suse_vex | SUSE CVE CVE-2022-2084 | known affected: 254 recommended: 249 | 2026-07-19T18:13:52+00:00 | Vulnerability · Source |
| CVE-2022-2122 | suse_vex | SUSE CVE CVE-2022-2122 | known affected: 2 known not affected: 10 recommended: 167 | 2026-07-19T18:13:51+00:00 | Vulnerability · Source |
| CVE-2022-2129 | suse_vex | SUSE CVE CVE-2022-2129 | known affected: 237 known not affected: 23 recommended: 489 | 2026-07-19T18:13:49+00:00 | Vulnerability · Source |
| CVE-2022-2207 | suse_vex | SUSE CVE CVE-2022-2207 | known affected: 237 known not affected: 23 recommended: 489 | 2026-07-19T18:13:48+00:00 | Vulnerability · Source |
| CVE-2022-2210 | suse_vex | SUSE CVE CVE-2022-2210 | known affected: 237 known not affected: 23 recommended: 489 | 2026-07-19T18:13:47+00:00 | Vulnerability · Source |
| CVE-2022-2264 | suse_vex | SUSE CVE CVE-2022-2264 | known affected: 237 known not affected: 23 recommended: 489 | 2026-07-19T18:13:45+00:00 | Vulnerability · Source |
| CVE-2022-2287 | suse_vex | SUSE CVE CVE-2022-2287 | known affected: 237 known not affected: 23 recommended: 489 | 2026-07-19T18:13:44+00:00 | Vulnerability · Source |
| CVE-2022-2288 | suse_vex | SUSE CVE CVE-2022-2288 | known not affected: 242 recommended: 21 | 2026-07-19T18:13:43+00:00 | Vulnerability · Source |
| CVE-2022-2345 | suse_vex | SUSE CVE CVE-2022-2345 | known affected: 237 known not affected: 2 recommended: 489 | 2026-07-19T18:13:42+00:00 | Vulnerability · Source |
| CVE-2022-2505 | suse_vex | SUSE CVE CVE-2022-2505 | known affected: 1 recommended: 445 | 2026-07-19T18:13:40+00:00 | Vulnerability · Source |
| CVE-2022-2521 | suse_vex | SUSE CVE CVE-2022-2521 | known affected: 395 known not affected: 1 recommended: 257 | 2026-07-19T18:13:39+00:00 | Vulnerability · Source |
| CVE-2022-2581 | suse_vex | SUSE CVE CVE-2022-2581 | known affected: 238 recommended: 489 | 2026-07-19T18:13:38+00:00 | Vulnerability · Source |
| CVE-2022-2601 | suse_vex | SUSE CVE CVE-2022-2601 | known affected: 260 recommended: 801 | 2026-07-19T18:13:36+00:00 | Vulnerability · Source |
| CVE-2022-2819 | suse_vex | SUSE CVE CVE-2022-2819 | known affected: 237 known not affected: 2 recommended: 489 | 2026-07-19T18:13:35+00:00 | Vulnerability · Source |
| CVE-2022-2845 | suse_vex | SUSE CVE CVE-2022-2845 | known affected: 238 recommended: 489 | 2026-07-19T18:13:34+00:00 | Vulnerability · Source |
| CVE-2022-2850 | suse_vex | SUSE CVE CVE-2022-2850 | known not affected: 70 recommended: 113 | 2026-07-19T18:13:32+00:00 | Vulnerability · Source |
| CVE-2022-2868 | suse_vex | SUSE CVE CVE-2022-2868 | known affected: 395 known not affected: 1 recommended: 254 | 2026-07-19T18:13:31+00:00 | Vulnerability · Source |
| CVE-2022-2869 | suse_vex | SUSE CVE CVE-2022-2869 | known affected: 395 known not affected: 1 recommended: 254 | 2026-07-19T18:13:30+00:00 | Vulnerability · Source |
| CVE-2022-2879 | suse_vex | SUSE CVE CVE-2022-2879 | recommended: 269 | 2026-07-19T18:13:29+00:00 | Vulnerability · Source |
| CVE-2022-2881 | suse_vex | SUSE CVE CVE-2022-2881 | known not affected: 487 recommended: 25 | 2026-07-19T18:13:27+00:00 | Vulnerability · Source |
| CVE-2022-3134 | suse_vex | SUSE CVE CVE-2022-3134 | known affected: 259 known not affected: 2 recommended: 469 | 2026-07-19T18:13:26+00:00 | Vulnerability · Source |
| CVE-2022-3235 | suse_vex | SUSE CVE CVE-2022-3235 | known affected: 259 known not affected: 2 recommended: 469 | 2026-07-19T18:13:24+00:00 | Vulnerability · Source |
| CVE-2022-3287 | suse_vex | SUSE CVE CVE-2022-3287 | known not affected: 227 recommended: 125 | 2026-07-19T18:13:23+00:00 | Vulnerability · Source |
| CVE-2022-3352 | suse_vex | SUSE CVE CVE-2022-3352 | known affected: 259 known not affected: 2 recommended: 469 | 2026-07-19T18:13:22+00:00 | Vulnerability · Source |
| CVE-2022-3599 | suse_vex | SUSE CVE CVE-2022-3599 | known affected: 395 known not affected: 1 recommended: 255 | 2026-07-19T18:13:20+00:00 | Vulnerability · Source |
| CVE-2022-3626 | suse_vex | SUSE CVE CVE-2022-3626 | known affected: 395 known not affected: 1 recommended: 255 | 2026-07-19T18:13:19+00:00 | Vulnerability · Source |
| CVE-2022-3775 | suse_vex | SUSE CVE CVE-2022-3775 | known affected: 260 recommended: 788 | 2026-07-19T18:13:17+00:00 | Vulnerability · Source |
| CVE-2022-3786 | suse_vex | SUSE CVE CVE-2022-3786 | known not affected: 582 recommended: 171 | 2026-07-19T18:13:16+00:00 | Vulnerability · Source |