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-45849 | suse_vex | SUSE CVE CVE-2026-45849 | known affected: 17 known not affected: 278 | 2026-08-03T23:42:15+00:00 | Vulnerability · Source |
| CVE-2026-45863 | suse_vex | SUSE CVE CVE-2026-45863 | known not affected: 293 | 2026-08-03T23:42:11+00:00 | Vulnerability · Source |
| CVE-2026-45865 | suse_vex | SUSE CVE CVE-2026-45865 | known affected: 114 known not affected: 181 | 2026-08-03T23:42:10+00:00 | Vulnerability · Source |
| CVE-2026-45866 | suse_vex | SUSE CVE CVE-2026-45866 | known affected: 274 known not affected: 21 recommended: 4 | 2026-08-03T23:42:09+00:00 | Vulnerability · Source |
| CVE-2026-45872 | suse_vex | SUSE CVE CVE-2026-45872 | known affected: 185 known not affected: 110 | 2026-08-03T23:42:06+00:00 | Vulnerability · Source |
| CVE-2026-45874 | suse_vex | SUSE CVE CVE-2026-45874 | known not affected: 293 | 2026-08-03T23:42:03+00:00 | Vulnerability · Source |
| CVE-2026-45895 | suse_vex | SUSE CVE CVE-2026-45895 | known affected: 17 known not affected: 278 | 2026-08-03T23:41:57+00:00 | Vulnerability · Source |
| CVE-2026-45896 | suse_vex | SUSE CVE CVE-2026-45896 | known not affected: 293 | 2026-08-03T23:41:56+00:00 | Vulnerability · Source |
| CVE-2026-45897 | suse_vex | SUSE CVE CVE-2026-45897 | known affected: 17 known not affected: 278 | 2026-08-03T23:41:54+00:00 | Vulnerability · Source |
| CVE-2026-45900 | suse_vex | SUSE CVE CVE-2026-45900 | known affected: 199 known not affected: 96 | 2026-08-03T23:41:53+00:00 | Vulnerability · Source |
| CVE-2026-45901 | suse_vex | SUSE CVE CVE-2026-45901 | first fixed: 2 known affected: 17 known not affected: 278 recommended: 172 | 2026-08-03T23:41:51+00:00 | Vulnerability · Source |
| CVE-2026-45925 | suse_vex | SUSE CVE CVE-2026-45925 | known not affected: 293 | 2026-08-03T23:41:41+00:00 | Vulnerability · Source |
| CVE-2026-45927 | suse_vex | SUSE CVE CVE-2026-45927 | known not affected: 293 | 2026-08-03T23:41:39+00:00 | Vulnerability · Source |
| CVE-2026-45930 | suse_vex | SUSE CVE CVE-2026-45930 | known affected: 114 known not affected: 181 | 2026-08-03T23:41:38+00:00 | Vulnerability · Source |
| CVE-2026-45950 | suse_vex | SUSE CVE CVE-2026-45950 | known not affected: 293 | 2026-08-03T23:41:32+00:00 | Vulnerability · Source |
| CVE-2026-45951 | suse_vex | SUSE CVE CVE-2026-45951 | known not affected: 293 | 2026-08-03T23:41:31+00:00 | Vulnerability · Source |
| CVE-2026-46001 | suse_vex | SUSE CVE CVE-2026-46001 | known not affected: 293 recommended: 4 | 2026-08-03T23:41:21+00:00 | Vulnerability · Source |
| CVE-2026-46034 | suse_vex | SUSE CVE CVE-2026-46034 | known affected: 72 known not affected: 223 recommended: 4 | 2026-08-03T23:41:11+00:00 | Vulnerability · Source |
| CVE-2026-46036 | suse_vex | SUSE CVE CVE-2026-46036 | known affected: 72 known not affected: 223 recommended: 4 | 2026-08-03T23:41:10+00:00 | Vulnerability · Source |
| CVE-2026-46042 | suse_vex | SUSE CVE CVE-2026-46042 | known not affected: 295 recommended: 4 | 2026-08-03T23:41:06+00:00 | Vulnerability · Source |
| CVE-2026-46060 | suse_vex | SUSE CVE CVE-2026-46060 | known not affected: 293 recommended: 4 | 2026-08-03T23:40:59+00:00 | Vulnerability · Source |
| CVE-2026-46073 | suse_vex | SUSE CVE CVE-2026-46073 | known not affected: 293 recommended: 4 | 2026-08-03T23:40:56+00:00 | Vulnerability · Source |
| CVE-2026-46074 | suse_vex | SUSE CVE CVE-2026-46074 | known not affected: 293 recommended: 4 | 2026-08-03T23:40:55+00:00 | Vulnerability · Source |
| CVE-2026-46096 | suse_vex | SUSE CVE CVE-2026-46096 | known not affected: 293 recommended: 4 | 2026-08-03T23:40:45+00:00 | Vulnerability · Source |
| CVE-2026-46113 | suse_vex | SUSE CVE CVE-2026-46113 | first fixed: 24 known affected: 446 known not affected: 15 recommended: 584 | 2026-08-03T23:40:38+00:00 | Vulnerability · Source |
| CVE-2026-46118 | suse_vex | SUSE CVE CVE-2026-46118 | known not affected: 295 recommended: 4 | 2026-08-03T23:40:35+00:00 | Vulnerability · Source |
| CVE-2026-46121 | suse_vex | SUSE CVE CVE-2026-46121 | known affected: 17 known not affected: 278 recommended: 4 | 2026-08-03T23:40:32+00:00 | Vulnerability · Source |
| CVE-2026-46125 | suse_vex | SUSE CVE CVE-2026-46125 | known affected: 424 known not affected: 208 recommended: 205 | 2026-08-03T23:40:29+00:00 | Vulnerability · Source |
| CVE-2026-46127 | suse_vex | SUSE CVE CVE-2026-46127 | known affected: 291 known not affected: 4 recommended: 4 | 2026-08-03T23:40:26+00:00 | Vulnerability · Source |
| CVE-2026-46130 | suse_vex | SUSE CVE CVE-2026-46130 | known affected: 114 known not affected: 181 recommended: 4 | 2026-08-03T23:40:23+00:00 | Vulnerability · Source |
| CVE-2026-46166 | suse_vex | SUSE CVE CVE-2026-46166 | known affected: 394 known not affected: 238 recommended: 185 | 2026-08-03T23:40:03+00:00 | Vulnerability · Source |
| CVE-2026-46182 | suse_vex | SUSE CVE CVE-2026-46182 | known not affected: 293 recommended: 4 | 2026-08-03T23:39:48+00:00 | Vulnerability · Source |
| CVE-2026-46200 | suse_vex | SUSE CVE CVE-2026-46200 | known affected: 278 known not affected: 17 recommended: 4 | 2026-08-03T23:39:40+00:00 | Vulnerability · Source |
| CVE-2026-46209 | suse_vex | SUSE CVE CVE-2026-46209 | known affected: 408 known not affected: 106 recommended: 240 | 2026-08-03T23:39:35+00:00 | Vulnerability · Source |
| 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-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-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-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-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-46325 | suse_vex | SUSE CVE CVE-2026-46325 | known affected: 97 known not affected: 181 | 2026-08-03T23:38:20+00:00 | Vulnerability · Source |