VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292126 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-40106 | suse_vex | SUSE CVE CVE-2025-40106 | first fixed: 2 known affected: 750 known not affected: 6 recommended: 313 | 2026-07-22T16:41:03+00:00 | Vulnerability · Source |
| CVE-2025-40134 | suse_vex | SUSE CVE CVE-2025-40134 | first fixed: 2 known affected: 616 known not affected: 97 recommended: 384 | 2026-07-22T16:41:01+00:00 | Vulnerability · Source |
| CVE-2026-43281 | redhat_vex | kernel: mailbox: Prevent out-of-bounds access in fw_mbox_index_xlate() | known affected: 260 known not affected: 14 | 2026-07-22T16:41:00+00:00 | Vulnerability · Source |
| CVE-2025-40014 | redhat_vex | kernel: objtool, spi: amd: Fix out-of-bounds stack access in amd_set_spi_freq() | known affected: 108 known not affected: 166 | 2026-07-22T16:40:59+00:00 | Vulnerability · Source |
| CVE-2025-40159 | suse_vex | SUSE CVE CVE-2025-40159 | first fixed: 2 known affected: 394 known not affected: 264 recommended: 573 | 2026-07-22T16:40:59+00:00 | Vulnerability · Source |
| CVE-2025-40160 | suse_vex | SUSE CVE CVE-2025-40160 | first fixed: 2 known affected: 602 known not affected: 122 recommended: 337 | 2026-07-22T16:40:58+00:00 | Vulnerability · Source |
| CVE-2025-40169 | suse_vex | SUSE CVE CVE-2025-40169 | first fixed: 2 known affected: 394 known not affected: 264 recommended: 500 | 2026-07-22T16:40:57+00:00 | Vulnerability · Source |
| CVE-2025-40178 | suse_vex | SUSE CVE CVE-2025-40178 | first fixed: 2 known affected: 683 recommended: 414 | 2026-07-22T16:40:54+00:00 | Vulnerability · Source |
| CVE-2025-40179 | suse_vex | SUSE CVE CVE-2025-40179 | first fixed: 2 known affected: 449 known not affected: 264 recommended: 402 | 2026-07-22T16:40:53+00:00 | Vulnerability · Source |
| CVE-2025-40190 | suse_vex | SUSE CVE CVE-2025-40190 | first fixed: 2 known affected: 657 known not affected: 97 recommended: 307 | 2026-07-22T16:40:51+00:00 | Vulnerability · Source |
| CVE-2025-40192 | suse_vex | SUSE CVE CVE-2025-40192 | first fixed: 2 known affected: 549 known not affected: 264 recommended: 163 | 2026-07-22T16:40:50+00:00 | Vulnerability · Source |
| CVE-2025-40201 | suse_vex | SUSE CVE CVE-2025-40201 | first fixed: 2 known affected: 494 known not affected: 264 recommended: 277 | 2026-07-22T16:40:49+00:00 | Vulnerability · Source |
| CVE-2025-40202 | suse_vex | SUSE CVE CVE-2025-40202 | first fixed: 2 known affected: 449 known not affected: 264 recommended: 384 | 2026-07-22T16:40:47+00:00 | Vulnerability · Source |
| CVE-2025-40307 | suse_vex | SUSE CVE CVE-2025-40307 | first fixed: 2 known affected: 754 recommended: 307 | 2026-07-22T16:40:44+00:00 | Vulnerability · Source |
| CVE-2025-40309 | suse_vex | SUSE CVE CVE-2025-40309 | first fixed: 2 known affected: 394 known not affected: 303 recommended: 474 | 2026-07-22T16:40:43+00:00 | Vulnerability · Source |
| CVE-2025-54409 | suse_vex | SUSE CVE CVE-2025-54409 | known affected: 58 recommended: 5 | 2026-07-22T16:40:32+00:00 | Vulnerability · Source |
| CVE-2025-68231 | suse_vex | SUSE CVE CVE-2025-68231 | known affected: 375 known not affected: 6 | 2026-07-22T16:40:20+00:00 | Vulnerability · Source |
| CVE-2025-68284 | suse_vex | SUSE CVE CVE-2025-68284 | first fixed: 2 known affected: 421 known not affected: 152 recommended: 685 | 2026-07-22T16:40:18+00:00 | Vulnerability · Source |
| CVE-2025-68733 | suse_vex | SUSE CVE CVE-2025-68733 | known affected: 770 known not affected: 6 recommended: 141 | 2026-07-22T16:40:15+00:00 | Vulnerability · Source |
| CVE-2025-68794 | suse_vex | SUSE CVE CVE-2025-68794 | first fixed: 2 known affected: 601 known not affected: 79 recommended: 295 | 2026-07-22T16:40:13+00:00 | Vulnerability · Source |
| CVE-2025-68972 | suse_vex | SUSE CVE CVE-2025-68972 | known affected: 523 | 2026-07-22T16:40:11+00:00 | Vulnerability · Source |
| CVE-2025-71079 | suse_vex | SUSE CVE CVE-2025-71079 | first fixed: 2 known affected: 650 known not affected: 9 recommended: 307 | 2026-07-22T16:40:10+00:00 | Vulnerability · Source |
| CVE-2026-4426 | suse_vex | SUSE CVE CVE-2026-4426 | known affected: 462 recommended: 74 | 2026-07-22T16:39:45+00:00 | Vulnerability · Source |
| CVE-2026-4873 | suse_vex | SUSE CVE CVE-2026-4873 | first fixed: 13 known affected: 420 recommended: 173 | 2026-07-22T16:39:41+00:00 | Vulnerability · Source |
| CVE-2026-6067 | suse_vex | SUSE CVE CVE-2026-6067 | first fixed: 5 known affected: 23 recommended: 2 | 2026-07-22T16:39:25+00:00 | Vulnerability · Source |
| CVE-2026-6068 | suse_vex | SUSE CVE CVE-2026-6068 | first fixed: 6 known affected: 24 recommended: 1 | 2026-07-22T16:39:23+00:00 | Vulnerability · Source |
| CVE-2026-10028 | suse_vex | SUSE CVE CVE-2026-10028 | known affected: 442 recommended: 33 | 2026-07-22T16:39:04+00:00 | Vulnerability · Source |
| CVE-2026-10275 | suse_vex | SUSE CVE CVE-2026-10275 | known affected: 406 recommended: 29 | 2026-07-22T16:39:03+00:00 | Vulnerability · Source |
| CVE-2026-23047 | suse_vex | SUSE CVE CVE-2026-23047 | first fixed: 2 known affected: 630 known not affected: 18 recommended: 295 | 2026-07-22T16:37:05+00:00 | Vulnerability · Source |
| CVE-2026-23049 | suse_vex | SUSE CVE CVE-2026-23049 | first fixed: 2 known affected: 605 known not affected: 43 recommended: 295 | 2026-07-22T16:37:04+00:00 | Vulnerability · Source |
| CVE-2026-23061 | suse_vex | SUSE CVE CVE-2026-23061 | first fixed: 2 known affected: 644 known not affected: 33 recommended: 295 | 2026-07-22T16:37:02+00:00 | Vulnerability · Source |
| CVE-2026-23108 | suse_vex | SUSE CVE CVE-2026-23108 | first fixed: 2 known affected: 642 known not affected: 6 recommended: 295 | 2026-07-22T16:37:00+00:00 | Vulnerability · Source |
| CVE-2026-23113 | suse_vex | SUSE CVE CVE-2026-23113 | known affected: 555 known not affected: 110 recommended: 150 | 2026-07-22T16:36:59+00:00 | Vulnerability · Source |
| CVE-2026-23121 | suse_vex | SUSE CVE CVE-2026-23121 | first fixed: 2 known affected: 485 known not affected: 180 recommended: 295 | 2026-07-22T16:36:57+00:00 | Vulnerability · Source |
| CVE-2026-23125 | suse_vex | SUSE CVE CVE-2026-23125 | first fixed: 2 known affected: 635 recommended: 325 | 2026-07-22T16:36:56+00:00 | Vulnerability · Source |
| CVE-2026-23140 | suse_vex | SUSE CVE CVE-2026-23140 | first fixed: 2 known affected: 515 known not affected: 150 recommended: 295 | 2026-07-22T16:36:54+00:00 | Vulnerability · Source |
| CVE-2026-23157 | suse_vex | SUSE CVE CVE-2026-23157 | first fixed: 2 known affected: 601 recommended: 390 | 2026-07-22T16:36:53+00:00 | Vulnerability · Source |
| CVE-2026-23187 | suse_vex | SUSE CVE CVE-2026-23187 | first fixed: 2 known affected: 467 known not affected: 198 recommended: 295 | 2026-07-22T16:36:50+00:00 | Vulnerability · Source |
| CVE-2026-23201 | suse_vex | SUSE CVE CVE-2026-23201 | first fixed: 2 known affected: 467 known not affected: 198 recommended: 295 | 2026-07-22T16:36:47+00:00 | Vulnerability · Source |
| CVE-2026-23216 | suse_vex | SUSE CVE CVE-2026-23216 | first fixed: 2 known affected: 639 recommended: 379 | 2026-07-22T16:36:44+00:00 | Vulnerability · Source |
| CVE-2026-23236 | suse_vex | SUSE CVE CVE-2026-23236 | first fixed: 2 known affected: 228 known not affected: 26 recommended: 299 | 2026-07-22T16:36:41+00:00 | Vulnerability · Source |
| CVE-2026-23239 | suse_vex | SUSE CVE CVE-2026-23239 | first fixed: 2 known affected: 435 known not affected: 91 recommended: 491 | 2026-07-22T16:36:39+00:00 | Vulnerability · Source |
| CVE-2026-23255 | suse_vex | SUSE CVE CVE-2026-23255 | first fixed: 2 known affected: 635 recommended: 325 | 2026-07-22T16:36:36+00:00 | Vulnerability · Source |
| CVE-2026-23268 | suse_vex | SUSE CVE CVE-2026-23268 | first fixed: 2 known affected: 482 known not affected: 404 recommended: 717 | 2026-07-22T16:36:33+00:00 | Vulnerability · Source |
| CVE-2026-23269 | suse_vex | SUSE CVE CVE-2026-23269 | first fixed: 2 known affected: 496 known not affected: 4 recommended: 584 | 2026-07-22T16:36:32+00:00 | Vulnerability · Source |
| CVE-2026-23271 | suse_vex | SUSE CVE CVE-2026-23271 | first fixed: 2 known affected: 476 recommended: 552 | 2026-07-22T16:36:29+00:00 | Vulnerability · Source |
| CVE-2026-23281 | suse_vex | SUSE CVE CVE-2026-23281 | first fixed: 2 known affected: 648 recommended: 295 | 2026-07-22T16:36:26+00:00 | Vulnerability · Source |
| CVE-2026-23303 | suse_vex | SUSE CVE CVE-2026-23303 | first fixed: 2 known affected: 631 known not affected: 4 recommended: 324 | 2026-07-22T16:36:24+00:00 | Vulnerability · Source |
| CVE-2026-23304 | suse_vex | SUSE CVE CVE-2026-23304 | first fixed: 2 known affected: 586 known not affected: 79 recommended: 295 | 2026-07-22T16:36:23+00:00 | Vulnerability · Source |
| CVE-2026-23306 | suse_vex | SUSE CVE CVE-2026-23306 | known affected: 121 known not affected: 150 recommended: 150 | 2026-07-22T16:36:22+00:00 | Vulnerability · Source |