VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
303784 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-43011 | suse_vex | SUSE CVE CVE-2026-43011 | known affected: 396 known not affected: 336 recommended: 250 | 2026-10-01T01:27:15+00:00 | Vulnerability · Source |
| CVE-2026-43014 | suse_vex | SUSE CVE CVE-2026-43014 | known affected: 740 known not affected: 4 recommended: 255 | 2026-10-01T01:27:12+00:00 | Vulnerability · Source |
| CVE-2026-43015 | suse_vex | SUSE CVE CVE-2026-43015 | known affected: 285 known not affected: 65 recommended: 255 | 2026-10-01T01:27:10+00:00 | Vulnerability · Source |
| CVE-2026-43016 | suse_vex | SUSE CVE CVE-2026-43016 | known affected: 513 known not affected: 219 recommended: 277 | 2026-10-01T01:27:07+00:00 | Vulnerability · Source |
| CVE-2026-43017 | suse_vex | SUSE CVE CVE-2026-43017 | known affected: 426 known not affected: 292 recommended: 250 | 2026-10-01T01:27:05+00:00 | Vulnerability · Source |
| CVE-2026-43018 | suse_vex | SUSE CVE CVE-2026-43018 | known affected: 484 known not affected: 234 recommended: 250 | 2026-10-01T01:27:02+00:00 | Vulnerability · Source |
| CVE-2026-43019 | suse_vex | SUSE CVE CVE-2026-43019 | known affected: 426 known not affected: 294 recommended: 250 | 2026-10-01T01:26:59+00:00 | Vulnerability · Source |
| CVE-2026-43020 | suse_vex | SUSE CVE CVE-2026-43020 | known affected: 641 known not affected: 19 recommended: 390 | 2026-10-01T01:26:56+00:00 | Vulnerability · Source |
| CVE-2026-43022 | suse_vex | SUSE CVE CVE-2026-43022 | known affected: 426 known not affected: 277 recommended: 250 | 2026-10-01T01:26:52+00:00 | Vulnerability · Source |
| CVE-2026-43023 | suse_vex | SUSE CVE CVE-2026-43023 | known affected: 396 known not affected: 294 recommended: 366 | 2026-10-01T01:26:49+00:00 | Vulnerability · Source |
| CVE-2026-43024 | suse_vex | SUSE CVE CVE-2026-43024 | known affected: 641 known not affected: 4 recommended: 302 | 2026-10-01T01:26:47+00:00 | Vulnerability · Source |
| CVE-2026-43028 | suse_vex | SUSE CVE CVE-2026-43028 | known affected: 641 known not affected: 4 recommended: 302 | 2026-10-01T01:26:45+00:00 | Vulnerability · Source |
| CVE-2026-43032 | suse_vex | SUSE CVE CVE-2026-43032 | known affected: 530 known not affected: 188 recommended: 250 | 2026-10-01T01:26:43+00:00 | Vulnerability · Source |
| CVE-2026-43033 | suse_vex | SUSE CVE CVE-2026-43033 | known affected: 91 known not affected: 82 recommended: 414 | 2026-10-01T01:26:41+00:00 | Vulnerability · Source |
| CVE-2026-43034 | suse_vex | SUSE CVE CVE-2026-43034 | known affected: 426 known not affected: 277 recommended: 250 | 2026-10-01T01:26:39+00:00 | Vulnerability · Source |
| CVE-2026-43035 | suse_vex | SUSE CVE CVE-2026-43035 | known affected: 613 known not affected: 32 recommended: 302 | 2026-10-01T01:26:37+00:00 | Vulnerability · Source |
| CVE-2026-43036 | suse_vex | SUSE CVE CVE-2026-43036 | known affected: 641 known not affected: 4 recommended: 302 | 2026-10-01T01:26:35+00:00 | Vulnerability · Source |
| CVE-2026-43043 | suse_vex | SUSE CVE CVE-2026-43043 | known affected: 645 known not affected: 15 recommended: 287 | 2026-10-01T01:26:33+00:00 | Vulnerability · Source |
| CVE-2026-43044 | suse_vex | SUSE CVE CVE-2026-43044 | known affected: 396 known not affected: 292 recommended: 284 | 2026-10-01T01:26:31+00:00 | Vulnerability · Source |
| CVE-2026-43046 | suse_vex | SUSE CVE CVE-2026-43046 | known affected: 673 known not affected: 46 recommended: 281 | 2026-10-01T01:26:29+00:00 | Vulnerability · Source |
| CVE-2026-43047 | suse_vex | SUSE CVE CVE-2026-43047 | known affected: 641 known not affected: 19 recommended: 287 | 2026-10-01T01:26:27+00:00 | Vulnerability · Source |
| CVE-2026-43049 | suse_vex | SUSE CVE CVE-2026-43049 | known affected: 580 known not affected: 138 recommended: 252 | 2026-10-01T01:26:25+00:00 | Vulnerability · Source |
| CVE-2026-43051 | suse_vex | SUSE CVE CVE-2026-43051 | known affected: 641 known not affected: 19 recommended: 390 | 2026-10-01T01:26:23+00:00 | Vulnerability · Source |
| CVE-2026-43052 | suse_vex | SUSE CVE CVE-2026-43052 | known affected: 641 known not affected: 19 recommended: 289 | 2026-10-01T01:26:21+00:00 | Vulnerability · Source |
| CVE-2026-43053 | suse_vex | SUSE CVE CVE-2026-43053 | known affected: 530 known not affected: 175 recommended: 279 | 2026-10-01T01:26:19+00:00 | Vulnerability · Source |
| CVE-2026-43055 | suse_vex | SUSE CVE CVE-2026-43055 | known not affected: 383 | 2026-10-01T01:26:17+00:00 | Vulnerability · Source |
| CVE-2026-43056 | suse_vex | SUSE CVE CVE-2026-43056 | known affected: 446 known not affected: 217 recommended: 452 | 2026-10-01T01:26:15+00:00 | Vulnerability · Source |
| CVE-2026-43057 | suse_vex | SUSE CVE CVE-2026-43057 | known affected: 426 known not affected: 277 recommended: 250 | 2026-10-01T01:26:13+00:00 | Vulnerability · Source |
| CVE-2026-43058 | suse_vex | SUSE CVE CVE-2026-43058 | known affected: 530 known not affected: 190 recommended: 254 | 2026-10-01T01:26:12+00:00 | Vulnerability · Source |
| CVE-2026-43059 | suse_vex | SUSE CVE CVE-2026-43059 | known affected: 484 known not affected: 236 recommended: 252 | 2026-10-01T01:26:10+00:00 | Vulnerability · Source |
| CVE-2026-43061 | suse_vex | SUSE CVE CVE-2026-43061 | known affected: 426 known not affected: 294 recommended: 250 | 2026-10-01T01:26:08+00:00 | Vulnerability · Source |
| CVE-2026-43062 | suse_vex | SUSE CVE CVE-2026-43062 | known affected: 556 known not affected: 164 recommended: 250 | 2026-10-01T01:26:06+00:00 | Vulnerability · Source |
| CVE-2026-43064 | suse_vex | SUSE CVE CVE-2026-43064 | known affected: 530 known not affected: 190 recommended: 250 | 2026-10-01T01:26:04+00:00 | Vulnerability · Source |
| CVE-2026-43069 | suse_vex | SUSE CVE CVE-2026-43069 | known affected: 645 known not affected: 23 recommended: 273 | 2026-10-01T01:26:02+00:00 | Vulnerability · Source |
| CVE-2026-43072 | suse_vex | SUSE CVE CVE-2026-43072 | known affected: 484 known not affected: 236 recommended: 254 | 2026-10-01T01:26:00+00:00 | Vulnerability · Source |
| CVE-2026-43074 | suse_vex | SUSE CVE CVE-2026-43074 | known affected: 396 known not affected: 279 recommended: 395 | 2026-10-01T01:25:58+00:00 | Vulnerability · Source |
| CVE-2026-43077 | suse_vex | SUSE CVE CVE-2026-43077 | known affected: 502 known not affected: 21 recommended: 751 | 2026-10-01T01:25:56+00:00 | Vulnerability · Source |
| CVE-2026-43079 | suse_vex | SUSE CVE CVE-2026-43079 | known affected: 530 known not affected: 175 recommended: 250 | 2026-10-01T01:25:54+00:00 | Vulnerability · Source |
| CVE-2026-43080 | suse_vex | SUSE CVE CVE-2026-43080 | known affected: 645 recommended: 287 | 2026-10-01T01:25:52+00:00 | Vulnerability · Source |
| CVE-2026-43081 | suse_vex | SUSE CVE CVE-2026-43081 | known affected: 426 known not affected: 279 recommended: 250 | 2026-10-01T01:25:50+00:00 | Vulnerability · Source |
| CVE-2026-43083 | suse_vex | SUSE CVE CVE-2026-43083 | known affected: 426 known not affected: 279 recommended: 279 | 2026-10-01T01:25:48+00:00 | Vulnerability · Source |
| CVE-2026-43085 | suse_vex | SUSE CVE CVE-2026-43085 | known affected: 705 recommended: 250 | 2026-10-01T01:25:46+00:00 | Vulnerability · Source |
| CVE-2026-43086 | suse_vex | SUSE CVE CVE-2026-43086 | known affected: 484 known not affected: 221 recommended: 250 | 2026-10-01T01:25:45+00:00 | Vulnerability · Source |
| CVE-2026-43089 | suse_vex | SUSE CVE CVE-2026-43089 | known affected: 645 recommended: 287 | 2026-10-01T01:25:43+00:00 | Vulnerability · Source |
| CVE-2026-43090 | suse_vex | SUSE CVE CVE-2026-43090 | known affected: 2 known not affected: 370 recommended: 145 | 2026-10-01T01:25:41+00:00 | Vulnerability · Source |
| CVE-2026-43091 | suse_vex | SUSE CVE CVE-2026-43091 | known affected: 366 known not affected: 6 recommended: 145 | 2026-10-01T01:25:39+00:00 | Vulnerability · Source |
| CVE-2026-43092 | suse_vex | SUSE CVE CVE-2026-43092 | known affected: 426 known not affected: 279 recommended: 250 | 2026-10-01T01:25:37+00:00 | Vulnerability · Source |
| CVE-2026-43093 | suse_vex | SUSE CVE CVE-2026-43093 | known affected: 613 known not affected: 34 recommended: 273 | 2026-10-01T01:25:35+00:00 | Vulnerability · Source |
| CVE-2026-43094 | suse_vex | SUSE CVE CVE-2026-43094 | known affected: 396 known not affected: 321 recommended: 228 | 2026-10-01T01:25:33+00:00 | Vulnerability · Source |
| CVE-2026-43095 | suse_vex | SUSE CVE CVE-2026-43095 | known not affected: 385 | 2026-10-01T01:25:31+00:00 | Vulnerability · Source |