VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291949 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2021-47333 | suse_vex | SUSE CVE CVE-2021-47333 | known affected: 388 known not affected: 271 recommended: 135 | 2026-07-25T17:34:07+00:00 | Vulnerability · Source |
| CVE-2021-47336 | suse_vex | SUSE CVE CVE-2021-47336 | known not affected: 353 | 2026-07-25T17:34:04+00:00 | Vulnerability · Source |
| CVE-2021-47339 | suse_vex | SUSE CVE CVE-2021-47339 | known not affected: 330 | 2026-07-25T17:34:03+00:00 | Vulnerability · Source |
| CVE-2021-47349 | suse_vex | SUSE CVE CVE-2021-47349 | known not affected: 330 | 2026-07-25T17:33:57+00:00 | Vulnerability · Source |
| CVE-2021-47363 | suse_vex | SUSE CVE CVE-2021-47363 | known affected: 275 known not affected: 217 recommended: 452 | 2026-07-25T17:33:52+00:00 | Vulnerability · Source |
| CVE-2021-47364 | suse_vex | SUSE CVE CVE-2021-47364 | known affected: 275 known not affected: 217 recommended: 452 | 2026-07-25T17:33:50+00:00 | Vulnerability · Source |
| CVE-2021-47365 | suse_vex | SUSE CVE CVE-2021-47365 | known affected: 275 known not affected: 217 recommended: 452 | 2026-07-25T17:33:49+00:00 | Vulnerability · Source |
| CVE-2021-47411 | suse_vex | SUSE CVE CVE-2021-47411 | known not affected: 169 | 2026-07-25T17:33:35+00:00 | Vulnerability · Source |
| CVE-2021-47435 | suse_vex | SUSE CVE CVE-2021-47435 | known affected: 318 known not affected: 113 recommended: 633 | 2026-07-25T17:33:26+00:00 | Vulnerability · Source |
| CVE-2021-47439 | suse_vex | SUSE CVE CVE-2021-47439 | known affected: 275 known not affected: 217 recommended: 452 | 2026-07-25T17:33:23+00:00 | Vulnerability · Source |
| CVE-2021-47481 | suse_vex | SUSE CVE CVE-2021-47481 | known affected: 275 known not affected: 217 recommended: 452 | 2026-07-25T17:32:54+00:00 | Vulnerability · Source |
| CVE-2021-47565 | suse_vex | SUSE CVE CVE-2021-47565 | known affected: 338 known not affected: 69 recommended: 671 | 2026-07-25T17:32:26+00:00 | Vulnerability · Source |
| CVE-2021-47567 | suse_vex | SUSE CVE CVE-2021-47567 | known not affected: 330 | 2026-07-25T17:32:24+00:00 | Vulnerability · Source |
| CVE-2021-47570 | suse_vex | SUSE CVE CVE-2021-47570 | known not affected: 330 | 2026-07-25T17:32:21+00:00 | Vulnerability · Source |
| CVE-2021-47573 | suse_vex | SUSE CVE CVE-2021-47573 | known affected: 6 known not affected: 312 | 2026-07-25T17:32:17+00:00 | Vulnerability · Source |
| CVE-2021-47575 | suse_vex | SUSE CVE CVE-2021-47575 | known affected: 6 known not affected: 312 | 2026-07-25T17:32:16+00:00 | Vulnerability · Source |
| CVE-2021-47619 | suse_vex | SUSE CVE CVE-2021-47619 | known affected: 412 known not affected: 60 recommended: 566 | 2026-07-25T17:31:57+00:00 | Vulnerability · Source |
| CVE-2021-47631 | suse_vex | SUSE CVE CVE-2021-47631 | known affected: 334 known not affected: 270 recommended: 293 | 2026-07-25T17:31:54+00:00 | Vulnerability · Source |
| CVE-2021-47645 | suse_vex | SUSE CVE CVE-2021-47645 | known affected: 334 known not affected: 270 recommended: 263 | 2026-07-25T17:31:49+00:00 | Vulnerability · Source |
| CVE-2021-47647 | suse_vex | SUSE CVE CVE-2021-47647 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:31:48+00:00 | Vulnerability · Source |
| CVE-2021-47655 | suse_vex | SUSE CVE CVE-2021-47655 | known not affected: 352 | 2026-07-25T17:31:43+00:00 | Vulnerability · Source |
| CVE-2021-47660 | suse_vex | SUSE CVE CVE-2021-47660 | known not affected: 352 | 2026-07-25T17:31:40+00:00 | Vulnerability · Source |
| CVE-2022-0135 | suse_vex | SUSE CVE CVE-2022-0135 | recommended: 161 | 2026-07-25T17:31:33+00:00 | Vulnerability · Source |
| CVE-2022-0358 | suse_vex | SUSE CVE CVE-2022-0358 | known affected: 394 known not affected: 921 recommended: 1121 | 2026-07-25T17:31:22+00:00 | Vulnerability · Source |
| CVE-2022-0413 | suse_vex | SUSE CVE CVE-2022-0413 | known affected: 341 known not affected: 30 recommended: 410 | 2026-07-25T17:31:19+00:00 | Vulnerability · Source |
| CVE-2022-0530 | suse_vex | SUSE CVE CVE-2022-0530 | known affected: 417 known not affected: 9 recommended: 52 | 2026-07-25T17:31:14+00:00 | Vulnerability · Source |
| CVE-2022-0561 | suse_vex | SUSE CVE CVE-2022-0561 | known affected: 395 known not affected: 5 recommended: 269 | 2026-07-25T17:31:13+00:00 | Vulnerability · Source |
| CVE-2022-0615 | suse_vex | SUSE CVE CVE-2022-0615 | known not affected: 401 | 2026-07-25T17:31:06+00:00 | Vulnerability · Source |
| CVE-2022-0934 | suse_vex | SUSE CVE CVE-2022-0934 | recommended: 102 | 2026-07-25T17:30:58+00:00 | Vulnerability · Source |
| CVE-2022-1122 | suse_vex | SUSE CVE CVE-2022-1122 | known not affected: 172 recommended: 213 | 2026-07-25T17:30:49+00:00 | Vulnerability · Source |
| CVE-2022-1184 | suse_vex | SUSE CVE CVE-2022-1184 | known affected: 190 known not affected: 2 recommended: 1872 | 2026-07-25T17:30:47+00:00 | Vulnerability · Source |
| CVE-2022-1195 | suse_vex | SUSE CVE CVE-2022-1195 | known affected: 216 known not affected: 325 recommended: 825 | 2026-07-25T17:30:45+00:00 | Vulnerability · Source |
| CVE-2022-1270 | suse_vex | SUSE CVE CVE-2022-1270 | known affected: 3 known not affected: 335 recommended: 142 | 2026-07-25T17:30:40+00:00 | Vulnerability · Source |
| CVE-2022-1304 | suse_vex | SUSE CVE CVE-2022-1304 | known affected: 351 known not affected: 3 recommended: 679 | 2026-07-25T17:30:37+00:00 | Vulnerability · Source |
| CVE-2022-1354 | suse_vex | SUSE CVE CVE-2022-1354 | known not affected: 211 recommended: 3 | 2026-07-25T17:30:33+00:00 | Vulnerability · Source |
| CVE-2022-1381 | suse_vex | SUSE CVE CVE-2022-1381 | known affected: 353 known not affected: 35 recommended: 387 | 2026-07-25T17:30:31+00:00 | Vulnerability · Source |
| CVE-2022-1615 | suse_vex | SUSE CVE CVE-2022-1615 | known affected: 245 known not affected: 1536 recommended: 1094 | 2026-07-25T17:30:28+00:00 | Vulnerability · Source |
| CVE-2022-1725 | suse_vex | SUSE CVE CVE-2022-1725 | known not affected: 240 | 2026-07-25T17:30:21+00:00 | Vulnerability · Source |
| CVE-2022-1736 | suse_vex | SUSE CVE CVE-2022-1736 | known not affected: 203 recommended: 3 | 2026-07-25T17:30:18+00:00 | Vulnerability · Source |
| CVE-2022-1852 | suse_vex | SUSE CVE CVE-2022-1852 | known affected: 257 known not affected: 335 recommended: 663 | 2026-07-25T17:30:16+00:00 | Vulnerability · Source |
| CVE-2022-1922 | suse_vex | SUSE CVE CVE-2022-1922 | known affected: 2 known not affected: 10 recommended: 175 | 2026-07-25T17:30:12+00:00 | Vulnerability · Source |
| CVE-2022-1924 | suse_vex | SUSE CVE CVE-2022-1924 | known affected: 2 known not affected: 10 recommended: 166 | 2026-07-25T17:30:09+00:00 | Vulnerability · Source |
| CVE-2022-2068 | suse_vex | SUSE CVE CVE-2022-2068 | known affected: 213 known not affected: 600 recommended: 1107 | 2026-07-25T17:30:02+00:00 | Vulnerability · Source |
| CVE-2022-2129 | suse_vex | SUSE CVE CVE-2022-2129 | known affected: 237 known not affected: 26 recommended: 505 | 2026-07-25T17:30:00+00:00 | Vulnerability · Source |
| CVE-2022-2209 | suse_vex | SUSE CVE CVE-2022-2209 | known not affected: 327 | 2026-07-25T17:29:58+00:00 | Vulnerability · Source |
| CVE-2022-2210 | suse_vex | SUSE CVE CVE-2022-2210 | known affected: 237 known not affected: 26 recommended: 505 | 2026-07-25T17:29:56+00:00 | Vulnerability · Source |
| CVE-2022-2257 | suse_vex | SUSE CVE CVE-2022-2257 | known affected: 247 recommended: 505 | 2026-07-25T17:29:55+00:00 | Vulnerability · Source |
| CVE-2022-2274 | suse_vex | SUSE CVE CVE-2022-2274 | known not affected: 681 recommended: 207 | 2026-07-25T17:29:53+00:00 | Vulnerability · Source |
| CVE-2022-2287 | suse_vex | SUSE CVE CVE-2022-2287 | known affected: 237 known not affected: 26 recommended: 505 | 2026-07-25T17:29:50+00:00 | Vulnerability · Source |
| CVE-2022-2309 | suse_vex | SUSE CVE CVE-2022-2309 | known affected: 394 known not affected: 100 recommended: 275 | 2026-07-25T17:29:47+00:00 | Vulnerability · Source |