VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
293832 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-26981 | suse_vex | SUSE CVE CVE-2026-26981 | known not affected: 137 recommended: 18 | 2026-07-15T05:25:31+00:00 | Vulnerability · Source |
| CVE-2026-26983 | suse_vex | SUSE CVE CVE-2026-26983 | known affected: 287 known not affected: 16 recommended: 258 | 2026-07-15T05:25:29+00:00 | Vulnerability · Source |
| CVE-2026-27205 | suse_vex | SUSE CVE CVE-2026-27205 | known affected: 61 recommended: 20 | 2026-07-15T05:25:16+00:00 | Vulnerability · Source |
| CVE-2026-27596 | suse_vex | SUSE CVE CVE-2026-27596 | known affected: 93 recommended: 31 | 2026-07-15T05:25:11+00:00 | Vulnerability · Source |
| CVE-2026-27622 | suse_vex | SUSE CVE CVE-2026-27622 | known not affected: 112 recommended: 63 | 2026-07-15T05:25:09+00:00 | Vulnerability · Source |
| CVE-2026-27631 | suse_vex | SUSE CVE CVE-2026-27631 | known affected: 93 recommended: 36 | 2026-07-15T05:25:08+00:00 | Vulnerability · Source |
| CVE-2026-27798 | suse_vex | SUSE CVE CVE-2026-27798 | known affected: 54 known not affected: 52 recommended: 248 | 2026-07-15T05:25:01+00:00 | Vulnerability · Source |
| CVE-2026-27853 | suse_vex | SUSE CVE CVE-2026-27853 | known affected: 19 recommended: 8 | 2026-07-15T05:24:59+00:00 | Vulnerability · Source |
| CVE-2026-27854 | suse_vex | SUSE CVE CVE-2026-27854 | known affected: 19 recommended: 9 | 2026-07-15T05:24:58+00:00 | Vulnerability · Source |
| CVE-2026-27855 | suse_vex | SUSE CVE CVE-2026-27855 | known affected: 215 known not affected: 34 recommended: 44 | 2026-07-15T05:24:56+00:00 | Vulnerability · Source |
| CVE-2026-27856 | suse_vex | SUSE CVE CVE-2026-27856 | known affected: 215 known not affected: 34 recommended: 44 | 2026-07-15T05:24:55+00:00 | Vulnerability · Source |
| CVE-2026-27859 | suse_vex | SUSE CVE CVE-2026-27859 | known affected: 215 known not affected: 34 recommended: 44 | 2026-07-15T05:24:50+00:00 | Vulnerability · Source |
| CVE-2026-27860 | suse_vex | SUSE CVE CVE-2026-27860 | known not affected: 261 recommended: 30 | 2026-07-15T05:24:48+00:00 | Vulnerability · Source |
| CVE-2026-28295 | suse_vex | SUSE CVE CVE-2026-28295 | known affected: 62 recommended: 174 | 2026-07-15T05:24:45+00:00 | Vulnerability · Source |
| CVE-2026-28296 | suse_vex | SUSE CVE CVE-2026-28296 | known affected: 62 recommended: 174 | 2026-07-15T05:24:43+00:00 | Vulnerability · Source |
| CVE-2026-28434 | suse_vex | SUSE CVE CVE-2026-28434 | known affected: 5 recommended: 8 | 2026-07-15T05:24:32+00:00 | Vulnerability · Source |
| CVE-2026-28435 | suse_vex | SUSE CVE CVE-2026-28435 | known affected: 5 recommended: 8 | 2026-07-15T05:24:31+00:00 | Vulnerability · Source |
| CVE-2026-28493 | suse_vex | SUSE CVE CVE-2026-28493 | known not affected: 106 recommended: 248 | 2026-07-15T05:24:30+00:00 | Vulnerability · Source |
| CVE-2026-28494 | suse_vex | SUSE CVE CVE-2026-28494 | known affected: 74 known not affected: 16 recommended: 264 | 2026-07-15T05:24:29+00:00 | Vulnerability · Source |
| CVE-2026-28684 | suse_vex | SUSE CVE CVE-2026-28684 | known affected: 29 recommended: 9 | 2026-07-15T05:24:27+00:00 | Vulnerability · Source |
| CVE-2026-28532 | suse_vex | SUSE CVE CVE-2026-28532 | known affected: 43 recommended: 245 | 2026-07-15T05:24:27+00:00 | Vulnerability · Source |
| CVE-2026-28686 | suse_vex | SUSE CVE CVE-2026-28686 | known affected: 74 known not affected: 16 recommended: 264 | 2026-07-15T05:24:26+00:00 | Vulnerability · Source |
| CVE-2026-28687 | suse_vex | SUSE CVE CVE-2026-28687 | known affected: 74 known not affected: 16 recommended: 264 | 2026-07-15T05:24:24+00:00 | Vulnerability · Source |
| CVE-2026-28688 | suse_vex | SUSE CVE CVE-2026-28688 | known affected: 74 known not affected: 16 recommended: 264 | 2026-07-15T05:24:23+00:00 | Vulnerability · Source |
| CVE-2026-28689 | suse_vex | SUSE CVE CVE-2026-28689 | known affected: 74 known not affected: 16 recommended: 264 | 2026-07-15T05:24:22+00:00 | Vulnerability · Source |
| CVE-2026-28690 | suse_vex | SUSE CVE CVE-2026-28690 | known affected: 74 recommended: 288 | 2026-07-15T05:24:21+00:00 | Vulnerability · Source |
| CVE-2026-28692 | suse_vex | SUSE CVE CVE-2026-28692 | known affected: 74 known not affected: 16 recommended: 264 | 2026-07-15T05:24:19+00:00 | Vulnerability · Source |
| CVE-2026-28753 | suse_vex | SUSE CVE CVE-2026-28753 | known affected: 406 recommended: 44 | 2026-07-15T05:24:17+00:00 | Vulnerability · Source |
| CVE-2026-28755 | suse_vex | SUSE CVE CVE-2026-28755 | known affected: 394 known not affected: 45 recommended: 8 | 2026-07-15T05:24:16+00:00 | Vulnerability · Source |
| CVE-2026-28883 | suse_vex | SUSE CVE CVE-2026-28883 | known affected: 70 recommended: 469 | 2026-07-15T05:24:06+00:00 | Vulnerability · Source |
| CVE-2026-28901 | suse_vex | SUSE CVE CVE-2026-28901 | known affected: 70 recommended: 469 | 2026-07-15T05:24:05+00:00 | Vulnerability · Source |
| CVE-2026-28902 | suse_vex | SUSE CVE CVE-2026-28902 | known affected: 70 recommended: 469 | 2026-07-15T05:24:04+00:00 | Vulnerability · Source |
| CVE-2026-28903 | suse_vex | SUSE CVE CVE-2026-28903 | known affected: 70 recommended: 469 | 2026-07-15T05:24:03+00:00 | Vulnerability · Source |
| CVE-2026-28904 | suse_vex | SUSE CVE CVE-2026-28904 | known affected: 70 recommended: 469 | 2026-07-15T05:24:02+00:00 | Vulnerability · Source |
| CVE-2026-28905 | suse_vex | SUSE CVE CVE-2026-28905 | known affected: 70 recommended: 469 | 2026-07-15T05:24:00+00:00 | Vulnerability · Source |
| CVE-2026-28907 | suse_vex | SUSE CVE CVE-2026-28907 | known affected: 70 recommended: 469 | 2026-07-15T05:23:59+00:00 | Vulnerability · Source |
| CVE-2026-28942 | suse_vex | SUSE CVE CVE-2026-28942 | known affected: 70 recommended: 469 | 2026-07-15T05:23:58+00:00 | Vulnerability · Source |
| CVE-2026-28946 | suse_vex | SUSE CVE CVE-2026-28946 | known affected: 70 recommended: 469 | 2026-07-15T05:23:57+00:00 | Vulnerability · Source |
| CVE-2026-28953 | suse_vex | SUSE CVE CVE-2026-28953 | known affected: 70 recommended: 469 | 2026-07-15T05:23:55+00:00 | Vulnerability · Source |
| CVE-2026-28955 | suse_vex | SUSE CVE CVE-2026-28955 | known affected: 70 recommended: 469 | 2026-07-15T05:23:54+00:00 | Vulnerability · Source |
| CVE-2026-29076 | suse_vex | SUSE CVE CVE-2026-29076 | recommended: 8 | 2026-07-15T05:23:51+00:00 | Vulnerability · Source |
| CVE-2026-29169 | suse_vex | SUSE CVE CVE-2026-29169 | known affected: 442 recommended: 178 | 2026-07-15T05:23:44+00:00 | Vulnerability · Source |
| CVE-2026-30883 | suse_vex | SUSE CVE CVE-2026-30883 | known affected: 74 recommended: 296 | 2026-07-15T05:23:38+00:00 | Vulnerability · Source |
| CVE-2026-30929 | suse_vex | SUSE CVE CVE-2026-30929 | known affected: 18 known not affected: 88 recommended: 248 | 2026-07-15T05:23:35+00:00 | Vulnerability · Source |
| CVE-2026-30931 | suse_vex | SUSE CVE CVE-2026-30931 | known not affected: 237 recommended: 117 | 2026-07-15T05:23:34+00:00 | Vulnerability · Source |
| CVE-2026-30936 | suse_vex | SUSE CVE CVE-2026-30936 | known affected: 54 known not affected: 52 recommended: 248 | 2026-07-15T05:23:33+00:00 | Vulnerability · Source |
| CVE-2026-30935 | suse_vex | SUSE CVE CVE-2026-30935 | known not affected: 179 recommended: 160 | 2026-07-15T05:23:33+00:00 | Vulnerability · Source |
| CVE-2026-30937 | suse_vex | SUSE CVE CVE-2026-30937 | known affected: 56 known not affected: 34 recommended: 264 | 2026-07-15T05:23:32+00:00 | Vulnerability · Source |
| CVE-2026-30997 | suse_vex | SUSE CVE CVE-2026-30997 | known not affected: 336 recommended: 184 | 2026-07-15T05:23:31+00:00 | Vulnerability · Source |
| CVE-2026-31391 | suse_vex | SUSE CVE CVE-2026-31391 | known affected: 244 known not affected: 65 | 2026-07-15T05:23:28+00:00 | Vulnerability · Source |