VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-8835 | suse_vex | SUSE CVE CVE-2025-8835 | known affected: 485 recommended: 54 | 2026-07-27T23:44:50+00:00 | Vulnerability · Source |
| CVE-2025-10535 | suse_vex | SUSE CVE CVE-2025-10535 | known affected: 37 recommended: 5 | 2026-07-27T23:44:48+00:00 | Vulnerability · Source |
| CVE-2025-11717 | suse_vex | SUSE CVE CVE-2025-11717 | known affected: 70 recommended: 5 | 2026-07-27T23:44:44+00:00 | Vulnerability · Source |
| CVE-2025-11721 | suse_vex | SUSE CVE CVE-2025-11721 | known affected: 70 recommended: 5 | 2026-07-27T23:44:43+00:00 | Vulnerability · Source |
| CVE-2025-13017 | suse_vex | SUSE CVE CVE-2025-13017 | known affected: 14 recommended: 183 | 2026-07-27T23:44:40+00:00 | Vulnerability · Source |
| CVE-2025-13026 | suse_vex | SUSE CVE CVE-2025-13026 | known affected: 14 recommended: 5 | 2026-07-27T23:44:38+00:00 | Vulnerability · Source |
| CVE-2025-13465 | suse_vex | SUSE CVE CVE-2025-13465 | first fixed: 36 known affected: 512 known not affected: 248 recommended: 228 | 2026-07-27T23:44:36+00:00 | Vulnerability · Source |
| CVE-2025-21797 | suse_vex | SUSE CVE CVE-2025-21797 | known affected: 47 known not affected: 232 | 2026-07-27T23:44:31+00:00 | Vulnerability · Source |
| CVE-2025-38349 | suse_vex | SUSE CVE CVE-2025-38349 | first fixed: 2 known affected: 445 known not affected: 283 recommended: 591 | 2026-07-27T23:44:04+00:00 | Vulnerability · Source |
| CVE-2025-38653 | suse_vex | SUSE CVE CVE-2025-38653 | first fixed: 2 known affected: 399 known not affected: 283 recommended: 583 | 2026-07-27T23:43:47+00:00 | Vulnerability · Source |
| CVE-2025-39971 | suse_vex | SUSE CVE CVE-2025-39971 | first fixed: 2 known affected: 585 known not affected: 52 recommended: 639 | 2026-07-27T23:43:33+00:00 | Vulnerability · Source |
| CVE-2025-40026 | suse_vex | SUSE CVE CVE-2025-40026 | known affected: 242 recommended: 26 | 2026-07-27T23:43:31+00:00 | Vulnerability · Source |
| CVE-2025-40058 | suse_vex | SUSE CVE CVE-2025-40058 | first fixed: 2 known affected: 451 known not affected: 211 recommended: 589 | 2026-07-27T23:43:28+00:00 | Vulnerability · Source |
| CVE-2025-40158 | suse_vex | SUSE CVE CVE-2025-40158 | first fixed: 2 known affected: 663 known not affected: 22 recommended: 510 | 2026-07-27T23:43:25+00:00 | Vulnerability · Source |
| CVE-2025-40170 | suse_vex | SUSE CVE CVE-2025-40170 | first fixed: 2 known affected: 663 known not affected: 22 recommended: 528 | 2026-07-27T23:43:23+00:00 | Vulnerability · Source |
| CVE-2025-40341 | suse_vex | SUSE CVE CVE-2025-40341 | first fixed: 55 known affected: 777 recommended: 209 | 2026-07-27T23:43:20+00:00 | Vulnerability · Source |
| CVE-2025-46836 | suse_vex | SUSE CVE CVE-2025-46836 | known affected: 439 recommended: 85 | 2026-07-27T23:43:17+00:00 | Vulnerability · Source |
| CVE-2025-64437 | suse_vex | SUSE CVE CVE-2025-64437 | first fixed: 1 known not affected: 70 recommended: 72 | 2026-07-27T23:43:06+00:00 | Vulnerability · Source |
| CVE-2025-71271 | suse_vex | SUSE CVE CVE-2025-71271 | known not affected: 227 | 2026-07-27T23:42:59+00:00 | Vulnerability · Source |
| CVE-2026-8458 | suse_vex | SUSE CVE CVE-2026-8458 | first fixed: 13 known affected: 459 known not affected: 2 recommended: 124 | 2026-07-27T23:42:40+00:00 | Vulnerability · Source |
| CVE-2026-8924 | suse_vex | SUSE CVE CVE-2026-8924 | first fixed: 13 known affected: 446 known not affected: 15 recommended: 128 | 2026-07-27T23:42:38+00:00 | Vulnerability · Source |
| CVE-2026-10536 | suse_vex | SUSE CVE CVE-2026-10536 | first fixed: 13 known affected: 432 known not affected: 29 recommended: 124 | 2026-07-27T23:42:31+00:00 | Vulnerability · Source |
| CVE-2026-12413 | suse_vex | SUSE CVE CVE-2026-12413 | recommended: 4 | 2026-07-27T23:42:27+00:00 | Vulnerability · Source |
| CVE-2026-12505 | suse_vex | SUSE CVE CVE-2026-12505 | known affected: 415 recommended: 61 | 2026-07-27T23:42:25+00:00 | Vulnerability · Source |
| CVE-2026-12892 | suse_vex | SUSE CVE CVE-2026-12892 | first fixed: 132 known affected: 181 known not affected: 83 recommended: 607 | 2026-07-27T23:42:23+00:00 | Vulnerability · Source |
| CVE-2026-23168 | suse_vex | SUSE CVE CVE-2026-23168 | first fixed: 2 known affected: 77 known not affected: 200 recommended: 337 | 2026-07-27T23:42:05+00:00 | Vulnerability · Source |
| CVE-2026-23193 | suse_vex | SUSE CVE CVE-2026-23193 | first fixed: 2 known affected: 631 known not affected: 4 recommended: 450 | 2026-07-27T23:42:03+00:00 | Vulnerability · Source |
| CVE-2026-23455 | suse_vex | SUSE CVE CVE-2026-23455 | first fixed: 2 known affected: 222 recommended: 448 | 2026-07-27T23:41:47+00:00 | Vulnerability · Source |
| CVE-2026-25547 | suse_vex | SUSE CVE CVE-2026-25547 | first fixed: 36 known affected: 552 known not affected: 255 recommended: 394 | 2026-07-27T23:41:42+00:00 | Vulnerability · Source |
| CVE-2026-26996 | suse_vex | SUSE CVE CVE-2026-26996 | first fixed: 36 known affected: 512 known not affected: 254 recommended: 214 | 2026-07-27T23:41:38+00:00 | Vulnerability · Source |
| CVE-2026-31429 | suse_vex | SUSE CVE CVE-2026-31429 | first fixed: 55 known affected: 459 known not affected: 186 recommended: 238 | 2026-07-27T23:41:28+00:00 | Vulnerability · Source |
| CVE-2026-31452 | suse_vex | SUSE CVE CVE-2026-31452 | first fixed: 55 known affected: 458 known not affected: 154 recommended: 275 | 2026-07-27T23:41:26+00:00 | Vulnerability · Source |
| CVE-2026-31469 | suse_vex | SUSE CVE CVE-2026-31469 | first fixed: 55 known affected: 595 recommended: 275 | 2026-07-27T23:41:23+00:00 | Vulnerability · Source |
| CVE-2026-31492 | suse_vex | SUSE CVE CVE-2026-31492 | first fixed: 55 known affected: 546 known not affected: 98 recommended: 238 | 2026-07-27T23:41:21+00:00 | Vulnerability · Source |
| CVE-2026-31503 | suse_vex | SUSE CVE CVE-2026-31503 | first fixed: 2 known affected: 644 recommended: 280 | 2026-07-27T23:41:18+00:00 | Vulnerability · Source |
| CVE-2026-31505 | suse_vex | SUSE CVE CVE-2026-31505 | first fixed: 26 known affected: 411 known not affected: 138 recommended: 525 | 2026-07-27T23:41:17+00:00 | Vulnerability · Source |
| CVE-2026-31533 | suse_vex | SUSE CVE CVE-2026-31533 | first fixed: 26 known affected: 442 known not affected: 67 recommended: 631 | 2026-07-27T23:41:15+00:00 | Vulnerability · Source |
| CVE-2026-31586 | suse_vex | SUSE CVE CVE-2026-31586 | first fixed: 26 known affected: 507 known not affected: 4 recommended: 635 | 2026-07-27T23:41:09+00:00 | Vulnerability · Source |
| CVE-2026-31596 | suse_vex | SUSE CVE CVE-2026-31596 | first fixed: 55 known affected: 612 recommended: 279 | 2026-07-27T23:41:07+00:00 | Vulnerability · Source |
| CVE-2026-31665 | suse_vex | SUSE CVE CVE-2026-31665 | first fixed: 55 known affected: 577 known not affected: 67 recommended: 238 | 2026-07-27T23:41:05+00:00 | Vulnerability · Source |
| CVE-2026-43010 | suse_vex | SUSE CVE CVE-2026-43010 | first fixed: 55 known affected: 489 known not affected: 131 recommended: 209 | 2026-07-27T23:40:02+00:00 | Vulnerability · Source |
| CVE-2026-43022 | suse_vex | SUSE CVE CVE-2026-43022 | first fixed: 55 known affected: 441 known not affected: 179 recommended: 209 | 2026-07-27T23:40:00+00:00 | Vulnerability · Source |
| CVE-2026-43025 | suse_vex | SUSE CVE CVE-2026-43025 | first fixed: 26 known affected: 468 known not affected: 4 recommended: 681 | 2026-07-27T23:39:58+00:00 | Vulnerability · Source |
| CVE-2026-43034 | suse_vex | SUSE CVE CVE-2026-43034 | first fixed: 55 known affected: 441 known not affected: 179 recommended: 209 | 2026-07-27T23:39:54+00:00 | Vulnerability · Source |
| CVE-2026-43037 | suse_vex | SUSE CVE CVE-2026-43037 | first fixed: 26 known affected: 458 recommended: 826 | 2026-07-27T23:39:52+00:00 | Vulnerability · Source |
| CVE-2026-43053 | suse_vex | SUSE CVE CVE-2026-43053 | first fixed: 55 known affected: 529 known not affected: 93 recommended: 238 | 2026-07-27T23:39:50+00:00 | Vulnerability · Source |
| CVE-2026-43081 | suse_vex | SUSE CVE CVE-2026-43081 | first fixed: 55 known affected: 441 known not affected: 181 recommended: 209 | 2026-07-27T23:39:49+00:00 | Vulnerability · Source |
| CVE-2026-43085 | suse_vex | SUSE CVE CVE-2026-43085 | first fixed: 55 known affected: 622 recommended: 209 | 2026-07-27T23:39:47+00:00 | Vulnerability · Source |
| CVE-2026-43086 | suse_vex | SUSE CVE CVE-2026-43086 | first fixed: 55 known affected: 489 known not affected: 133 recommended: 209 | 2026-07-27T23:39:45+00:00 | Vulnerability · Source |
| CVE-2026-43089 | suse_vex | SUSE CVE CVE-2026-43089 | first fixed: 55 known affected: 590 recommended: 246 | 2026-07-27T23:39:44+00:00 | Vulnerability · Source |