VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
306232 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-40321 | suse_vex | SUSE CVE CVE-2025-40321 | known affected: 718 known not affected: 53 recommended: 421 | 2026-10-10T16:31:43+00:00 | Vulnerability · Source |
| CVE-2025-40327 | suse_vex | SUSE CVE CVE-2025-40327 | known not affected: 515 recommended: 27 | 2026-10-10T16:31:39+00:00 | Vulnerability · Source |
| CVE-2025-40330 | suse_vex | SUSE CVE CVE-2025-40330 | known affected: 396 known not affected: 488 recommended: 265 | 2026-10-10T16:31:37+00:00 | Vulnerability · Source |
| CVE-2025-40349 | suse_vex | SUSE CVE CVE-2025-40349 | known affected: 394 known not affected: 392 recommended: 249 | 2026-10-10T16:31:35+00:00 | Vulnerability · Source |
| CVE-2025-40357 | suse_vex | SUSE CVE CVE-2025-40357 | known affected: 396 known not affected: 488 recommended: 265 | 2026-10-10T16:31:32+00:00 | Vulnerability · Source |
| CVE-2025-40777 | suse_vex | SUSE CVE CVE-2025-40777 | known affected: 394 known not affected: 515 recommended: 43 | 2026-10-10T16:31:30+00:00 | Vulnerability · Source |
| CVE-2025-41395 | suse_vex | SUSE CVE CVE-2025-41395 | recommended: 4 | 2026-10-10T16:31:27+00:00 | Vulnerability · Source |
| CVE-2025-41410 | suse_vex | SUSE CVE CVE-2025-41410 | recommended: 1 | 2026-10-10T16:31:25+00:00 | Vulnerability · Source |
| CVE-2025-43368 | suse_vex | SUSE CVE CVE-2025-43368 | known affected: 237 recommended: 564 | 2026-10-10T16:31:23+00:00 | Vulnerability · Source |
| CVE-2025-43429 | suse_vex | SUSE CVE CVE-2025-43429 | known affected: 221 known not affected: 16 recommended: 588 | 2026-10-10T16:31:21+00:00 | Vulnerability · Source |
| CVE-2025-43433 | suse_vex | SUSE CVE CVE-2025-43433 | known affected: 176 recommended: 508 | 2026-10-10T16:31:20+00:00 | Vulnerability · Source |
| CVE-2025-43440 | suse_vex | SUSE CVE CVE-2025-43440 | known affected: 221 known not affected: 16 recommended: 588 | 2026-10-10T16:31:18+00:00 | Vulnerability · Source |
| CVE-2025-43501 | suse_vex | SUSE CVE CVE-2025-43501 | known affected: 238 recommended: 580 | 2026-10-10T16:31:15+00:00 | Vulnerability · Source |
| CVE-2026-98383 | redhat_vex | kernel: bpf: Disallow bpf_skb_pull_data() for LWT_SEG6LOCAL | known affected: 249 known not affected: 28 | 2026-10-10T16:31:13+00:00 | Vulnerability · Source |
| CVE-2025-43718 | suse_vex | SUSE CVE CVE-2025-43718 | known affected: 32 known not affected: 140 recommended: 177 | 2026-10-10T16:31:13+00:00 | Vulnerability · Source |
| CVE-2025-43964 | suse_vex | SUSE CVE CVE-2025-43964 | known affected: 34 recommended: 49 | 2026-10-10T16:31:12+00:00 | Vulnerability · Source |
| CVE-2025-43970 | suse_vex | SUSE CVE CVE-2025-43970 | recommended: 4 | 2026-10-10T16:31:10+00:00 | Vulnerability · Source |
| CVE-2025-46334 | suse_vex | SUSE CVE CVE-2025-46334 | known not affected: 703 recommended: 53 | 2026-10-10T16:31:07+00:00 | Vulnerability · Source |
| CVE-2025-46342 | suse_vex | SUSE CVE CVE-2025-46342 | recommended: 4 | 2026-10-10T16:31:05+00:00 | Vulnerability · Source |
| CVE-2025-46394 | suse_vex | SUSE CVE CVE-2025-46394 | known affected: 41 recommended: 115 | 2026-10-10T16:31:03+00:00 | Vulnerability · Source |
| CVE-2025-46735 | suse_vex | SUSE CVE CVE-2025-46735 | recommended: 4 | 2026-10-10T16:31:00+00:00 | Vulnerability · Source |
| CVE-2025-46784 | suse_vex | SUSE CVE CVE-2025-46784 | known affected: 12 known not affected: 24 recommended: 32 | 2026-10-10T16:30:58+00:00 | Vulnerability · Source |
| CVE-2025-46818 | suse_vex | SUSE CVE CVE-2025-46818 | known affected: 4 known not affected: 7 recommended: 80 | 2026-10-10T16:30:53+00:00 | Vulnerability · Source |
| CVE-2025-47268 | suse_vex | SUSE CVE CVE-2025-47268 | known affected: 404 recommended: 100 | 2026-10-10T16:30:51+00:00 | Vulnerability · Source |
| CVE-2025-47287 | suse_vex | SUSE CVE CVE-2025-47287 | known affected: 430 known not affected: 22 recommended: 421 | 2026-10-10T16:30:48+00:00 | Vulnerability · Source |
| CVE-2025-47906 | suse_vex | SUSE CVE CVE-2025-47906 | known affected: 36 known not affected: 69 recommended: 483 | 2026-10-10T16:30:45+00:00 | Vulnerability · Source |
| CVE-2025-47933 | suse_vex | SUSE CVE CVE-2025-47933 | recommended: 4 | 2026-10-10T16:30:41+00:00 | Vulnerability · Source |
| CVE-2025-48039 | suse_vex | SUSE CVE CVE-2025-48039 | known affected: 63 recommended: 100 | 2026-10-10T16:30:39+00:00 | Vulnerability · Source |
| CVE-2025-48174 | suse_vex | SUSE CVE CVE-2025-48174 | known affected: 6 recommended: 39 | 2026-10-10T16:30:36+00:00 | Vulnerability · Source |
| CVE-2025-48945 | suse_vex | SUSE CVE CVE-2025-48945 | recommended: 27 | 2026-10-10T16:30:33+00:00 | Vulnerability · Source |
| CVE-2025-48949 | suse_vex | SUSE CVE CVE-2025-48949 | recommended: 4 | 2026-10-10T16:30:31+00:00 | Vulnerability · Source |
| CVE-2025-48964 | suse_vex | SUSE CVE CVE-2025-48964 | known affected: 421 recommended: 90 | 2026-10-10T16:30:29+00:00 | Vulnerability · Source |
| CVE-2025-49125 | suse_vex | SUSE CVE CVE-2025-49125 | known affected: 514 known not affected: 38 recommended: 473 | 2026-10-10T16:30:27+00:00 | Vulnerability · Source |
| CVE-2025-49175 | suse_vex | SUSE CVE CVE-2025-49175 | known affected: 447 recommended: 195 | 2026-10-10T16:30:24+00:00 | Vulnerability · Source |
| CVE-2025-49176 | suse_vex | SUSE CVE CVE-2025-49176 | known affected: 447 recommended: 195 | 2026-10-10T16:30:22+00:00 | Vulnerability · Source |
| CVE-2025-49630 | suse_vex | SUSE CVE CVE-2025-49630 | known affected: 484 known not affected: 49 recommended: 251 | 2026-10-10T16:30:19+00:00 | Vulnerability · Source |
| CVE-2025-49709 | suse_vex | SUSE CVE CVE-2025-49709 | known affected: 57 known not affected: 136 recommended: 9 | 2026-10-10T16:30:17+00:00 | Vulnerability · Source |
| CVE-2025-49825 | suse_vex | SUSE CVE CVE-2025-49825 | recommended: 17 | 2026-10-10T16:30:16+00:00 | Vulnerability · Source |
| CVE-2025-50738 | suse_vex | SUSE CVE CVE-2025-50738 | recommended: 4 | 2026-10-10T16:30:13+00:00 | Vulnerability · Source |
| CVE-2025-51471 | suse_vex | SUSE CVE CVE-2025-51471 | recommended: 4 | 2026-10-10T16:30:11+00:00 | Vulnerability · Source |
| CVE-2025-52520 | suse_vex | SUSE CVE CVE-2025-52520 | known affected: 521 known not affected: 38 recommended: 466 | 2026-10-10T16:30:09+00:00 | Vulnerability · Source |
| CVE-2025-52881 | suse_vex | SUSE CVE CVE-2025-52881 | known affected: 397 known not affected: 1291 recommended: 281 | 2026-10-10T16:30:07+00:00 | Vulnerability · Source |
| CVE-2025-52894 | suse_vex | SUSE CVE CVE-2025-52894 | recommended: 12 | 2026-10-10T16:30:05+00:00 | Vulnerability · Source |
| CVE-2025-53013 | suse_vex | SUSE CVE CVE-2025-53013 | recommended: 40 | 2026-10-10T16:30:03+00:00 | Vulnerability · Source |
| CVE-2025-53015 | suse_vex | SUSE CVE CVE-2025-53015 | known not affected: 355 recommended: 164 | 2026-10-10T16:30:02+00:00 | Vulnerability · Source |
| CVE-2025-53512 | suse_vex | SUSE CVE CVE-2025-53512 | recommended: 4 | 2026-10-10T16:29:59+00:00 | Vulnerability · Source |
| CVE-2025-53534 | suse_vex | SUSE CVE CVE-2025-53534 | recommended: 4 | 2026-10-10T16:29:57+00:00 | Vulnerability · Source |
| CVE-2025-53942 | suse_vex | SUSE CVE CVE-2025-53942 | recommended: 4 | 2026-10-10T16:29:52+00:00 | Vulnerability · Source |
| CVE-2025-54121 | suse_vex | SUSE CVE CVE-2025-54121 | known affected: 3 recommended: 8 | 2026-10-10T16:29:50+00:00 | Vulnerability · Source |
| CVE-2025-54368 | suse_vex | SUSE CVE CVE-2025-54368 | recommended: 15 | 2026-10-10T16:29:49+00:00 | Vulnerability · Source |