VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291890 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-68366 | suse_vex | SUSE CVE CVE-2025-68366 | first fixed: 2 known affected: 709 known not affected: 22 recommended: 439 | 2026-08-12T16:46:59+00:00 | Vulnerability · Source |
| CVE-2025-68471 | suse_vex | SUSE CVE CVE-2025-68471 | known affected: 711 recommended: 368 | 2026-08-12T16:46:53+00:00 | Vulnerability · Source |
| CVE-2025-68615 | suse_vex | SUSE CVE CVE-2025-68615 | known affected: 492 known not affected: 10 recommended: 234 | 2026-08-12T16:46:50+00:00 | Vulnerability · Source |
| CVE-2025-68729 | suse_vex | SUSE CVE CVE-2025-68729 | known not affected: 453 recommended: 6 | 2026-08-12T16:46:47+00:00 | Vulnerability · Source |
| CVE-2025-68754 | suse_vex | SUSE CVE CVE-2025-68754 | known not affected: 353 recommended: 6 | 2026-08-12T16:46:42+00:00 | Vulnerability · Source |
| CVE-2025-68784 | suse_vex | SUSE CVE CVE-2025-68784 | first fixed: 2 known affected: 5 known not affected: 331 recommended: 172 | 2026-08-12T16:46:36+00:00 | Vulnerability · Source |
| CVE-2025-68790 | suse_vex | SUSE CVE CVE-2025-68790 | known not affected: 336 recommended: 27 | 2026-08-12T16:46:33+00:00 | Vulnerability · Source |
| CVE-2025-68807 | suse_vex | SUSE CVE CVE-2025-68807 | known not affected: 336 recommended: 27 | 2026-08-12T16:46:29+00:00 | Vulnerability · Source |
| CVE-2025-68823 | suse_vex | SUSE CVE CVE-2025-68823 | known not affected: 222 | 2026-08-12T16:46:25+00:00 | Vulnerability · Source |
| CVE-2025-68950 | suse_vex | SUSE CVE CVE-2025-68950 | known affected: 196 known not affected: 117 recommended: 164 | 2026-08-12T16:46:23+00:00 | Vulnerability · Source |
| CVE-2025-69230 | suse_vex | SUSE CVE CVE-2025-69230 | known not affected: 66 recommended: 4 | 2026-08-12T16:46:20+00:00 | Vulnerability · Source |
| CVE-2025-70067 | suse_vex | SUSE CVE CVE-2025-70067 | known affected: 736 recommended: 2 | 2026-08-12T16:46:13+00:00 | Vulnerability · Source |
| CVE-2025-70069 | suse_vex | SUSE CVE CVE-2025-70069 | known affected: 736 | 2026-08-12T16:46:12+00:00 | Vulnerability · Source |
| CVE-2025-71096 | suse_vex | SUSE CVE CVE-2025-71096 | first fixed: 2 known affected: 544 known not affected: 40 recommended: 344 | 2026-08-12T16:46:05+00:00 | Vulnerability · Source |
| CVE-2025-71121 | suse_vex | SUSE CVE CVE-2025-71121 | known not affected: 340 | 2026-08-12T16:46:00+00:00 | Vulnerability · Source |
| CVE-2025-71129 | suse_vex | SUSE CVE CVE-2025-71129 | known not affected: 342 | 2026-08-12T16:45:58+00:00 | Vulnerability · Source |
| CVE-2025-71142 | suse_vex | SUSE CVE CVE-2025-71142 | first fixed: 2 known affected: 399 known not affected: 259 recommended: 283 | 2026-08-12T16:45:54+00:00 | Vulnerability · Source |
| CVE-2025-71176 | suse_vex | SUSE CVE CVE-2025-71176 | known affected: 44 recommended: 13 | 2026-08-12T16:45:50+00:00 | Vulnerability · Source |
| CVE-2025-71193 | suse_vex | SUSE CVE CVE-2025-71193 | first fixed: 2 known affected: 124 known not affected: 138 recommended: 172 | 2026-08-12T16:45:47+00:00 | Vulnerability · Source |
| CVE-2025-71265 | suse_vex | SUSE CVE CVE-2025-71265 | known not affected: 332 | 2026-08-12T16:45:39+00:00 | Vulnerability · Source |
| CVE-2025-71266 | suse_vex | SUSE CVE CVE-2025-71266 | known not affected: 332 | 2026-08-12T16:45:38+00:00 | Vulnerability · Source |
| CVE-2025-71288 | suse_vex | SUSE CVE CVE-2025-71288 | first fixed: 68 known affected: 97 known not affected: 198 recommended: 76 | 2026-08-12T16:45:30+00:00 | Vulnerability · Source |
| CVE-2025-71302 | suse_vex | SUSE CVE CVE-2025-71302 | first fixed: 2 known affected: 411 known not affected: 223 recommended: 270 | 2026-08-12T16:45:25+00:00 | Vulnerability · Source |
| CVE-2025-71304 | suse_vex | SUSE CVE CVE-2025-71304 | known affected: 57 known not affected: 236 | 2026-08-12T16:45:23+00:00 | Vulnerability · Source |
| CVE-2025-71315 | suse_vex | SUSE CVE CVE-2025-71315 | known affected: 144 known not affected: 67 | 2026-08-12T16:45:20+00:00 | Vulnerability · Source |
| CVE-2026-3832 | suse_vex | SUSE CVE CVE-2026-3832 | known affected: 394 known not affected: 219 recommended: 45 | 2026-08-12T16:45:05+00:00 | Vulnerability · Source |
| CVE-2026-5419 | suse_vex | SUSE CVE CVE-2026-5419 | known affected: 554 recommended: 91 | 2026-08-12T16:44:56+00:00 | Vulnerability · Source |
| CVE-2026-5947 | suse_vex | SUSE CVE CVE-2026-5947 | known affected: 394 known not affected: 218 recommended: 55 | 2026-08-12T16:44:51+00:00 | Vulnerability · Source |
| CVE-2026-6368 | suse_vex | SUSE CVE CVE-2026-6368 | known affected: 385 | 2026-08-12T16:44:44+00:00 | Vulnerability · Source |
| CVE-2026-12996 | suse_vex | SUSE CVE CVE-2026-12996 | known affected: 17 known not affected: 50 recommended: 35 | 2026-08-12T16:43:55+00:00 | Vulnerability · Source |
| CVE-2026-14586 | suse_vex | SUSE CVE CVE-2026-14586 | first fixed: 10 known affected: 20 known not affected: 110 recommended: 14 | 2026-08-12T16:43:40+00:00 | Vulnerability · Source |
| CVE-2026-15928 | suse_vex | SUSE CVE CVE-2026-15928 | known affected: 121 recommended: 52 | 2026-08-12T16:43:26+00:00 | Vulnerability · Source |
| CVE-2026-18348 | suse_vex | SUSE CVE CVE-2026-18348 | known affected: 5 | 2026-08-12T16:43:10+00:00 | Vulnerability · Source |
| CVE-2026-18497 | suse_vex | SUSE CVE CVE-2026-18497 | No product status | 2026-08-12T16:43:08+00:00 | Vulnerability · Source |
| CVE-2026-27606 | suse_vex | SUSE CVE CVE-2026-27606 | known affected: 88 known not affected: 342 recommended: 122 | 2026-08-12T16:40:47+00:00 | Vulnerability · Source |
| CVE-2026-31450 | suse_vex | SUSE CVE CVE-2026-31450 | first fixed: 2 known affected: 595 known not affected: 4 recommended: 329 | 2026-08-12T16:40:13+00:00 | Vulnerability · Source |
| CVE-2026-31696 | suse_vex | SUSE CVE CVE-2026-31696 | known not affected: 312 recommended: 4 | 2026-08-12T16:39:22+00:00 | Vulnerability · Source |
| CVE-2026-31725 | suse_vex | SUSE CVE CVE-2026-31725 | known affected: 308 known not affected: 4 | 2026-08-12T16:39:20+00:00 | Vulnerability · Source |
| CVE-2026-32665 | suse_vex | SUSE CVE CVE-2026-32665 | first fixed: 10 known affected: 20 known not affected: 110 recommended: 14 | 2026-08-12T16:39:04+00:00 | Vulnerability · Source |
| CVE-2026-34191 | suse_vex | SUSE CVE CVE-2026-34191 | known affected: 167 | 2026-08-12T16:38:51+00:00 | Vulnerability · Source |
| CVE-2026-35058 | suse_vex | SUSE CVE CVE-2026-35058 | first fixed: 3 known affected: 34 known not affected: 29 recommended: 35 | 2026-08-12T16:38:46+00:00 | Vulnerability · Source |
| CVE-2026-40215 | suse_vex | SUSE CVE CVE-2026-40215 | known affected: 9 known not affected: 54 recommended: 35 | 2026-08-12T16:38:34+00:00 | Vulnerability · Source |
| CVE-2026-40467 | suse_vex | SUSE CVE CVE-2026-40467 | known affected: 421 recommended: 14 | 2026-08-12T16:38:32+00:00 | Vulnerability · Source |
| CVE-2026-40468 | suse_vex | SUSE CVE CVE-2026-40468 | known affected: 418 recommended: 17 | 2026-08-12T16:38:29+00:00 | Vulnerability · Source |
| CVE-2026-40553 | suse_vex | SUSE CVE CVE-2026-40553 | known affected: 421 recommended: 14 | 2026-08-12T16:38:27+00:00 | Vulnerability · Source |
| CVE-2026-41316 | suse_vex | SUSE CVE CVE-2026-41316 | known affected: 565 recommended: 118 | 2026-08-12T16:38:21+00:00 | Vulnerability · Source |
| CVE-2026-41637 | suse_vex | SUSE CVE CVE-2026-41637 | first fixed: 10 known affected: 20 known not affected: 110 recommended: 14 | 2026-08-12T16:38:18+00:00 | Vulnerability · Source |
| CVE-2026-43076 | suse_vex | SUSE CVE CVE-2026-43076 | known affected: 61 | 2026-08-12T16:37:22+00:00 | Vulnerability · Source |
| CVE-2026-43215 | suse_vex | SUSE CVE CVE-2026-43215 | known affected: 394 known not affected: 49 recommended: 98 | 2026-08-12T16:36:51+00:00 | Vulnerability · Source |
| CVE-2026-43268 | suse_vex | SUSE CVE CVE-2026-43268 | known not affected: 293 recommended: 23 | 2026-08-12T16:36:24+00:00 | Vulnerability · Source |