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-23266 | suse_vex | SUSE CVE CVE-2026-23266 | first fixed: 2 known affected: 61 known not affected: 204 recommended: 268 | 2026-07-24T02:38:02+00:00 | Vulnerability · Source |
| CVE-2026-23273 | suse_vex | SUSE CVE CVE-2026-23273 | first fixed: 2 known not affected: 102 recommended: 483 | 2026-07-24T02:37:59+00:00 | Vulnerability · Source |
| CVE-2026-23277 | suse_vex | SUSE CVE CVE-2026-23277 | first fixed: 2 known affected: 600 known not affected: 20 recommended: 291 | 2026-07-24T02:37:56+00:00 | Vulnerability · Source |
| CVE-2026-23278 | suse_vex | SUSE CVE CVE-2026-23278 | first fixed: 2 known affected: 403 known not affected: 198 recommended: 398 | 2026-07-24T02:37:55+00:00 | Vulnerability · Source |
| CVE-2026-23279 | suse_vex | SUSE CVE CVE-2026-23279 | first fixed: 2 known affected: 605 known not affected: 28 recommended: 298 | 2026-07-24T02:37:53+00:00 | Vulnerability · Source |
| CVE-2026-23290 | suse_vex | SUSE CVE CVE-2026-23290 | first fixed: 2 known affected: 223 known not affected: 16 recommended: 325 | 2026-07-24T02:37:51+00:00 | Vulnerability · Source |
| CVE-2026-23291 | suse_vex | SUSE CVE CVE-2026-23291 | first fixed: 2 known affected: 241 known not affected: 30 recommended: 268 | 2026-07-24T02:37:49+00:00 | Vulnerability · Source |
| CVE-2026-23293 | suse_vex | SUSE CVE CVE-2026-23293 | first fixed: 2 known affected: 562 known not affected: 4 recommended: 335 | 2026-07-24T02:37:47+00:00 | Vulnerability · Source |
| CVE-2026-23298 | suse_vex | SUSE CVE CVE-2026-23298 | first fixed: 2 known affected: 61 known not affected: 99 recommended: 268 | 2026-07-24T02:37:45+00:00 | Vulnerability · Source |
| CVE-2026-23300 | suse_vex | SUSE CVE CVE-2026-23300 | first fixed: 2 known affected: 156 known not affected: 94 recommended: 268 | 2026-07-24T02:37:43+00:00 | Vulnerability · Source |
| CVE-2026-23307 | suse_vex | SUSE CVE CVE-2026-23307 | first fixed: 2 known affected: 104 known not affected: 165 recommended: 268 | 2026-07-24T02:37:40+00:00 | Vulnerability · Source |
| CVE-2026-23308 | suse_vex | SUSE CVE CVE-2026-23308 | known affected: 9 known not affected: 260 recommended: 123 | 2026-07-24T02:37:39+00:00 | Vulnerability · Source |
| CVE-2026-23312 | suse_vex | SUSE CVE CVE-2026-23312 | first fixed: 2 known affected: 219 known not affected: 24 recommended: 298 | 2026-07-24T02:37:37+00:00 | Vulnerability · Source |
| CVE-2026-23315 | suse_vex | SUSE CVE CVE-2026-23315 | first fixed: 2 known affected: 135 known not affected: 130 recommended: 268 | 2026-07-24T02:37:35+00:00 | Vulnerability · Source |
| CVE-2026-23317 | suse_vex | SUSE CVE CVE-2026-23317 | first fixed: 2 known affected: 376 known not affected: 174 recommended: 489 | 2026-07-24T02:37:33+00:00 | Vulnerability · Source |
| CVE-2026-23318 | suse_vex | SUSE CVE CVE-2026-23318 | first fixed: 2 known affected: 577 known not affected: 58 recommended: 291 | 2026-07-24T02:37:31+00:00 | Vulnerability · Source |
| CVE-2026-23324 | suse_vex | SUSE CVE CVE-2026-23324 | first fixed: 2 known affected: 135 known not affected: 130 recommended: 268 | 2026-07-24T02:37:29+00:00 | Vulnerability · Source |
| CVE-2026-23325 | suse_vex | SUSE CVE CVE-2026-23325 | first fixed: 2 known affected: 47 known not affected: 218 recommended: 268 | 2026-07-24T02:37:27+00:00 | Vulnerability · Source |
| CVE-2026-23336 | suse_vex | SUSE CVE CVE-2026-23336 | first fixed: 2 known affected: 245 known not affected: 26 recommended: 268 | 2026-07-24T02:37:25+00:00 | Vulnerability · Source |
| CVE-2026-23339 | suse_vex | SUSE CVE CVE-2026-23339 | first fixed: 2 known affected: 104 known not affected: 28 recommended: 268 | 2026-07-24T02:37:23+00:00 | Vulnerability · Source |
| CVE-2026-23357 | suse_vex | SUSE CVE CVE-2026-23357 | first fixed: 2 known not affected: 265 recommended: 268 | 2026-07-24T02:37:20+00:00 | Vulnerability · Source |
| CVE-2026-23362 | suse_vex | SUSE CVE CVE-2026-23362 | first fixed: 2 known affected: 443 known not affected: 192 recommended: 291 | 2026-07-24T02:37:18+00:00 | Vulnerability · Source |
| CVE-2026-23363 | suse_vex | SUSE CVE CVE-2026-23363 | first fixed: 2 known affected: 47 known not affected: 218 recommended: 268 | 2026-07-24T02:37:16+00:00 | Vulnerability · Source |
| CVE-2026-23365 | suse_vex | SUSE CVE CVE-2026-23365 | first fixed: 2 known affected: 47 known not affected: 20 recommended: 268 | 2026-07-24T02:37:14+00:00 | Vulnerability · Source |
| CVE-2026-23367 | suse_vex | SUSE CVE CVE-2026-23367 | first fixed: 2 known affected: 609 known not affected: 24 recommended: 298 | 2026-07-24T02:37:13+00:00 | Vulnerability · Source |
| CVE-2026-23370 | suse_vex | SUSE CVE CVE-2026-23370 | first fixed: 2 known affected: 135 known not affected: 130 recommended: 268 | 2026-07-24T02:37:10+00:00 | Vulnerability · Source |
| CVE-2026-23372 | suse_vex | SUSE CVE CVE-2026-23372 | first fixed: 2 known affected: 211 known not affected: 28 recommended: 268 | 2026-07-24T02:37:09+00:00 | Vulnerability · Source |
| CVE-2026-23373 | suse_vex | SUSE CVE CVE-2026-23373 | first fixed: 2 known affected: 47 known not affected: 218 recommended: 268 | 2026-07-24T02:37:07+00:00 | Vulnerability · Source |
| CVE-2026-23382 | suse_vex | SUSE CVE CVE-2026-23382 | first fixed: 2 known affected: 595 known not affected: 40 recommended: 291 | 2026-07-24T02:37:04+00:00 | Vulnerability · Source |
| CVE-2026-23403 | suse_vex | SUSE CVE CVE-2026-23403 | first fixed: 2 known affected: 437 known not affected: 44 recommended: 490 | 2026-07-24T02:36:57+00:00 | Vulnerability · Source |
| CVE-2026-23404 | suse_vex | SUSE CVE CVE-2026-23404 | first fixed: 2 known affected: 451 known not affected: 443 recommended: 490 | 2026-07-24T02:36:55+00:00 | Vulnerability · Source |
| CVE-2026-23405 | suse_vex | SUSE CVE CVE-2026-23405 | first fixed: 2 known affected: 443 known not affected: 40 recommended: 483 | 2026-07-24T02:36:53+00:00 | Vulnerability · Source |
| CVE-2026-23406 | suse_vex | SUSE CVE CVE-2026-23406 | first fixed: 2 known affected: 406 known not affected: 518 recommended: 460 | 2026-07-24T02:36:51+00:00 | Vulnerability · Source |
| CVE-2026-23407 | suse_vex | SUSE CVE CVE-2026-23407 | first fixed: 2 known affected: 406 known not affected: 518 recommended: 460 | 2026-07-24T02:36:49+00:00 | Vulnerability · Source |
| CVE-2026-23408 | suse_vex | SUSE CVE CVE-2026-23408 | first fixed: 2 known affected: 437 known not affected: 459 recommended: 483 | 2026-07-24T02:36:48+00:00 | Vulnerability · Source |
| CVE-2026-23409 | suse_vex | SUSE CVE CVE-2026-23409 | first fixed: 2 known affected: 406 known not affected: 489 recommended: 460 | 2026-07-24T02:36:46+00:00 | Vulnerability · Source |
| CVE-2026-23410 | suse_vex | SUSE CVE CVE-2026-23410 | first fixed: 2 known affected: 442 known not affected: 482 recommended: 460 | 2026-07-24T02:36:44+00:00 | Vulnerability · Source |
| CVE-2026-23411 | suse_vex | SUSE CVE CVE-2026-23411 | first fixed: 2 known affected: 442 known not affected: 482 recommended: 460 | 2026-07-24T02:36:43+00:00 | Vulnerability · Source |
| CVE-2026-23412 | suse_vex | SUSE CVE CVE-2026-23412 | known affected: 406 known not affected: 184 recommended: 181 | 2026-07-24T02:36:41+00:00 | Vulnerability · Source |
| CVE-2026-23413 | suse_vex | SUSE CVE CVE-2026-23413 | first fixed: 2 known affected: 406 known not affected: 184 recommended: 326 | 2026-07-24T02:36:39+00:00 | Vulnerability · Source |
| CVE-2026-23414 | suse_vex | SUSE CVE CVE-2026-23414 | first fixed: 2 known affected: 453 known not affected: 184 recommended: 295 | 2026-07-24T02:36:38+00:00 | Vulnerability · Source |
| CVE-2026-23419 | suse_vex | SUSE CVE CVE-2026-23419 | first fixed: 2 known affected: 452 known not affected: 184 recommended: 295 | 2026-07-24T02:36:36+00:00 | Vulnerability · Source |
| CVE-2026-23420 | suse_vex | SUSE CVE CVE-2026-23420 | first fixed: 2 known affected: 166 known not affected: 74 recommended: 268 | 2026-07-24T02:36:34+00:00 | Vulnerability · Source |
| CVE-2026-23426 | suse_vex | SUSE CVE CVE-2026-23426 | first fixed: 2 known affected: 95 known not affected: 145 recommended: 268 | 2026-07-24T02:36:32+00:00 | Vulnerability · Source |
| CVE-2026-23434 | suse_vex | SUSE CVE CVE-2026-23434 | first fixed: 2 known affected: 135 known not affected: 117 recommended: 268 | 2026-07-24T02:36:31+00:00 | Vulnerability · Source |
| CVE-2026-23438 | suse_vex | SUSE CVE CVE-2026-23438 | first fixed: 2 known affected: 544 known not affected: 96 recommended: 294 | 2026-07-24T02:36:29+00:00 | Vulnerability · Source |
| CVE-2026-23440 | suse_vex | SUSE CVE CVE-2026-23440 | first fixed: 2 known affected: 58 known not affected: 184 recommended: 295 | 2026-07-24T02:36:27+00:00 | Vulnerability · Source |
| CVE-2026-23441 | suse_vex | SUSE CVE CVE-2026-23441 | first fixed: 2 known affected: 30 known not affected: 206 recommended: 268 | 2026-07-24T02:36:26+00:00 | Vulnerability · Source |
| CVE-2026-23442 | suse_vex | SUSE CVE CVE-2026-23442 | first fixed: 2 known affected: 208 known not affected: 6 recommended: 318 | 2026-07-24T02:36:24+00:00 | Vulnerability · Source |
| CVE-2026-23443 | suse_vex | SUSE CVE CVE-2026-23443 | first fixed: 2 known not affected: 240 recommended: 268 | 2026-07-24T02:36:22+00:00 | Vulnerability · Source |