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-43156 | suse_vex | SUSE CVE CVE-2026-43156 | known affected: 649 known not affected: 17 recommended: 345 | 2026-10-17T00:38:02+00:00 | Vulnerability · Source |
| CVE-2026-43157 | suse_vex | SUSE CVE CVE-2026-43157 | known affected: 530 known not affected: 175 recommended: 308 | 2026-10-17T00:38:01+00:00 | Vulnerability · Source |
| CVE-2026-43158 | suse_vex | SUSE CVE CVE-2026-43158 | known affected: 641 known not affected: 4 recommended: 503 | 2026-10-17T00:37:59+00:00 | Vulnerability · Source |
| CVE-2026-43159 | suse_vex | SUSE CVE CVE-2026-43159 | known affected: 537 known not affected: 21 recommended: 308 | 2026-10-17T00:37:57+00:00 | Vulnerability · Source |
| CVE-2026-43162 | suse_vex | SUSE CVE CVE-2026-43162 | known affected: 542 known not affected: 192 recommended: 286 | 2026-10-17T00:37:55+00:00 | Vulnerability · Source |
| CVE-2026-43163 | suse_vex | SUSE CVE CVE-2026-43163 | known affected: 748 known not affected: 4 recommended: 368 | 2026-10-17T00:37:54+00:00 | Vulnerability · Source |
| CVE-2026-43167 | suse_vex | SUSE CVE CVE-2026-43167 | known affected: 699 known not affected: 6 recommended: 308 | 2026-10-17T00:37:52+00:00 | Vulnerability · Source |
| CVE-2026-43168 | suse_vex | SUSE CVE CVE-2026-43168 | known affected: 680 recommended: 331 | 2026-10-17T00:37:51+00:00 | Vulnerability · Source |
| CVE-2026-43169 | suse_vex | SUSE CVE CVE-2026-43169 | known affected: 426 known not affected: 294 recommended: 308 | 2026-10-17T00:37:49+00:00 | Vulnerability · Source |
| CVE-2026-43170 | suse_vex | SUSE CVE CVE-2026-43170 | known affected: 559 known not affected: 192 recommended: 308 | 2026-10-17T00:37:48+00:00 | Vulnerability · Source |
| CVE-2026-43171 | suse_vex | SUSE CVE CVE-2026-43171 | known affected: 556 known not affected: 149 recommended: 310 | 2026-10-17T00:37:46+00:00 | Vulnerability · Source |
| CVE-2026-43172 | suse_vex | SUSE CVE CVE-2026-43172 | known affected: 585 known not affected: 149 recommended: 308 | 2026-10-17T00:37:44+00:00 | Vulnerability · Source |
| CVE-2026-43176 | suse_vex | SUSE CVE CVE-2026-43176 | known affected: 0 known not affected: 385 recommended: 58 | 2026-10-17T00:37:42+00:00 | Vulnerability · Source |
| CVE-2026-43180 | suse_vex | SUSE CVE CVE-2026-43180 | known affected: 645 known not affected: 21 recommended: 345 | 2026-10-17T00:37:40+00:00 | Vulnerability · Source |
| CVE-2026-43182 | suse_vex | SUSE CVE CVE-2026-43182 | known affected: 701 known not affected: 21 recommended: 308 | 2026-10-17T00:37:38+00:00 | Vulnerability · Source |
| CVE-2026-43183 | suse_vex | SUSE CVE CVE-2026-43183 | known affected: 645 known not affected: 15 recommended: 308 | 2026-10-17T00:37:36+00:00 | Vulnerability · Source |
| CVE-2026-43186 | suse_vex | SUSE CVE CVE-2026-43186 | known affected: 0 known not affected: 401 recommended: 42 | 2026-10-17T00:37:35+00:00 | Vulnerability · Source |
| CVE-2026-43187 | suse_vex | SUSE CVE CVE-2026-43187 | known affected: 641 known not affected: 4 recommended: 347 | 2026-10-17T00:37:33+00:00 | Vulnerability · Source |
| CVE-2026-43189 | suse_vex | SUSE CVE CVE-2026-43189 | known affected: 396 known not affected: 336 recommended: 286 | 2026-10-17T00:37:31+00:00 | Vulnerability · Source |
| CVE-2026-43190 | suse_vex | SUSE CVE CVE-2026-43190 | known affected: 507 recommended: 856 | 2026-10-17T00:37:29+00:00 | Vulnerability · Source |
| CVE-2026-43194 | suse_vex | SUSE CVE CVE-2026-43194 | known affected: 701 known not affected: 4 recommended: 308 | 2026-10-17T00:37:27+00:00 | Vulnerability · Source |
| CVE-2026-43196 | suse_vex | SUSE CVE CVE-2026-43196 | known affected: 530 known not affected: 190 recommended: 308 | 2026-10-17T00:37:25+00:00 | Vulnerability · Source |
| CVE-2026-43197 | suse_vex | SUSE CVE CVE-2026-43197 | known affected: 396 known not affected: 370 recommended: 203 | 2026-10-17T00:37:24+00:00 | Vulnerability · Source |
| CVE-2026-43198 | suse_vex | SUSE CVE CVE-2026-43198 | known affected: 502 recommended: 708 | 2026-10-17T00:37:22+00:00 | Vulnerability · Source |
| CVE-2026-43199 | suse_vex | SUSE CVE CVE-2026-43199 | known affected: 426 known not affected: 279 recommended: 308 | 2026-10-17T00:37:20+00:00 | Vulnerability · Source |
| CVE-2026-43200 | suse_vex | SUSE CVE CVE-2026-43200 | known affected: 530 known not affected: 190 recommended: 308 | 2026-10-17T00:37:18+00:00 | Vulnerability · Source |
| CVE-2026-43202 | suse_vex | SUSE CVE CVE-2026-43202 | known affected: 701 known not affected: 21 recommended: 308 | 2026-10-17T00:37:16+00:00 | Vulnerability · Source |
| CVE-2026-43203 | suse_vex | SUSE CVE CVE-2026-43203 | known affected: 705 known not affected: 17 recommended: 308 | 2026-10-17T00:37:14+00:00 | Vulnerability · Source |
| CVE-2026-43205 | suse_vex | SUSE CVE CVE-2026-43205 | known affected: 530 known not affected: 175 recommended: 350 | 2026-10-17T00:37:13+00:00 | Vulnerability · Source |
| CVE-2026-43206 | suse_vex | SUSE CVE CVE-2026-43206 | known affected: 469 known not affected: 49 recommended: 750 | 2026-10-17T00:37:11+00:00 | Vulnerability · Source |
| CVE-2026-43207 | suse_vex | SUSE CVE CVE-2026-43207 | known affected: 699 known not affected: 23 recommended: 308 | 2026-10-17T00:37:10+00:00 | Vulnerability · Source |
| CVE-2026-43211 | suse_vex | SUSE CVE CVE-2026-43211 | known affected: 430 known not affected: 182 recommended: 413 | 2026-10-17T00:37:08+00:00 | Vulnerability · Source |
| CVE-2026-43213 | suse_vex | SUSE CVE CVE-2026-43213 | known affected: 571 known not affected: 175 recommended: 286 | 2026-10-17T00:37:06+00:00 | Vulnerability · Source |
| CVE-2026-43214 | suse_vex | SUSE CVE CVE-2026-43214 | known affected: 396 known not affected: 190 recommended: 503 | 2026-10-17T00:37:04+00:00 | Vulnerability · Source |
| CVE-2026-43215 | suse_vex | SUSE CVE CVE-2026-43215 | known affected: 394 known not affected: 91 recommended: 83 | 2026-10-17T00:37:03+00:00 | Vulnerability · Source |
| CVE-2026-43218 | suse_vex | SUSE CVE CVE-2026-43218 | known affected: 511 known not affected: 19 recommended: 308 | 2026-10-17T00:37:01+00:00 | Vulnerability · Source |
| CVE-2026-43220 | suse_vex | SUSE CVE CVE-2026-43220 | known affected: 396 known not affected: 324 recommended: 308 | 2026-10-17T00:36:59+00:00 | Vulnerability · Source |
| CVE-2026-43221 | suse_vex | SUSE CVE CVE-2026-43221 | known affected: 426 known not affected: 294 recommended: 308 | 2026-10-17T00:36:57+00:00 | Vulnerability · Source |
| CVE-2026-43222 | suse_vex | SUSE CVE CVE-2026-43222 | known affected: 396 known not affected: 336 recommended: 286 | 2026-10-17T00:36:56+00:00 | Vulnerability · Source |
| CVE-2026-43223 | suse_vex | SUSE CVE CVE-2026-43223 | known affected: 645 known not affected: 15 recommended: 308 | 2026-10-17T00:36:54+00:00 | Vulnerability · Source |
| CVE-2026-43225 | suse_vex | SUSE CVE CVE-2026-43225 | known affected: 699 known not affected: 23 recommended: 308 | 2026-10-17T00:36:53+00:00 | Vulnerability · Source |
| CVE-2026-43226 | suse_vex | SUSE CVE CVE-2026-43226 | known affected: 645 known not affected: 6 recommended: 331 | 2026-10-17T00:36:51+00:00 | Vulnerability · Source |
| CVE-2026-43230 | suse_vex | SUSE CVE CVE-2026-43230 | known affected: 680 recommended: 331 | 2026-10-17T00:36:49+00:00 | Vulnerability · Source |
| CVE-2026-43231 | suse_vex | SUSE CVE CVE-2026-43231 | known affected: 701 known not affected: 21 recommended: 308 | 2026-10-17T00:36:47+00:00 | Vulnerability · Source |
| CVE-2026-43232 | suse_vex | SUSE CVE CVE-2026-43232 | known affected: 426 known not affected: 294 recommended: 308 | 2026-10-17T00:36:46+00:00 | Vulnerability · Source |
| CVE-2026-43233 | suse_vex | SUSE CVE CVE-2026-43233 | known affected: 580 known not affected: 37 recommended: 406 | 2026-10-17T00:36:44+00:00 | Vulnerability · Source |
| CVE-2026-43234 | suse_vex | SUSE CVE CVE-2026-43234 | known affected: 641 known not affected: 4 recommended: 347 | 2026-10-17T00:36:42+00:00 | Vulnerability · Source |
| CVE-2026-43236 | suse_vex | SUSE CVE CVE-2026-43236 | known affected: 701 known not affected: 21 recommended: 308 | 2026-10-17T00:36:41+00:00 | Vulnerability · Source |
| CVE-2026-43237 | suse_vex | SUSE CVE CVE-2026-43237 | known affected: 0 known not affected: 385 recommended: 141 | 2026-10-17T00:36:39+00:00 | Vulnerability · Source |
| CVE-2026-43238 | suse_vex | SUSE CVE CVE-2026-43238 | known affected: 426 known not affected: 279 recommended: 308 | 2026-10-17T00:36:37+00:00 | Vulnerability · Source |