VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
288586 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-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-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-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-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-53014 | suse_vex | SUSE CVE CVE-2026-53014 | known affected: 17 known not affected: 278 | 2026-08-03T23:36:45+00:00 | Vulnerability · Source |
| CVE-2026-53038 | suse_vex | SUSE CVE CVE-2026-53038 | known affected: 17 known not affected: 278 | 2026-08-03T23:36:39+00:00 | Vulnerability · Source |
| CVE-2026-53044 | suse_vex | SUSE CVE CVE-2026-53044 | known not affected: 293 | 2026-08-03T23:36:37+00:00 | Vulnerability · Source |
| CVE-2026-53051 | suse_vex | SUSE CVE CVE-2026-53051 | known not affected: 293 | 2026-08-03T23:36:34+00:00 | Vulnerability · Source |
| CVE-2026-53071 | suse_vex | SUSE CVE CVE-2026-53071 | known affected: 408 known not affected: 108 recommended: 415 | 2026-08-03T23:36:24+00:00 | Vulnerability · Source |
| CVE-2026-53085 | suse_vex | SUSE CVE CVE-2026-53085 | known affected: 162 known not affected: 133 | 2026-08-03T23:36:18+00:00 | Vulnerability · Source |
| CVE-2026-53092 | suse_vex | SUSE CVE CVE-2026-53092 | known affected: 17 known not affected: 278 | 2026-08-03T23:36:16+00:00 | Vulnerability · Source |
| CVE-2026-53097 | suse_vex | SUSE CVE CVE-2026-53097 | known not affected: 293 | 2026-08-03T23:36:12+00:00 | Vulnerability · Source |
| CVE-2026-53099 | suse_vex | SUSE CVE CVE-2026-53099 | known not affected: 293 | 2026-08-03T23:36:11+00:00 | Vulnerability · Source |
| CVE-2026-53100 | suse_vex | SUSE CVE CVE-2026-53100 | known not affected: 293 | 2026-08-03T23:36:09+00:00 | Vulnerability · Source |
| CVE-2026-53101 | suse_vex | SUSE CVE CVE-2026-53101 | known affected: 114 known not affected: 181 | 2026-08-03T23:36:08+00:00 | Vulnerability · Source |
| CVE-2026-53102 | suse_vex | SUSE CVE CVE-2026-53102 | known affected: 78 known not affected: 148 | 2026-08-03T23:36:06+00:00 | Vulnerability · Source |
| CVE-2026-53104 | suse_vex | SUSE CVE CVE-2026-53104 | known affected: 17 known not affected: 278 | 2026-08-03T23:36:05+00:00 | Vulnerability · Source |
| CVE-2026-53105 | suse_vex | SUSE CVE CVE-2026-53105 | known not affected: 293 | 2026-08-03T23:36:03+00:00 | Vulnerability · Source |
| CVE-2026-53113 | suse_vex | SUSE CVE CVE-2026-53113 | known affected: 97 known not affected: 198 | 2026-08-03T23:36:00+00:00 | Vulnerability · Source |
| CVE-2026-53121 | suse_vex | SUSE CVE CVE-2026-53121 | known affected: 17 known not affected: 278 | 2026-08-03T23:35:58+00:00 | Vulnerability · Source |
| CVE-2026-53152 | suse_vex | SUSE CVE CVE-2026-53152 | known not affected: 293 | 2026-08-03T23:35:47+00:00 | Vulnerability · Source |
| CVE-2026-53157 | suse_vex | SUSE CVE CVE-2026-53157 | known affected: 295 | 2026-08-03T23:35:46+00:00 | Vulnerability · Source |
| 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-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-53193 | suse_vex | SUSE CVE CVE-2026-53193 | known not affected: 293 | 2026-08-03T23:35:29+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-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-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-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-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-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-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 |