VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291709 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-46299 | suse_vex | SUSE CVE CVE-2026-46299 | known affected: 259 known not affected: 4 recommended: 41 | 2026-08-06T01:17:05+00:00 | Vulnerability · Source |
| CVE-2026-46304 | suse_vex | SUSE CVE CVE-2026-46304 | known affected: 291 known not affected: 4 recommended: 4 | 2026-08-06T01:17:04+00:00 | Vulnerability · Source |
| CVE-2026-46311 | suse_vex | SUSE CVE CVE-2026-46311 | known not affected: 293 recommended: 4 | 2026-08-06T01:17:02+00:00 | Vulnerability · Source |
| CVE-2026-46328 | suse_vex | SUSE CVE CVE-2026-46328 | first fixed: 2 known affected: 555 known not affected: 35 recommended: 288 | 2026-08-06T01:16:55+00:00 | Vulnerability · Source |
| CVE-2026-46332 | suse_vex | SUSE CVE CVE-2026-46332 | known not affected: 293 recommended: 4 | 2026-08-06T01:16:53+00:00 | Vulnerability · Source |
| CVE-2026-47781 | suse_vex | SUSE CVE CVE-2026-47781 | recommended: 4 | 2026-08-06T01:16:35+00:00 | Vulnerability · Source |
| CVE-2026-48154 | suse_vex | SUSE CVE CVE-2026-48154 | No product status | 2026-08-06T01:16:33+00:00 | Vulnerability · Source |
| CVE-2026-48864 | suse_vex | SUSE CVE CVE-2026-48864 | known affected: 243 recommended: 10 | 2026-08-06T01:16:31+00:00 | Vulnerability · Source |
| CVE-2026-50151 | suse_vex | SUSE CVE CVE-2026-50151 | known affected: 71 known not affected: 12 recommended: 11 | 2026-08-06T01:16:24+00:00 | Vulnerability · Source |
| CVE-2026-51400 | suse_vex | SUSE CVE CVE-2026-51400 | known not affected: 177 | 2026-08-06T01:16:11+00:00 | Vulnerability · Source |
| CVE-2026-51401 | suse_vex | SUSE CVE CVE-2026-51401 | known not affected: 177 | 2026-08-06T01:16:10+00:00 | Vulnerability · Source |
| CVE-2026-52906 | suse_vex | SUSE CVE CVE-2026-52906 | known not affected: 293 recommended: 4 | 2026-08-06T01:16:09+00:00 | Vulnerability · Source |
| CVE-2026-52907 | suse_vex | SUSE CVE CVE-2026-52907 | known not affected: 293 recommended: 4 | 2026-08-06T01:16:08+00:00 | Vulnerability · Source |
| CVE-2026-52911 | suse_vex | SUSE CVE CVE-2026-52911 | known not affected: 293 | 2026-08-06T01:16:04+00:00 | Vulnerability · Source |
| CVE-2026-52912 | suse_vex | SUSE CVE CVE-2026-52912 | known affected: 289 known not affected: 6 | 2026-08-06T01:16:03+00:00 | Vulnerability · Source |
| CVE-2026-52917 | suse_vex | SUSE CVE CVE-2026-52917 | known affected: 289 known not affected: 6 | 2026-08-06T01:16:01+00:00 | Vulnerability · Source |
| CVE-2026-52920 | suse_vex | SUSE CVE CVE-2026-52920 | known affected: 295 | 2026-08-06T01:15:59+00:00 | Vulnerability · Source |
| CVE-2026-52929 | suse_vex | SUSE CVE CVE-2026-52929 | known affected: 228 known not affected: 67 | 2026-08-06T01:15:55+00:00 | Vulnerability · Source |
| CVE-2026-52932 | suse_vex | SUSE CVE CVE-2026-52932 | known not affected: 293 | 2026-08-06T01:15:53+00:00 | Vulnerability · Source |
| CVE-2026-52935 | suse_vex | SUSE CVE CVE-2026-52935 | known affected: 216 known not affected: 79 | 2026-08-06T01:15:51+00:00 | Vulnerability · Source |
| CVE-2026-52945 | suse_vex | SUSE CVE CVE-2026-52945 | known not affected: 293 | 2026-08-06T01:15:49+00:00 | Vulnerability · Source |
| CVE-2026-52946 | suse_vex | SUSE CVE CVE-2026-52946 | known affected: 295 recommended: 4 | 2026-08-06T01:15:48+00:00 | Vulnerability · Source |
| CVE-2026-52952 | suse_vex | SUSE CVE CVE-2026-52952 | known not affected: 293 | 2026-08-06T01:15:45+00:00 | Vulnerability · Source |
| CVE-2026-52957 | suse_vex | SUSE CVE CVE-2026-52957 | first fixed: 2 known affected: 590 recommended: 302 | 2026-08-06T01:15:40+00:00 | Vulnerability · Source |
| CVE-2026-52960 | suse_vex | SUSE CVE CVE-2026-52960 | known not affected: 293 | 2026-08-06T01:15:38+00:00 | Vulnerability · Source |
| CVE-2026-52968 | suse_vex | SUSE CVE CVE-2026-52968 | known affected: 162 known not affected: 133 | 2026-08-06T01:15:35+00:00 | Vulnerability · Source |
| CVE-2026-52971 | suse_vex | SUSE CVE CVE-2026-52971 | known not affected: 293 | 2026-08-06T01:15:34+00:00 | Vulnerability · Source |
| CVE-2026-52973 | suse_vex | SUSE CVE CVE-2026-52973 | known not affected: 293 recommended: 83 | 2026-08-06T01:15:32+00:00 | Vulnerability · Source |
| CVE-2026-52975 | suse_vex | SUSE CVE CVE-2026-52975 | first fixed: 2 known affected: 291 known not affected: 4 recommended: 145 | 2026-08-06T01:15:31+00:00 | Vulnerability · Source |
| CVE-2026-52983 | suse_vex | SUSE CVE CVE-2026-52983 | known not affected: 293 | 2026-08-06T01:15:29+00:00 | Vulnerability · Source |
| CVE-2026-52993 | suse_vex | SUSE CVE CVE-2026-52993 | first fixed: 2 known affected: 437 known not affected: 67 recommended: 560 | 2026-08-06T01:15:24+00:00 | Vulnerability · Source |
| CVE-2026-53010 | suse_vex | SUSE CVE CVE-2026-53010 | known affected: 17 known not affected: 278 | 2026-08-06T01:15:21+00:00 | Vulnerability · Source |
| CVE-2026-53020 | suse_vex | SUSE CVE CVE-2026-53020 | known not affected: 293 | 2026-08-06T01:15:19+00:00 | Vulnerability · Source |
| CVE-2026-53024 | suse_vex | SUSE CVE CVE-2026-53024 | known affected: 289 known not affected: 6 | 2026-08-06T01:15:17+00:00 | Vulnerability · Source |
| CVE-2026-53025 | suse_vex | SUSE CVE CVE-2026-53025 | known affected: 289 known not affected: 6 | 2026-08-06T01:15:16+00:00 | Vulnerability · Source |
| CVE-2026-53026 | suse_vex | SUSE CVE CVE-2026-53026 | known not affected: 293 | 2026-08-06T01:15:15+00:00 | Vulnerability · Source |
| CVE-2026-53031 | suse_vex | SUSE CVE CVE-2026-53031 | known affected: 17 known not affected: 278 | 2026-08-06T01:15:14+00:00 | Vulnerability · Source |
| CVE-2026-53033 | suse_vex | SUSE CVE CVE-2026-53033 | known affected: 162 known not affected: 133 | 2026-08-06T01:15:12+00:00 | Vulnerability · Source |
| CVE-2026-53043 | suse_vex | SUSE CVE CVE-2026-53043 | known affected: 295 | 2026-08-06T01:15:10+00:00 | Vulnerability · Source |
| CVE-2026-53054 | suse_vex | SUSE CVE CVE-2026-53054 | known not affected: 293 | 2026-08-06T01:15:05+00:00 | Vulnerability · Source |
| CVE-2026-53055 | suse_vex | SUSE CVE CVE-2026-53055 | known not affected: 293 | 2026-08-06T01:15:04+00:00 | Vulnerability · Source |
| CVE-2026-53057 | suse_vex | SUSE CVE CVE-2026-53057 | known not affected: 293 | 2026-08-06T01:15:03+00:00 | Vulnerability · Source |
| CVE-2026-53076 | suse_vex | SUSE CVE CVE-2026-53076 | known affected: 275 known not affected: 20 | 2026-08-06T01:14:58+00:00 | Vulnerability · Source |
| CVE-2026-53077 | suse_vex | SUSE CVE CVE-2026-53077 | known affected: 291 known not affected: 4 | 2026-08-06T01:14:57+00:00 | Vulnerability · Source |
| CVE-2026-53081 | suse_vex | SUSE CVE CVE-2026-53081 | first fixed: 2 known affected: 162 known not affected: 133 recommended: 145 | 2026-08-06T01:14:55+00:00 | Vulnerability · Source |
| CVE-2026-53087 | suse_vex | SUSE CVE CVE-2026-53087 | known not affected: 293 | 2026-08-06T01:14:53+00:00 | Vulnerability · Source |
| CVE-2026-53091 | suse_vex | SUSE CVE CVE-2026-53091 | known affected: 291 known not affected: 4 | 2026-08-06T01:14:49+00:00 | Vulnerability · Source |
| CVE-2026-53094 | suse_vex | SUSE CVE CVE-2026-53094 | known affected: 289 known not affected: 6 | 2026-08-06T01:14:47+00:00 | Vulnerability · Source |
| CVE-2026-53096 | suse_vex | SUSE CVE CVE-2026-53096 | known affected: 202 known not affected: 93 | 2026-08-06T01:14:46+00:00 | Vulnerability · Source |
| CVE-2026-53110 | suse_vex | SUSE CVE CVE-2026-53110 | known affected: 114 known not affected: 181 | 2026-08-06T01:14:44+00:00 | Vulnerability · Source |