VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
287135 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-46226 | suse_vex | SUSE CVE CVE-2026-46226 | known affected: 274 known not affected: 21 recommended: 4 | 2026-08-03T23:39:29+00:00 | Vulnerability · Source |
| CVE-2026-46234 | suse_vex | SUSE CVE CVE-2026-46234 | known affected: 202 known not affected: 93 recommended: 4 | 2026-08-03T23:39:24+00:00 | Vulnerability · Source |
| CVE-2026-46241 | suse_vex | SUSE CVE CVE-2026-46241 | known affected: 278 known not affected: 17 recommended: 4 | 2026-08-03T23:39:19+00:00 | Vulnerability · Source |
| CVE-2026-46245 | suse_vex | SUSE CVE CVE-2026-46245 | known affected: 275 known not affected: 20 | 2026-08-03T23:39:16+00:00 | Vulnerability · Source |
| CVE-2026-46246 | suse_vex | SUSE CVE CVE-2026-46246 | known not affected: 293 | 2026-08-03T23:39:13+00:00 | Vulnerability · Source |
| CVE-2026-46248 | suse_vex | SUSE CVE CVE-2026-46248 | known not affected: 293 | 2026-08-03T23:39:10+00:00 | Vulnerability · Source |
| CVE-2026-46255 | suse_vex | SUSE CVE CVE-2026-46255 | known not affected: 293 | 2026-08-03T23:39:06+00:00 | Vulnerability · Source |
| CVE-2026-46262 | suse_vex | SUSE CVE CVE-2026-46262 | known not affected: 293 | 2026-08-03T23:39:02+00:00 | Vulnerability · Source |
| CVE-2026-46265 | suse_vex | SUSE CVE CVE-2026-46265 | known affected: 216 known not affected: 79 | 2026-08-03T23:39:00+00:00 | Vulnerability · Source |
| CVE-2026-46268 | suse_vex | SUSE CVE CVE-2026-46268 | known not affected: 293 | 2026-08-03T23:38:57+00:00 | Vulnerability · Source |
| CVE-2026-46271 | suse_vex | SUSE CVE CVE-2026-46271 | known not affected: 293 | 2026-08-03T23:38:54+00:00 | Vulnerability · Source |
| CVE-2026-46282 | suse_vex | SUSE CVE CVE-2026-46282 | known not affected: 293 recommended: 4 | 2026-08-03T23:38:50+00:00 | Vulnerability · Source |
| CVE-2026-46283 | suse_vex | SUSE CVE CVE-2026-46283 | known affected: 17 known not affected: 278 recommended: 4 | 2026-08-03T23:38:47+00:00 | Vulnerability · Source |
| CVE-2026-46287 | suse_vex | SUSE CVE CVE-2026-46287 | known affected: 17 known not affected: 278 recommended: 4 | 2026-08-03T23:38:44+00:00 | Vulnerability · Source |
| CVE-2026-46292 | suse_vex | SUSE CVE CVE-2026-46292 | known affected: 228 known not affected: 67 recommended: 4 | 2026-08-03T23:38:40+00:00 | Vulnerability · Source |
| CVE-2026-46296 | suse_vex | SUSE CVE CVE-2026-46296 | known not affected: 293 recommended: 4 | 2026-08-03T23:38:37+00:00 | Vulnerability · Source |
| CVE-2026-46298 | suse_vex | SUSE CVE CVE-2026-46298 | known not affected: 293 recommended: 4 | 2026-08-03T23:38:35+00:00 | Vulnerability · Source |
| CVE-2026-46301 | suse_vex | SUSE CVE CVE-2026-46301 | known affected: 274 known not affected: 21 recommended: 4 | 2026-08-03T23:38:32+00:00 | Vulnerability · Source |
| CVE-2026-46303 | suse_vex | SUSE CVE CVE-2026-46303 | known affected: 295 recommended: 46 | 2026-08-03T23:38:30+00:00 | Vulnerability · Source |
| CVE-2026-46306 | suse_vex | SUSE CVE CVE-2026-46306 | known affected: 162 known not affected: 133 recommended: 4 | 2026-08-03T23:38:28+00:00 | Vulnerability · Source |
| CVE-2026-46325 | suse_vex | SUSE CVE CVE-2026-46325 | known affected: 97 known not affected: 181 | 2026-08-03T23:38:20+00:00 | Vulnerability · Source |
| CVE-2026-46326 | suse_vex | SUSE CVE CVE-2026-46326 | known not affected: 293 | 2026-08-03T23:38:18+00:00 | Vulnerability · Source |
| CVE-2026-46329 | suse_vex | SUSE CVE CVE-2026-46329 | known affected: 17 known not affected: 278 | 2026-08-03T23:38:15+00:00 | Vulnerability · Source |
| CVE-2026-48163 | suse_vex | SUSE CVE CVE-2026-48163 | known affected: 505 known not affected: 23 recommended: 213 | 2026-08-03T23:37:52+00:00 | Vulnerability · Source |
| CVE-2026-48165 | suse_vex | SUSE CVE CVE-2026-48165 | known affected: 505 known not affected: 23 recommended: 213 | 2026-08-03T23:37:49+00:00 | Vulnerability · Source |
| CVE-2026-49261 | suse_vex | SUSE CVE CVE-2026-49261 | known affected: 505 known not affected: 23 recommended: 213 | 2026-08-03T23:37:47+00:00 | Vulnerability · Source |
| CVE-2026-50031 | suse_vex | SUSE CVE CVE-2026-50031 | known affected: 186 recommended: 77 | 2026-08-03T23:37:43+00:00 | Vulnerability · Source |
| CVE-2026-52720 | suse_vex | SUSE CVE CVE-2026-52720 | known affected: 152 recommended: 826 | 2026-08-03T23:37:39+00:00 | Vulnerability · Source |
| CVE-2026-52722 | suse_vex | SUSE CVE CVE-2026-52722 | known affected: 152 recommended: 747 | 2026-08-03T23:37:37+00:00 | Vulnerability · Source |
| CVE-2026-52921 | suse_vex | SUSE CVE CVE-2026-52921 | known affected: 114 known not affected: 181 | 2026-08-03T23:37:32+00:00 | Vulnerability · Source |
| CVE-2026-52925 | suse_vex | SUSE CVE CVE-2026-52925 | known affected: 289 known not affected: 6 | 2026-08-03T23:37:28+00:00 | Vulnerability · Source |
| CVE-2026-52927 | suse_vex | SUSE CVE CVE-2026-52927 | known affected: 216 known not affected: 79 | 2026-08-03T23:37:27+00:00 | Vulnerability · Source |
| CVE-2026-52930 | suse_vex | SUSE CVE CVE-2026-52930 | known affected: 291 known not affected: 4 | 2026-08-03T23:37:25+00:00 | Vulnerability · Source |
| CVE-2026-52934 | suse_vex | SUSE CVE CVE-2026-52934 | known affected: 291 known not affected: 4 | 2026-08-03T23:37:23+00:00 | Vulnerability · Source |
| CVE-2026-52937 | suse_vex | SUSE CVE CVE-2026-52937 | known affected: 202 known not affected: 93 | 2026-08-03T23:37:21+00:00 | Vulnerability · Source |
| CVE-2026-52941 | suse_vex | SUSE CVE CVE-2026-52941 | known affected: 202 known not affected: 93 | 2026-08-03T23:37:20+00:00 | Vulnerability · Source |
| CVE-2026-52947 | suse_vex | SUSE CVE CVE-2026-52947 | known affected: 289 known not affected: 6 | 2026-08-03T23:37:17+00:00 | Vulnerability · Source |
| CVE-2026-52959 | suse_vex | SUSE CVE CVE-2026-52959 | known not affected: 293 | 2026-08-03T23:37:14+00:00 | Vulnerability · Source |
| CVE-2026-52965 | suse_vex | SUSE CVE CVE-2026-52965 | known affected: 114 known not affected: 181 | 2026-08-03T23:37:12+00:00 | Vulnerability · Source |
| CVE-2026-52970 | suse_vex | SUSE CVE CVE-2026-52970 | known affected: 228 known not affected: 67 | 2026-08-03T23:37:10+00:00 | Vulnerability · Source |
| CVE-2026-52974 | suse_vex | SUSE CVE CVE-2026-52974 | known affected: 114 known not affected: 181 | 2026-08-03T23:37:08+00:00 | Vulnerability · Source |
| CVE-2026-52984 | suse_vex | SUSE CVE CVE-2026-52984 | known affected: 275 known not affected: 20 | 2026-08-03T23:37:06+00:00 | Vulnerability · Source |
| CVE-2026-52988 | suse_vex | SUSE CVE CVE-2026-52988 | known affected: 17 known not affected: 278 | 2026-08-03T23:37:03+00:00 | Vulnerability · Source |
| CVE-2026-52999 | suse_vex | SUSE CVE CVE-2026-52999 | known affected: 228 known not affected: 67 | 2026-08-03T23:36:59+00:00 | Vulnerability · Source |
| CVE-2026-53000 | suse_vex | SUSE CVE CVE-2026-53000 | known affected: 202 known not affected: 93 | 2026-08-03T23:36:57+00:00 | Vulnerability · Source |
| CVE-2026-53006 | suse_vex | SUSE CVE CVE-2026-53006 | known affected: 291 known not affected: 4 recommended: 103 | 2026-08-03T23:36:55+00:00 | Vulnerability · Source |
| CVE-2026-53007 | suse_vex | SUSE CVE CVE-2026-53007 | known not affected: 293 | 2026-08-03T23:36:53+00:00 | Vulnerability · Source |
| CVE-2026-53008 | suse_vex | SUSE CVE CVE-2026-53008 | known not affected: 293 | 2026-08-03T23:36:52+00:00 | Vulnerability · Source |
| CVE-2026-53009 | suse_vex | SUSE CVE CVE-2026-53009 | known affected: 614 known not affected: 20 recommended: 140 | 2026-08-03T23:36:50+00:00 | Vulnerability · Source |
| CVE-2026-53011 | suse_vex | SUSE CVE CVE-2026-53011 | known affected: 228 known not affected: 67 | 2026-08-03T23:36:49+00:00 | Vulnerability · Source |