VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291933 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-43344 | suse_vex | SUSE CVE CVE-2026-43344 | known affected: 228 known not affected: 67 | 2026-08-03T23:44:06+00:00 | Vulnerability · Source |
| CVE-2026-43348 | suse_vex | SUSE CVE CVE-2026-43348 | known not affected: 293 recommended: 4 | 2026-08-03T23:44:03+00:00 | Vulnerability · Source |
| CVE-2026-43354 | suse_vex | SUSE CVE CVE-2026-43354 | known not affected: 293 | 2026-08-03T23:44:01+00:00 | Vulnerability · Source |
| CVE-2026-43368 | suse_vex | SUSE CVE CVE-2026-43368 | known not affected: 293 | 2026-08-03T23:43:56+00:00 | Vulnerability · Source |
| CVE-2026-43447 | suse_vex | SUSE CVE CVE-2026-43447 | known not affected: 293 | 2026-08-03T23:43:43+00:00 | Vulnerability · Source |
| CVE-2026-43464 | suse_vex | SUSE CVE CVE-2026-43464 | known not affected: 293 | 2026-08-03T23:43:39+00:00 | Vulnerability · Source |
| CVE-2026-43473 | suse_vex | SUSE CVE CVE-2026-43473 | known affected: 472 known not affected: 150 recommended: 120 | 2026-08-03T23:43:35+00:00 | Vulnerability · Source |
| CVE-2026-43478 | suse_vex | SUSE CVE CVE-2026-43478 | known not affected: 272 | 2026-08-03T23:43:31+00:00 | Vulnerability · Source |
| CVE-2026-43481 | suse_vex | SUSE CVE CVE-2026-43481 | known not affected: 272 | 2026-08-03T23:43:28+00:00 | Vulnerability · Source |
| CVE-2026-43486 | suse_vex | SUSE CVE CVE-2026-43486 | known not affected: 300 | 2026-08-03T23:43:25+00:00 | Vulnerability · Source |
| CVE-2026-43487 | suse_vex | SUSE CVE CVE-2026-43487 | known not affected: 300 | 2026-08-03T23:43:23+00:00 | Vulnerability · Source |
| CVE-2026-43495 | suse_vex | SUSE CVE CVE-2026-43495 | known affected: 97 known not affected: 198 recommended: 4 | 2026-08-03T23:43:19+00:00 | Vulnerability · Source |
| CVE-2026-44168 | suse_vex | SUSE CVE CVE-2026-44168 | known affected: 527 known not affected: 1 recommended: 213 | 2026-08-03T23:42:41+00:00 | Vulnerability · Source |
| CVE-2026-44170 | suse_vex | SUSE CVE CVE-2026-44170 | known affected: 394 known not affected: 92 recommended: 213 | 2026-08-03T23:42:39+00:00 | Vulnerability · Source |
| CVE-2026-44173 | suse_vex | SUSE CVE CVE-2026-44173 | known affected: 528 recommended: 213 | 2026-08-03T23:42:38+00:00 | Vulnerability · Source |
| CVE-2026-44405 | suse_vex | SUSE CVE CVE-2026-44405 | known affected: 443 recommended: 32 | 2026-08-03T23:42:35+00:00 | Vulnerability · Source |
| CVE-2026-45623 | suse_vex | SUSE CVE CVE-2026-45623 | known affected: 145 known not affected: 313 | 2026-08-03T23:42:24+00:00 | Vulnerability · Source |
| CVE-2026-45845 | suse_vex | SUSE CVE CVE-2026-45845 | known affected: 17 known not affected: 278 recommended: 4 | 2026-08-03T23:42:17+00:00 | Vulnerability · Source |
| 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-45927 | suse_vex | SUSE CVE CVE-2026-45927 | known not affected: 293 | 2026-08-03T23:41:39+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-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-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-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-46248 | suse_vex | SUSE CVE CVE-2026-46248 | known not affected: 293 | 2026-08-03T23:39:10+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-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-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 |
| 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-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 |