VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
293832 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-33594 | suse_vex | SUSE CVE CVE-2026-33594 | known affected: 27 recommended: 4 | 2026-07-15T05:18:47+00:00 | Vulnerability · Source |
| CVE-2026-33595 | suse_vex | SUSE CVE CVE-2026-33595 | known affected: 27 recommended: 4 | 2026-07-15T05:18:46+00:00 | Vulnerability · Source |
| CVE-2026-33596 | suse_vex | SUSE CVE CVE-2026-33596 | known affected: 27 recommended: 4 | 2026-07-15T05:18:45+00:00 | Vulnerability · Source |
| CVE-2026-33597 | suse_vex | SUSE CVE CVE-2026-33597 | known affected: 27 recommended: 4 | 2026-07-15T05:18:44+00:00 | Vulnerability · Source |
| CVE-2026-33598 | suse_vex | SUSE CVE CVE-2026-33598 | known affected: 27 recommended: 4 | 2026-07-15T05:18:42+00:00 | Vulnerability · Source |
| CVE-2026-33599 | suse_vex | SUSE CVE CVE-2026-33599 | known affected: 27 recommended: 4 | 2026-07-15T05:18:41+00:00 | Vulnerability · Source |
| CVE-2026-33602 | suse_vex | SUSE CVE CVE-2026-33602 | known affected: 27 recommended: 4 | 2026-07-15T05:18:40+00:00 | Vulnerability · Source |
| CVE-2026-33603 | suse_vex | SUSE CVE CVE-2026-33603 | known affected: 198 known not affected: 31 recommended: 44 | 2026-07-15T05:18:39+00:00 | Vulnerability · Source |
| CVE-2026-33745 | suse_vex | SUSE CVE CVE-2026-33745 | known not affected: 5 recommended: 2 | 2026-07-15T05:18:37+00:00 | Vulnerability · Source |
| CVE-2026-33857 | suse_vex | SUSE CVE CVE-2026-33857 | known affected: 442 recommended: 189 | 2026-07-15T05:18:28+00:00 | Vulnerability · Source |
| CVE-2026-33899 | suse_vex | SUSE CVE CVE-2026-33899 | known affected: 85 known not affected: 16 recommended: 245 | 2026-07-15T05:18:27+00:00 | Vulnerability · Source |
| CVE-2026-33900 | suse_vex | SUSE CVE CVE-2026-33900 | known affected: 85 known not affected: 16 recommended: 245 | 2026-07-15T05:18:26+00:00 | Vulnerability · Source |
| CVE-2026-33901 | suse_vex | SUSE CVE CVE-2026-33901 | known affected: 75 known not affected: 42 recommended: 229 | 2026-07-15T05:18:25+00:00 | Vulnerability · Source |
| CVE-2026-33902 | suse_vex | SUSE CVE CVE-2026-33902 | known affected: 21 known not affected: 227 recommended: 117 | 2026-07-15T05:18:24+00:00 | Vulnerability · Source |
| CVE-2026-33905 | suse_vex | SUSE CVE CVE-2026-33905 | known affected: 85 known not affected: 16 recommended: 245 | 2026-07-15T05:18:23+00:00 | Vulnerability · Source |
| CVE-2026-33908 | suse_vex | SUSE CVE CVE-2026-33908 | known affected: 85 known not affected: 16 recommended: 245 | 2026-07-15T05:18:22+00:00 | Vulnerability · Source |
| CVE-2026-33929 | suse_vex | SUSE CVE CVE-2026-33929 | known not affected: 25 recommended: 8 | 2026-07-15T05:18:21+00:00 | Vulnerability · Source |
| CVE-2026-33936 | suse_vex | SUSE CVE CVE-2026-33936 | known affected: 70 recommended: 18 | 2026-07-15T05:18:20+00:00 | Vulnerability · Source |
| CVE-2026-33999 | suse_vex | SUSE CVE CVE-2026-33999 | known affected: 424 recommended: 144 | 2026-07-15T05:18:06+00:00 | Vulnerability · Source |
| CVE-2026-34000 | suse_vex | SUSE CVE CVE-2026-34000 | known affected: 420 known not affected: 4 recommended: 116 | 2026-07-15T05:18:04+00:00 | Vulnerability · Source |
| CVE-2026-34002 | suse_vex | SUSE CVE CVE-2026-34002 | known affected: 424 recommended: 109 | 2026-07-15T05:18:02+00:00 | Vulnerability · Source |
| CVE-2026-34003 | suse_vex | SUSE CVE CVE-2026-34003 | known affected: 424 recommended: 144 | 2026-07-15T05:18:01+00:00 | Vulnerability · Source |
| CVE-2026-34032 | suse_vex | SUSE CVE CVE-2026-34032 | known affected: 442 recommended: 189 | 2026-07-15T05:18:00+00:00 | Vulnerability · Source |
| CVE-2026-34059 | suse_vex | SUSE CVE CVE-2026-34059 | known affected: 442 recommended: 189 | 2026-07-15T05:17:58+00:00 | Vulnerability · Source |
| CVE-2026-34073 | suse_vex | SUSE CVE CVE-2026-34073 | known affected: 394 known not affected: 77 recommended: 8 | 2026-07-15T05:17:56+00:00 | Vulnerability · Source |
| CVE-2026-34080 | suse_vex | SUSE CVE CVE-2026-34080 | known affected: 15 recommended: 10 | 2026-07-15T05:17:55+00:00 | Vulnerability · Source |
| CVE-2026-34238 | suse_vex | SUSE CVE CVE-2026-34238 | known affected: 85 known not affected: 16 recommended: 245 | 2026-07-15T05:17:51+00:00 | Vulnerability · Source |
| CVE-2026-34303 | suse_vex | SUSE CVE CVE-2026-34303 | known affected: 139 recommended: 106 | 2026-07-15T05:17:47+00:00 | Vulnerability · Source |
| CVE-2026-34352 | suse_vex | SUSE CVE CVE-2026-34352 | known affected: 442 recommended: 171 | 2026-07-15T05:17:46+00:00 | Vulnerability · Source |
| CVE-2026-34378 | suse_vex | SUSE CVE CVE-2026-34378 | known not affected: 108 recommended: 18 | 2026-07-15T05:17:43+00:00 | Vulnerability · Source |
| CVE-2026-34379 | suse_vex | SUSE CVE CVE-2026-34379 | known not affected: 108 recommended: 55 | 2026-07-15T05:17:42+00:00 | Vulnerability · Source |
| CVE-2026-34380 | suse_vex | SUSE CVE CVE-2026-34380 | known not affected: 108 recommended: 55 | 2026-07-15T05:17:41+00:00 | Vulnerability · Source |
| CVE-2026-34441 | suse_vex | SUSE CVE CVE-2026-34441 | known affected: 5 recommended: 2 | 2026-07-15T05:17:39+00:00 | Vulnerability · Source |
| CVE-2026-34543 | suse_vex | SUSE CVE CVE-2026-34543 | known not affected: 108 recommended: 18 | 2026-07-15T05:17:24+00:00 | Vulnerability · Source |
| CVE-2026-34544 | suse_vex | SUSE CVE CVE-2026-34544 | known not affected: 108 recommended: 18 | 2026-07-15T05:17:23+00:00 | Vulnerability · Source |
| CVE-2026-34545 | suse_vex | SUSE CVE CVE-2026-34545 | known not affected: 108 recommended: 18 | 2026-07-15T05:17:22+00:00 | Vulnerability · Source |
| CVE-2026-34941 | suse_vex | SUSE CVE CVE-2026-34941 | recommended: 14 | 2026-07-15T05:17:11+00:00 | Vulnerability · Source |
| CVE-2026-34942 | suse_vex | SUSE CVE CVE-2026-34942 | recommended: 10 | 2026-07-15T05:17:10+00:00 | Vulnerability · Source |
| CVE-2026-34943 | suse_vex | SUSE CVE CVE-2026-34943 | recommended: 14 | 2026-07-15T05:17:09+00:00 | Vulnerability · Source |
| CVE-2026-34944 | suse_vex | SUSE CVE CVE-2026-34944 | recommended: 10 | 2026-07-15T05:17:08+00:00 | Vulnerability · Source |
| CVE-2026-34945 | suse_vex | SUSE CVE CVE-2026-34945 | recommended: 14 | 2026-07-15T05:17:07+00:00 | Vulnerability · Source |
| CVE-2026-34946 | suse_vex | SUSE CVE CVE-2026-34946 | recommended: 10 | 2026-07-15T05:17:06+00:00 | Vulnerability · Source |
| CVE-2026-34987 | suse_vex | SUSE CVE CVE-2026-34987 | recommended: 10 | 2026-07-15T05:17:03+00:00 | Vulnerability · Source |
| CVE-2026-34988 | suse_vex | SUSE CVE CVE-2026-34988 | recommended: 14 | 2026-07-15T05:17:01+00:00 | Vulnerability · Source |
| CVE-2026-35094 | suse_vex | SUSE CVE CVE-2026-35094 | known not affected: 129 recommended: 5 | 2026-07-15T05:16:57+00:00 | Vulnerability · Source |
| CVE-2026-35186 | suse_vex | SUSE CVE CVE-2026-35186 | recommended: 14 | 2026-07-15T05:16:56+00:00 | Vulnerability · Source |
| CVE-2026-35195 | suse_vex | SUSE CVE CVE-2026-35195 | recommended: 10 | 2026-07-15T05:16:55+00:00 | Vulnerability · Source |
| CVE-2026-39244 | suse_vex | SUSE CVE CVE-2026-39244 | known affected: 16 known not affected: 65 | 2026-07-15T05:16:33+00:00 | Vulnerability · Source |
| CVE-2026-39886 | suse_vex | SUSE CVE CVE-2026-39886 | known not affected: 133 recommended: 18 | 2026-07-15T05:16:08+00:00 | Vulnerability · Source |
| CVE-2026-40016 | suse_vex | SUSE CVE CVE-2026-40016 | known affected: 210 known not affected: 31 recommended: 30 | 2026-07-15T05:16:04+00:00 | Vulnerability · Source |