VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292115 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2021-39685 | suse_vex | SUSE CVE CVE-2021-39685 | known affected: 344 known not affected: 362 recommended: 777 | 2026-07-23T02:40:55+00:00 | Vulnerability · Source |
| CVE-2021-39735 | suse_vex | SUSE CVE CVE-2021-39735 | known not affected: 401 | 2026-07-23T02:40:53+00:00 | Vulnerability · Source |
| CVE-2021-39801 | suse_vex | SUSE CVE CVE-2021-39801 | known not affected: 390 | 2026-07-23T02:40:51+00:00 | Vulnerability · Source |
| CVE-2021-39920 | suse_vex | SUSE CVE CVE-2021-39920 | known affected: 20 recommended: 288 | 2026-07-23T02:40:50+00:00 | Vulnerability · Source |
| CVE-2021-39926 | suse_vex | SUSE CVE CVE-2021-39926 | known affected: 20 recommended: 288 | 2026-07-23T02:40:48+00:00 | Vulnerability · Source |
| CVE-2021-42574 | suse_vex | SUSE CVE CVE-2021-42574 | recommended: 116 | 2026-07-23T02:40:43+00:00 | Vulnerability · Source |
| CVE-2021-43085 | suse_vex | SUSE CVE CVE-2021-43085 | known not affected: 728 | 2026-07-23T02:40:38+00:00 | Vulnerability · Source |
| CVE-2021-43312 | suse_vex | SUSE CVE CVE-2021-43312 | recommended: 2 | 2026-07-23T02:40:36+00:00 | Vulnerability · Source |
| CVE-2021-43332 | suse_vex | SUSE CVE CVE-2021-43332 | known affected: 3 recommended: 21 | 2026-07-23T02:40:34+00:00 | Vulnerability · Source |
| CVE-2021-43798 | suse_vex | SUSE CVE CVE-2021-43798 | known not affected: 5 recommended: 245 | 2026-07-23T02:40:32+00:00 | Vulnerability · Source |
| CVE-2021-45931 | suse_vex | SUSE CVE CVE-2021-45931 | known not affected: 310 | 2026-07-23T02:40:24+00:00 | Vulnerability · Source |
| CVE-2021-46913 | suse_vex | SUSE CVE CVE-2021-46913 | known not affected: 312 | 2026-07-23T02:40:12+00:00 | Vulnerability · Source |
| CVE-2021-46928 | suse_vex | SUSE CVE CVE-2021-46928 | known not affected: 458 | 2026-07-23T02:40:08+00:00 | Vulnerability · Source |
| CVE-2021-46930 | suse_vex | SUSE CVE CVE-2021-46930 | known affected: 254 known not affected: 205 recommended: 608 | 2026-07-23T02:40:06+00:00 | Vulnerability · Source |
| CVE-2021-46980 | suse_vex | SUSE CVE CVE-2021-46980 | known affected: 388 known not affected: 256 recommended: 91 | 2026-07-23T02:39:59+00:00 | Vulnerability · Source |
| CVE-2021-47016 | suse_vex | SUSE CVE CVE-2021-47016 | known not affected: 292 | 2026-07-23T02:39:54+00:00 | Vulnerability · Source |
| CVE-2021-47019 | suse_vex | SUSE CVE CVE-2021-47019 | known not affected: 292 | 2026-07-23T02:39:52+00:00 | Vulnerability · Source |
| CVE-2021-47030 | suse_vex | SUSE CVE CVE-2021-47030 | known not affected: 292 | 2026-07-23T02:39:51+00:00 | Vulnerability · Source |
| CVE-2021-47043 | suse_vex | SUSE CVE CVE-2021-47043 | known not affected: 292 | 2026-07-23T02:39:49+00:00 | Vulnerability · Source |
| CVE-2021-47052 | suse_vex | SUSE CVE CVE-2021-47052 | known not affected: 292 | 2026-07-23T02:39:47+00:00 | Vulnerability · Source |
| CVE-2021-47067 | suse_vex | SUSE CVE CVE-2021-47067 | known not affected: 292 | 2026-07-23T02:39:44+00:00 | Vulnerability · Source |
| CVE-2021-47088 | suse_vex | SUSE CVE CVE-2021-47088 | known not affected: 292 | 2026-07-23T02:39:43+00:00 | Vulnerability · Source |
| CVE-2021-47124 | suse_vex | SUSE CVE CVE-2021-47124 | known not affected: 292 | 2026-07-23T02:39:37+00:00 | Vulnerability · Source |
| CVE-2021-47148 | suse_vex | SUSE CVE CVE-2021-47148 | known not affected: 292 | 2026-07-23T02:39:31+00:00 | Vulnerability · Source |
| CVE-2021-47211 | suse_vex | SUSE CVE CVE-2021-47211 | known affected: 414 known not affected: 81 recommended: 546 | 2026-07-23T02:39:20+00:00 | Vulnerability · Source |
| CVE-2021-47232 | suse_vex | SUSE CVE CVE-2021-47232 | known not affected: 330 | 2026-07-23T02:39:15+00:00 | Vulnerability · Source |
| CVE-2021-47264 | suse_vex | SUSE CVE CVE-2021-47264 | known not affected: 330 | 2026-07-23T02:39:14+00:00 | Vulnerability · Source |
| CVE-2021-47268 | suse_vex | SUSE CVE CVE-2021-47268 | known not affected: 330 | 2026-07-23T02:39:12+00:00 | Vulnerability · Source |
| CVE-2021-47288 | suse_vex | SUSE CVE CVE-2021-47288 | known affected: 463 known not affected: 175 recommended: 219 | 2026-07-23T02:39:05+00:00 | Vulnerability · Source |
| CVE-2021-47298 | suse_vex | SUSE CVE CVE-2021-47298 | known not affected: 330 | 2026-07-23T02:39:01+00:00 | Vulnerability · Source |
| CVE-2021-47303 | suse_vex | SUSE CVE CVE-2021-47303 | known not affected: 330 | 2026-07-23T02:38:58+00:00 | Vulnerability · Source |
| CVE-2021-47316 | suse_vex | SUSE CVE CVE-2021-47316 | known not affected: 330 | 2026-07-23T02:38:53+00:00 | Vulnerability · Source |
| CVE-2021-47327 | suse_vex | SUSE CVE CVE-2021-47327 | known affected: 55 known not affected: 271 | 2026-07-23T02:38:51+00:00 | Vulnerability · Source |
| CVE-2021-47337 | suse_vex | SUSE CVE CVE-2021-47337 | known affected: 388 known not affected: 273 recommended: 175 | 2026-07-23T02:38:50+00:00 | Vulnerability · Source |
| CVE-2021-47340 | suse_vex | SUSE CVE CVE-2021-47340 | known affected: 388 known not affected: 288 recommended: 91 | 2026-07-23T02:38:48+00:00 | Vulnerability · Source |
| CVE-2021-47373 | suse_vex | SUSE CVE CVE-2021-47373 | known affected: 342 known not affected: 76 recommended: 564 | 2026-07-23T02:38:45+00:00 | Vulnerability · Source |
| CVE-2021-47468 | suse_vex | SUSE CVE CVE-2021-47468 | known affected: 346 known not affected: 61 recommended: 691 | 2026-07-23T02:38:24+00:00 | Vulnerability · Source |
| CVE-2021-47519 | suse_vex | SUSE CVE CVE-2021-47519 | known not affected: 330 | 2026-07-23T02:38:15+00:00 | Vulnerability · Source |
| CVE-2022-0005 | suse_vex | SUSE CVE CVE-2022-0005 | known affected: 3 known not affected: 58 recommended: 1 | 2026-07-23T02:37:46+00:00 | Vulnerability · Source |
| CVE-2022-0433 | suse_vex | SUSE CVE CVE-2022-0433 | known not affected: 390 | 2026-07-23T02:37:40+00:00 | Vulnerability · Source |
| CVE-2022-0685 | suse_vex | SUSE CVE CVE-2022-0685 | known not affected: 271 recommended: 21 | 2026-07-23T02:37:34+00:00 | Vulnerability · Source |
| CVE-2022-0891 | suse_vex | SUSE CVE CVE-2022-0891 | known affected: 439 known not affected: 13 recommended: 238 | 2026-07-23T02:37:29+00:00 | Vulnerability · Source |
| CVE-2022-1043 | suse_vex | SUSE CVE CVE-2022-1043 | known not affected: 401 | 2026-07-23T02:37:24+00:00 | Vulnerability · Source |
| CVE-2022-1210 | suse_vex | SUSE CVE CVE-2022-1210 | known affected: 531 known not affected: 300 recommended: 95 | 2026-07-23T02:37:22+00:00 | Vulnerability · Source |
| CVE-2022-1473 | suse_vex | SUSE CVE CVE-2022-1473 | known not affected: 667 recommended: 140 | 2026-07-23T02:37:15+00:00 | Vulnerability · Source |
| CVE-2022-1622 | suse_vex | SUSE CVE CVE-2022-1622 | known affected: 394 known not affected: 139 recommended: 138 | 2026-07-23T02:37:13+00:00 | Vulnerability · Source |
| CVE-2022-1804 | suse_vex | SUSE CVE CVE-2022-1804 | known not affected: 159 | 2026-07-23T02:37:06+00:00 | Vulnerability · Source |
| CVE-2022-1920 | suse_vex | SUSE CVE CVE-2022-1920 | known affected: 2 known not affected: 10 recommended: 175 | 2026-07-23T02:37:03+00:00 | Vulnerability · Source |
| CVE-2022-1973 | suse_vex | SUSE CVE CVE-2022-1973 | known not affected: 390 recommended: 6 | 2026-07-23T02:36:59+00:00 | Vulnerability · Source |
| CVE-2022-2031 | suse_vex | SUSE CVE CVE-2022-2031 | known affected: 231 known not affected: 465 recommended: 1289 | 2026-07-23T02:36:57+00:00 | Vulnerability · Source |