VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-50560 | suse_vex | SUSE CVE CVE-2022-50560 | known affected: 516 known not affected: 221 recommended: 196 | 2026-10-16T14:04:07+00:00 | Vulnerability · Source |
| CVE-2022-50562 | suse_vex | SUSE CVE CVE-2022-50562 | known affected: 423 known not affected: 314 recommended: 274 | 2026-10-16T14:04:05+00:00 | Vulnerability · Source |
| CVE-2022-50565 | suse_vex | SUSE CVE CVE-2022-50565 | known affected: 0 known not affected: 511 | 2026-10-16T14:04:02+00:00 | Vulnerability · Source |
| CVE-2022-50568 | suse_vex | SUSE CVE CVE-2022-50568 | known affected: 507 known not affected: 230 recommended: 196 | 2026-10-16T14:04:00+00:00 | Vulnerability · Source |
| CVE-2022-50575 | suse_vex | SUSE CVE CVE-2022-50575 | known affected: 358 known not affected: 379 recommended: 196 | 2026-10-16T14:03:57+00:00 | Vulnerability · Source |
| CVE-2022-50576 | suse_vex | SUSE CVE CVE-2022-50576 | known affected: 354 known not affected: 383 recommended: 196 | 2026-10-16T14:03:55+00:00 | Vulnerability · Source |
| CVE-2022-50579 | suse_vex | SUSE CVE CVE-2022-50579 | known affected: 354 known not affected: 383 recommended: 196 | 2026-10-16T14:03:53+00:00 | Vulnerability · Source |
| CVE-2022-50581 | suse_vex | SUSE CVE CVE-2022-50581 | known affected: 518 known not affected: 161 recommended: 219 | 2026-10-16T14:03:52+00:00 | Vulnerability · Source |
| CVE-2022-50582 | suse_vex | SUSE CVE CVE-2022-50582 | known affected: 354 known not affected: 383 recommended: 254 | 2026-10-16T14:03:50+00:00 | Vulnerability · Source |
| CVE-2022-50630 | suse_vex | SUSE CVE CVE-2022-50630 | known affected: 354 known not affected: 359 recommended: 252 | 2026-10-16T14:03:48+00:00 | Vulnerability · Source |
| CVE-2022-50636 | suse_vex | SUSE CVE CVE-2022-50636 | known affected: 520 known not affected: 202 recommended: 248 | 2026-10-16T14:03:46+00:00 | Vulnerability · Source |
| CVE-2022-50650 | suse_vex | SUSE CVE CVE-2022-50650 | known affected: 128 known not affected: 384 recommended: 29 | 2026-10-16T14:03:42+00:00 | Vulnerability · Source |
| CVE-2022-50656 | suse_vex | SUSE CVE CVE-2022-50656 | known affected: 548 known not affected: 170 recommended: 233 | 2026-10-16T14:03:40+00:00 | Vulnerability · Source |
| CVE-2022-50660 | suse_vex | SUSE CVE CVE-2022-50660 | known affected: 612 known not affected: 166 recommended: 210 | 2026-10-16T14:03:38+00:00 | Vulnerability · Source |
| CVE-2022-50665 | suse_vex | SUSE CVE CVE-2022-50665 | known affected: 374 known not affected: 445 recommended: 87 | 2026-10-16T14:03:37+00:00 | Vulnerability · Source |
| CVE-2022-50666 | suse_vex | SUSE CVE CVE-2022-50666 | known affected: 421 known not affected: 317 recommended: 196 | 2026-10-16T14:03:35+00:00 | Vulnerability · Source |
| CVE-2022-50671 | suse_vex | SUSE CVE CVE-2022-50671 | known affected: 533 known not affected: 241 recommended: 249 | 2026-10-16T14:03:33+00:00 | Vulnerability · Source |
| CVE-2022-50673 | suse_vex | SUSE CVE CVE-2022-50673 | known affected: 473 known not affected: 205 recommended: 258 | 2026-10-16T14:03:30+00:00 | Vulnerability · Source |
| CVE-2022-50677 | suse_vex | SUSE CVE CVE-2022-50677 | known affected: 454 known not affected: 226 recommended: 268 | 2026-10-16T14:03:28+00:00 | Vulnerability · Source |
| CVE-2022-50697 | suse_vex | SUSE CVE CVE-2022-50697 | known affected: 541 known not affected: 175 recommended: 273 | 2026-10-16T14:03:26+00:00 | Vulnerability · Source |
| CVE-2022-50700 | suse_vex | SUSE CVE CVE-2022-50700 | known affected: 485 known not affected: 235 recommended: 306 | 2026-10-16T14:03:24+00:00 | Vulnerability · Source |
| CVE-2022-50701 | suse_vex | SUSE CVE CVE-2022-50701 | known affected: 374 known not affected: 490 recommended: 136 | 2026-10-16T14:03:21+00:00 | Vulnerability · Source |
| CVE-2022-50714 | suse_vex | SUSE CVE CVE-2022-50714 | known affected: 379 known not affected: 485 recommended: 134 | 2026-10-16T14:03:18+00:00 | Vulnerability · Source |
| CVE-2022-50716 | suse_vex | SUSE CVE CVE-2022-50716 | known affected: 518 known not affected: 209 recommended: 219 | 2026-10-16T14:03:16+00:00 | Vulnerability · Source |
| CVE-2022-50722 | suse_vex | SUSE CVE CVE-2022-50722 | known affected: 427 known not affected: 358 recommended: 196 | 2026-10-16T14:03:13+00:00 | Vulnerability · Source |
| CVE-2022-50746 | suse_vex | SUSE CVE CVE-2022-50746 | known affected: 154 known not affected: 403 | 2026-10-16T14:03:11+00:00 | Vulnerability · Source |
| CVE-2022-50750 | suse_vex | SUSE CVE CVE-2022-50750 | known affected: 354 known not affected: 356 recommended: 245 | 2026-10-16T14:03:09+00:00 | Vulnerability · Source |
| CVE-2022-50755 | suse_vex | SUSE CVE CVE-2022-50755 | known affected: 548 known not affected: 175 recommended: 233 | 2026-10-16T14:03:07+00:00 | Vulnerability · Source |
| CVE-2022-50756 | suse_vex | SUSE CVE CVE-2022-50756 | known affected: 420 known not affected: 298 recommended: 261 | 2026-10-16T14:03:06+00:00 | Vulnerability · Source |
| CVE-2022-50771 | suse_vex | SUSE CVE CVE-2022-50771 | known affected: 292 known not affected: 166 recommended: 29 | 2026-10-16T14:03:04+00:00 | Vulnerability · Source |
| CVE-2022-50774 | suse_vex | SUSE CVE CVE-2022-50774 | known affected: 576 known not affected: 166 recommended: 196 | 2026-10-16T14:02:55+00:00 | Vulnerability · Source |
| CVE-2022-50816 | suse_vex | SUSE CVE CVE-2022-50816 | known affected: 690 known not affected: 155 recommended: 84 | 2026-10-16T14:02:52+00:00 | Vulnerability · Source |
| CVE-2022-50821 | suse_vex | SUSE CVE CVE-2022-50821 | known affected: 503 known not affected: 217 recommended: 223 | 2026-10-16T14:02:50+00:00 | Vulnerability · Source |
| CVE-2022-50822 | suse_vex | SUSE CVE CVE-2022-50822 | known affected: 354 known not affected: 429 recommended: 245 | 2026-10-16T14:02:48+00:00 | Vulnerability · Source |
| CVE-2022-50832 | suse_vex | SUSE CVE CVE-2022-50832 | known affected: 608 known not affected: 177 recommended: 225 | 2026-10-16T14:02:46+00:00 | Vulnerability · Source |
| CVE-2022-50840 | suse_vex | SUSE CVE CVE-2022-50840 | known affected: 501 known not affected: 217 recommended: 237 | 2026-10-16T14:02:45+00:00 | Vulnerability · Source |
| CVE-2022-50849 | suse_vex | SUSE CVE CVE-2022-50849 | known affected: 548 known not affected: 175 recommended: 233 | 2026-10-16T14:02:43+00:00 | Vulnerability · Source |
| CVE-2022-50871 | suse_vex | SUSE CVE CVE-2022-50871 | known affected: 128 known not affected: 429 | 2026-10-16T14:02:41+00:00 | Vulnerability · Source |
| CVE-2022-50880 | suse_vex | SUSE CVE CVE-2022-50880 | known affected: 354 known not affected: 364 recommended: 223 | 2026-10-16T14:02:39+00:00 | Vulnerability · Source |
| CVE-2022-50885 | suse_vex | SUSE CVE CVE-2022-50885 | known affected: 357 known not affected: 366 recommended: 262 | 2026-10-16T14:02:38+00:00 | Vulnerability · Source |
| CVE-2023-0030 | suse_vex | SUSE CVE CVE-2023-0030 | known not affected: 402 | 2026-10-16T14:02:36+00:00 | Vulnerability · Source |
| CVE-2023-0109 | suse_vex | SUSE CVE CVE-2023-0109 | recommended: 4 | 2026-10-16T14:02:34+00:00 | Vulnerability · Source |
| CVE-2023-0122 | suse_vex | SUSE CVE CVE-2023-0122 | known affected: 289 known not affected: 335 recommended: 738 | 2026-10-16T14:02:32+00:00 | Vulnerability · Source |
| CVE-2023-0160 | suse_vex | SUSE CVE CVE-2023-0160 | known affected: 337 known not affected: 118 recommended: 1043 | 2026-10-16T14:02:30+00:00 | Vulnerability · Source |
| CVE-2023-0179 | suse_vex | SUSE CVE CVE-2023-0179 | known affected: 247 known not affected: 308 recommended: 1271 | 2026-10-16T14:02:28+00:00 | Vulnerability · Source |
| CVE-2023-0215 | suse_vex | SUSE CVE CVE-2023-0215 | known affected: 274 known not affected: 174 recommended: 905 | 2026-10-16T14:02:25+00:00 | Vulnerability · Source |
| CVE-2023-0216 | suse_vex | SUSE CVE CVE-2023-0216 | known affected: 0 known not affected: 543 recommended: 148 | 2026-10-16T14:02:22+00:00 | Vulnerability · Source |
| CVE-2023-0217 | suse_vex | SUSE CVE CVE-2023-0217 | known affected: 0 known not affected: 543 recommended: 148 | 2026-10-16T14:02:20+00:00 | Vulnerability · Source |
| CVE-2023-0240 | suse_vex | SUSE CVE CVE-2023-0240 | known affected: 0 known not affected: 295 | 2026-10-16T14:02:19+00:00 | Vulnerability · Source |
| CVE-2023-0266 | suse_vex | SUSE CVE CVE-2023-0266 | known affected: 277 known not affected: 165 recommended: 1142 | 2026-10-16T14:02:17+00:00 | Vulnerability · Source |