VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292287 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-50042 | suse_vex | SUSE CVE CVE-2022-50042 | known affected: 55 known not affected: 346 recommended: 49 | 2026-07-23T02:26:48+00:00 | Vulnerability · Source |
| CVE-2022-50057 | suse_vex | SUSE CVE CVE-2022-50057 | known not affected: 401 | 2026-07-23T02:26:45+00:00 | Vulnerability · Source |
| CVE-2022-50069 | suse_vex | SUSE CVE CVE-2022-50069 | known affected: 55 known not affected: 346 recommended: 47 | 2026-07-23T02:26:41+00:00 | Vulnerability · Source |
| CVE-2022-50075 | suse_vex | SUSE CVE CVE-2022-50075 | known not affected: 401 | 2026-07-23T02:26:40+00:00 | Vulnerability · Source |
| CVE-2022-50090 | suse_vex | SUSE CVE CVE-2022-50090 | known affected: 55 known not affected: 346 | 2026-07-23T02:26:37+00:00 | Vulnerability · Source |
| CVE-2022-50112 | suse_vex | SUSE CVE CVE-2022-50112 | known affected: 442 known not affected: 215 recommended: 249 | 2026-07-23T02:26:34+00:00 | Vulnerability · Source |
| CVE-2022-50118 | suse_vex | SUSE CVE CVE-2022-50118 | known affected: 344 known not affected: 309 recommended: 273 | 2026-07-23T02:26:32+00:00 | Vulnerability · Source |
| CVE-2022-50158 | suse_vex | SUSE CVE CVE-2022-50158 | known affected: 358 known not affected: 280 recommended: 273 | 2026-07-23T02:26:27+00:00 | Vulnerability · Source |
| CVE-2022-50167 | suse_vex | SUSE CVE CVE-2022-50167 | known affected: 106 known not affected: 295 | 2026-07-23T02:26:23+00:00 | Vulnerability · Source |
| CVE-2022-50177 | suse_vex | SUSE CVE CVE-2022-50177 | known affected: 55 known not affected: 346 recommended: 20 | 2026-07-23T02:26:20+00:00 | Vulnerability · Source |
| CVE-2022-50179 | suse_vex | SUSE CVE CVE-2022-50179 | known not affected: 264 recommended: 294 | 2026-07-23T02:26:19+00:00 | Vulnerability · Source |
| CVE-2022-50256 | suse_vex | SUSE CVE CVE-2022-50256 | known affected: 8 known not affected: 408 | 2026-07-23T02:26:02+00:00 | Vulnerability · Source |
| CVE-2022-50267 | suse_vex | SUSE CVE CVE-2022-50267 | known affected: 344 known not affected: 304 recommended: 206 | 2026-07-23T02:26:00+00:00 | Vulnerability · Source |
| CVE-2022-50284 | suse_vex | SUSE CVE CVE-2022-50284 | known not affected: 416 | 2026-07-23T02:25:57+00:00 | Vulnerability · Source |
| CVE-2022-50307 | suse_vex | SUSE CVE CVE-2022-50307 | known not affected: 416 | 2026-07-23T02:25:53+00:00 | Vulnerability · Source |
| CVE-2022-50310 | suse_vex | SUSE CVE CVE-2022-50310 | known not affected: 416 | 2026-07-23T02:25:52+00:00 | Vulnerability · Source |
| CVE-2022-50311 | suse_vex | SUSE CVE CVE-2022-50311 | known affected: 590 known not affected: 190 recommended: 23 | 2026-07-23T02:25:50+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-50322 | suse_vex | SUSE CVE CVE-2022-50322 | known not affected: 416 recommended: 29 | 2026-07-23T02:25:46+00:00 | Vulnerability · Source |
| CVE-2022-50349 | suse_vex | SUSE CVE CVE-2022-50349 | known affected: 468 known not affected: 181 recommended: 243 | 2026-07-23T02:25:44+00:00 | Vulnerability · Source |
| CVE-2022-50400 | suse_vex | SUSE CVE CVE-2022-50400 | known affected: 112 known not affected: 304 | 2026-07-23T02:25:39+00:00 | Vulnerability · Source |
| CVE-2022-50413 | suse_vex | SUSE CVE CVE-2022-50413 | known not affected: 416 | 2026-07-23T02:25:36+00:00 | Vulnerability · Source |
| CVE-2022-50424 | suse_vex | SUSE CVE CVE-2022-50424 | known not affected: 416 | 2026-07-23T02:25:32+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-50481 | suse_vex | SUSE CVE CVE-2022-50481 | known affected: 618 known not affected: 162 recommended: 23 | 2026-07-23T02:25:22+00:00 | Vulnerability · Source |
| CVE-2022-50483 | suse_vex | SUSE CVE CVE-2022-50483 | known affected: 112 known not affected: 304 | 2026-07-23T02:25:20+00:00 | Vulnerability · Source |
| CVE-2022-50495 | suse_vex | SUSE CVE CVE-2022-50495 | recommended: 49 | 2026-07-23T02:25:14+00:00 | Vulnerability · Source |
| CVE-2022-50502 | suse_vex | SUSE CVE CVE-2022-50502 | known not affected: 416 | 2026-07-23T02:25:13+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-50533 | suse_vex | SUSE CVE CVE-2022-50533 | known not affected: 416 | 2026-07-23T02:25:06+00:00 | Vulnerability · Source |
| CVE-2022-50552 | suse_vex | SUSE CVE CVE-2022-50552 | known affected: 61 known not affected: 160 | 2026-07-23T02:25:01+00:00 | Vulnerability · Source |
| CVE-2022-50632 | suse_vex | SUSE CVE CVE-2022-50632 | known affected: 57 known not affected: 351 recommended: 29 | 2026-07-23T02:24:52+00:00 | Vulnerability · Source |
| CVE-2022-50637 | suse_vex | SUSE CVE CVE-2022-50637 | known not affected: 448 recommended: 29 | 2026-07-23T02:24:50+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 |
| CVE-2022-50720 | suse_vex | SUSE CVE CVE-2022-50720 | known affected: 234 known not affected: 187 | 2026-07-23T02:24:45+00:00 | Vulnerability · Source |
| CVE-2022-50739 | suse_vex | SUSE CVE CVE-2022-50739 | known not affected: 448 | 2026-07-23T02:24:42+00:00 | Vulnerability · Source |
| CVE-2022-50778 | suse_vex | SUSE CVE CVE-2022-50778 | known not affected: 421 recommended: 47 | 2026-07-23T02:24:38+00:00 | Vulnerability · Source |
| CVE-2022-50783 | suse_vex | SUSE CVE CVE-2022-50783 | known affected: 112 known not affected: 341 recommended: 27 | 2026-07-23T02:24:37+00:00 | Vulnerability · Source |
| CVE-2022-50813 | suse_vex | SUSE CVE CVE-2022-50813 | known not affected: 453 | 2026-07-23T02:24:36+00:00 | Vulnerability · Source |
| CVE-2022-50837 | suse_vex | SUSE CVE CVE-2022-50837 | known not affected: 453 | 2026-07-23T02:24:34+00:00 | Vulnerability · Source |
| CVE-2022-50871 | suse_vex | SUSE CVE CVE-2022-50871 | known affected: 112 known not affected: 341 | 2026-07-23T02:24:24+00:00 | Vulnerability · Source |
| CVE-2022-50877 | suse_vex | SUSE CVE CVE-2022-50877 | known affected: 112 known not affected: 341 | 2026-07-23T02:24:21+00:00 | Vulnerability · Source |
| CVE-2023-0286 | suse_vex | SUSE CVE CVE-2023-0286 | known affected: 274 known not affected: 164 recommended: 1135 | 2026-07-23T02:24:13+00:00 | Vulnerability · Source |
| CVE-2023-0950 | suse_vex | SUSE CVE CVE-2023-0950 | known affected: 163 recommended: 1819 | 2026-07-23T02:24:07+00:00 | Vulnerability · Source |
| CVE-2023-1194 | suse_vex | SUSE CVE CVE-2023-1194 | known not affected: 327 | 2026-07-23T02:24:03+00:00 | Vulnerability · Source |
| CVE-2023-1295 | suse_vex | SUSE CVE CVE-2023-1295 | known not affected: 361 | 2026-07-23T02:24:00+00:00 | Vulnerability · Source |
| CVE-2023-1350 | suse_vex | SUSE CVE CVE-2023-1350 | known not affected: 25 recommended: 6 | 2026-07-23T02:23:59+00:00 | Vulnerability · Source |
| CVE-2023-1583 | suse_vex | SUSE CVE CVE-2023-1583 | known not affected: 288 recommended: 370 | 2026-07-23T02:23:56+00:00 | Vulnerability · Source |
| CVE-2023-2004 | suse_vex | SUSE CVE CVE-2023-2004 | known affected: 249 known not affected: 82 recommended: 382 | 2026-07-23T02:23:48+00:00 | Vulnerability · Source |
| CVE-2023-2137 | suse_vex | SUSE CVE CVE-2023-2137 | known affected: 219 known not affected: 2 recommended: 434 | 2026-07-23T02:23:45+00:00 | Vulnerability · Source |