VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104648 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-43059 | suse_vex | SUSE CVE CVE-2026-43059 | known affected: 484 known not affected: 236 recommended: 310 | 2026-10-17T00:39:27+00:00 | Vulnerability · Source |
| CVE-2026-43060 | suse_vex | SUSE CVE CVE-2026-43060 | known affected: 580 known not affected: 125 recommended: 311 | 2026-10-17T00:39:26+00:00 | Vulnerability · Source |
| CVE-2026-43061 | suse_vex | SUSE CVE CVE-2026-43061 | known affected: 426 known not affected: 294 recommended: 308 | 2026-10-17T00:39:24+00:00 | Vulnerability · Source |
| CVE-2026-43062 | suse_vex | SUSE CVE CVE-2026-43062 | known affected: 556 known not affected: 164 recommended: 308 | 2026-10-17T00:39:23+00:00 | Vulnerability · Source |
| CVE-2026-43063 | suse_vex | SUSE CVE CVE-2026-43063 | known affected: 396 known not affected: 370 recommended: 203 | 2026-10-17T00:39:21+00:00 | Vulnerability · Source |
| CVE-2026-43064 | suse_vex | SUSE CVE CVE-2026-43064 | known affected: 530 known not affected: 190 recommended: 308 | 2026-10-17T00:39:20+00:00 | Vulnerability · Source |
| CVE-2026-43065 | suse_vex | SUSE CVE CVE-2026-43065 | known affected: 426 known not affected: 279 recommended: 310 | 2026-10-17T00:39:18+00:00 | Vulnerability · Source |
| CVE-2026-43066 | suse_vex | SUSE CVE CVE-2026-43066 | known affected: 530 known not affected: 175 recommended: 310 | 2026-10-17T00:39:17+00:00 | Vulnerability · Source |
| CVE-2026-43067 | suse_vex | SUSE CVE CVE-2026-43067 | known affected: 0 known not affected: 385 | 2026-10-17T00:39:15+00:00 | Vulnerability · Source |
| CVE-2026-43068 | suse_vex | SUSE CVE CVE-2026-43068 | known affected: 647 known not affected: 4 recommended: 333 | 2026-10-17T00:39:14+00:00 | Vulnerability · Source |
| CVE-2026-43069 | suse_vex | SUSE CVE CVE-2026-43069 | known affected: 645 known not affected: 23 recommended: 331 | 2026-10-17T00:39:12+00:00 | Vulnerability · Source |
| CVE-2026-43072 | suse_vex | SUSE CVE CVE-2026-43072 | known affected: 484 known not affected: 236 recommended: 312 | 2026-10-17T00:39:11+00:00 | Vulnerability · Source |
| CVE-2026-43077 | suse_vex | SUSE CVE CVE-2026-43077 | known affected: 502 known not affected: 21 recommended: 850 | 2026-10-17T00:39:09+00:00 | Vulnerability · Source |
| CVE-2026-43078 | suse_vex | SUSE CVE CVE-2026-43078 | known affected: 381 known not affected: 6 recommended: 58 | 2026-10-17T00:39:07+00:00 | Vulnerability · Source |
| CVE-2026-43079 | suse_vex | SUSE CVE CVE-2026-43079 | known affected: 530 known not affected: 175 recommended: 308 | 2026-10-17T00:39:06+00:00 | Vulnerability · Source |
| CVE-2026-43081 | suse_vex | SUSE CVE CVE-2026-43081 | known affected: 426 known not affected: 279 recommended: 308 | 2026-10-17T00:39:03+00:00 | Vulnerability · Source |
| CVE-2026-43083 | suse_vex | SUSE CVE CVE-2026-43083 | known affected: 426 known not affected: 279 recommended: 310 | 2026-10-17T00:39:01+00:00 | Vulnerability · Source |
| CVE-2026-43084 | suse_vex | SUSE CVE CVE-2026-43084 | known affected: 0 known not affected: 385 | 2026-10-17T00:38:59+00:00 | Vulnerability · Source |
| CVE-2026-43086 | suse_vex | SUSE CVE CVE-2026-43086 | known affected: 484 known not affected: 221 recommended: 308 | 2026-10-17T00:38:57+00:00 | Vulnerability · Source |
| CVE-2026-43088 | suse_vex | SUSE CVE CVE-2026-43088 | known affected: 645 recommended: 348 | 2026-10-17T00:38:56+00:00 | Vulnerability · Source |
| CVE-2026-43091 | suse_vex | SUSE CVE CVE-2026-43091 | known affected: 366 known not affected: 6 recommended: 203 | 2026-10-17T00:38:54+00:00 | Vulnerability · Source |
| CVE-2026-43092 | suse_vex | SUSE CVE CVE-2026-43092 | known affected: 426 known not affected: 279 recommended: 308 | 2026-10-17T00:38:53+00:00 | Vulnerability · Source |
| CVE-2026-43098 | suse_vex | SUSE CVE CVE-2026-43098 | known affected: 530 known not affected: 190 recommended: 308 | 2026-10-17T00:38:50+00:00 | Vulnerability · Source |
| CVE-2026-43101 | suse_vex | SUSE CVE CVE-2026-43101 | known affected: 426 known not affected: 279 recommended: 310 | 2026-10-17T00:38:48+00:00 | Vulnerability · Source |
| CVE-2026-43104 | suse_vex | SUSE CVE CVE-2026-43104 | known affected: 699 known not affected: 23 recommended: 308 | 2026-10-17T00:38:46+00:00 | Vulnerability · Source |
| CVE-2026-43105 | suse_vex | SUSE CVE CVE-2026-43105 | known affected: 699 known not affected: 23 recommended: 308 | 2026-10-17T00:38:45+00:00 | Vulnerability · Source |
| CVE-2026-43107 | suse_vex | SUSE CVE CVE-2026-43107 | known affected: 580 known not affected: 125 recommended: 308 | 2026-10-17T00:38:43+00:00 | Vulnerability · Source |
| CVE-2026-43113 | suse_vex | SUSE CVE CVE-2026-43113 | known affected: 705 known not affected: 17 recommended: 308 | 2026-10-17T00:38:40+00:00 | Vulnerability · Source |
| CVE-2026-43118 | suse_vex | SUSE CVE CVE-2026-43118 | known affected: 590 known not affected: 130 recommended: 308 | 2026-10-17T00:38:38+00:00 | Vulnerability · Source |
| CVE-2026-43119 | suse_vex | SUSE CVE CVE-2026-43119 | known affected: 580 known not affected: 142 recommended: 310 | 2026-10-17T00:38:36+00:00 | Vulnerability · Source |
| CVE-2026-43120 | suse_vex | SUSE CVE CVE-2026-43120 | known affected: 396 known not affected: 294 recommended: 488 | 2026-10-17T00:38:35+00:00 | Vulnerability · Source |
| CVE-2026-43123 | suse_vex | SUSE CVE CVE-2026-43123 | known affected: 649 known not affected: 17 recommended: 345 | 2026-10-17T00:38:33+00:00 | Vulnerability · Source |
| CVE-2026-43124 | suse_vex | SUSE CVE CVE-2026-43124 | known affected: 645 known not affected: 6 recommended: 331 | 2026-10-17T00:38:32+00:00 | Vulnerability · Source |
| CVE-2026-43125 | suse_vex | SUSE CVE CVE-2026-43125 | known affected: 693 known not affected: 4 recommended: 402 | 2026-10-17T00:38:30+00:00 | Vulnerability · Source |
| CVE-2026-43126 | suse_vex | SUSE CVE CVE-2026-43126 | known affected: 507 known not affected: 15 recommended: 555 | 2026-10-17T00:38:29+00:00 | Vulnerability · Source |
| CVE-2026-43128 | suse_vex | SUSE CVE CVE-2026-43128 | known affected: 530 known not affected: 175 recommended: 444 | 2026-10-17T00:38:27+00:00 | Vulnerability · Source |
| CVE-2026-43129 | suse_vex | SUSE CVE CVE-2026-43129 | known affected: 32 known not affected: 279 recommended: 308 | 2026-10-17T00:38:25+00:00 | Vulnerability · Source |
| CVE-2026-43133 | suse_vex | SUSE CVE CVE-2026-43133 | known affected: 530 known not affected: 175 recommended: 411 | 2026-10-17T00:38:23+00:00 | Vulnerability · Source |
| CVE-2026-43134 | suse_vex | SUSE CVE CVE-2026-43134 | known affected: 647 known not affected: 21 recommended: 331 | 2026-10-17T00:38:21+00:00 | Vulnerability · Source |
| CVE-2026-43135 | suse_vex | SUSE CVE CVE-2026-43135 | known affected: 641 known not affected: 19 recommended: 308 | 2026-10-17T00:38:19+00:00 | Vulnerability · Source |
| CVE-2026-43136 | suse_vex | SUSE CVE CVE-2026-43136 | known affected: 580 known not affected: 140 recommended: 308 | 2026-10-17T00:38:17+00:00 | Vulnerability · Source |
| CVE-2026-43137 | suse_vex | SUSE CVE CVE-2026-43137 | known affected: 484 known not affected: 238 recommended: 308 | 2026-10-17T00:38:15+00:00 | Vulnerability · Source |
| CVE-2026-43139 | suse_vex | SUSE CVE CVE-2026-43139 | known affected: 645 recommended: 345 | 2026-10-17T00:38:14+00:00 | Vulnerability · Source |
| CVE-2026-43140 | suse_vex | SUSE CVE CVE-2026-43140 | known affected: 645 known not affected: 15 recommended: 345 | 2026-10-17T00:38:13+00:00 | Vulnerability · Source |
| CVE-2026-43141 | suse_vex | SUSE CVE CVE-2026-43141 | known affected: 476 known not affected: 140 recommended: 308 | 2026-10-17T00:38:11+00:00 | Vulnerability · Source |
| CVE-2026-43143 | suse_vex | SUSE CVE CVE-2026-43143 | known affected: 530 known not affected: 190 recommended: 308 | 2026-10-17T00:38:10+00:00 | Vulnerability · Source |
| CVE-2026-43149 | suse_vex | SUSE CVE CVE-2026-43149 | known affected: 715 known not affected: 6 recommended: 105 | 2026-10-17T00:38:08+00:00 | Vulnerability · Source |
| CVE-2026-43150 | suse_vex | SUSE CVE CVE-2026-43150 | known affected: 396 known not affected: 321 recommended: 286 | 2026-10-17T00:38:07+00:00 | Vulnerability · Source |
| CVE-2026-43152 | suse_vex | SUSE CVE CVE-2026-43152 | known affected: 705 known not affected: 17 recommended: 308 | 2026-10-17T00:38:05+00:00 | Vulnerability · Source |
| CVE-2026-43153 | suse_vex | SUSE CVE CVE-2026-43153 | known affected: 542 known not affected: 224 recommended: 203 | 2026-10-17T00:38:04+00:00 | Vulnerability · Source |