VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2021-28703 | suse_vex | SUSE CVE CVE-2021-28703 | known not affected: 357 recommended: 8 | 2026-07-26T16:53:12+00:00 | Vulnerability · Source |
| CVE-2021-29964 | suse_vex | SUSE CVE CVE-2021-29964 | known affected: 46 recommended: 438 | 2026-07-26T16:53:10+00:00 | Vulnerability · Source |
| CVE-2021-29967 | suse_vex | SUSE CVE CVE-2021-29967 | known affected: 46 recommended: 442 | 2026-07-26T16:53:09+00:00 | Vulnerability · Source |
| CVE-2021-29989 | suse_vex | SUSE CVE CVE-2021-29989 | known affected: 1 known not affected: 24 recommended: 522 | 2026-07-26T16:53:07+00:00 | Vulnerability · Source |
| CVE-2021-31440 | suse_vex | SUSE CVE CVE-2021-31440 | known affected: 2 known not affected: 328 recommended: 29 | 2026-07-26T16:53:03+00:00 | Vulnerability · Source |
| CVE-2021-34403 | suse_vex | SUSE CVE CVE-2021-34403 | known not affected: 419 | 2026-07-26T16:52:59+00:00 | Vulnerability · Source |
| CVE-2021-35331 | suse_vex | SUSE CVE CVE-2021-35331 | recommended: 216 | 2026-07-26T16:52:58+00:00 | Vulnerability · Source |
| CVE-2021-35465 | suse_vex | SUSE CVE CVE-2021-35465 | known affected: 2 known not affected: 2537 | 2026-07-26T16:52:56+00:00 | Vulnerability · Source |
| CVE-2021-35604 | suse_vex | SUSE CVE CVE-2021-35604 | known not affected: 86 recommended: 446 | 2026-07-26T16:52:54+00:00 | Vulnerability · Source |
| CVE-2021-38604 | suse_vex | SUSE CVE CVE-2021-38604 | known not affected: 651 | 2026-07-26T16:52:52+00:00 | Vulnerability · Source |
| CVE-2021-39921 | suse_vex | SUSE CVE CVE-2021-39921 | known affected: 20 recommended: 288 | 2026-07-26T16:52:50+00:00 | Vulnerability · Source |
| CVE-2021-43535 | suse_vex | SUSE CVE CVE-2021-43535 | known not affected: 156 recommended: 2 | 2026-07-26T16:52:47+00:00 | Vulnerability · Source |
| CVE-2021-45046 | suse_vex | SUSE CVE CVE-2021-45046 | known not affected: 201 recommended: 134 | 2026-07-26T16:52:46+00:00 | Vulnerability · Source |
| CVE-2021-46101 | suse_vex | SUSE CVE CVE-2021-46101 | known not affected: 573 | 2026-07-26T16:52:42+00:00 | Vulnerability · Source |
| CVE-2021-46935 | suse_vex | SUSE CVE CVE-2021-46935 | known not affected: 312 | 2026-07-26T16:52:39+00:00 | Vulnerability · Source |
| CVE-2021-47634 | suse_vex | SUSE CVE CVE-2021-47634 | known affected: 649 known not affected: 152 recommended: 40 | 2026-07-26T16:52:14+00:00 | Vulnerability · Source |
| CVE-2022-0392 | suse_vex | SUSE CVE CVE-2022-0392 | known affected: 353 known not affected: 32 recommended: 392 | 2026-07-26T16:52:05+00:00 | Vulnerability · Source |
| CVE-2022-2526 | suse_vex | SUSE CVE CVE-2022-2526 | known not affected: 598 recommended: 18 | 2026-07-26T16:51:52+00:00 | Vulnerability · Source |
| CVE-2022-4127 | suse_vex | SUSE CVE CVE-2022-4127 | known not affected: 333 | 2026-07-26T16:51:45+00:00 | Vulnerability · Source |
| CVE-2022-20008 | suse_vex | SUSE CVE CVE-2022-20008 | known affected: 222 known not affected: 155 recommended: 1074 | 2026-07-26T16:51:43+00:00 | Vulnerability · Source |
| CVE-2022-21131 | suse_vex | SUSE CVE CVE-2022-21131 | known not affected: 87 | 2026-07-26T16:51:42+00:00 | Vulnerability · Source |
| CVE-2022-23033 | suse_vex | SUSE CVE CVE-2022-23033 | known affected: 340 known not affected: 238 recommended: 333 | 2026-07-26T16:51:39+00:00 | Vulnerability · Source |
| CVE-2022-23218 | suse_vex | SUSE CVE CVE-2022-23218 | known affected: 339 recommended: 1452 | 2026-07-26T16:51:37+00:00 | Vulnerability · Source |
| CVE-2022-26125 | suse_vex | SUSE CVE CVE-2022-26125 | recommended: 255 | 2026-07-26T16:51:32+00:00 | Vulnerability · Source |
| CVE-2022-31737 | suse_vex | SUSE CVE CVE-2022-31737 | known not affected: 1 recommended: 405 | 2026-07-26T16:51:24+00:00 | Vulnerability · Source |
| CVE-2022-32087 | suse_vex | SUSE CVE CVE-2022-32087 | known not affected: 94 recommended: 378 | 2026-07-26T16:51:21+00:00 | Vulnerability · Source |
| CVE-2022-38229 | suse_vex | SUSE CVE CVE-2022-38229 | known not affected: 330 | 2026-07-26T16:51:15+00:00 | Vulnerability · Source |
| CVE-2022-45404 | suse_vex | SUSE CVE CVE-2022-45404 | known affected: 1 recommended: 405 | 2026-07-26T16:51:11+00:00 | Vulnerability · Source |
| CVE-2022-47939 | suse_vex | SUSE CVE CVE-2022-47939 | known not affected: 362 | 2026-07-26T16:51:09+00:00 | Vulnerability · Source |
| CVE-2022-48560 | suse_vex | SUSE CVE CVE-2022-48560 | known affected: 394 known not affected: 698 recommended: 209 | 2026-07-26T16:51:06+00:00 | Vulnerability · Source |
| CVE-2022-48670 | suse_vex | SUSE CVE CVE-2022-48670 | known not affected: 554 | 2026-07-26T16:51:03+00:00 | Vulnerability · Source |
| CVE-2022-48740 | suse_vex | SUSE CVE CVE-2022-48740 | known affected: 330 known not affected: 198 recommended: 475 | 2026-07-26T16:50:59+00:00 | Vulnerability · Source |
| CVE-2022-48745 | suse_vex | SUSE CVE CVE-2022-48745 | known affected: 330 known not affected: 205 recommended: 391 | 2026-07-26T16:50:57+00:00 | Vulnerability · Source |
| CVE-2022-48811 | suse_vex | SUSE CVE CVE-2022-48811 | known affected: 385 known not affected: 121 recommended: 581 | 2026-07-26T16:50:52+00:00 | Vulnerability · Source |
| CVE-2022-48920 | suse_vex | SUSE CVE CVE-2022-48920 | known affected: 512 known not affected: 86 recommended: 358 | 2026-07-26T16:50:45+00:00 | Vulnerability · Source |
| CVE-2022-48998 | suse_vex | SUSE CVE CVE-2022-48998 | known not affected: 379 | 2026-07-26T16:50:33+00:00 | Vulnerability · Source |
| CVE-2022-49043 | suse_vex | SUSE CVE CVE-2022-49043 | known affected: 396 known not affected: 397 recommended: 243 | 2026-07-26T16:50:32+00:00 | Vulnerability · Source |
| CVE-2022-49297 | suse_vex | SUSE CVE CVE-2022-49297 | known affected: 395 known not affected: 179 recommended: 341 | 2026-07-26T16:50:22+00:00 | Vulnerability · Source |
| CVE-2022-49355 | suse_vex | SUSE CVE CVE-2022-49355 | known not affected: 352 | 2026-07-26T16:50:20+00:00 | Vulnerability · Source |
| CVE-2022-49407 | suse_vex | SUSE CVE CVE-2022-49407 | known affected: 452 known not affected: 154 recommended: 263 | 2026-07-26T16:50:19+00:00 | Vulnerability · Source |
| CVE-2022-49462 | suse_vex | SUSE CVE CVE-2022-49462 | known affected: 348 known not affected: 256 recommended: 293 | 2026-07-26T16:50:17+00:00 | Vulnerability · Source |
| CVE-2022-49464 | suse_vex | SUSE CVE CVE-2022-49464 | known not affected: 352 | 2026-07-26T16:50:15+00:00 | Vulnerability · Source |
| CVE-2022-49500 | suse_vex | SUSE CVE CVE-2022-49500 | known not affected: 352 | 2026-07-26T16:50:12+00:00 | Vulnerability · Source |
| CVE-2022-49557 | suse_vex | SUSE CVE CVE-2022-49557 | known not affected: 352 recommended: 42 | 2026-07-26T16:50:10+00:00 | Vulnerability · Source |
| CVE-2022-49675 | suse_vex | SUSE CVE CVE-2022-49675 | known affected: 334 known not affected: 298 recommended: 243 | 2026-07-26T16:50:06+00:00 | Vulnerability · Source |
| CVE-2022-49757 | suse_vex | SUSE CVE CVE-2022-49757 | known affected: 224 known not affected: 120 | 2026-07-26T16:50:01+00:00 | Vulnerability · Source |
| CVE-2022-49779 | suse_vex | SUSE CVE CVE-2022-49779 | known affected: 339 known not affected: 294 recommended: 214 | 2026-07-26T16:50:00+00:00 | Vulnerability · Source |
| CVE-2022-49803 | suse_vex | SUSE CVE CVE-2022-49803 | known affected: 149 known not affected: 248 | 2026-07-26T16:49:58+00:00 | Vulnerability · Source |
| CVE-2022-49995 | suse_vex | SUSE CVE CVE-2022-49995 | known affected: 344 known not affected: 298 recommended: 253 | 2026-07-26T16:49:53+00:00 | Vulnerability · Source |
| CVE-2022-50033 | suse_vex | SUSE CVE CVE-2022-50033 | known affected: 429 known not affected: 196 recommended: 337 | 2026-07-26T16:49:51+00:00 | Vulnerability · Source |