VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291900 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-3592 | suse_vex | SUSE CVE CVE-2026-3592 | known affected: 516 known not affected: 1 recommended: 212 | 2026-08-11T00:12:58+00:00 | Vulnerability · Source |
| CVE-2026-3593 | suse_vex | SUSE CVE CVE-2026-3593 | known affected: 411 known not affected: 194 recommended: 61 | 2026-08-11T00:12:57+00:00 | Vulnerability · Source |
| CVE-2026-4424 | suse_vex | SUSE CVE CVE-2026-4424 | known affected: 463 recommended: 84 | 2026-08-11T00:12:52+00:00 | Vulnerability · Source |
| CVE-2026-5121 | suse_vex | SUSE CVE CVE-2026-5121 | known affected: 458 known not affected: 5 recommended: 81 | 2026-08-11T00:12:43+00:00 | Vulnerability · Source |
| CVE-2026-5946 | suse_vex | SUSE CVE CVE-2026-5946 | known affected: 516 known not affected: 1 recommended: 263 | 2026-08-11T00:12:38+00:00 | Vulnerability · Source |
| CVE-2026-5950 | suse_vex | SUSE CVE CVE-2026-5950 | known affected: 411 known not affected: 194 recommended: 61 | 2026-08-11T00:12:35+00:00 | Vulnerability · Source |
| CVE-2026-6993 | suse_vex | SUSE CVE CVE-2026-6993 | No product status | 2026-08-11T00:12:29+00:00 | Vulnerability · Source |
| CVE-2026-7009 | suse_vex | SUSE CVE CVE-2026-7009 | known not affected: 151 | 2026-08-11T00:12:27+00:00 | Vulnerability · Source |
| CVE-2026-7819 | suse_vex | SUSE CVE CVE-2026-7819 | known affected: 75 | 2026-08-11T00:12:21+00:00 | Vulnerability · Source |
| CVE-2026-8763 | suse_vex | SUSE CVE CVE-2026-8763 | first fixed: 16 known affected: 16 recommended: 80 | 2026-08-11T00:12:15+00:00 | Vulnerability · Source |
| CVE-2026-10822 | suse_vex | SUSE CVE CVE-2026-10822 | known affected: 394 known not affected: 168 recommended: 53 | 2026-08-11T00:12:04+00:00 | Vulnerability · Source |
| CVE-2026-12045 | suse_vex | SUSE CVE CVE-2026-12045 | known not affected: 75 | 2026-08-11T00:11:49+00:00 | Vulnerability · Source |
| CVE-2026-12185 | suse_vex | SUSE CVE CVE-2026-12185 | first fixed: 16 known affected: 16 recommended: 80 | 2026-08-11T00:11:46+00:00 | Vulnerability · Source |
| CVE-2026-12617 | suse_vex | SUSE CVE CVE-2026-12617 | known affected: 394 known not affected: 168 recommended: 53 | 2026-08-11T00:11:43+00:00 | Vulnerability · Source |
| CVE-2026-12802 | suse_vex | SUSE CVE CVE-2026-12802 | first fixed: 16 known affected: 16 recommended: 80 | 2026-08-11T00:11:42+00:00 | Vulnerability · Source |
| CVE-2026-12803 | suse_vex | SUSE CVE CVE-2026-12803 | first fixed: 16 known affected: 16 recommended: 80 | 2026-08-11T00:11:41+00:00 | Vulnerability · Source |
| CVE-2026-12816 | suse_vex | SUSE CVE CVE-2026-12816 | first fixed: 16 known affected: 16 recommended: 80 | 2026-08-11T00:11:39+00:00 | Vulnerability · Source |
| CVE-2026-12817 | suse_vex | SUSE CVE CVE-2026-12817 | first fixed: 16 known affected: 16 recommended: 80 | 2026-08-11T00:11:38+00:00 | Vulnerability · Source |
| CVE-2026-12852 | suse_vex | SUSE CVE CVE-2026-12852 | first fixed: 16 known affected: 16 recommended: 80 | 2026-08-11T00:11:36+00:00 | Vulnerability · Source |
| CVE-2026-12860 | suse_vex | SUSE CVE CVE-2026-12860 | first fixed: 16 known affected: 16 recommended: 80 | 2026-08-11T00:11:35+00:00 | Vulnerability · Source |
| CVE-2026-13506 | suse_vex | SUSE CVE CVE-2026-13506 | first fixed: 16 known affected: 16 recommended: 80 | 2026-08-11T00:11:30+00:00 | Vulnerability · Source |
| CVE-2026-13586 | suse_vex | SUSE CVE CVE-2026-13586 | first fixed: 16 known affected: 16 recommended: 80 | 2026-08-11T00:11:29+00:00 | Vulnerability · Source |
| CVE-2026-14682 | suse_vex | SUSE CVE CVE-2026-14682 | first fixed: 16 known affected: 16 recommended: 80 | 2026-08-11T00:11:24+00:00 | Vulnerability · Source |
| CVE-2026-15055 | suse_vex | SUSE CVE CVE-2026-15055 | first fixed: 16 known affected: 16 recommended: 80 | 2026-08-11T00:11:22+00:00 | Vulnerability · Source |
| CVE-2026-15059 | suse_vex | SUSE CVE CVE-2026-15059 | known affected: 80 known not affected: 255 | 2026-08-11T00:11:20+00:00 | Vulnerability · Source |
| CVE-2026-15060 | suse_vex | SUSE CVE CVE-2026-15060 | known not affected: 410 | 2026-08-11T00:11:18+00:00 | Vulnerability · Source |
| CVE-2026-16349 | suse_vex | SUSE CVE CVE-2026-16349 | first fixed: 8 known affected: 24 recommended: 116 | 2026-08-11T00:11:12+00:00 | Vulnerability · Source |
| CVE-2026-16353 | suse_vex | SUSE CVE CVE-2026-16353 | first fixed: 8 known affected: 24 recommended: 116 | 2026-08-11T00:11:10+00:00 | Vulnerability · Source |
| CVE-2026-16362 | suse_vex | SUSE CVE CVE-2026-16362 | first fixed: 8 known affected: 24 recommended: 116 | 2026-08-11T00:11:09+00:00 | Vulnerability · Source |
| CVE-2026-16364 | suse_vex | SUSE CVE CVE-2026-16364 | known affected: 24 recommended: 9 | 2026-08-11T00:11:07+00:00 | Vulnerability · Source |
| CVE-2026-16365 | suse_vex | SUSE CVE CVE-2026-16365 | known affected: 24 recommended: 9 | 2026-08-11T00:11:05+00:00 | Vulnerability · Source |
| CVE-2026-16376 | suse_vex | SUSE CVE CVE-2026-16376 | known affected: 24 recommended: 9 | 2026-08-11T00:11:04+00:00 | Vulnerability · Source |
| CVE-2026-16380 | suse_vex | SUSE CVE CVE-2026-16380 | known affected: 24 recommended: 9 | 2026-08-11T00:11:02+00:00 | Vulnerability · Source |
| CVE-2026-16389 | suse_vex | SUSE CVE CVE-2026-16389 | known affected: 24 recommended: 9 | 2026-08-11T00:11:00+00:00 | Vulnerability · Source |
| CVE-2026-16392 | suse_vex | SUSE CVE CVE-2026-16392 | known affected: 24 recommended: 9 | 2026-08-11T00:10:59+00:00 | Vulnerability · Source |
| CVE-2026-16397 | suse_vex | SUSE CVE CVE-2026-16397 | known affected: 24 recommended: 9 | 2026-08-11T00:10:57+00:00 | Vulnerability · Source |
| CVE-2026-16402 | suse_vex | SUSE CVE CVE-2026-16402 | known affected: 24 recommended: 9 | 2026-08-11T00:10:55+00:00 | Vulnerability · Source |
| CVE-2026-16406 | suse_vex | SUSE CVE CVE-2026-16406 | known affected: 24 recommended: 9 | 2026-08-11T00:10:52+00:00 | Vulnerability · Source |
| CVE-2026-16408 | suse_vex | SUSE CVE CVE-2026-16408 | known affected: 24 recommended: 9 | 2026-08-11T00:10:51+00:00 | Vulnerability · Source |
| CVE-2026-16409 | suse_vex | SUSE CVE CVE-2026-16409 | known affected: 24 recommended: 9 | 2026-08-11T00:10:49+00:00 | Vulnerability · Source |
| CVE-2026-16742 | suse_vex | SUSE CVE CVE-2026-16742 | known affected: 77 known not affected: 337 | 2026-08-11T00:10:39+00:00 | Vulnerability · Source |
| CVE-2026-22815 | suse_vex | SUSE CVE CVE-2026-22815 | known affected: 396 recommended: 46 | 2026-08-11T00:10:35+00:00 | Vulnerability · Source |
| CVE-2026-23631 | suse_vex | SUSE CVE CVE-2026-23631 | known not affected: 13 recommended: 49 | 2026-08-11T00:10:24+00:00 | Vulnerability · Source |
| CVE-2026-24450 | suse_vex | SUSE CVE CVE-2026-24450 | known not affected: 25 recommended: 31 | 2026-08-11T00:10:22+00:00 | Vulnerability · Source |
| CVE-2026-24451 | suse_vex | SUSE CVE CVE-2026-24451 | No product status | 2026-08-11T00:10:20+00:00 | Vulnerability · Source |
| CVE-2026-25038 | suse_vex | SUSE CVE CVE-2026-25038 | No product status | 2026-08-11T00:10:17+00:00 | Vulnerability · Source |
| CVE-2026-25707 | suse_vex | SUSE CVE CVE-2026-25707 | first fixed: 54 known affected: 412 recommended: 351 | 2026-08-11T00:10:13+00:00 | Vulnerability · Source |
| CVE-2026-27951 | suse_vex | SUSE CVE CVE-2026-27951 | known affected: 27 recommended: 110 | 2026-08-11T00:10:09+00:00 | Vulnerability · Source |
| CVE-2026-30246 | suse_vex | SUSE CVE CVE-2026-30246 | No product status | 2026-08-11T00:10:07+00:00 | Vulnerability · Source |
| CVE-2026-33174 | suse_vex | SUSE CVE CVE-2026-33174 | known not affected: 98 | 2026-08-11T00:09:56+00:00 | Vulnerability · Source |