VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283485 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-23042 | suse_vex | SUSE CVE CVE-2022-23042 | known affected: 344 known not affected: 61 recommended: 1327 | 2026-07-25T17:26:37+00:00 | Vulnerability · Source |
| CVE-2022-23132 | suse_vex | SUSE CVE CVE-2022-23132 | known not affected: 37 | 2026-07-25T17:26:36+00:00 | Vulnerability · Source |
| CVE-2022-23222 | suse_vex | SUSE CVE CVE-2022-23222 | known not affected: 368 recommended: 580 | 2026-07-25T17:26:34+00:00 | Vulnerability · Source |
| CVE-2022-23307 | suse_vex | SUSE CVE CVE-2022-23307 | known affected: 395 known not affected: 36 recommended: 352 | 2026-07-25T17:26:33+00:00 | Vulnerability · Source |
| CVE-2022-23308 | suse_vex | SUSE CVE CVE-2022-23308 | known affected: 216 known not affected: 44 recommended: 664 | 2026-07-25T17:26:31+00:00 | Vulnerability · Source |
| CVE-2022-23468 | suse_vex | SUSE CVE CVE-2022-23468 | known affected: 395 known not affected: 1 recommended: 202 | 2026-07-25T17:26:30+00:00 | Vulnerability · Source |
| CVE-2022-23483 | suse_vex | SUSE CVE CVE-2022-23483 | known affected: 395 known not affected: 1 recommended: 202 | 2026-07-25T17:26:28+00:00 | Vulnerability · Source |
| CVE-2022-23521 | suse_vex | SUSE CVE CVE-2022-23521 | known affected: 1 known not affected: 131 recommended: 726 | 2026-07-25T17:26:27+00:00 | Vulnerability · Source |
| CVE-2022-23525 | suse_vex | SUSE CVE CVE-2022-23525 | known affected: 406 recommended: 99 | 2026-07-25T17:26:25+00:00 | Vulnerability · Source |
| CVE-2022-23527 | suse_vex | SUSE CVE CVE-2022-23527 | known affected: 18 recommended: 39 | 2026-07-25T17:26:24+00:00 | Vulnerability · Source |
| CVE-2022-23820 | suse_vex | SUSE CVE CVE-2022-23820 | known affected: 22 recommended: 1381 | 2026-07-25T17:26:22+00:00 | Vulnerability · Source |
| CVE-2022-23824 | suse_vex | SUSE CVE CVE-2022-23824 | known affected: 274 recommended: 381 | 2026-07-25T17:26:21+00:00 | Vulnerability · Source |
| CVE-2022-23901 | suse_vex | SUSE CVE CVE-2022-23901 | known not affected: 66 | 2026-07-25T17:26:19+00:00 | Vulnerability · Source |
| CVE-2022-23943 | suse_vex | SUSE CVE CVE-2022-23943 | known affected: 395 known not affected: 21 recommended: 519 | 2026-07-25T17:26:18+00:00 | Vulnerability · Source |
| CVE-2022-23990 | suse_vex | SUSE CVE CVE-2022-23990 | known affected: 339 known not affected: 32 recommended: 373 | 2026-07-25T17:26:16+00:00 | Vulnerability · Source |
| CVE-2022-24052 | suse_vex | SUSE CVE CVE-2022-24052 | known affected: 1 recommended: 505 | 2026-07-25T17:26:14+00:00 | Vulnerability · Source |
| CVE-2022-24107 | suse_vex | SUSE CVE CVE-2022-24107 | known affected: 1 known not affected: 259 | 2026-07-25T17:26:13+00:00 | Vulnerability · Source |
| CVE-2022-24713 | suse_vex | SUSE CVE CVE-2022-24713 | known affected: 620 known not affected: 882 recommended: 610 | 2026-07-25T17:26:11+00:00 | Vulnerability · Source |
| CVE-2022-24765 | suse_vex | SUSE CVE CVE-2022-24765 | recommended: 1094 | 2026-07-25T17:26:09+00:00 | Vulnerability · Source |
| CVE-2022-24810 | suse_vex | SUSE CVE CVE-2022-24810 | known affected: 394 known not affected: 190 recommended: 254 | 2026-07-25T17:26:08+00:00 | Vulnerability · Source |
| CVE-2022-24903 | suse_vex | SUSE CVE CVE-2022-24903 | known affected: 144 known not affected: 66 recommended: 956 | 2026-07-25T17:26:06+00:00 | Vulnerability · Source |
| CVE-2022-25235 | suse_vex | SUSE CVE CVE-2022-25235 | known affected: 282 recommended: 449 | 2026-07-25T17:26:05+00:00 | Vulnerability · Source |
| CVE-2022-25258 | suse_vex | SUSE CVE CVE-2022-25258 | known affected: 210 known not affected: 252 recommended: 556 | 2026-07-25T17:26:01+00:00 | Vulnerability · Source |
| CVE-2022-25265 | suse_vex | SUSE CVE CVE-2022-25265 | known not affected: 3490 recommended: 20 | 2026-07-25T17:26:00+00:00 | Vulnerability · Source |
| CVE-2022-25309 | suse_vex | SUSE CVE CVE-2022-25309 | known affected: 437 recommended: 205 | 2026-07-25T17:25:58+00:00 | Vulnerability · Source |
| CVE-2022-25310 | suse_vex | SUSE CVE CVE-2022-25310 | known affected: 437 recommended: 205 | 2026-07-25T17:25:57+00:00 | Vulnerability · Source |
| CVE-2022-25315 | suse_vex | SUSE CVE CVE-2022-25315 | known affected: 282 recommended: 444 | 2026-07-25T17:25:55+00:00 | Vulnerability · Source |
| CVE-2022-25368 | suse_vex | SUSE CVE CVE-2022-25368 | known not affected: 401 | 2026-07-25T17:25:54+00:00 | Vulnerability · Source |
| CVE-2022-26356 | suse_vex | SUSE CVE CVE-2022-26356 | known affected: 349 known not affected: 46 recommended: 453 | 2026-07-25T17:25:52+00:00 | Vulnerability · Source |
| CVE-2022-26357 | suse_vex | SUSE CVE CVE-2022-26357 | known affected: 349 known not affected: 74 recommended: 446 | 2026-07-25T17:25:51+00:00 | Vulnerability · Source |
| CVE-2022-26381 | suse_vex | SUSE CVE CVE-2022-26381 | known affected: 1 recommended: 411 | 2026-07-25T17:25:49+00:00 | Vulnerability · Source |
| CVE-2022-26700 | suse_vex | SUSE CVE CVE-2022-26700 | known affected: 1 recommended: 1016 | 2026-07-25T17:25:48+00:00 | Vulnerability · Source |
| CVE-2022-26716 | suse_vex | SUSE CVE CVE-2022-26716 | known affected: 1 recommended: 1016 | 2026-07-25T17:25:46+00:00 | Vulnerability · Source |
| CVE-2022-26966 | suse_vex | SUSE CVE CVE-2022-26966 | known affected: 344 known not affected: 21 recommended: 1273 | 2026-07-25T17:25:44+00:00 | Vulnerability · Source |
| CVE-2022-27191 | suse_vex | SUSE CVE CVE-2022-27191 | known affected: 259 known not affected: 329 recommended: 811 | 2026-07-25T17:25:43+00:00 | Vulnerability · Source |
| CVE-2022-27376 | suse_vex | SUSE CVE CVE-2022-27376 | known not affected: 93 recommended: 378 | 2026-07-25T17:25:41+00:00 | Vulnerability · Source |
| CVE-2022-27381 | suse_vex | SUSE CVE CVE-2022-27381 | known not affected: 93 recommended: 490 | 2026-07-25T17:25:40+00:00 | Vulnerability · Source |
| CVE-2022-27383 | suse_vex | SUSE CVE CVE-2022-27383 | known not affected: 93 recommended: 490 | 2026-07-25T17:25:39+00:00 | Vulnerability · Source |
| CVE-2022-27385 | suse_vex | SUSE CVE CVE-2022-27385 | known not affected: 347 recommended: 16 | 2026-07-25T17:25:37+00:00 | Vulnerability · Source |
| CVE-2022-27404 | suse_vex | SUSE CVE CVE-2022-27404 | known affected: 246 known not affected: 68 recommended: 1219 | 2026-07-25T17:25:35+00:00 | Vulnerability · Source |
| CVE-2022-27405 | suse_vex | SUSE CVE CVE-2022-27405 | known affected: 237 known not affected: 130 recommended: 460 | 2026-07-25T17:25:34+00:00 | Vulnerability · Source |
| CVE-2022-27406 | suse_vex | SUSE CVE CVE-2022-27406 | known affected: 248 known not affected: 65 recommended: 466 | 2026-07-25T17:25:33+00:00 | Vulnerability · Source |
| CVE-2022-27446 | suse_vex | SUSE CVE CVE-2022-27446 | known not affected: 216 recommended: 378 | 2026-07-25T17:25:32+00:00 | Vulnerability · Source |
| CVE-2022-27447 | suse_vex | SUSE CVE CVE-2022-27447 | known not affected: 93 recommended: 378 | 2026-07-25T17:25:30+00:00 | Vulnerability · Source |
| CVE-2022-27455 | suse_vex | SUSE CVE CVE-2022-27455 | known not affected: 216 recommended: 378 | 2026-07-25T17:25:29+00:00 | Vulnerability · Source |
| CVE-2022-27456 | suse_vex | SUSE CVE CVE-2022-27456 | known not affected: 93 recommended: 378 | 2026-07-25T17:25:28+00:00 | Vulnerability · Source |
| CVE-2022-27775 | suse_vex | SUSE CVE CVE-2022-27775 | known affected: 280 known not affected: 140 recommended: 313 | 2026-07-25T17:25:26+00:00 | Vulnerability · Source |
| CVE-2022-27779 | suse_vex | SUSE CVE CVE-2022-27779 | known affected: 304 known not affected: 209 recommended: 174 | 2026-07-25T17:25:25+00:00 | Vulnerability · Source |
| CVE-2022-27780 | suse_vex | SUSE CVE CVE-2022-27780 | known affected: 304 known not affected: 209 recommended: 174 | 2026-07-25T17:25:24+00:00 | Vulnerability · Source |
| CVE-2022-27781 | suse_vex | SUSE CVE CVE-2022-27781 | known affected: 263 known not affected: 32 recommended: 458 | 2026-07-25T17:25:22+00:00 | Vulnerability · Source |