VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
303796 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-43097 | suse_vex | SUSE CVE CVE-2026-43097 | known not affected: 387 | 2026-10-01T01:25:28+00:00 | Vulnerability · Source |
| CVE-2026-43098 | suse_vex | SUSE CVE CVE-2026-43098 | known affected: 530 known not affected: 190 recommended: 250 | 2026-10-01T01:25:26+00:00 | Vulnerability · Source |
| CVE-2026-43101 | suse_vex | SUSE CVE CVE-2026-43101 | known affected: 426 known not affected: 279 recommended: 279 | 2026-10-01T01:25:24+00:00 | Vulnerability · Source |
| CVE-2026-43104 | suse_vex | SUSE CVE CVE-2026-43104 | known affected: 699 known not affected: 23 recommended: 250 | 2026-10-01T01:25:22+00:00 | Vulnerability · Source |
| CVE-2026-43105 | suse_vex | SUSE CVE CVE-2026-43105 | known affected: 699 known not affected: 23 recommended: 250 | 2026-10-01T01:25:20+00:00 | Vulnerability · Source |
| CVE-2026-43107 | suse_vex | SUSE CVE CVE-2026-43107 | known affected: 580 known not affected: 125 recommended: 250 | 2026-10-01T01:25:18+00:00 | Vulnerability · Source |
| CVE-2026-43108 | suse_vex | SUSE CVE CVE-2026-43108 | known affected: 2 known not affected: 385 recommended: 145 | 2026-10-01T01:25:16+00:00 | Vulnerability · Source |
| CVE-2026-43110 | suse_vex | SUSE CVE CVE-2026-43110 | known affected: 507 known not affected: 21 recommended: 740 | 2026-10-01T01:25:14+00:00 | Vulnerability · Source |
| CVE-2026-43111 | suse_vex | SUSE CVE CVE-2026-43111 | known affected: 705 known not affected: 17 recommended: 250 | 2026-10-01T01:25:11+00:00 | Vulnerability · Source |
| CVE-2026-43113 | suse_vex | SUSE CVE CVE-2026-43113 | known affected: 705 known not affected: 17 recommended: 250 | 2026-10-01T01:25:09+00:00 | Vulnerability · Source |
| CVE-2026-43114 | suse_vex | SUSE CVE CVE-2026-43114 | known affected: 585 known not affected: 149 recommended: 291 | 2026-10-01T01:25:07+00:00 | Vulnerability · Source |
| CVE-2026-43117 | suse_vex | SUSE CVE CVE-2026-43117 | known affected: 645 known not affected: 15 recommended: 287 | 2026-10-01T01:25:04+00:00 | Vulnerability · Source |
| CVE-2026-43118 | suse_vex | SUSE CVE CVE-2026-43118 | known affected: 590 known not affected: 130 recommended: 250 | 2026-10-01T01:25:01+00:00 | Vulnerability · Source |
| CVE-2026-43119 | suse_vex | SUSE CVE CVE-2026-43119 | known affected: 580 known not affected: 142 recommended: 279 | 2026-10-01T01:24:58+00:00 | Vulnerability · Source |
| CVE-2026-43120 | suse_vex | SUSE CVE CVE-2026-43120 | known affected: 396 known not affected: 294 recommended: 430 | 2026-10-01T01:24:56+00:00 | Vulnerability · Source |
| CVE-2026-43123 | suse_vex | SUSE CVE CVE-2026-43123 | known affected: 649 known not affected: 17 recommended: 287 | 2026-10-01T01:24:53+00:00 | Vulnerability · Source |
| CVE-2026-43124 | suse_vex | SUSE CVE CVE-2026-43124 | known affected: 645 known not affected: 6 recommended: 273 | 2026-10-01T01:24:51+00:00 | Vulnerability · Source |
| CVE-2026-43125 | suse_vex | SUSE CVE CVE-2026-43125 | known affected: 693 known not affected: 4 recommended: 361 | 2026-10-01T01:24:49+00:00 | Vulnerability · Source |
| CVE-2026-43126 | suse_vex | SUSE CVE CVE-2026-43126 | known affected: 507 known not affected: 15 recommended: 497 | 2026-10-01T01:24:47+00:00 | Vulnerability · Source |
| CVE-2026-43128 | suse_vex | SUSE CVE CVE-2026-43128 | known affected: 530 known not affected: 175 recommended: 345 | 2026-10-01T01:24:45+00:00 | Vulnerability · Source |
| CVE-2026-43129 | suse_vex | SUSE CVE CVE-2026-43129 | known affected: 32 known not affected: 279 recommended: 250 | 2026-10-01T01:24:43+00:00 | Vulnerability · Source |
| CVE-2026-43130 | suse_vex | SUSE CVE CVE-2026-43130 | known affected: 139 known not affected: 87 | 2026-10-01T01:24:42+00:00 | Vulnerability · Source |
| CVE-2026-43132 | suse_vex | SUSE CVE CVE-2026-43132 | known affected: 368 known not affected: 4 recommended: 145 | 2026-10-01T01:24:40+00:00 | Vulnerability · Source |
| CVE-2026-43133 | suse_vex | SUSE CVE CVE-2026-43133 | known affected: 530 known not affected: 175 recommended: 353 | 2026-10-01T01:24:36+00:00 | Vulnerability · Source |
| CVE-2026-43134 | suse_vex | SUSE CVE CVE-2026-43134 | known affected: 647 known not affected: 21 recommended: 273 | 2026-10-01T01:24:33+00:00 | Vulnerability · Source |
| CVE-2026-43135 | suse_vex | SUSE CVE CVE-2026-43135 | known affected: 641 known not affected: 19 recommended: 250 | 2026-10-01T01:24:31+00:00 | Vulnerability · Source |
| CVE-2026-43136 | suse_vex | SUSE CVE CVE-2026-43136 | known affected: 580 known not affected: 140 recommended: 250 | 2026-10-01T01:24:29+00:00 | Vulnerability · Source |
| CVE-2026-43137 | suse_vex | SUSE CVE CVE-2026-43137 | known affected: 484 known not affected: 238 recommended: 250 | 2026-10-01T01:24:27+00:00 | Vulnerability · Source |
| CVE-2026-43138 | suse_vex | SUSE CVE CVE-2026-43138 | known affected: 2 known not affected: 385 recommended: 145 | 2026-10-01T01:24:26+00:00 | Vulnerability · Source |
| CVE-2026-43139 | suse_vex | SUSE CVE CVE-2026-43139 | known affected: 645 recommended: 287 | 2026-10-01T01:24:24+00:00 | Vulnerability · Source |
| CVE-2026-43140 | suse_vex | SUSE CVE CVE-2026-43140 | known affected: 645 known not affected: 15 recommended: 287 | 2026-10-01T01:24:22+00:00 | Vulnerability · Source |
| CVE-2026-43141 | suse_vex | SUSE CVE CVE-2026-43141 | known affected: 476 known not affected: 140 recommended: 250 | 2026-10-01T01:24:20+00:00 | Vulnerability · Source |
| CVE-2026-43143 | suse_vex | SUSE CVE CVE-2026-43143 | known affected: 530 known not affected: 190 recommended: 250 | 2026-10-01T01:24:17+00:00 | Vulnerability · Source |
| CVE-2026-43144 | suse_vex | SUSE CVE CVE-2026-43144 | known not affected: 385 | 2026-10-01T01:24:14+00:00 | Vulnerability · Source |
| CVE-2026-43145 | suse_vex | SUSE CVE CVE-2026-43145 | known affected: 2 known not affected: 370 recommended: 145 | 2026-10-01T01:24:11+00:00 | Vulnerability · Source |
| CVE-2026-43147 | suse_vex | SUSE CVE CVE-2026-43147 | known affected: 454 known not affected: 238 recommended: 281 | 2026-10-01T01:24:09+00:00 | Vulnerability · Source |
| CVE-2026-43152 | suse_vex | SUSE CVE CVE-2026-43152 | known affected: 705 known not affected: 17 recommended: 250 | 2026-10-01T01:24:06+00:00 | Vulnerability · Source |
| CVE-2026-43156 | suse_vex | SUSE CVE CVE-2026-43156 | known affected: 649 known not affected: 17 recommended: 287 | 2026-10-01T01:24:03+00:00 | Vulnerability · Source |
| CVE-2026-43157 | suse_vex | SUSE CVE CVE-2026-43157 | known affected: 530 known not affected: 175 recommended: 250 | 2026-10-01T01:24:01+00:00 | Vulnerability · Source |
| CVE-2026-43158 | suse_vex | SUSE CVE CVE-2026-43158 | known affected: 641 known not affected: 4 recommended: 434 | 2026-10-01T01:23:57+00:00 | Vulnerability · Source |
| CVE-2026-43159 | suse_vex | SUSE CVE CVE-2026-43159 | known affected: 537 known not affected: 21 recommended: 250 | 2026-10-01T01:23:54+00:00 | Vulnerability · Source |
| CVE-2026-43161 | suse_vex | SUSE CVE CVE-2026-43161 | known affected: 187 known not affected: 39 | 2026-10-01T01:23:54+00:00 | Vulnerability · Source |
| CVE-2026-43162 | suse_vex | SUSE CVE CVE-2026-43162 | known affected: 542 known not affected: 192 recommended: 228 | 2026-10-01T01:23:52+00:00 | Vulnerability · Source |
| CVE-2026-43167 | suse_vex | SUSE CVE CVE-2026-43167 | known affected: 699 known not affected: 6 recommended: 250 | 2026-10-01T01:23:50+00:00 | Vulnerability · Source |
| CVE-2026-43168 | suse_vex | SUSE CVE CVE-2026-43168 | known affected: 680 recommended: 273 | 2026-10-01T01:23:48+00:00 | Vulnerability · Source |
| CVE-2026-43169 | suse_vex | SUSE CVE CVE-2026-43169 | known affected: 426 known not affected: 294 recommended: 250 | 2026-10-01T01:23:46+00:00 | Vulnerability · Source |
| CVE-2026-43170 | suse_vex | SUSE CVE CVE-2026-43170 | known affected: 559 known not affected: 192 recommended: 250 | 2026-10-01T01:23:44+00:00 | Vulnerability · Source |
| CVE-2026-43171 | suse_vex | SUSE CVE CVE-2026-43171 | known affected: 556 known not affected: 149 recommended: 279 | 2026-10-01T01:23:43+00:00 | Vulnerability · Source |
| CVE-2026-43172 | suse_vex | SUSE CVE CVE-2026-43172 | known affected: 585 known not affected: 149 recommended: 250 | 2026-10-01T01:23:41+00:00 | Vulnerability · Source |
| CVE-2026-43175 | suse_vex | SUSE CVE CVE-2026-43175 | known affected: 2 known not affected: 370 recommended: 145 | 2026-10-01T01:23:39+00:00 | Vulnerability · Source |