VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294018 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2026-23105 | suse_vex | SUSE CVE CVE-2026-23105 | first fixed: 2 known affected: 614 known not affected: 4 recommended: 332 | 2026-07-24T02:39:41+00:00 | Vulnerability · Source |
| CVE-2026-23107 | suse_vex | SUSE CVE CVE-2026-23107 | first fixed: 2 known affected: 403 known not affected: 200 recommended: 295 | 2026-07-24T02:39:39+00:00 | Vulnerability · Source |
| CVE-2026-23110 | suse_vex | SUSE CVE CVE-2026-23110 | first fixed: 2 known affected: 538 known not affected: 112 recommended: 336 | 2026-07-24T02:39:37+00:00 | Vulnerability · Source |
| CVE-2026-23112 | suse_vex | SUSE CVE CVE-2026-23112 | first fixed: 2 known affected: 586 known not affected: 34 recommended: 318 | 2026-07-24T02:39:34+00:00 | Vulnerability · Source |
| CVE-2026-23116 | suse_vex | SUSE CVE CVE-2026-23116 | first fixed: 2 known affected: 450 known not affected: 200 recommended: 295 | 2026-07-24T02:39:32+00:00 | Vulnerability · Source |
| CVE-2026-23119 | suse_vex | SUSE CVE CVE-2026-23119 | first fixed: 2 known affected: 538 known not affected: 112 recommended: 295 | 2026-07-24T02:39:30+00:00 | Vulnerability · Source |
| CVE-2026-23129 | suse_vex | SUSE CVE CVE-2026-23129 | first fixed: 2 known affected: 394 known not affected: 209 recommended: 295 | 2026-07-24T02:39:27+00:00 | Vulnerability · Source |
| CVE-2026-23133 | suse_vex | SUSE CVE CVE-2026-23133 | first fixed: 2 known affected: 577 known not affected: 43 recommended: 295 | 2026-07-24T02:39:25+00:00 | Vulnerability · Source |
| CVE-2026-23135 | suse_vex | SUSE CVE CVE-2026-23135 | first fixed: 2 known affected: 394 known not affected: 256 recommended: 295 | 2026-07-24T02:39:24+00:00 | Vulnerability · Source |
| CVE-2026-23136 | suse_vex | SUSE CVE CVE-2026-23136 | first fixed: 2 known affected: 498 known not affected: 152 recommended: 336 | 2026-07-24T02:39:22+00:00 | Vulnerability · Source |
| CVE-2026-23139 | suse_vex | SUSE CVE CVE-2026-23139 | first fixed: 2 known affected: 450 known not affected: 200 recommended: 295 | 2026-07-24T02:39:20+00:00 | Vulnerability · Source |
| CVE-2026-23141 | suse_vex | SUSE CVE CVE-2026-23141 | first fixed: 2 known affected: 553 known not affected: 20 recommended: 413 | 2026-07-24T02:39:18+00:00 | Vulnerability · Source |
| CVE-2026-23145 | suse_vex | SUSE CVE CVE-2026-23145 | first fixed: 2 known affected: 394 known not affected: 256 recommended: 295 | 2026-07-24T02:39:17+00:00 | Vulnerability · Source |
| CVE-2026-23146 | suse_vex | SUSE CVE CVE-2026-23146 | first fixed: 2 known affected: 394 known not affected: 209 recommended: 378 | 2026-07-24T02:39:15+00:00 | Vulnerability · Source |
| CVE-2026-23150 | suse_vex | SUSE CVE CVE-2026-23150 | first fixed: 2 known affected: 605 known not affected: 13 recommended: 295 | 2026-07-24T02:39:14+00:00 | Vulnerability · Source |
| CVE-2026-23151 | suse_vex | SUSE CVE CVE-2026-23151 | first fixed: 2 known affected: 442 known not affected: 161 recommended: 295 | 2026-07-24T02:39:12+00:00 | Vulnerability · Source |
| CVE-2026-23152 | suse_vex | SUSE CVE CVE-2026-23152 | first fixed: 2 known affected: 394 known not affected: 256 recommended: 295 | 2026-07-24T02:39:10+00:00 | Vulnerability · Source |
| CVE-2026-23154 | suse_vex | SUSE CVE CVE-2026-23154 | first fixed: 2 known affected: 538 known not affected: 112 recommended: 295 | 2026-07-24T02:39:08+00:00 | Vulnerability · Source |
| CVE-2026-23155 | suse_vex | SUSE CVE CVE-2026-23155 | first fixed: 2 known affected: 451 known not affected: 222 recommended: 295 | 2026-07-24T02:39:07+00:00 | Vulnerability · Source |
| CVE-2026-23156 | suse_vex | SUSE CVE CVE-2026-23156 | first fixed: 2 known affected: 489 known not affected: 184 recommended: 337 | 2026-07-24T02:39:05+00:00 | Vulnerability · Source |
| CVE-2026-23163 | suse_vex | SUSE CVE CVE-2026-23163 | first fixed: 2 known affected: 450 known not affected: 227 recommended: 295 | 2026-07-24T02:39:03+00:00 | Vulnerability · Source |
| CVE-2026-23166 | suse_vex | SUSE CVE CVE-2026-23166 | first fixed: 2 known affected: 450 known not affected: 200 recommended: 295 | 2026-07-24T02:39:01+00:00 | Vulnerability · Source |
| CVE-2026-23167 | suse_vex | SUSE CVE CVE-2026-23167 | first fixed: 2 known affected: 605 known not affected: 72 recommended: 295 | 2026-07-24T02:39:00+00:00 | Vulnerability · Source |
| CVE-2026-23169 | suse_vex | SUSE CVE CVE-2026-23169 | first fixed: 2 known affected: 538 known not affected: 112 recommended: 295 | 2026-07-24T02:38:56+00:00 | Vulnerability · Source |
| CVE-2026-23170 | suse_vex | SUSE CVE CVE-2026-23170 | first fixed: 2 known affected: 394 known not affected: 239 recommended: 295 | 2026-07-24T02:38:55+00:00 | Vulnerability · Source |
| CVE-2026-23172 | suse_vex | SUSE CVE CVE-2026-23172 | first fixed: 2 known affected: 441 known not affected: 209 recommended: 295 | 2026-07-24T02:38:51+00:00 | Vulnerability · Source |
| CVE-2026-23173 | suse_vex | SUSE CVE CVE-2026-23173 | first fixed: 2 known affected: 450 known not affected: 200 recommended: 295 | 2026-07-24T02:38:49+00:00 | Vulnerability · Source |