VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291933 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-25800 | suse_vex | SUSE CVE CVE-2026-25800 | known affected: 112 known not affected: 643 | 2026-08-03T23:49:29+00:00 | Vulnerability · Source |
| CVE-2026-30922 | suse_vex | SUSE CVE CVE-2026-30922 | known affected: 394 recommended: 246 | 2026-08-03T23:49:17+00:00 | Vulnerability · Source |
| CVE-2026-31442 | suse_vex | SUSE CVE CVE-2026-31442 | known not affected: 324 | 2026-08-03T23:49:07+00:00 | Vulnerability · Source |
| CVE-2026-31443 | suse_vex | SUSE CVE CVE-2026-31443 | known affected: 17 known not affected: 300 | 2026-08-03T23:49:06+00:00 | Vulnerability · Source |
| CVE-2026-31467 | suse_vex | SUSE CVE CVE-2026-31467 | known affected: 185 known not affected: 115 recommended: 42 | 2026-08-03T23:49:02+00:00 | Vulnerability · Source |
| CVE-2026-31475 | suse_vex | SUSE CVE CVE-2026-31475 | known not affected: 315 | 2026-08-03T23:48:58+00:00 | Vulnerability · Source |
| CVE-2026-31487 | suse_vex | SUSE CVE CVE-2026-31487 | known affected: 250 known not affected: 67 | 2026-08-03T23:48:54+00:00 | Vulnerability · Source |
| CVE-2026-31489 | suse_vex | SUSE CVE CVE-2026-31489 | known not affected: 298 | 2026-08-03T23:48:52+00:00 | Vulnerability · Source |
| CVE-2026-31491 | suse_vex | SUSE CVE CVE-2026-31491 | known affected: 202 known not affected: 93 | 2026-08-03T23:48:51+00:00 | Vulnerability · Source |
| CVE-2026-31527 | suse_vex | SUSE CVE CVE-2026-31527 | known affected: 313 known not affected: 4 | 2026-08-03T23:48:39+00:00 | Vulnerability · Source |
| CVE-2026-31529 | suse_vex | SUSE CVE CVE-2026-31529 | known not affected: 320 | 2026-08-03T23:48:37+00:00 | Vulnerability · Source |
| CVE-2026-31557 | suse_vex | SUSE CVE CVE-2026-31557 | known affected: 202 known not affected: 115 | 2026-08-03T23:48:29+00:00 | Vulnerability · Source |
| CVE-2026-31582 | suse_vex | SUSE CVE CVE-2026-31582 | known affected: 29 known not affected: 292 recommended: 4 | 2026-08-03T23:48:22+00:00 | Vulnerability · Source |
| CVE-2026-31591 | suse_vex | SUSE CVE CVE-2026-31591 | known affected: 394 known not affected: 260 recommended: 102 | 2026-08-03T23:48:18+00:00 | Vulnerability · Source |
| CVE-2026-31595 | suse_vex | SUSE CVE CVE-2026-31595 | known affected: 114 known not affected: 203 recommended: 4 | 2026-08-03T23:48:15+00:00 | Vulnerability · Source |
| CVE-2026-31600 | suse_vex | SUSE CVE CVE-2026-31600 | known affected: 321 recommended: 4 | 2026-08-03T23:48:10+00:00 | Vulnerability · Source |
| CVE-2026-31606 | suse_vex | SUSE CVE CVE-2026-31606 | known affected: 296 known not affected: 21 recommended: 4 | 2026-08-03T23:48:05+00:00 | Vulnerability · Source |
| CVE-2026-31620 | suse_vex | SUSE CVE CVE-2026-31620 | known not affected: 315 recommended: 4 | 2026-08-03T23:48:00+00:00 | Vulnerability · Source |
| CVE-2026-31721 | suse_vex | SUSE CVE CVE-2026-31721 | known affected: 30 known not affected: 263 | 2026-08-03T23:47:41+00:00 | Vulnerability · Source |
| CVE-2026-31740 | suse_vex | SUSE CVE CVE-2026-31740 | known not affected: 293 | 2026-08-03T23:47:35+00:00 | Vulnerability · Source |
| CVE-2026-31741 | suse_vex | SUSE CVE CVE-2026-31741 | known not affected: 291 | 2026-08-03T23:47:33+00:00 | Vulnerability · Source |
| CVE-2026-31775 | suse_vex | SUSE CVE CVE-2026-31775 | known not affected: 291 | 2026-08-03T23:47:24+00:00 | Vulnerability · Source |
| CVE-2026-34933 | suse_vex | SUSE CVE CVE-2026-34933 | known affected: 716 recommended: 306 | 2026-08-03T23:47:07+00:00 | Vulnerability · Source |
| CVE-2026-38974 | suse_vex | SUSE CVE CVE-2026-38974 | recommended: 29 | 2026-08-03T23:46:57+00:00 | Vulnerability · Source |
| CVE-2026-42006 | suse_vex | SUSE CVE CVE-2026-42006 | known affected: 198 known not affected: 32 recommended: 70 | 2026-08-03T23:46:16+00:00 | Vulnerability · Source |
| CVE-2026-42492 | suse_vex | SUSE CVE CVE-2026-42492 | known not affected: 151 recommended: 7 | 2026-08-03T23:46:09+00:00 | Vulnerability · Source |
| CVE-2026-43019 | suse_vex | SUSE CVE CVE-2026-43019 | known affected: 424 known not affected: 196 recommended: 120 | 2026-08-03T23:46:00+00:00 | Vulnerability · Source |
| CVE-2026-43023 | suse_vex | SUSE CVE CVE-2026-43023 | known affected: 394 known not affected: 196 recommended: 236 | 2026-08-03T23:45:56+00:00 | Vulnerability · Source |
| CVE-2026-43095 | suse_vex | SUSE CVE CVE-2026-43095 | known not affected: 293 | 2026-08-03T23:45:32+00:00 | Vulnerability · Source |
| CVE-2026-43096 | suse_vex | SUSE CVE CVE-2026-43096 | known not affected: 295 | 2026-08-03T23:45:30+00:00 | Vulnerability · Source |
| CVE-2026-43097 | suse_vex | SUSE CVE CVE-2026-43097 | known not affected: 295 | 2026-08-03T23:45:29+00:00 | Vulnerability · Source |
| CVE-2026-43108 | suse_vex | SUSE CVE CVE-2026-43108 | known not affected: 293 | 2026-08-03T23:45:26+00:00 | Vulnerability · Source |
| CVE-2026-43138 | suse_vex | SUSE CVE CVE-2026-43138 | known not affected: 293 | 2026-08-03T23:45:17+00:00 | Vulnerability · Source |
| CVE-2026-43144 | suse_vex | SUSE CVE CVE-2026-43144 | known not affected: 293 | 2026-08-03T23:45:14+00:00 | Vulnerability · Source |
| CVE-2026-43176 | suse_vex | SUSE CVE CVE-2026-43176 | known not affected: 293 | 2026-08-03T23:45:04+00:00 | Vulnerability · Source |
| CVE-2026-43189 | suse_vex | SUSE CVE CVE-2026-43189 | known affected: 394 known not affected: 238 recommended: 98 | 2026-08-03T23:45:02+00:00 | Vulnerability · Source |
| CVE-2026-43222 | suse_vex | SUSE CVE CVE-2026-43222 | known affected: 394 known not affected: 238 recommended: 98 | 2026-08-03T23:44:53+00:00 | Vulnerability · Source |
| CVE-2026-43229 | suse_vex | SUSE CVE CVE-2026-43229 | known not affected: 293 | 2026-08-03T23:44:51+00:00 | Vulnerability · Source |
| CVE-2026-43247 | suse_vex | SUSE CVE CVE-2026-43247 | known not affected: 293 | 2026-08-03T23:44:45+00:00 | Vulnerability · Source |
| CVE-2026-43250 | suse_vex | SUSE CVE CVE-2026-43250 | known affected: 278 known not affected: 17 | 2026-08-03T23:44:43+00:00 | Vulnerability · Source |
| CVE-2026-43267 | suse_vex | SUSE CVE CVE-2026-43267 | known not affected: 293 | 2026-08-03T23:44:37+00:00 | Vulnerability · Source |
| CVE-2026-43275 | suse_vex | SUSE CVE CVE-2026-43275 | known affected: 291 known not affected: 4 | 2026-08-03T23:44:36+00:00 | Vulnerability · Source |
| CVE-2026-43282 | suse_vex | SUSE CVE CVE-2026-43282 | known not affected: 293 | 2026-08-03T23:44:29+00:00 | Vulnerability · Source |
| CVE-2026-43290 | suse_vex | SUSE CVE CVE-2026-43290 | known not affected: 293 | 2026-08-03T23:44:27+00:00 | Vulnerability · Source |
| CVE-2026-43293 | suse_vex | SUSE CVE CVE-2026-43293 | known not affected: 293 | 2026-08-03T23:44:25+00:00 | Vulnerability · Source |
| CVE-2026-43297 | suse_vex | SUSE CVE CVE-2026-43297 | known not affected: 293 | 2026-08-03T23:44:23+00:00 | Vulnerability · Source |
| CVE-2026-43306 | suse_vex | SUSE CVE CVE-2026-43306 | known not affected: 293 | 2026-08-03T23:44:20+00:00 | Vulnerability · Source |
| CVE-2026-43307 | suse_vex | SUSE CVE CVE-2026-43307 | known not affected: 293 | 2026-08-03T23:44:19+00:00 | Vulnerability · Source |
| CVE-2026-43320 | suse_vex | SUSE CVE CVE-2026-43320 | known affected: 424 known not affected: 198 recommended: 120 | 2026-08-03T23:44:14+00:00 | Vulnerability · Source |
| CVE-2026-43323 | suse_vex | SUSE CVE CVE-2026-43323 | known not affected: 293 | 2026-08-03T23:44:13+00:00 | Vulnerability · Source |