VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291286 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-29901 | suse_vex | SUSE CVE CVE-2022-29901 | known affected: 219 recommended: 1811 | 2026-08-14T01:28:27+00:00 | Vulnerability · Source |
| CVE-2022-30580 | suse_vex | SUSE CVE CVE-2022-30580 | known affected: 13 known not affected: 114 recommended: 201 | 2026-08-14T01:28:24+00:00 | Vulnerability · Source |
| CVE-2022-30630 | suse_vex | SUSE CVE CVE-2022-30630 | known not affected: 51 recommended: 288 | 2026-08-14T01:28:23+00:00 | Vulnerability · Source |
| CVE-2022-30635 | suse_vex | SUSE CVE CVE-2022-30635 | known not affected: 51 recommended: 285 | 2026-08-14T01:28:22+00:00 | Vulnerability · Source |
| CVE-2022-30787 | suse_vex | SUSE CVE CVE-2022-30787 | recommended: 124 | 2026-08-14T01:28:20+00:00 | Vulnerability · Source |
| CVE-2022-30790 | suse_vex | SUSE CVE CVE-2022-30790 | recommended: 407 | 2026-08-14T01:28:18+00:00 | Vulnerability · Source |
| CVE-2022-31256 | suse_vex | SUSE CVE CVE-2022-31256 | known not affected: 1 recommended: 83 | 2026-08-14T01:28:16+00:00 | Vulnerability · Source |
| CVE-2022-31622 | suse_vex | SUSE CVE CVE-2022-31622 | known not affected: 326 recommended: 32 | 2026-08-14T01:28:15+00:00 | Vulnerability · Source |
| CVE-2022-31623 | suse_vex | SUSE CVE CVE-2022-31623 | known not affected: 326 recommended: 32 | 2026-08-14T01:28:13+00:00 | Vulnerability · Source |
| CVE-2022-32215 | suse_vex | SUSE CVE CVE-2022-32215 | recommended: 627 | 2026-08-14T01:28:09+00:00 | Vulnerability · Source |
| CVE-2022-32250 | suse_vex | SUSE CVE CVE-2022-32250 | known affected: 237 recommended: 1400 | 2026-08-14T01:28:07+00:00 | Vulnerability · Source |
| CVE-2022-33743 | suse_vex | SUSE CVE CVE-2022-33743 | known affected: 259 known not affected: 639 recommended: 646 | 2026-08-14T01:28:00+00:00 | Vulnerability · Source |
| CVE-2022-34169 | suse_vex | SUSE CVE CVE-2022-34169 | known affected: 397 known not affected: 25 recommended: 1419 | 2026-08-14T01:27:57+00:00 | Vulnerability · Source |
| CVE-2022-34472 | suse_vex | SUSE CVE CVE-2022-34472 | known affected: 1 recommended: 482 | 2026-08-14T01:27:55+00:00 | Vulnerability · Source |
| CVE-2022-35977 | suse_vex | SUSE CVE CVE-2022-35977 | recommended: 30 | 2026-08-14T01:27:51+00:00 | Vulnerability · Source |
| CVE-2022-36402 | suse_vex | SUSE CVE CVE-2022-36402 | known affected: 388 known not affected: 439 recommended: 409 | 2026-08-14T01:27:49+00:00 | Vulnerability · Source |
| CVE-2022-36440 | suse_vex | SUSE CVE CVE-2022-36440 | known not affected: 227 recommended: 2 | 2026-08-14T01:27:47+00:00 | Vulnerability · Source |
| CVE-2022-37866 | suse_vex | SUSE CVE CVE-2022-37866 | recommended: 150 | 2026-08-14T01:27:45+00:00 | Vulnerability · Source |
| CVE-2022-38457 | suse_vex | SUSE CVE CVE-2022-38457 | known not affected: 140 recommended: 291 | 2026-08-14T01:27:42+00:00 | Vulnerability · Source |
| CVE-2022-38928 | suse_vex | SUSE CVE CVE-2022-38928 | known not affected: 330 | 2026-08-14T01:27:38+00:00 | Vulnerability · Source |
| CVE-2022-39317 | suse_vex | SUSE CVE CVE-2022-39317 | recommended: 145 | 2026-08-14T01:27:34+00:00 | Vulnerability · Source |
| CVE-2022-41222 | suse_vex | SUSE CVE CVE-2022-41222 | known affected: 376 known not affected: 232 recommended: 692 | 2026-08-14T01:27:28+00:00 | Vulnerability · Source |
| CVE-2022-41848 | suse_vex | SUSE CVE CVE-2022-41848 | known affected: 253 known not affected: 20 recommended: 1493 | 2026-08-14T01:27:25+00:00 | Vulnerability · Source |
| CVE-2022-41849 | suse_vex | SUSE CVE CVE-2022-41849 | known affected: 253 known not affected: 175 recommended: 1125 | 2026-08-14T01:27:24+00:00 | Vulnerability · Source |
| CVE-2022-42311 | suse_vex | SUSE CVE CVE-2022-42311 | known affected: 253 recommended: 518 | 2026-08-14T01:27:15+00:00 | Vulnerability · Source |
| CVE-2022-42326 | suse_vex | SUSE CVE CVE-2022-42326 | known not affected: 13 recommended: 358 | 2026-08-14T01:27:13+00:00 | Vulnerability · Source |
| CVE-2022-42334 | suse_vex | SUSE CVE CVE-2022-42334 | known not affected: 43 recommended: 261 | 2026-08-14T01:27:11+00:00 | Vulnerability · Source |
| CVE-2022-42703 | suse_vex | SUSE CVE CVE-2022-42703 | known affected: 255 recommended: 1764 | 2026-08-14T01:27:09+00:00 | Vulnerability · Source |
| CVE-2022-43945 | suse_vex | SUSE CVE CVE-2022-43945 | known affected: 242 known not affected: 6 recommended: 2126 | 2026-08-14T01:27:06+00:00 | Vulnerability · Source |
| CVE-2022-45047 | suse_vex | SUSE CVE CVE-2022-45047 | known affected: 8 recommended: 36 | 2026-08-14T01:27:02+00:00 | Vulnerability · Source |
| CVE-2022-45587 | suse_vex | SUSE CVE CVE-2022-45587 | known not affected: 350 | 2026-08-14T01:26:54+00:00 | Vulnerability · Source |
| CVE-2022-46872 | suse_vex | SUSE CVE CVE-2022-46872 | known affected: 21 recommended: 378 | 2026-08-14T01:26:46+00:00 | Vulnerability · Source |
| CVE-2022-47085 | suse_vex | SUSE CVE CVE-2022-47085 | known not affected: 138 | 2026-08-14T01:26:41+00:00 | Vulnerability · Source |
| CVE-2022-48424 | suse_vex | SUSE CVE CVE-2022-48424 | known not affected: 288 | 2026-08-14T01:26:30+00:00 | Vulnerability · Source |
| CVE-2022-48564 | suse_vex | SUSE CVE CVE-2022-48564 | known affected: 402 known not affected: 685 | 2026-08-14T01:26:26+00:00 | Vulnerability · Source |
| CVE-2022-48631 | suse_vex | SUSE CVE CVE-2022-48631 | known affected: 362 known not affected: 79 recommended: 648 | 2026-08-14T01:26:24+00:00 | Vulnerability · Source |
| CVE-2022-48633 | suse_vex | SUSE CVE CVE-2022-48633 | known affected: 315 known not affected: 247 recommended: 313 | 2026-08-14T01:26:22+00:00 | Vulnerability · Source |
| CVE-2022-48639 | suse_vex | SUSE CVE CVE-2022-48639 | known affected: 441 known not affected: 195 recommended: 318 | 2026-08-14T01:26:20+00:00 | Vulnerability · Source |
| CVE-2022-48648 | suse_vex | SUSE CVE CVE-2022-48648 | known affected: 265 known not affected: 202 recommended: 462 | 2026-08-14T01:26:18+00:00 | Vulnerability · Source |
| CVE-2022-48652 | suse_vex | SUSE CVE CVE-2022-48652 | known affected: 270 known not affected: 202 recommended: 457 | 2026-08-14T01:26:17+00:00 | Vulnerability · Source |
| CVE-2022-48659 | suse_vex | SUSE CVE CVE-2022-48659 | known affected: 331 known not affected: 326 recommended: 318 | 2026-08-14T01:26:15+00:00 | Vulnerability · Source |
| CVE-2022-48668 | suse_vex | SUSE CVE CVE-2022-48668 | known affected: 320 known not affected: 145 recommended: 532 | 2026-08-14T01:26:13+00:00 | Vulnerability · Source |
| CVE-2022-48673 | suse_vex | SUSE CVE CVE-2022-48673 | known affected: 280 known not affected: 157 recommended: 592 | 2026-08-14T01:26:11+00:00 | Vulnerability · Source |
| CVE-2022-48686 | suse_vex | SUSE CVE CVE-2022-48686 | known affected: 281 known not affected: 151 recommended: 670 | 2026-08-14T01:26:09+00:00 | Vulnerability · Source |
| CVE-2022-48688 | suse_vex | SUSE CVE CVE-2022-48688 | known affected: 303 known not affected: 79 recommended: 527 | 2026-08-14T01:26:06+00:00 | Vulnerability · Source |
| CVE-2022-48709 | suse_vex | SUSE CVE CVE-2022-48709 | known affected: 275 known not affected: 217 recommended: 452 | 2026-08-14T01:26:04+00:00 | Vulnerability · Source |
| CVE-2022-48711 | suse_vex | SUSE CVE CVE-2022-48711 | known not affected: 163 recommended: 526 | 2026-08-14T01:26:02+00:00 | Vulnerability · Source |
| CVE-2022-48713 | suse_vex | SUSE CVE CVE-2022-48713 | known affected: 295 known not affected: 205 recommended: 428 | 2026-08-14T01:26:01+00:00 | Vulnerability · Source |
| CVE-2022-48716 | suse_vex | SUSE CVE CVE-2022-48716 | known affected: 391 known not affected: 245 recommended: 298 | 2026-08-14T01:25:59+00:00 | Vulnerability · Source |
| CVE-2022-48725 | suse_vex | SUSE CVE CVE-2022-48725 | known affected: 330 known not affected: 205 recommended: 391 | 2026-08-14T01:25:58+00:00 | Vulnerability · Source |