VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
287116 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-2889 | suse_vex | SUSE CVE CVE-2022-2889 | known affected: 237 known not affected: 2 recommended: 505 | 2026-07-31T01:33:28+00:00 | Vulnerability · Source |
| CVE-2022-3115 | suse_vex | SUSE CVE CVE-2022-3115 | known affected: 272 known not affected: 255 recommended: 880 | 2026-07-31T01:33:26+00:00 | Vulnerability · Source |
| CVE-2022-3534 | suse_vex | SUSE CVE CVE-2022-3534 | known not affected: 95 recommended: 60 | 2026-07-31T01:33:23+00:00 | Vulnerability · Source |
| CVE-2022-3566 | suse_vex | SUSE CVE CVE-2022-3566 | known affected: 275 known not affected: 276 recommended: 1157 | 2026-07-31T01:33:21+00:00 | Vulnerability · Source |
| CVE-2022-3567 | suse_vex | SUSE CVE CVE-2022-3567 | known affected: 269 known not affected: 257 recommended: 1589 | 2026-07-31T01:33:19+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-3629 | suse_vex | SUSE CVE CVE-2022-3629 | known affected: 261 known not affected: 325 recommended: 1465 | 2026-07-31T01:33:15+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-3633 | suse_vex | SUSE CVE CVE-2022-3633 | known affected: 271 known not affected: 568 recommended: 635 | 2026-07-31T01:33:11+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-4603 | suse_vex | SUSE CVE CVE-2022-4603 | known affected: 95 recommended: 61 | 2026-07-31T01:33:05+00:00 | Vulnerability · Source |
| CVE-2022-21216 | suse_vex | SUSE CVE CVE-2022-21216 | recommended: 71 | 2026-07-31T01:33:00+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-26490 | suse_vex | SUSE CVE CVE-2022-26490 | known affected: 209 known not affected: 21 recommended: 1749 | 2026-07-31T01:32:43+00:00 | Vulnerability · Source |
| CVE-2022-26520 | suse_vex | SUSE CVE CVE-2022-26520 | known affected: 395 known not affected: 28 recommended: 137 | 2026-07-31T01:32:41+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-30790 | suse_vex | SUSE CVE CVE-2022-30790 | recommended: 407 | 2026-07-31T01:32:35+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-32088 | suse_vex | SUSE CVE CVE-2022-32088 | known not affected: 94 recommended: 378 | 2026-07-31T01:32:31+00:00 | Vulnerability · Source |
| CVE-2022-33196 | suse_vex | SUSE CVE CVE-2022-33196 | recommended: 71 | 2026-07-31T01:32:29+00:00 | Vulnerability · Source |
| CVE-2022-33741 | suse_vex | SUSE CVE CVE-2022-33741 | known affected: 249 known not affected: 216 recommended: 1575 | 2026-07-31T01:32:27+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-42895 | suse_vex | SUSE CVE CVE-2022-42895 | known affected: 384 known not affected: 275 recommended: 1441 | 2026-07-31T01:32:16+00:00 | Vulnerability · Source |
| CVE-2022-42969 | suse_vex | SUSE CVE CVE-2022-42969 | known affected: 383 recommended: 147 | 2026-07-31T01:32:15+00:00 | Vulnerability · Source |
| CVE-2022-43945 | suse_vex | SUSE CVE CVE-2022-43945 | known affected: 242 known not affected: 6 recommended: 2126 | 2026-07-31T01:32:12+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-48656 | suse_vex | SUSE CVE CVE-2022-48656 | known affected: 265 known not affected: 202 recommended: 462 | 2026-07-31T01:32:02+00:00 | Vulnerability · Source |
| CVE-2022-48799 | suse_vex | SUSE CVE CVE-2022-48799 | known affected: 420 known not affected: 81 recommended: 496 | 2026-07-31T01:31:52+00:00 | Vulnerability · Source |
| CVE-2022-48815 | suse_vex | SUSE CVE CVE-2022-48815 | known affected: 295 known not affected: 205 recommended: 426 | 2026-07-31T01:31:50+00:00 | Vulnerability · Source |
| CVE-2022-48903 | suse_vex | SUSE CVE CVE-2022-48903 | known affected: 310 known not affected: 190 recommended: 411 | 2026-07-31T01:31:47+00:00 | Vulnerability · Source |
| CVE-2022-48969 | suse_vex | SUSE CVE CVE-2022-48969 | known affected: 462 known not affected: 110 recommended: 477 | 2026-07-31T01:31:40+00:00 | Vulnerability · Source |
| CVE-2022-48971 | suse_vex | SUSE CVE CVE-2022-48971 | known affected: 462 known not affected: 159 recommended: 420 | 2026-07-31T01:31:38+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-49115 | suse_vex | SUSE CVE CVE-2022-49115 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-31T01:31:32+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-49145 | suse_vex | SUSE CVE CVE-2022-49145 | known affected: 421 known not affected: 232 recommended: 411 | 2026-07-31T01:31:27+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-49202 | suse_vex | SUSE CVE CVE-2022-49202 | known affected: 364 known not affected: 302 recommended: 100 | 2026-07-31T01:31:22+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-49422 | suse_vex | SUSE CVE CVE-2022-49422 | known affected: 334 known not affected: 270 recommended: 293 | 2026-07-31T01:31:17+00:00 | Vulnerability · Source |