VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292114 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-22992 | suse_vex | SUSE CVE CVE-2026-22992 | first fixed: 2 known affected: 538 known not affected: 112 recommended: 307 | 2026-07-24T02:41:27+00:00 | Vulnerability · Source |
| CVE-2026-22993 | suse_vex | SUSE CVE CVE-2026-22993 | first fixed: 2 known affected: 534 known not affected: 112 recommended: 307 | 2026-07-24T02:41:25+00:00 | Vulnerability · Source |
| CVE-2026-22996 | suse_vex | SUSE CVE CVE-2026-22996 | first fixed: 2 known affected: 482 known not affected: 132 recommended: 307 | 2026-07-24T02:41:23+00:00 | Vulnerability · Source |
| CVE-2026-22997 | suse_vex | SUSE CVE CVE-2026-22997 | first fixed: 2 known affected: 538 known not affected: 112 recommended: 307 | 2026-07-24T02:41:20+00:00 | Vulnerability · Source |
| CVE-2026-22999 | suse_vex | SUSE CVE CVE-2026-22999 | first fixed: 2 known affected: 428 known not affected: 4 recommended: 763 | 2026-07-24T02:41:16+00:00 | Vulnerability · Source |
| CVE-2026-23000 | suse_vex | SUSE CVE CVE-2026-23000 | first fixed: 2 known affected: 487 known not affected: 112 recommended: 307 | 2026-07-24T02:41:14+00:00 | Vulnerability · Source |
| CVE-2026-23003 | suse_vex | SUSE CVE CVE-2026-23003 | first fixed: 2 known affected: 498 known not affected: 122 recommended: 318 | 2026-07-24T02:41:11+00:00 | Vulnerability · Source |
| CVE-2026-23004 | suse_vex | SUSE CVE CVE-2026-23004 | first fixed: 2 known affected: 432 known not affected: 4 recommended: 754 | 2026-07-24T02:41:09+00:00 | Vulnerability · Source |
| CVE-2026-23005 | suse_vex | SUSE CVE CVE-2026-23005 | first fixed: 2 known affected: 399 known not affected: 200 recommended: 307 | 2026-07-24T02:41:07+00:00 | Vulnerability · Source |
| CVE-2026-23006 | suse_vex | SUSE CVE CVE-2026-23006 | first fixed: 2 known affected: 450 known not affected: 200 recommended: 307 | 2026-07-24T02:41:05+00:00 | Vulnerability · Source |
| CVE-2026-23011 | suse_vex | SUSE CVE CVE-2026-23011 | first fixed: 2 known affected: 614 known not affected: 4 recommended: 344 | 2026-07-24T02:41:02+00:00 | Vulnerability · Source |
| CVE-2026-23017 | suse_vex | SUSE CVE CVE-2026-23017 | first fixed: 2 known affected: 538 known not affected: 112 recommended: 295 | 2026-07-24T02:41:00+00:00 | Vulnerability · Source |
| CVE-2026-23021 | suse_vex | SUSE CVE CVE-2026-23021 | first fixed: 2 known affected: 558 known not affected: 13 recommended: 295 | 2026-07-24T02:40:57+00:00 | Vulnerability · Source |
| CVE-2026-23026 | suse_vex | SUSE CVE CVE-2026-23026 | first fixed: 2 known affected: 482 known not affected: 121 recommended: 295 | 2026-07-24T02:40:55+00:00 | Vulnerability · Source |
| CVE-2026-23030 | suse_vex | SUSE CVE CVE-2026-23030 | first fixed: 2 known affected: 445 known not affected: 201 recommended: 295 | 2026-07-24T02:40:54+00:00 | Vulnerability · Source |
| CVE-2026-23033 | suse_vex | SUSE CVE CVE-2026-23033 | first fixed: 2 known affected: 500 known not affected: 133 recommended: 295 | 2026-07-24T02:40:52+00:00 | Vulnerability · Source |
| CVE-2026-23035 | suse_vex | SUSE CVE CVE-2026-23035 | first fixed: 2 known affected: 538 known not affected: 112 recommended: 295 | 2026-07-24T02:40:50+00:00 | Vulnerability · Source |
| CVE-2026-23037 | suse_vex | SUSE CVE CVE-2026-23037 | first fixed: 2 known affected: 394 known not affected: 121 recommended: 295 | 2026-07-24T02:40:48+00:00 | Vulnerability · Source |
| CVE-2026-23053 | suse_vex | SUSE CVE CVE-2026-23053 | first fixed: 2 known affected: 450 known not affected: 200 recommended: 295 | 2026-07-24T02:40:46+00:00 | Vulnerability · Source |
| CVE-2026-23054 | suse_vex | SUSE CVE CVE-2026-23054 | first fixed: 2 known affected: 416 known not affected: 31 recommended: 623 | 2026-07-24T02:40:44+00:00 | Vulnerability · Source |
| CVE-2026-23056 | suse_vex | SUSE CVE CVE-2026-23056 | first fixed: 2 known affected: 482 known not affected: 121 recommended: 295 | 2026-07-24T02:40:43+00:00 | Vulnerability · Source |
| CVE-2026-23057 | suse_vex | SUSE CVE CVE-2026-23057 | first fixed: 2 known affected: 450 known not affected: 200 recommended: 295 | 2026-07-24T02:40:41+00:00 | Vulnerability · Source |
| CVE-2026-23058 | suse_vex | SUSE CVE CVE-2026-23058 | first fixed: 2 known affected: 451 known not affected: 11 recommended: 295 | 2026-07-24T02:40:39+00:00 | Vulnerability · Source |
| CVE-2026-23060 | suse_vex | SUSE CVE CVE-2026-23060 | first fixed: 2 known affected: 423 known not affected: 13 recommended: 627 | 2026-07-24T02:40:38+00:00 | Vulnerability · Source |
| CVE-2026-23063 | suse_vex | SUSE CVE CVE-2026-23063 | first fixed: 2 known affected: 482 known not affected: 144 recommended: 295 | 2026-07-24T02:40:36+00:00 | Vulnerability · Source |
| CVE-2026-23064 | suse_vex | SUSE CVE CVE-2026-23064 | first fixed: 2 known affected: 604 known not affected: 20 recommended: 318 | 2026-07-24T02:40:34+00:00 | Vulnerability · Source |
| CVE-2026-23068 | suse_vex | SUSE CVE CVE-2026-23068 | first fixed: 2 known affected: 518 known not affected: 93 recommended: 295 | 2026-07-24T02:40:32+00:00 | Vulnerability · Source |
| CVE-2026-23069 | suse_vex | SUSE CVE CVE-2026-23069 | first fixed: 2 known affected: 600 known not affected: 20 recommended: 318 | 2026-07-24T02:40:30+00:00 | Vulnerability · Source |
| CVE-2026-23071 | suse_vex | SUSE CVE CVE-2026-23071 | first fixed: 2 known affected: 513 known not affected: 90 recommended: 295 | 2026-07-24T02:40:28+00:00 | Vulnerability · Source |
| CVE-2026-23073 | suse_vex | SUSE CVE CVE-2026-23073 | first fixed: 2 known affected: 451 known not affected: 13 recommended: 295 | 2026-07-24T02:40:26+00:00 | Vulnerability · Source |
| CVE-2026-23074 | suse_vex | SUSE CVE CVE-2026-23074 | first fixed: 2 known affected: 432 recommended: 810 | 2026-07-24T02:40:24+00:00 | Vulnerability · Source |
| CVE-2026-23076 | suse_vex | SUSE CVE CVE-2026-23076 | first fixed: 2 known affected: 641 known not affected: 9 recommended: 295 | 2026-07-24T02:40:21+00:00 | Vulnerability · Source |
| CVE-2026-23078 | suse_vex | SUSE CVE CVE-2026-23078 | first fixed: 2 known affected: 529 known not affected: 121 recommended: 295 | 2026-07-24T02:40:19+00:00 | Vulnerability · Source |
| CVE-2026-23080 | suse_vex | SUSE CVE CVE-2026-23080 | first fixed: 2 known affected: 437 known not affected: 29 recommended: 295 | 2026-07-24T02:40:17+00:00 | Vulnerability · Source |
| CVE-2026-23082 | suse_vex | SUSE CVE CVE-2026-23082 | first fixed: 2 known affected: 394 known not affected: 256 recommended: 295 | 2026-07-24T02:40:15+00:00 | Vulnerability · Source |
| CVE-2026-23083 | suse_vex | SUSE CVE CVE-2026-23083 | first fixed: 2 known affected: 610 known not affected: 4 recommended: 318 | 2026-07-24T02:40:12+00:00 | Vulnerability · Source |
| CVE-2026-23084 | suse_vex | SUSE CVE CVE-2026-23084 | first fixed: 2 known affected: 618 recommended: 332 | 2026-07-24T02:40:10+00:00 | Vulnerability · Source |
| CVE-2026-23085 | suse_vex | SUSE CVE CVE-2026-23085 | first fixed: 2 known affected: 616 known not affected: 4 recommended: 318 | 2026-07-24T02:40:08+00:00 | Vulnerability · Source |
| CVE-2026-23086 | suse_vex | SUSE CVE CVE-2026-23086 | first fixed: 2 known affected: 600 known not affected: 20 recommended: 318 | 2026-07-24T02:40:06+00:00 | Vulnerability · Source |
| CVE-2026-23088 | suse_vex | SUSE CVE CVE-2026-23088 | first fixed: 2 known affected: 450 known not affected: 200 recommended: 295 | 2026-07-24T02:40:04+00:00 | Vulnerability · Source |
| CVE-2026-23089 | suse_vex | SUSE CVE CVE-2026-23089 | first fixed: 2 known affected: 423 known not affected: 9 recommended: 642 | 2026-07-24T02:40:02+00:00 | Vulnerability · Source |
| CVE-2026-23090 | suse_vex | SUSE CVE CVE-2026-23090 | first fixed: 2 known affected: 513 known not affected: 90 recommended: 295 | 2026-07-24T02:39:59+00:00 | Vulnerability · Source |
| CVE-2026-23091 | suse_vex | SUSE CVE CVE-2026-23091 | first fixed: 2 known affected: 637 known not affected: 13 recommended: 295 | 2026-07-24T02:39:57+00:00 | Vulnerability · Source |
| CVE-2026-23094 | suse_vex | SUSE CVE CVE-2026-23094 | first fixed: 2 known affected: 394 known not affected: 209 recommended: 295 | 2026-07-24T02:39:55+00:00 | Vulnerability · Source |
| CVE-2026-23095 | suse_vex | SUSE CVE CVE-2026-23095 | first fixed: 2 known affected: 614 known not affected: 4 recommended: 332 | 2026-07-24T02:39:52+00:00 | Vulnerability · Source |
| CVE-2026-23096 | suse_vex | SUSE CVE CVE-2026-23096 | first fixed: 2 known affected: 482 known not affected: 121 recommended: 295 | 2026-07-24T02:39:50+00:00 | Vulnerability · Source |
| CVE-2026-23099 | suse_vex | SUSE CVE CVE-2026-23099 | first fixed: 2 known affected: 618 recommended: 332 | 2026-07-24T02:39:49+00:00 | Vulnerability · Source |
| CVE-2026-23101 | suse_vex | SUSE CVE CVE-2026-23101 | first fixed: 2 known affected: 562 known not affected: 32 recommended: 295 | 2026-07-24T02:39:47+00:00 | Vulnerability · Source |
| CVE-2026-23102 | suse_vex | SUSE CVE CVE-2026-23102 | first fixed: 2 known affected: 454 known not affected: 200 recommended: 295 | 2026-07-24T02:39:45+00:00 | Vulnerability · Source |
| CVE-2026-23104 | suse_vex | SUSE CVE CVE-2026-23104 | first fixed: 2 known affected: 441 known not affected: 200 recommended: 295 | 2026-07-24T02:39:43+00:00 | Vulnerability · Source |