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-47498 | suse_vex | SUSE CVE CVE-2021-47498 | known affected: 377 known not affected: 67 recommended: 647 | 2026-07-31T01:34:10+00:00 | Vulnerability · Source |
| CVE-2021-47540 | suse_vex | SUSE CVE CVE-2021-47540 | known affected: 269 known not affected: 181 recommended: 543 | 2026-07-31T01:34:06+00:00 | Vulnerability · Source |
| CVE-2021-47546 | suse_vex | SUSE CVE CVE-2021-47546 | known affected: 357 known not affected: 181 recommended: 302 | 2026-07-31T01:34:04+00:00 | Vulnerability · Source |
| CVE-2021-47581 | suse_vex | SUSE CVE CVE-2021-47581 | known not affected: 318 | 2026-07-31T01:34:02+00:00 | Vulnerability · Source |
| CVE-2021-47659 | suse_vex | SUSE CVE CVE-2021-47659 | known affected: 407 known not affected: 270 recommended: 319 | 2026-07-31T01:33:58+00:00 | Vulnerability · Source |
| CVE-2022-0286 | suse_vex | SUSE CVE CVE-2022-0286 | known affected: 344 known not affected: 580 recommended: 433 | 2026-07-31T01:33:56+00:00 | Vulnerability · Source |
| CVE-2022-1678 | suse_vex | SUSE CVE CVE-2022-1678 | known not affected: 390 | 2026-07-31T01:33:42+00:00 | Vulnerability · Source |
| CVE-2022-2264 | suse_vex | SUSE CVE CVE-2022-2264 | known affected: 237 known not affected: 26 recommended: 505 | 2026-07-31T01:33:34+00:00 | Vulnerability · Source |
| CVE-2022-2308 | suse_vex | SUSE CVE CVE-2022-2308 | known not affected: 564 recommended: 6 | 2026-07-31T01:33:32+00:00 | Vulnerability · Source |
| CVE-2022-3624 | suse_vex | SUSE CVE CVE-2022-3624 | known not affected: 564 | 2026-07-31T01:33:17+00:00 | Vulnerability · Source |
| CVE-2022-3630 | suse_vex | SUSE CVE CVE-2022-3630 | known not affected: 564 | 2026-07-31T01:33:13+00:00 | Vulnerability · Source |
| CVE-2022-3636 | suse_vex | SUSE CVE CVE-2022-3636 | known not affected: 720 | 2026-07-31T01:33:09+00:00 | Vulnerability · Source |
| CVE-2022-21538 | suse_vex | SUSE CVE CVE-2022-21538 | recommended: 17 | 2026-07-31T01:32:58+00:00 | Vulnerability · Source |
| CVE-2022-21539 | suse_vex | SUSE CVE CVE-2022-21539 | recommended: 17 | 2026-07-31T01:32:56+00:00 | Vulnerability · Source |
| CVE-2022-22753 | suse_vex | SUSE CVE CVE-2022-22753 | recommended: 404 | 2026-07-31T01:32:53+00:00 | Vulnerability · Source |
| CVE-2022-23041 | suse_vex | SUSE CVE CVE-2022-23041 | known affected: 344 known not affected: 61 recommended: 1327 | 2026-07-31T01:32:50+00:00 | Vulnerability · Source |
| CVE-2022-23478 | suse_vex | SUSE CVE CVE-2022-23478 | known affected: 394 known not affected: 3 recommended: 171 | 2026-07-31T01:32:48+00:00 | Vulnerability · Source |
| CVE-2022-28349 | suse_vex | SUSE CVE CVE-2022-28349 | known not affected: 390 | 2026-07-31T01:32:39+00:00 | Vulnerability · Source |
| CVE-2022-31624 | suse_vex | SUSE CVE CVE-2022-31624 | known not affected: 233 recommended: 16 | 2026-07-31T01:32:34+00:00 | Vulnerability · Source |
| CVE-2022-34266 | suse_vex | SUSE CVE CVE-2022-34266 | known affected: 394 known not affected: 2 recommended: 263 | 2026-07-31T01:32:25+00:00 | Vulnerability · Source |
| CVE-2022-40897 | suse_vex | SUSE CVE CVE-2022-40897 | known affected: 272 known not affected: 95 recommended: 350 | 2026-07-31T01:32:21+00:00 | Vulnerability · Source |
| CVE-2022-42325 | suse_vex | SUSE CVE CVE-2022-42325 | known affected: 253 known not affected: 13 recommended: 499 | 2026-07-31T01:32:19+00:00 | Vulnerability · Source |
| CVE-2022-45786 | suse_vex | SUSE CVE CVE-2022-45786 | No product status | 2026-07-31T01:32:11+00:00 | Vulnerability · Source |
| CVE-2022-48554 | suse_vex | SUSE CVE CVE-2022-48554 | known not affected: 247 recommended: 4 | 2026-07-31T01:32:08+00:00 | Vulnerability · Source |
| CVE-2022-48624 | suse_vex | SUSE CVE CVE-2022-48624 | known affected: 269 known not affected: 6 recommended: 177 | 2026-07-31T01:32:06+00:00 | Vulnerability · Source |
| CVE-2022-48651 | suse_vex | SUSE CVE CVE-2022-48651 | known affected: 338 known not affected: 76 recommended: 852 | 2026-07-31T01:32:04+00:00 | Vulnerability · Source |
| CVE-2022-49055 | suse_vex | SUSE CVE CVE-2022-49055 | known affected: 421 known not affected: 193 recommended: 333 | 2026-07-31T01:31:34+00:00 | Vulnerability · Source |
| CVE-2022-49142 | suse_vex | SUSE CVE CVE-2022-49142 | known affected: 55 known not affected: 297 recommended: 22 | 2026-07-31T01:31:29+00:00 | Vulnerability · Source |
| CVE-2022-49146 | suse_vex | SUSE CVE CVE-2022-49146 | known not affected: 352 | 2026-07-31T01:31:25+00:00 | Vulnerability · Source |
| CVE-2022-49383 | suse_vex | SUSE CVE CVE-2022-49383 | known not affected: 352 | 2026-07-31T01:31:19+00:00 | Vulnerability · Source |
| CVE-2022-49497 | suse_vex | SUSE CVE CVE-2022-49497 | known affected: 545 known not affected: 91 recommended: 140 | 2026-07-31T01:31:15+00:00 | Vulnerability · Source |
| CVE-2022-49567 | suse_vex | SUSE CVE CVE-2022-49567 | known affected: 268 known not affected: 82 recommended: 29 | 2026-07-31T01:31:06+00:00 | Vulnerability · Source |
| CVE-2022-49580 | suse_vex | SUSE CVE CVE-2022-49580 | known not affected: 163 recommended: 27 | 2026-07-31T01:31:04+00:00 | Vulnerability · Source |
| CVE-2022-49632 | suse_vex | SUSE CVE CVE-2022-49632 | known not affected: 141 recommended: 27 | 2026-07-31T01:31:01+00:00 | Vulnerability · Source |
| CVE-2022-49679 | suse_vex | SUSE CVE CVE-2022-49679 | known affected: 334 known not affected: 349 recommended: 223 | 2026-07-31T01:30:59+00:00 | Vulnerability · Source |
| CVE-2022-49904 | suse_vex | SUSE CVE CVE-2022-49904 | known not affected: 397 | 2026-07-31T01:30:53+00:00 | Vulnerability · Source |
| CVE-2022-49955 | suse_vex | SUSE CVE CVE-2022-49955 | known not affected: 401 | 2026-07-31T01:30:51+00:00 | Vulnerability · Source |
| CVE-2022-50029 | suse_vex | SUSE CVE CVE-2022-50029 | known affected: 358 known not affected: 280 recommended: 300 | 2026-07-31T01:30:49+00:00 | Vulnerability · Source |
| CVE-2022-50043 | suse_vex | SUSE CVE CVE-2022-50043 | known affected: 55 known not affected: 346 | 2026-07-31T01:30:47+00:00 | Vulnerability · Source |
| CVE-2022-50128 | suse_vex | SUSE CVE CVE-2022-50128 | known not affected: 401 | 2026-07-31T01:30:45+00:00 | Vulnerability · Source |
| CVE-2022-50217 | suse_vex | SUSE CVE CVE-2022-50217 | known not affected: 401 | 2026-07-31T01:30:43+00:00 | Vulnerability · Source |
| CVE-2022-50316 | suse_vex | SUSE CVE CVE-2022-50316 | known affected: 210 known not affected: 176 | 2026-07-31T01:30:35+00:00 | Vulnerability · Source |
| CVE-2022-50317 | suse_vex | SUSE CVE CVE-2022-50317 | known affected: 344 known not affected: 267 recommended: 322 | 2026-07-31T01:30:33+00:00 | Vulnerability · Source |
| CVE-2022-50442 | suse_vex | SUSE CVE CVE-2022-50442 | known not affected: 416 | 2026-07-31T01:30:26+00:00 | Vulnerability · Source |
| CVE-2022-50491 | suse_vex | SUSE CVE CVE-2022-50491 | known affected: 149 known not affected: 267 recommended: 43 | 2026-07-31T01:30:22+00:00 | Vulnerability · Source |
| CVE-2022-50503 | suse_vex | SUSE CVE CVE-2022-50503 | known affected: 354 known not affected: 304 recommended: 196 | 2026-07-31T01:30:20+00:00 | Vulnerability · Source |
| CVE-2022-50547 | suse_vex | SUSE CVE CVE-2022-50547 | known affected: 4 known not affected: 412 | 2026-07-31T01:30:17+00:00 | Vulnerability · Source |
| CVE-2022-50628 | suse_vex | SUSE CVE CVE-2022-50628 | known affected: 112 known not affected: 296 recommended: 49 | 2026-07-31T01:30:15+00:00 | Vulnerability · Source |
| CVE-2022-50869 | suse_vex | SUSE CVE CVE-2022-50869 | known not affected: 453 | 2026-07-31T01:30:05+00:00 | Vulnerability · Source |
| CVE-2023-0030 | suse_vex | SUSE CVE CVE-2023-0030 | known not affected: 402 | 2026-07-31T01:30:04+00:00 | Vulnerability · Source |