VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
287124 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-53164 | suse_vex | SUSE CVE CVE-2026-53164 | known not affected: 295 | 2026-08-03T23:35:43+00:00 | Vulnerability · Source |
| CVE-2026-53175 | suse_vex | SUSE CVE CVE-2026-53175 | known affected: 84 known not affected: 211 | 2026-08-03T23:35:41+00:00 | Vulnerability · Source |
| CVE-2026-53177 | suse_vex | SUSE CVE CVE-2026-53177 | known not affected: 293 | 2026-08-03T23:35:40+00:00 | Vulnerability · Source |
| CVE-2026-53184 | suse_vex | SUSE CVE CVE-2026-53184 | known affected: 114 known not affected: 181 | 2026-08-03T23:35:37+00:00 | Vulnerability · Source |
| CVE-2026-53185 | suse_vex | SUSE CVE CVE-2026-53185 | known affected: 275 known not affected: 20 | 2026-08-03T23:35:36+00:00 | Vulnerability · Source |
| CVE-2026-53187 | suse_vex | SUSE CVE CVE-2026-53187 | known not affected: 293 | 2026-08-03T23:35:34+00:00 | Vulnerability · Source |
| CVE-2026-53188 | suse_vex | SUSE CVE CVE-2026-53188 | known not affected: 293 | 2026-08-03T23:35:33+00:00 | Vulnerability · Source |
| CVE-2026-53191 | suse_vex | SUSE CVE CVE-2026-53191 | known affected: 68 known not affected: 215 | 2026-08-03T23:35:31+00:00 | Vulnerability · Source |
| CVE-2026-53193 | suse_vex | SUSE CVE CVE-2026-53193 | known not affected: 293 | 2026-08-03T23:35:29+00:00 | Vulnerability · Source |
| CVE-2026-53196 | suse_vex | SUSE CVE CVE-2026-53196 | known affected: 559 known not affected: 17 recommended: 165 | 2026-08-03T23:35:27+00:00 | Vulnerability · Source |
| CVE-2026-53199 | suse_vex | SUSE CVE CVE-2026-53199 | known affected: 278 known not affected: 17 | 2026-08-03T23:35:26+00:00 | Vulnerability · Source |
| CVE-2026-53205 | suse_vex | SUSE CVE CVE-2026-53205 | known not affected: 293 | 2026-08-03T23:35:24+00:00 | Vulnerability · Source |
| CVE-2026-53212 | suse_vex | SUSE CVE CVE-2026-53212 | known affected: 228 known not affected: 67 | 2026-08-03T23:35:22+00:00 | Vulnerability · Source |
| CVE-2026-53214 | suse_vex | SUSE CVE CVE-2026-53214 | known affected: 17 known not affected: 278 | 2026-08-03T23:35:20+00:00 | Vulnerability · Source |
| CVE-2026-53221 | suse_vex | SUSE CVE CVE-2026-53221 | known affected: 291 known not affected: 4 | 2026-08-03T23:35:17+00:00 | Vulnerability · Source |
| CVE-2026-53230 | suse_vex | SUSE CVE CVE-2026-53230 | known affected: 291 known not affected: 4 | 2026-08-03T23:35:14+00:00 | Vulnerability · Source |
| CVE-2026-53233 | suse_vex | SUSE CVE CVE-2026-53233 | known affected: 17 known not affected: 278 | 2026-08-03T23:35:13+00:00 | Vulnerability · Source |
| CVE-2026-53235 | suse_vex | SUSE CVE CVE-2026-53235 | known affected: 17 known not affected: 278 | 2026-08-03T23:35:12+00:00 | Vulnerability · Source |
| CVE-2026-53236 | suse_vex | SUSE CVE CVE-2026-53236 | known affected: 295 | 2026-08-03T23:35:10+00:00 | Vulnerability · Source |
| CVE-2026-53247 | suse_vex | SUSE CVE CVE-2026-53247 | known affected: 114 known not affected: 181 | 2026-08-03T23:35:07+00:00 | Vulnerability · Source |
| CVE-2026-53250 | suse_vex | SUSE CVE CVE-2026-53250 | known affected: 114 known not affected: 181 | 2026-08-03T23:35:05+00:00 | Vulnerability · Source |
| CVE-2026-53251 | suse_vex | SUSE CVE CVE-2026-53251 | known not affected: 293 | 2026-08-03T23:35:03+00:00 | Vulnerability · Source |
| CVE-2026-53264 | suse_vex | SUSE CVE CVE-2026-53264 | known affected: 275 known not affected: 20 | 2026-08-03T23:34:59+00:00 | Vulnerability · Source |
| CVE-2026-53275 | suse_vex | SUSE CVE CVE-2026-53275 | known affected: 295 | 2026-08-03T23:34:56+00:00 | Vulnerability · Source |
| CVE-2026-53277 | suse_vex | SUSE CVE CVE-2026-53277 | known not affected: 293 | 2026-08-03T23:34:55+00:00 | Vulnerability · Source |
| CVE-2026-53278 | suse_vex | SUSE CVE CVE-2026-53278 | known not affected: 295 | 2026-08-03T23:34:53+00:00 | Vulnerability · Source |
| CVE-2026-53281 | suse_vex | SUSE CVE CVE-2026-53281 | first fixed: 2 known affected: 441 known not affected: 181 recommended: 348 | 2026-08-03T23:34:51+00:00 | Vulnerability · Source |
| CVE-2026-53289 | suse_vex | SUSE CVE CVE-2026-53289 | known affected: 216 known not affected: 79 | 2026-08-03T23:34:49+00:00 | Vulnerability · Source |
| CVE-2026-53291 | suse_vex | SUSE CVE CVE-2026-53291 | known affected: 162 known not affected: 133 | 2026-08-03T23:34:48+00:00 | Vulnerability · Source |
| CVE-2026-53297 | suse_vex | SUSE CVE CVE-2026-53297 | known affected: 177 known not affected: 118 | 2026-08-03T23:34:46+00:00 | Vulnerability · Source |
| CVE-2026-53310 | suse_vex | SUSE CVE CVE-2026-53310 | known not affected: 293 | 2026-08-03T23:34:44+00:00 | Vulnerability · Source |
| CVE-2026-53314 | suse_vex | SUSE CVE CVE-2026-53314 | known affected: 228 known not affected: 67 | 2026-08-03T23:34:42+00:00 | Vulnerability · Source |
| CVE-2026-53317 | suse_vex | SUSE CVE CVE-2026-53317 | known affected: 185 known not affected: 110 | 2026-08-03T23:34:41+00:00 | Vulnerability · Source |
| CVE-2026-53318 | suse_vex | SUSE CVE CVE-2026-53318 | known not affected: 293 | 2026-08-03T23:34:39+00:00 | Vulnerability · Source |
| CVE-2026-53324 | suse_vex | SUSE CVE CVE-2026-53324 | known affected: 88 known not affected: 205 | 2026-08-03T23:34:38+00:00 | Vulnerability · Source |
| CVE-2026-53331 | suse_vex | SUSE CVE CVE-2026-53331 | known affected: 185 known not affected: 96 | 2026-08-03T23:34:35+00:00 | Vulnerability · Source |
| CVE-2026-53345 | suse_vex | SUSE CVE CVE-2026-53345 | known affected: 97 known not affected: 184 | 2026-08-03T23:34:33+00:00 | Vulnerability · Source |
| CVE-2026-53348 | suse_vex | SUSE CVE CVE-2026-53348 | known not affected: 279 | 2026-08-03T23:34:31+00:00 | Vulnerability · Source |
| CVE-2026-53381 | suse_vex | SUSE CVE CVE-2026-53381 | known affected: 251 known not affected: 33 recommended: 4 | 2026-08-03T23:34:23+00:00 | Vulnerability · Source |
| CVE-2026-53667 | suse_vex | SUSE CVE CVE-2026-53667 | known affected: 9 known not affected: 11 | 2026-08-03T23:34:09+00:00 | Vulnerability · Source |
| CVE-2026-53669 | suse_vex | SUSE CVE CVE-2026-53669 | known affected: 15 known not affected: 5 | 2026-08-03T23:34:08+00:00 | Vulnerability · Source |
| CVE-2026-54603 | suse_vex | SUSE CVE CVE-2026-54603 | No product status | 2026-08-03T23:34:03+00:00 | Vulnerability · Source |
| CVE-2026-54605 | suse_vex | SUSE CVE CVE-2026-54605 | No product status | 2026-08-03T23:34:01+00:00 | Vulnerability · Source |
| CVE-2026-54891 | suse_vex | SUSE CVE CVE-2026-54891 | known affected: 58 | 2026-08-03T23:34:00+00:00 | Vulnerability · Source |
| CVE-2026-55685 | suse_vex | SUSE CVE CVE-2026-55685 | known affected: 15 | 2026-08-03T23:33:57+00:00 | Vulnerability · Source |
| CVE-2026-58010 | suse_vex | SUSE CVE CVE-2026-58010 | known affected: 518 recommended: 358 | 2026-08-03T23:33:45+00:00 | Vulnerability · Source |
| CVE-2026-58011 | suse_vex | SUSE CVE CVE-2026-58011 | known affected: 472 recommended: 358 | 2026-08-03T23:33:44+00:00 | Vulnerability · Source |
| CVE-2026-58012 | suse_vex | SUSE CVE CVE-2026-58012 | known affected: 518 recommended: 358 | 2026-08-03T23:33:42+00:00 | Vulnerability · Source |
| CVE-2026-58013 | suse_vex | SUSE CVE CVE-2026-58013 | known affected: 518 recommended: 358 | 2026-08-03T23:33:41+00:00 | Vulnerability · Source |
| CVE-2026-58014 | suse_vex | SUSE CVE CVE-2026-58014 | known affected: 518 recommended: 358 | 2026-08-03T23:33:39+00:00 | Vulnerability · Source |