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-43207 | suse_vex | SUSE CVE CVE-2026-43207 | known affected: 699 known not affected: 23 recommended: 250 | 2026-10-01T01:22:57+00:00 | Vulnerability · Source |
| CVE-2026-43211 | suse_vex | SUSE CVE CVE-2026-43211 | known affected: 430 known not affected: 182 recommended: 355 | 2026-10-01T01:22:55+00:00 | Vulnerability · Source |
| CVE-2026-43213 | suse_vex | SUSE CVE CVE-2026-43213 | known affected: 571 known not affected: 175 recommended: 228 | 2026-10-01T01:22:52+00:00 | Vulnerability · Source |
| CVE-2026-43214 | suse_vex | SUSE CVE CVE-2026-43214 | known affected: 396 known not affected: 190 recommended: 445 | 2026-10-01T01:22:49+00:00 | Vulnerability · Source |
| CVE-2026-43216 | suse_vex | SUSE CVE CVE-2026-43216 | known affected: 676 known not affected: 4 recommended: 273 | 2026-10-01T01:22:47+00:00 | Vulnerability · Source |
| CVE-2026-43218 | suse_vex | SUSE CVE CVE-2026-43218 | known affected: 511 known not affected: 19 recommended: 250 | 2026-10-01T01:22:45+00:00 | Vulnerability · Source |
| CVE-2026-43220 | suse_vex | SUSE CVE CVE-2026-43220 | known affected: 396 known not affected: 324 recommended: 250 | 2026-10-01T01:22:43+00:00 | Vulnerability · Source |
| CVE-2026-43221 | suse_vex | SUSE CVE CVE-2026-43221 | known affected: 426 known not affected: 294 recommended: 250 | 2026-10-01T01:22:40+00:00 | Vulnerability · Source |
| CVE-2026-43222 | suse_vex | SUSE CVE CVE-2026-43222 | known affected: 396 known not affected: 336 recommended: 228 | 2026-10-01T01:22:38+00:00 | Vulnerability · Source |
| CVE-2026-43223 | suse_vex | SUSE CVE CVE-2026-43223 | known affected: 645 known not affected: 15 recommended: 250 | 2026-10-01T01:22:35+00:00 | Vulnerability · Source |
| CVE-2026-43225 | suse_vex | SUSE CVE CVE-2026-43225 | known affected: 699 known not affected: 23 recommended: 250 | 2026-10-01T01:22:32+00:00 | Vulnerability · Source |
| CVE-2026-43226 | suse_vex | SUSE CVE CVE-2026-43226 | known affected: 645 known not affected: 6 recommended: 273 | 2026-10-01T01:22:29+00:00 | Vulnerability · Source |
| CVE-2026-43229 | suse_vex | SUSE CVE CVE-2026-43229 | known affected: 2 known not affected: 385 recommended: 145 | 2026-10-01T01:22:27+00:00 | Vulnerability · Source |
| CVE-2026-43230 | suse_vex | SUSE CVE CVE-2026-43230 | known affected: 680 recommended: 273 | 2026-10-01T01:22:24+00:00 | Vulnerability · Source |
| CVE-2026-43231 | suse_vex | SUSE CVE CVE-2026-43231 | known affected: 701 known not affected: 21 recommended: 250 | 2026-10-01T01:22:20+00:00 | Vulnerability · Source |
| CVE-2026-43232 | suse_vex | SUSE CVE CVE-2026-43232 | known affected: 426 known not affected: 294 recommended: 250 | 2026-10-01T01:22:18+00:00 | Vulnerability · Source |
| CVE-2026-43233 | suse_vex | SUSE CVE CVE-2026-43233 | known affected: 580 known not affected: 37 recommended: 348 | 2026-10-01T01:22:15+00:00 | Vulnerability · Source |
| CVE-2026-43236 | suse_vex | SUSE CVE CVE-2026-43236 | known affected: 701 known not affected: 21 recommended: 250 | 2026-10-01T01:22:12+00:00 | Vulnerability · Source |
| CVE-2026-43238 | suse_vex | SUSE CVE CVE-2026-43238 | known affected: 426 known not affected: 279 recommended: 250 | 2026-10-01T01:22:11+00:00 | Vulnerability · Source |
| CVE-2026-43240 | suse_vex | SUSE CVE CVE-2026-43240 | known affected: 426 known not affected: 279 recommended: 250 | 2026-10-01T01:22:09+00:00 | Vulnerability · Source |
| CVE-2026-43241 | suse_vex | SUSE CVE CVE-2026-43241 | known affected: 446 known not affected: 142 recommended: 250 | 2026-10-01T01:22:07+00:00 | Vulnerability · Source |
| CVE-2026-43242 | suse_vex | SUSE CVE CVE-2026-43242 | known affected: 426 known not affected: 294 recommended: 250 | 2026-10-01T01:22:05+00:00 | Vulnerability · Source |
| CVE-2026-43243 | suse_vex | SUSE CVE CVE-2026-43243 | known affected: 396 known not affected: 336 recommended: 228 | 2026-10-01T01:22:03+00:00 | Vulnerability · Source |
| CVE-2026-43244 | suse_vex | SUSE CVE CVE-2026-43244 | known affected: 645 known not affected: 6 recommended: 273 | 2026-10-01T01:22:01+00:00 | Vulnerability · Source |
| CVE-2026-43246 | suse_vex | SUSE CVE CVE-2026-43246 | known affected: 701 known not affected: 21 recommended: 250 | 2026-10-01T01:21:59+00:00 | Vulnerability · Source |
| CVE-2026-43247 | suse_vex | SUSE CVE CVE-2026-43247 | known not affected: 385 | 2026-10-01T01:21:57+00:00 | Vulnerability · Source |
| CVE-2026-43248 | suse_vex | SUSE CVE CVE-2026-43248 | known affected: 426 known not affected: 279 recommended: 333 | 2026-10-01T01:21:55+00:00 | Vulnerability · Source |
| CVE-2026-43249 | suse_vex | SUSE CVE CVE-2026-43249 | known affected: 426 known not affected: 296 recommended: 252 | 2026-10-01T01:21:52+00:00 | Vulnerability · Source |
| CVE-2026-43250 | suse_vex | SUSE CVE CVE-2026-43250 | known affected: 372 known not affected: 17 recommended: 145 | 2026-10-01T01:21:50+00:00 | Vulnerability · Source |
| CVE-2026-43251 | suse_vex | SUSE CVE CVE-2026-43251 | known affected: 396 known not affected: 324 recommended: 250 | 2026-10-01T01:21:48+00:00 | Vulnerability · Source |
| CVE-2026-43253 | suse_vex | SUSE CVE CVE-2026-43253 | known affected: 396 known not affected: 270 recommended: 273 | 2026-10-01T01:21:45+00:00 | Vulnerability · Source |
| CVE-2026-43255 | suse_vex | SUSE CVE CVE-2026-43255 | known affected: 645 known not affected: 15 recommended: 287 | 2026-10-01T01:21:43+00:00 | Vulnerability · Source |
| CVE-2026-43256 | suse_vex | SUSE CVE CVE-2026-43256 | known affected: 426 known not affected: 294 recommended: 250 | 2026-10-01T01:21:39+00:00 | Vulnerability · Source |
| CVE-2026-43257 | suse_vex | SUSE CVE CVE-2026-43257 | known affected: 647 known not affected: 21 recommended: 273 | 2026-10-01T01:21:37+00:00 | Vulnerability · Source |
| CVE-2026-43260 | suse_vex | SUSE CVE CVE-2026-43260 | known affected: 396 known not affected: 321 recommended: 311 | 2026-10-01T01:21:35+00:00 | Vulnerability · Source |
| CVE-2026-43261 | suse_vex | SUSE CVE CVE-2026-43261 | known affected: 607 known not affected: 113 recommended: 252 | 2026-10-01T01:21:32+00:00 | Vulnerability · Source |
| CVE-2026-43262 | suse_vex | SUSE CVE CVE-2026-43262 | known affected: 734 recommended: 250 | 2026-10-01T01:21:30+00:00 | Vulnerability · Source |
| CVE-2026-43264 | suse_vex | SUSE CVE CVE-2026-43264 | known affected: 641 known not affected: 21 recommended: 273 | 2026-10-01T01:21:28+00:00 | Vulnerability · Source |
| CVE-2026-43266 | suse_vex | SUSE CVE CVE-2026-43266 | known affected: 609 known not affected: 71 recommended: 273 | 2026-10-01T01:21:26+00:00 | Vulnerability · Source |
| CVE-2026-43267 | suse_vex | SUSE CVE CVE-2026-43267 | known not affected: 385 | 2026-10-01T01:21:24+00:00 | Vulnerability · Source |
| CVE-2026-43269 | suse_vex | SUSE CVE CVE-2026-43269 | known affected: 509 known not affected: 211 recommended: 250 | 2026-10-01T01:21:21+00:00 | Vulnerability · Source |
| CVE-2026-43270 | suse_vex | SUSE CVE CVE-2026-43270 | known affected: 699 known not affected: 23 recommended: 250 | 2026-10-01T01:21:19+00:00 | Vulnerability · Source |
| CVE-2026-43273 | suse_vex | SUSE CVE CVE-2026-43273 | known affected: 676 known not affected: 4 recommended: 275 | 2026-10-01T01:21:16+00:00 | Vulnerability · Source |
| CVE-2026-43275 | suse_vex | SUSE CVE CVE-2026-43275 | known affected: 368 known not affected: 4 recommended: 145 | 2026-10-01T01:21:14+00:00 | Vulnerability · Source |
| CVE-2026-43276 | suse_vex | SUSE CVE CVE-2026-43276 | known affected: 396 known not affected: 269 recommended: 432 | 2026-10-01T01:21:12+00:00 | Vulnerability · Source |
| CVE-2026-43277 | suse_vex | SUSE CVE CVE-2026-43277 | known affected: 651 known not affected: 17 recommended: 273 | 2026-10-01T01:21:09+00:00 | Vulnerability · Source |
| CVE-2026-43278 | suse_vex | SUSE CVE CVE-2026-43278 | known affected: 426 known not affected: 296 recommended: 252 | 2026-10-01T01:21:07+00:00 | Vulnerability · Source |
| CVE-2026-43279 | suse_vex | SUSE CVE CVE-2026-43279 | known affected: 641 known not affected: 19 recommended: 405 | 2026-10-01T01:21:05+00:00 | Vulnerability · Source |
| CVE-2026-43281 | suse_vex | SUSE CVE CVE-2026-43281 | known affected: 676 known not affected: 4 recommended: 273 | 2026-10-01T01:21:03+00:00 | Vulnerability · Source |
| CVE-2026-43282 | suse_vex | SUSE CVE CVE-2026-43282 | known not affected: 385 | 2026-10-01T01:21:01+00:00 | Vulnerability · Source |