VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292260 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-29774 | suse_vex | SUSE CVE CVE-2026-29774 | recommended: 142 | 2026-07-15T05:23:41+00:00 | Vulnerability · Source |
| CVE-2026-29775 | suse_vex | SUSE CVE CVE-2026-29775 | recommended: 158 | 2026-07-15T05:23:40+00:00 | Vulnerability · Source |
| CVE-2026-29776 | suse_vex | SUSE CVE CVE-2026-29776 | recommended: 142 | 2026-07-15T05:23:39+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 |
| CVE-2026-31394 | suse_vex | SUSE CVE CVE-2026-31394 | first fixed: 2 known not affected: 252 recommended: 244 | 2026-07-15T05:23:25+00:00 | Vulnerability · Source |
| CVE-2026-31395 | suse_vex | SUSE CVE CVE-2026-31395 | first fixed: 2 known affected: 11 known not affected: 243 recommended: 244 | 2026-07-15T05:23:24+00:00 | Vulnerability · Source |
| CVE-2026-31438 | suse_vex | SUSE CVE CVE-2026-31438 | known affected: 17 known not affected: 281 | 2026-07-15T05:22:47+00:00 | Vulnerability · Source |
| CVE-2026-31456 | suse_vex | SUSE CVE CVE-2026-31456 | first fixed: 2 known affected: 411 known not affected: 298 recommended: 145 | 2026-07-15T05:22:34+00:00 | Vulnerability · Source |
| CVE-2026-31461 | suse_vex | SUSE CVE CVE-2026-31461 | known affected: 167 known not affected: 147 | 2026-07-15T05:22:33+00:00 | Vulnerability · Source |
| CVE-2026-31506 | suse_vex | SUSE CVE CVE-2026-31506 | known affected: 18 known not affected: 298 | 2026-07-15T05:22:06+00:00 | Vulnerability · Source |
| CVE-2026-31521 | suse_vex | SUSE CVE CVE-2026-31521 | first fixed: 2 known affected: 618 recommended: 145 | 2026-07-15T05:21:57+00:00 | Vulnerability · Source |
| CVE-2026-31526 | suse_vex | SUSE CVE CVE-2026-31526 | first fixed: 2 known affected: 17 known not affected: 298 recommended: 145 | 2026-07-15T05:21:54+00:00 | Vulnerability · Source |
| CVE-2026-31530 | suse_vex | SUSE CVE CVE-2026-31530 | known affected: 131 known not affected: 184 | 2026-07-15T05:21:52+00:00 | Vulnerability · Source |
| CVE-2026-31547 | suse_vex | SUSE CVE CVE-2026-31547 | first fixed: 2 known affected: 411 known not affected: 243 recommended: 244 | 2026-07-15T05:21:48+00:00 | Vulnerability · Source |
| CVE-2026-31556 | suse_vex | SUSE CVE CVE-2026-31556 | first fixed: 2 known affected: 394 known not affected: 298 recommended: 145 | 2026-07-15T05:21:43+00:00 | Vulnerability · Source |
| CVE-2026-31562 | suse_vex | SUSE CVE CVE-2026-31562 | first fixed: 2 known affected: 394 known not affected: 298 recommended: 145 | 2026-07-15T05:21:41+00:00 | Vulnerability · Source |
| CVE-2026-31571 | suse_vex | SUSE CVE CVE-2026-31571 | known not affected: 317 | 2026-07-15T05:21:35+00:00 | Vulnerability · Source |
| CVE-2026-31575 | suse_vex | SUSE CVE CVE-2026-31575 | first fixed: 2 known affected: 411 known not affected: 298 recommended: 149 | 2026-07-15T05:21:34+00:00 | Vulnerability · Source |