VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
287304 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2026-53012 | suse_vex | SUSE CVE CVE-2026-53012 | known affected: 228 known not affected: 67 | 2026-08-03T23:36:47+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-53016 | suse_vex | SUSE CVE CVE-2026-53016 | known affected: 481 known not affected: 21 recommended: 409 | 2026-08-03T23:36:44+00:00 | Vulnerability · Source |
| CVE-2026-53032 | suse_vex | SUSE CVE CVE-2026-53032 | known affected: 114 known not affected: 181 | 2026-08-03T23:36:41+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-53062 | suse_vex | SUSE CVE CVE-2026-53062 | known affected: 289 known not affected: 6 | 2026-08-03T23:36:31+00:00 | Vulnerability · Source |
| CVE-2026-53063 | suse_vex | SUSE CVE CVE-2026-53063 | known affected: 289 known not affected: 6 | 2026-08-03T23:36:30+00:00 | Vulnerability · Source |
| CVE-2026-53064 | suse_vex | SUSE CVE CVE-2026-53064 | known affected: 289 known not affected: 6 | 2026-08-03T23:36:28+00:00 | Vulnerability · Source |
| CVE-2026-53069 | suse_vex | SUSE CVE CVE-2026-53069 | known affected: 162 known not affected: 133 | 2026-08-03T23:36:26+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-53083 | suse_vex | SUSE CVE CVE-2026-53083 | known affected: 202 known not affected: 93 | 2026-08-03T23:36:19+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-53106 | suse_vex | SUSE CVE CVE-2026-53106 | known affected: 202 known not affected: 93 | 2026-08-03T23:36:02+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-53123 | suse_vex | SUSE CVE CVE-2026-53123 | known affected: 114 known not affected: 181 | 2026-08-03T23:35:57+00:00 | Vulnerability · Source |
| CVE-2026-53132 | suse_vex | SUSE CVE CVE-2026-53132 | known affected: 114 known not affected: 181 | 2026-08-03T23:35:55+00:00 | Vulnerability · Source |
| CVE-2026-53134 | suse_vex | SUSE CVE CVE-2026-53134 | known affected: 289 known not affected: 6 | 2026-08-03T23:35:53+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-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 |