VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294018 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-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-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-47519 | suse_vex | SUSE CVE CVE-2021-47519 | known not affected: 330 | 2026-07-23T02:38:15+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-1043 | suse_vex | SUSE CVE CVE-2022-1043 | known not affected: 401 | 2026-07-23T02:37:24+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-2347 | suse_vex | SUSE CVE CVE-2022-2347 | known not affected: 77 | 2026-07-23T02:36:47+00:00 | Vulnerability · Source |
| CVE-2022-2476 | suse_vex | SUSE CVE CVE-2022-2476 | known affected: 444 recommended: 122 | 2026-07-23T02:36:45+00:00 | Vulnerability · Source |
| CVE-2022-3077 | suse_vex | SUSE CVE CVE-2022-3077 | known not affected: 327 recommended: 22 | 2026-07-23T02:36:34+00:00 | Vulnerability · Source |
| CVE-2022-3238 | suse_vex | SUSE CVE CVE-2022-3238 | known not affected: 333 | 2026-07-23T02:36:29+00:00 | Vulnerability · Source |
| CVE-2022-3528 | suse_vex | SUSE CVE CVE-2022-3528 | known not affected: 117 | 2026-07-23T02:36:23+00:00 | Vulnerability · Source |
| CVE-2022-3595 | suse_vex | SUSE CVE CVE-2022-3595 | known not affected: 327 | 2026-07-23T02:36:14+00:00 | Vulnerability · Source |
| CVE-2022-3642 | suse_vex | SUSE CVE CVE-2022-3642 | known not affected: 327 | 2026-07-23T02:36:10+00:00 | Vulnerability · Source |
| CVE-2022-3977 | suse_vex | SUSE CVE CVE-2022-3977 | known not affected: 354 | 2026-07-23T02:36:07+00:00 | Vulnerability · Source |
| CVE-2022-4292 | suse_vex | SUSE CVE CVE-2022-4292 | known affected: 267 known not affected: 26 recommended: 417 | 2026-07-23T02:36:04+00:00 | Vulnerability · Source |
| CVE-2022-21547 | suse_vex | SUSE CVE CVE-2022-21547 | recommended: 17 | 2026-07-23T02:35:34+00:00 | Vulnerability · Source |
| CVE-2022-23035 | suse_vex | SUSE CVE CVE-2022-23035 | known affected: 340 known not affected: 48 recommended: 463 | 2026-07-23T02:35:27+00:00 | Vulnerability · Source |
| CVE-2022-24919 | suse_vex | SUSE CVE CVE-2022-24919 | known affected: 21 recommended: 5 | 2026-07-23T02:35:14+00:00 | Vulnerability · Source |
| CVE-2022-26981 | suse_vex | SUSE CVE CVE-2022-26981 | known not affected: 71 recommended: 247 | 2026-07-23T02:34:40+00:00 | Vulnerability · Source |
| CVE-2022-29869 | suse_vex | SUSE CVE CVE-2022-29869 | known affected: 274 recommended: 244 | 2026-07-23T02:34:16+00:00 | Vulnerability · Source |
| CVE-2022-29913 | suse_vex | SUSE CVE CVE-2022-29913 | known not affected: 2 recommended: 93 | 2026-07-23T02:34:14+00:00 | Vulnerability · Source |
| CVE-2022-30294 | suse_vex | SUSE CVE CVE-2022-30294 | known affected: 1 known not affected: 231 | 2026-07-23T02:34:08+00:00 | Vulnerability · Source |
| CVE-2022-32547 | suse_vex | SUSE CVE CVE-2022-32547 | recommended: 523 | 2026-07-23T02:33:50+00:00 | Vulnerability · Source |
| CVE-2022-32981 | suse_vex | SUSE CVE CVE-2022-32981 | known not affected: 381 | 2026-07-23T02:33:36+00:00 | Vulnerability · Source |
| CVE-2022-37050 | suse_vex | SUSE CVE CVE-2022-37050 | known affected: 79 known not affected: 5 recommended: 273 | 2026-07-23T02:33:13+00:00 | Vulnerability · Source |
| CVE-2022-42322 | suse_vex | SUSE CVE CVE-2022-42322 | known affected: 253 recommended: 518 | 2026-07-23T02:32:39+00:00 | Vulnerability · Source |
| CVE-2022-47518 | suse_vex | SUSE CVE CVE-2022-47518 | known not affected: 362 | 2026-07-23T02:32:01+00:00 | Vulnerability · Source |
| CVE-2022-47519 | suse_vex | SUSE CVE CVE-2022-47519 | known not affected: 362 | 2026-07-23T02:31:59+00:00 | Vulnerability · Source |
| CVE-2022-49198 | suse_vex | SUSE CVE CVE-2022-49198 | known not affected: 352 | 2026-07-23T02:29:55+00:00 | Vulnerability · Source |
| CVE-2022-49240 | suse_vex | SUSE CVE CVE-2022-49240 | known not affected: 352 | 2026-07-23T02:29:50+00:00 | Vulnerability · Source |
| CVE-2022-49420 | suse_vex | SUSE CVE CVE-2022-49420 | known affected: 559 known not affected: 161 recommended: 37 | 2026-07-23T02:29:00+00:00 | Vulnerability · Source |
| CVE-2022-49572 | suse_vex | SUSE CVE CVE-2022-49572 | known not affected: 141 recommended: 27 | 2026-07-23T02:28:29+00:00 | Vulnerability · Source |
| CVE-2022-49819 | suse_vex | SUSE CVE CVE-2022-49819 | known not affected: 397 | 2026-07-23T02:27:47+00:00 | Vulnerability · Source |
| CVE-2022-49847 | suse_vex | SUSE CVE CVE-2022-49847 | known not affected: 397 | 2026-07-23T02:27:40+00:00 | Vulnerability · Source |
| CVE-2022-49932 | suse_vex | SUSE CVE CVE-2022-49932 | known affected: 277 known not affected: 191 | 2026-07-23T02:27:23+00:00 | Vulnerability · Source |
| CVE-2022-50315 | suse_vex | SUSE CVE CVE-2022-50315 | known affected: 268 known not affected: 189 | 2026-07-23T02:25:49+00:00 | Vulnerability · Source |
| CVE-2022-50451 | suse_vex | SUSE CVE CVE-2022-50451 | known not affected: 416 | 2026-07-23T02:25:28+00:00 | Vulnerability · Source |
| CVE-2022-50520 | suse_vex | SUSE CVE CVE-2022-50520 | known affected: 472 known not affected: 154 recommended: 245 | 2026-07-23T02:25:09+00:00 | Vulnerability · Source |
| CVE-2022-50713 | suse_vex | SUSE CVE CVE-2022-50713 | known not affected: 453 | 2026-07-23T02:24:46+00:00 | Vulnerability · Source |