VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291864 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2026-43273 | suse_vex | SUSE CVE CVE-2026-43273 | first fixed: 68 known affected: 265 known not affected: 4 recommended: 99 | 2026-08-12T16:36:22+00:00 | Vulnerability · Source |
| CVE-2026-43325 | suse_vex | SUSE CVE CVE-2026-43325 | first fixed: 2 known affected: 424 known not affected: 181 recommended: 294 | 2026-08-12T16:36:07+00:00 | Vulnerability · Source |
| CVE-2026-43326 | suse_vex | SUSE CVE CVE-2026-43326 | known not affected: 311 | 2026-08-12T16:36:06+00:00 | Vulnerability · Source |
| CVE-2026-43337 | suse_vex | SUSE CVE CVE-2026-43337 | first fixed: 2 known affected: 394 known not affected: 223 recommended: 243 | 2026-08-12T16:36:02+00:00 | Vulnerability · Source |
| CVE-2026-43421 | suse_vex | SUSE CVE CVE-2026-43421 | known affected: 57 known not affected: 36 | 2026-08-12T16:35:50+00:00 | Vulnerability · Source |
| CVE-2026-44420 | suse_vex | SUSE CVE CVE-2026-44420 | known affected: 38 recommended: 123 | 2026-08-12T16:35:15+00:00 | Vulnerability · Source |
| CVE-2026-44421 | suse_vex | SUSE CVE CVE-2026-44421 | known affected: 38 recommended: 123 | 2026-08-12T16:35:13+00:00 | Vulnerability · Source |
| CVE-2026-44422 | suse_vex | SUSE CVE CVE-2026-44422 | known affected: 38 recommended: 123 | 2026-08-12T16:35:12+00:00 | Vulnerability · Source |
| CVE-2026-45700 | suse_vex | SUSE CVE CVE-2026-45700 | known affected: 38 recommended: 133 | 2026-08-12T16:34:53+00:00 | Vulnerability · Source |
| CVE-2026-46116 | suse_vex | SUSE CVE CVE-2026-46116 | first fixed: 2 known affected: 469 recommended: 632 | 2026-08-12T16:33:01+00:00 | Vulnerability · Source |
| CVE-2026-48724 | suse_vex | SUSE CVE CVE-2026-48724 | known not affected: 201 recommended: 117 | 2026-08-12T16:31:37+00:00 | Vulnerability · Source |
| CVE-2026-48802 | suse_vex | SUSE CVE CVE-2026-48802 | recommended: 8 | 2026-08-12T16:31:34+00:00 | Vulnerability · Source |
| CVE-2026-48804 | suse_vex | SUSE CVE CVE-2026-48804 | recommended: 10 | 2026-08-12T16:31:33+00:00 | Vulnerability · Source |
| CVE-2026-48809 | suse_vex | SUSE CVE CVE-2026-48809 | recommended: 11 | 2026-08-12T16:31:31+00:00 | Vulnerability · Source |
| CVE-2026-49349 | suse_vex | SUSE CVE CVE-2026-49349 | No product status | 2026-08-12T16:31:22+00:00 | Vulnerability · Source |
| CVE-2026-49476 | suse_vex | SUSE CVE CVE-2026-49476 | known affected: 8 recommended: 29 | 2026-08-12T16:31:20+00:00 | Vulnerability · Source |
| CVE-2026-49477 | suse_vex | SUSE CVE CVE-2026-49477 | known affected: 8 recommended: 29 | 2026-08-12T16:31:18+00:00 | Vulnerability · Source |
| CVE-2026-50045 | suse_vex | SUSE CVE CVE-2026-50045 | first fixed: 10 known affected: 20 known not affected: 110 recommended: 14 | 2026-08-12T16:31:08+00:00 | Vulnerability · Source |
| CVE-2026-55991 | suse_vex | SUSE CVE CVE-2026-55991 | first fixed: 10 known affected: 20 known not affected: 110 recommended: 14 | 2026-08-12T16:27:12+00:00 | Vulnerability · Source |
| CVE-2026-56297 | suse_vex | SUSE CVE CVE-2026-56297 | known affected: 8 known not affected: 27 recommended: 50 | 2026-08-12T16:27:07+00:00 | Vulnerability · Source |
| CVE-2026-57156 | suse_vex | SUSE CVE CVE-2026-57156 | known affected: 65 recommended: 65 | 2026-08-12T16:26:53+00:00 | Vulnerability · Source |
| CVE-2026-57157 | suse_vex | SUSE CVE CVE-2026-57157 | known affected: 27 known not affected: 38 recommended: 65 | 2026-08-12T16:26:51+00:00 | Vulnerability · Source |
| CVE-2026-64294 | redhat_vex | kernel: mm: do file ownership checks with the proper mount idmap | known affected: 198 known not affected: 76 | 2026-08-12T16:25:23+00:00 | Vulnerability · Source |