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-2026-41568 | suse_vex | SUSE CVE CVE-2026-41568 | known affected: 352 | 2026-10-16T00:25:10+00:00 | Vulnerability · Source |
| CVE-2026-41602 | suse_vex | SUSE CVE CVE-2026-41602 | known affected: 48 known not affected: 469 recommended: 266 | 2026-10-16T00:25:08+00:00 | Vulnerability · Source |
| CVE-2026-41604 | suse_vex | SUSE CVE CVE-2026-41604 | known affected: 44 known not affected: 480 recommended: 150 | 2026-10-16T00:25:04+00:00 | Vulnerability · Source |
| CVE-2026-41605 | suse_vex | SUSE CVE CVE-2026-41605 | known affected: 44 known not affected: 480 recommended: 150 | 2026-10-16T00:25:02+00:00 | Vulnerability · Source |
| CVE-2026-41636 | suse_vex | SUSE CVE CVE-2026-41636 | known affected: 28 known not affected: 506 recommended: 150 | 2026-10-16T00:24:57+00:00 | Vulnerability · Source |
| CVE-2026-41651 | suse_vex | SUSE CVE CVE-2026-41651 | known affected: 498 recommended: 206 | 2026-10-16T00:24:55+00:00 | Vulnerability · Source |
| CVE-2026-41990 | suse_vex | SUSE CVE CVE-2026-41990 | known affected: 425 known not affected: 696 recommended: 17 | 2026-10-16T00:24:48+00:00 | Vulnerability · Source |
| CVE-2026-42055 | suse_vex | SUSE CVE CVE-2026-42055 | known affected: 24 recommended: 71 | 2026-10-16T00:24:44+00:00 | Vulnerability · Source |
| CVE-2026-42245 | suse_vex | SUSE CVE CVE-2026-42245 | known affected: 5 known not affected: 339 recommended: 87 | 2026-10-16T00:24:42+00:00 | Vulnerability · Source |
| CVE-2026-42256 | suse_vex | SUSE CVE CVE-2026-42256 | known affected: 5 known not affected: 329 recommended: 105 | 2026-10-16T00:24:37+00:00 | Vulnerability · Source |
| CVE-2026-42764 | suse_vex | SUSE CVE CVE-2026-42764 | known not affected: 610 recommended: 98 | 2026-10-16T00:24:21+00:00 | Vulnerability · Source |
| CVE-2026-42766 | suse_vex | SUSE CVE CVE-2026-42766 | known affected: 568 known not affected: 104 recommended: 347 | 2026-10-16T00:24:19+00:00 | Vulnerability · Source |
| CVE-2026-42768 | suse_vex | SUSE CVE CVE-2026-42768 | known affected: 412 known not affected: 592 recommended: 74 | 2026-10-16T00:24:17+00:00 | Vulnerability · Source |
| CVE-2026-42769 | suse_vex | SUSE CVE CVE-2026-42769 | known affected: 394 known not affected: 610 recommended: 74 | 2026-10-16T00:24:15+00:00 | Vulnerability · Source |
| CVE-2026-42770 | suse_vex | SUSE CVE CVE-2026-42770 | known affected: 413 known not affected: 544 recommended: 132 | 2026-10-16T00:24:13+00:00 | Vulnerability · Source |
| CVE-2026-42784 | suse_vex | SUSE CVE CVE-2026-42784 | known affected: 4 known not affected: 23 recommended: 6 | 2026-10-16T00:24:12+00:00 | Vulnerability · Source |
| CVE-2026-43332 | suse_vex | SUSE CVE CVE-2026-43332 | first fixed: 2 known affected: 485 known not affected: 279 recommended: 172 | 2026-10-16T00:24:03+00:00 | Vulnerability · Source |
| CVE-2026-43617 | suse_vex | SUSE CVE CVE-2026-43617 | known affected: 406 known not affected: 4 recommended: 33 | 2026-10-16T00:23:48+00:00 | Vulnerability · Source |
| CVE-2026-43618 | suse_vex | SUSE CVE CVE-2026-43618 | known affected: 410 recommended: 41 | 2026-10-16T00:23:46+00:00 | Vulnerability · Source |
| CVE-2026-43619 | suse_vex | SUSE CVE CVE-2026-43619 | known affected: 410 recommended: 18 | 2026-10-16T00:23:44+00:00 | Vulnerability · Source |
| CVE-2026-43620 | suse_vex | SUSE CVE CVE-2026-43620 | known affected: 410 recommended: 33 | 2026-10-16T00:23:41+00:00 | Vulnerability · Source |
| CVE-2026-44507 | suse_vex | SUSE CVE CVE-2026-44507 | known affected: 406 known not affected: 4 recommended: 5 | 2026-10-16T00:23:29+00:00 | Vulnerability · Source |
| CVE-2026-44508 | suse_vex | SUSE CVE CVE-2026-44508 | known affected: 410 recommended: 5 | 2026-10-16T00:23:27+00:00 | Vulnerability · Source |
| CVE-2026-44509 | suse_vex | SUSE CVE CVE-2026-44509 | known affected: 410 recommended: 5 | 2026-10-16T00:23:25+00:00 | Vulnerability · Source |
| CVE-2026-44510 | suse_vex | SUSE CVE CVE-2026-44510 | known affected: 410 recommended: 5 | 2026-10-16T00:23:22+00:00 | Vulnerability · Source |
| CVE-2026-44604 | suse_vex | SUSE CVE CVE-2026-44604 | known affected: 418 known not affected: 175 recommended: 57 | 2026-10-16T00:23:19+00:00 | Vulnerability · Source |
| CVE-2026-44705 | suse_vex | SUSE CVE CVE-2026-44705 | known not affected: 513 | 2026-10-16T00:23:16+00:00 | Vulnerability · Source |
| CVE-2026-44933 | suse_vex | SUSE CVE CVE-2026-44933 | first fixed: 51 known affected: 419 known not affected: 26 recommended: 326 | 2026-10-16T00:23:12+00:00 | Vulnerability · Source |
| CVE-2026-44941 | suse_vex | SUSE CVE CVE-2026-44941 | first fixed: 51 known affected: 419 known not affected: 26 recommended: 323 | 2026-10-16T00:23:10+00:00 | Vulnerability · Source |
| CVE-2026-44942 | suse_vex | SUSE CVE CVE-2026-44942 | first fixed: 51 known affected: 427 known not affected: 2 recommended: 333 | 2026-10-16T00:23:08+00:00 | Vulnerability · Source |
| CVE-2026-45232 | suse_vex | SUSE CVE CVE-2026-45232 | known affected: 410 recommended: 33 | 2026-10-16T00:23:05+00:00 | Vulnerability · Source |
| CVE-2026-45446 | suse_vex | SUSE CVE CVE-2026-45446 | known affected: 394 known not affected: 549 recommended: 132 | 2026-10-16T00:23:00+00:00 | Vulnerability · Source |
| CVE-2026-45623 | suse_vex | SUSE CVE CVE-2026-45623 | known affected: 165 known not affected: 403 | 2026-10-16T00:22:56+00:00 | Vulnerability · Source |
| CVE-2026-45679 | suse_vex | SUSE CVE CVE-2026-45679 | known affected: 2 recommended: 5 | 2026-10-16T00:22:53+00:00 | Vulnerability · Source |
| CVE-2026-45680 | suse_vex | SUSE CVE CVE-2026-45680 | known affected: 2 recommended: 5 | 2026-10-16T00:22:50+00:00 | Vulnerability · Source |
| CVE-2026-45681 | suse_vex | SUSE CVE CVE-2026-45681 | known affected: 2 recommended: 5 | 2026-10-16T00:22:48+00:00 | Vulnerability · Source |
| CVE-2026-45683 | suse_vex | SUSE CVE CVE-2026-45683 | known affected: 7 recommended: 1 | 2026-10-16T00:22:46+00:00 | Vulnerability · Source |
| CVE-2026-45684 | suse_vex | SUSE CVE CVE-2026-45684 | known affected: 2 recommended: 5 | 2026-10-16T00:22:43+00:00 | Vulnerability · Source |
| CVE-2026-45822 | suse_vex | SUSE CVE CVE-2026-45822 | known affected: 215 known not affected: 318 | 2026-10-16T00:22:40+00:00 | Vulnerability · Source |
| CVE-2026-46032 | suse_vex | SUSE CVE CVE-2026-46032 | known affected: 202 known not affected: 99 recommended: 4 | 2026-10-16T00:22:34+00:00 | Vulnerability · Source |
| CVE-2026-46116 | suse_vex | SUSE CVE CVE-2026-46116 | known affected: 549 recommended: 815 | 2026-10-16T00:22:27+00:00 | Vulnerability · Source |
| CVE-2026-46600 | suse_vex | SUSE CVE CVE-2026-46600 | known affected: 273 known not affected: 391 recommended: 54 | 2026-10-16T00:22:04+00:00 | Vulnerability · Source |
| CVE-2026-47240 | suse_vex | SUSE CVE CVE-2026-47240 | known affected: 16 known not affected: 176 recommended: 124 | 2026-10-16T00:22:02+00:00 | Vulnerability · Source |
| CVE-2026-47241 | suse_vex | SUSE CVE CVE-2026-47241 | known affected: 16 known not affected: 176 recommended: 124 | 2026-10-16T00:22:01+00:00 | Vulnerability · Source |
| CVE-2026-47242 | suse_vex | SUSE CVE CVE-2026-47242 | known affected: 16 known not affected: 176 recommended: 152 | 2026-10-16T00:21:59+00:00 | Vulnerability · Source |
| CVE-2026-47489 | suse_vex | SUSE CVE CVE-2026-47489 | known affected: 152 recommended: 4 | 2026-10-16T00:21:57+00:00 | Vulnerability · Source |
| CVE-2026-47491 | suse_vex | SUSE CVE CVE-2026-47491 | known affected: 152 recommended: 9 | 2026-10-16T00:21:55+00:00 | Vulnerability · Source |
| CVE-2026-47492 | suse_vex | SUSE CVE CVE-2026-47492 | known affected: 152 recommended: 9 | 2026-10-16T00:21:53+00:00 | Vulnerability · Source |
| CVE-2026-47494 | suse_vex | SUSE CVE CVE-2026-47494 | known affected: 152 recommended: 4 | 2026-10-16T00:21:52+00:00 | Vulnerability · Source |
| CVE-2026-47500 | suse_vex | SUSE CVE CVE-2026-47500 | known affected: 152 recommended: 9 | 2026-10-16T00:21:50+00:00 | Vulnerability · Source |