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-2022-2132 | suse_vex | SUSE CVE CVE-2022-2132 | known affected: 1 known not affected: 40 recommended: 469 | 2026-07-23T02:36:51+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-2929 | suse_vex | SUSE CVE CVE-2022-2929 | known affected: 394 recommended: 304 | 2026-07-23T02:36:38+00:00 | Vulnerability · Source |
| CVE-2022-2962 | suse_vex | SUSE CVE CVE-2022-2962 | known not affected: 403 recommended: 422 | 2026-07-23T02:36:36+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-3437 | suse_vex | SUSE CVE CVE-2022-3437 | known affected: 269 known not affected: 1561 recommended: 1153 | 2026-07-23T02:36:25+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-3593 | suse_vex | SUSE CVE CVE-2022-3593 | known not affected: 130 | 2026-07-23T02:36:16+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-3757 | suse_vex | SUSE CVE CVE-2022-3757 | known not affected: 142 | 2026-07-23T02:36:09+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-4515 | suse_vex | SUSE CVE CVE-2022-4515 | known affected: 1 recommended: 60 | 2026-07-23T02:36:02+00:00 | Vulnerability · Source |
| CVE-2022-20148 | suse_vex | SUSE CVE CVE-2022-20148 | known not affected: 377 | 2026-07-23T02:35:58+00:00 | Vulnerability · Source |
| CVE-2022-20371 | suse_vex | SUSE CVE CVE-2022-20371 | known not affected: 327 | 2026-07-23T02:35:57+00:00 | Vulnerability · Source |
| CVE-2022-20572 | suse_vex | SUSE CVE CVE-2022-20572 | known not affected: 327 recommended: 42 | 2026-07-23T02:35:55+00:00 | Vulnerability · Source |
| CVE-2022-20771 | suse_vex | SUSE CVE CVE-2022-20771 | known affected: 51 recommended: 181 | 2026-07-23T02:35:52+00:00 | Vulnerability · Source |
| CVE-2022-21151 | suse_vex | SUSE CVE CVE-2022-21151 | recommended: 87 | 2026-07-23T02:35:49+00:00 | Vulnerability · Source |
| CVE-2022-21349 | suse_vex | SUSE CVE CVE-2022-21349 | known affected: 14 known not affected: 261 recommended: 638 | 2026-07-23T02:35:46+00:00 | Vulnerability · Source |
| CVE-2022-21365 | suse_vex | SUSE CVE CVE-2022-21365 | known affected: 406 known not affected: 32 recommended: 1076 | 2026-07-23T02:35:44+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-21619 | suse_vex | SUSE CVE CVE-2022-21619 | known affected: 396 recommended: 1148 | 2026-07-23T02:35:32+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-23134 | suse_vex | SUSE CVE CVE-2022-23134 | known not affected: 37 recommended: 30 | 2026-07-23T02:35:23+00:00 | Vulnerability · Source |
| CVE-2022-23303 | suse_vex | SUSE CVE CVE-2022-23303 | recommended: 84 | 2026-07-23T02:35:22+00:00 | Vulnerability · Source |
| CVE-2022-23479 | suse_vex | SUSE CVE CVE-2022-23479 | known affected: 394 recommended: 202 | 2026-07-23T02:35:18+00:00 | Vulnerability · Source |
| CVE-2022-23952 | suse_vex | SUSE CVE CVE-2022-23952 | known not affected: 72 recommended: 201 | 2026-07-23T02:35:16+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-24958 | suse_vex | SUSE CVE CVE-2022-24958 | known affected: 347 known not affected: 293 recommended: 934 | 2026-07-23T02:35:12+00:00 | Vulnerability · Source |
| CVE-2022-25313 | suse_vex | SUSE CVE CVE-2022-25313 | known affected: 282 recommended: 439 | 2026-07-23T02:35:07+00:00 | Vulnerability · Source |
| CVE-2022-25762 | suse_vex | SUSE CVE CVE-2022-25762 | known affected: 27 known not affected: 338 | 2026-07-23T02:34:59+00:00 | Vulnerability · Source |
| CVE-2022-26280 | suse_vex | SUSE CVE CVE-2022-26280 | known affected: 394 known not affected: 85 recommended: 125 | 2026-07-23T02:34:57+00:00 | Vulnerability · Source |
| CVE-2022-26363 | suse_vex | SUSE CVE CVE-2022-26363 | known affected: 215 recommended: 564 | 2026-07-23T02:34:55+00:00 | Vulnerability · Source |
| CVE-2022-26364 | suse_vex | SUSE CVE CVE-2022-26364 | recommended: 377 | 2026-07-23T02:34:52+00:00 | Vulnerability · Source |
| CVE-2022-26691 | suse_vex | SUSE CVE CVE-2022-26691 | known affected: 350 known not affected: 83 recommended: 725 | 2026-07-23T02:34:45+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-27776 | suse_vex | SUSE CVE CVE-2022-27776 | known affected: 298 known not affected: 56 recommended: 342 | 2026-07-23T02:34:28+00:00 | Vulnerability · Source |
| CVE-2022-28285 | suse_vex | SUSE CVE CVE-2022-28285 | known affected: 3 known not affected: 128 recommended: 405 | 2026-07-23T02:34:26+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-30293 | suse_vex | SUSE CVE CVE-2022-30293 | known affected: 1 known not affected: 231 recommended: 1016 | 2026-07-23T02:34:09+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-31621 | suse_vex | SUSE CVE CVE-2022-31621 | known not affected: 326 recommended: 16 | 2026-07-23T02:34:03+00:00 | Vulnerability · Source |
| CVE-2022-31629 | suse_vex | SUSE CVE CVE-2022-31629 | recommended: 4584 | 2026-07-23T02:34:00+00:00 | Vulnerability · Source |
| CVE-2022-31742 | suse_vex | SUSE CVE CVE-2022-31742 | known not affected: 1 recommended: 405 | 2026-07-23T02:33:58+00:00 | Vulnerability · Source |
| CVE-2022-32149 | suse_vex | SUSE CVE CVE-2022-32149 | known not affected: 197 recommended: 312 | 2026-07-23T02:33:54+00:00 | Vulnerability · Source |
| CVE-2022-32166 | suse_vex | SUSE CVE CVE-2022-32166 | known affected: 4 known not affected: 412 recommended: 63 | 2026-07-23T02:33:53+00:00 | Vulnerability · Source |