VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104648 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-63861 | suse_vex | SUSE CVE CVE-2026-63861 | known affected: 426 known not affected: 326 recommended: 308 | 2026-10-17T00:17:29+00:00 | Vulnerability · Source |
| CVE-2026-63862 | suse_vex | SUSE CVE CVE-2026-63862 | known affected: 530 known not affected: 183 recommended: 308 | 2026-10-17T00:17:27+00:00 | Vulnerability · Source |
| CVE-2026-63863 | suse_vex | SUSE CVE CVE-2026-63863 | known affected: 0 known not affected: 376 | 2026-10-17T00:17:26+00:00 | Vulnerability · Source |
| CVE-2026-63867 | suse_vex | SUSE CVE CVE-2026-63867 | known affected: 126 known not affected: 251 | 2026-10-17T00:17:24+00:00 | Vulnerability · Source |
| CVE-2026-63869 | suse_vex | SUSE CVE CVE-2026-63869 | known affected: 426 known not affected: 326 recommended: 391 | 2026-10-17T00:17:21+00:00 | Vulnerability · Source |
| CVE-2026-63870 | suse_vex | SUSE CVE CVE-2026-63870 | known affected: 373 known not affected: 4 | 2026-10-17T00:17:20+00:00 | Vulnerability · Source |
| CVE-2026-63882 | suse_vex | SUSE CVE CVE-2026-63882 | known affected: 530 known not affected: 183 recommended: 308 | 2026-10-17T00:17:17+00:00 | Vulnerability · Source |
| CVE-2026-63885 | suse_vex | SUSE CVE CVE-2026-63885 | known affected: 0 known not affected: 376 | 2026-10-17T00:17:14+00:00 | Vulnerability · Source |
| CVE-2026-63889 | suse_vex | SUSE CVE CVE-2026-63889 | known affected: 559 known not affected: 147 recommended: 355 | 2026-10-17T00:17:11+00:00 | Vulnerability · Source |
| CVE-2026-63892 | suse_vex | SUSE CVE CVE-2026-63892 | known affected: 613 known not affected: 85 recommended: 331 | 2026-10-17T00:17:07+00:00 | Vulnerability · Source |
| CVE-2026-63895 | suse_vex | SUSE CVE CVE-2026-63895 | known affected: 530 known not affected: 222 recommended: 308 | 2026-10-17T00:17:06+00:00 | Vulnerability · Source |
| CVE-2026-63896 | suse_vex | SUSE CVE CVE-2026-63896 | known affected: 426 known not affected: 326 recommended: 308 | 2026-10-17T00:17:04+00:00 | Vulnerability · Source |
| CVE-2026-63897 | suse_vex | SUSE CVE CVE-2026-63897 | known affected: 675 known not affected: 75 recommended: 331 | 2026-10-17T00:17:03+00:00 | Vulnerability · Source |
| CVE-2026-63900 | suse_vex | SUSE CVE CVE-2026-63900 | known affected: 677 known not affected: 46 recommended: 331 | 2026-10-17T00:17:00+00:00 | Vulnerability · Source |
| CVE-2026-63901 | suse_vex | SUSE CVE CVE-2026-63901 | known affected: 636 recommended: 273 | 2026-10-17T00:16:58+00:00 | Vulnerability · Source |
| CVE-2026-63902 | suse_vex | SUSE CVE CVE-2026-63902 | known affected: 677 known not affected: 46 recommended: 331 | 2026-10-17T00:16:57+00:00 | Vulnerability · Source |
| CVE-2026-63903 | suse_vex | SUSE CVE CVE-2026-63903 | known affected: 456 known not affected: 267 recommended: 331 | 2026-10-17T00:16:55+00:00 | Vulnerability · Source |
| CVE-2026-63904 | suse_vex | SUSE CVE CVE-2026-63904 | known affected: 675 known not affected: 48 recommended: 331 | 2026-10-17T00:16:54+00:00 | Vulnerability · Source |
| CVE-2026-63905 | suse_vex | SUSE CVE CVE-2026-63905 | known affected: 671 known not affected: 52 recommended: 308 | 2026-10-17T00:16:53+00:00 | Vulnerability · Source |
| CVE-2026-63908 | suse_vex | SUSE CVE CVE-2026-63908 | known affected: 580 known not affected: 172 recommended: 308 | 2026-10-17T00:16:51+00:00 | Vulnerability · Source |
| CVE-2026-63916 | suse_vex | SUSE CVE CVE-2026-63916 | known affected: 677 known not affected: 75 recommended: 308 | 2026-10-17T00:16:47+00:00 | Vulnerability · Source |
| CVE-2026-63927 | suse_vex | SUSE CVE CVE-2026-63927 | known affected: 619 known not affected: 50 recommended: 331 | 2026-10-17T00:16:40+00:00 | Vulnerability · Source |
| CVE-2026-63928 | suse_vex | SUSE CVE CVE-2026-63928 | known affected: 619 known not affected: 46 recommended: 333 | 2026-10-17T00:16:39+00:00 | Vulnerability · Source |
| CVE-2026-63930 | suse_vex | SUSE CVE CVE-2026-63930 | known affected: 580 known not affected: 143 recommended: 308 | 2026-10-17T00:16:37+00:00 | Vulnerability · Source |
| CVE-2026-63931 | suse_vex | SUSE CVE CVE-2026-63931 | known affected: 530 known not affected: 193 recommended: 308 | 2026-10-17T00:16:36+00:00 | Vulnerability · Source |
| CVE-2026-63934 | suse_vex | SUSE CVE CVE-2026-63934 | known affected: 673 known not affected: 50 recommended: 308 | 2026-10-17T00:16:35+00:00 | Vulnerability · Source |
| CVE-2026-63937 | suse_vex | SUSE CVE CVE-2026-63937 | known affected: 396 known not affected: 342 recommended: 286 | 2026-10-17T00:16:33+00:00 | Vulnerability · Source |
| CVE-2026-63938 | suse_vex | SUSE CVE CVE-2026-63938 | known affected: 425 known not affected: 313 recommended: 286 | 2026-10-17T00:16:32+00:00 | Vulnerability · Source |
| CVE-2026-63940 | suse_vex | SUSE CVE CVE-2026-63940 | known affected: 530 known not affected: 193 recommended: 308 | 2026-10-17T00:16:29+00:00 | Vulnerability · Source |
| CVE-2026-63942 | suse_vex | SUSE CVE CVE-2026-63942 | known affected: 613 known not affected: 79 recommended: 331 | 2026-10-17T00:16:27+00:00 | Vulnerability · Source |
| CVE-2026-63943 | suse_vex | SUSE CVE CVE-2026-63943 | known affected: 426 known not affected: 314 recommended: 308 | 2026-10-17T00:16:25+00:00 | Vulnerability · Source |
| CVE-2026-63945 | suse_vex | SUSE CVE CVE-2026-63945 | known affected: 484 known not affected: 268 recommended: 349 | 2026-10-17T00:16:24+00:00 | Vulnerability · Source |
| CVE-2026-63947 | suse_vex | SUSE CVE CVE-2026-63947 | known affected: 677 known not affected: 75 recommended: 411 | 2026-10-17T00:16:22+00:00 | Vulnerability · Source |
| CVE-2026-63948 | suse_vex | SUSE CVE CVE-2026-63948 | known affected: 544 known not affected: 208 recommended: 308 | 2026-10-17T00:16:21+00:00 | Vulnerability · Source |
| CVE-2026-63949 | suse_vex | SUSE CVE CVE-2026-63949 | known affected: 426 known not affected: 326 recommended: 308 | 2026-10-17T00:16:19+00:00 | Vulnerability · Source |
| CVE-2026-63957 | suse_vex | SUSE CVE CVE-2026-63957 | known affected: 677 known not affected: 46 recommended: 331 | 2026-10-17T00:16:16+00:00 | Vulnerability · Source |
| CVE-2026-63958 | suse_vex | SUSE CVE CVE-2026-63958 | known affected: 617 known not affected: 52 recommended: 331 | 2026-10-17T00:16:15+00:00 | Vulnerability · Source |
| CVE-2026-63959 | suse_vex | SUSE CVE CVE-2026-63959 | known affected: 530 known not affected: 193 recommended: 308 | 2026-10-17T00:16:13+00:00 | Vulnerability · Source |
| CVE-2026-63960 | suse_vex | SUSE CVE CVE-2026-63960 | known affected: 580 known not affected: 143 recommended: 308 | 2026-10-17T00:16:12+00:00 | Vulnerability · Source |
| CVE-2026-63961 | suse_vex | SUSE CVE CVE-2026-63961 | known affected: 671 known not affected: 52 recommended: 331 | 2026-10-17T00:16:11+00:00 | Vulnerability · Source |
| CVE-2026-63964 | suse_vex | SUSE CVE CVE-2026-63964 | known affected: 580 known not affected: 143 recommended: 308 | 2026-10-17T00:16:06+00:00 | Vulnerability · Source |
| CVE-2026-63967 | suse_vex | SUSE CVE CVE-2026-63967 | known affected: 530 known not affected: 193 recommended: 308 | 2026-10-17T00:16:05+00:00 | Vulnerability · Source |
| CVE-2026-63969 | suse_vex | SUSE CVE CVE-2026-63969 | known affected: 485 known not affected: 251 recommended: 252 | 2026-10-17T00:16:03+00:00 | Vulnerability · Source |
| CVE-2026-63976 | suse_vex | SUSE CVE CVE-2026-63976 | known affected: 556 known not affected: 196 recommended: 308 | 2026-10-17T00:15:58+00:00 | Vulnerability · Source |
| CVE-2026-63977 | suse_vex | SUSE CVE CVE-2026-63977 | known affected: 0 known not affected: 376 recommended: 58 | 2026-10-17T00:15:57+00:00 | Vulnerability · Source |
| CVE-2026-63978 | suse_vex | SUSE CVE CVE-2026-63978 | known affected: 113 known not affected: 251 recommended: 58 | 2026-10-17T00:15:56+00:00 | Vulnerability · Source |
| CVE-2026-63979 | suse_vex | SUSE CVE CVE-2026-63979 | known affected: 113 known not affected: 251 recommended: 58 | 2026-10-17T00:15:55+00:00 | Vulnerability · Source |
| CVE-2026-63980 | suse_vex | SUSE CVE CVE-2026-63980 | known affected: 470 known not affected: 251 recommended: 165 | 2026-10-17T00:15:53+00:00 | Vulnerability · Source |
| CVE-2026-63985 | suse_vex | SUSE CVE CVE-2026-63985 | known affected: 589 known not affected: 147 recommended: 252 | 2026-10-17T00:15:52+00:00 | Vulnerability · Source |
| CVE-2026-63990 | suse_vex | SUSE CVE CVE-2026-63990 | known affected: 682 recommended: 275 | 2026-10-17T00:15:49+00:00 | Vulnerability · Source |