VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291757 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-53021 | suse_vex | SUSE CVE CVE-2026-53021 | first fixed: 2 known affected: 592 known not affected: 4 recommended: 288 | 2026-08-13T01:30:48+00:00 | Vulnerability · Source |
| CVE-2026-53039 | suse_vex | SUSE CVE CVE-2026-53039 | first fixed: 2 known affected: 596 recommended: 288 | 2026-08-13T01:30:43+00:00 | Vulnerability · Source |
| CVE-2026-53060 | suse_vex | SUSE CVE CVE-2026-53060 | first fixed: 2 known affected: 547 known not affected: 49 recommended: 288 | 2026-08-13T01:30:39+00:00 | Vulnerability · Source |
| CVE-2026-53167 | suse_vex | SUSE CVE CVE-2026-53167 | first fixed: 2 known affected: 596 recommended: 288 | 2026-08-13T01:30:32+00:00 | Vulnerability · Source |
| CVE-2026-53176 | suse_vex | SUSE CVE CVE-2026-53176 | first fixed: 2 known affected: 590 known not affected: 4 recommended: 302 | 2026-08-13T01:30:30+00:00 | Vulnerability · Source |
| CVE-2026-53249 | suse_vex | SUSE CVE CVE-2026-53249 | first fixed: 2 known affected: 579 recommended: 288 | 2026-08-13T01:30:20+00:00 | Vulnerability · Source |
| CVE-2026-53306 | suse_vex | SUSE CVE CVE-2026-53306 | first fixed: 2 known affected: 596 recommended: 288 | 2026-08-13T01:30:10+00:00 | Vulnerability · Source |
| CVE-2026-55653 | suse_vex | SUSE CVE CVE-2026-55653 | recommended: 20 | 2026-08-13T01:29:48+00:00 | Vulnerability · Source |
| CVE-2026-55654 | suse_vex | SUSE CVE CVE-2026-55654 | recommended: 12 | 2026-08-13T01:29:47+00:00 | Vulnerability · Source |
| CVE-2026-55655 | suse_vex | SUSE CVE CVE-2026-55655 | recommended: 20 | 2026-08-13T01:29:46+00:00 | Vulnerability · Source |
| CVE-2026-64262 | suse_vex | SUSE CVE CVE-2026-64262 | known not affected: 298 recommended: 4 | 2026-08-13T01:28:40+00:00 | Vulnerability · Source |
| CVE-2026-66484 | suse_vex | SUSE CVE CVE-2026-66484 | known affected: 93 | 2026-08-13T01:28:29+00:00 | Vulnerability · Source |
| CVE-2026-66485 | suse_vex | SUSE CVE CVE-2026-66485 | known affected: 93 | 2026-08-13T01:28:28+00:00 | Vulnerability · Source |
| CVE-2026-68104 | suse_vex | SUSE CVE CVE-2026-68104 | known affected: 205 known not affected: 91 | 2026-08-13T01:28:26+00:00 | Vulnerability · Source |
| CVE-2026-68105 | suse_vex | SUSE CVE CVE-2026-68105 | known affected: 82 known not affected: 214 | 2026-08-13T01:28:24+00:00 | Vulnerability · Source |
| CVE-2026-68106 | suse_vex | SUSE CVE CVE-2026-68106 | known affected: 209 known not affected: 87 | 2026-08-13T01:28:23+00:00 | Vulnerability · Source |
| CVE-2026-68191 | suse_vex | SUSE CVE CVE-2026-68191 | known not affected: 296 | 2026-08-13T01:28:22+00:00 | Vulnerability · Source |
| CVE-2026-68192 | suse_vex | SUSE CVE CVE-2026-68192 | known affected: 144 known not affected: 152 | 2026-08-13T01:28:21+00:00 | Vulnerability · Source |
| CVE-2026-68193 | suse_vex | SUSE CVE CVE-2026-68193 | known affected: 30 known not affected: 266 | 2026-08-13T01:28:19+00:00 | Vulnerability · Source |
| CVE-2026-68194 | suse_vex | SUSE CVE CVE-2026-68194 | known affected: 78 known not affected: 218 | 2026-08-13T01:28:18+00:00 | Vulnerability · Source |
| CVE-2026-68195 | suse_vex | SUSE CVE CVE-2026-68195 | known affected: 132 known not affected: 164 | 2026-08-13T01:28:17+00:00 | Vulnerability · Source |
| CVE-2026-68196 | suse_vex | SUSE CVE CVE-2026-68196 | known affected: 193 known not affected: 103 | 2026-08-13T01:28:16+00:00 | Vulnerability · Source |
| CVE-2026-68197 | suse_vex | SUSE CVE CVE-2026-68197 | known affected: 193 known not affected: 103 | 2026-08-13T01:28:14+00:00 | Vulnerability · Source |
| CVE-2026-68198 | suse_vex | SUSE CVE CVE-2026-68198 | known affected: 292 known not affected: 4 | 2026-08-13T01:28:13+00:00 | Vulnerability · Source |
| CVE-2026-68377 | suse_vex | SUSE CVE CVE-2026-68377 | known affected: 290 known not affected: 6 | 2026-08-13T01:28:12+00:00 | Vulnerability · Source |
| CVE-2026-68379 | suse_vex | SUSE CVE CVE-2026-68379 | known not affected: 296 | 2026-08-13T01:28:10+00:00 | Vulnerability · Source |
| CVE-2026-68380 | suse_vex | SUSE CVE CVE-2026-68380 | known not affected: 296 | 2026-08-13T01:28:09+00:00 | Vulnerability · Source |
| CVE-2026-68381 | suse_vex | SUSE CVE CVE-2026-68381 | known not affected: 296 | 2026-08-13T01:28:08+00:00 | Vulnerability · Source |
| CVE-2026-68382 | suse_vex | SUSE CVE CVE-2026-68382 | known affected: 82 known not affected: 214 | 2026-08-13T01:28:07+00:00 | Vulnerability · Source |
| CVE-2026-68383 | suse_vex | SUSE CVE CVE-2026-68383 | known affected: 82 known not affected: 214 | 2026-08-13T01:28:06+00:00 | Vulnerability · Source |
| CVE-2026-68384 | suse_vex | SUSE CVE CVE-2026-68384 | known not affected: 296 | 2026-08-13T01:28:04+00:00 | Vulnerability · Source |
| CVE-2026-68385 | suse_vex | SUSE CVE CVE-2026-68385 | known affected: 29 known not affected: 267 | 2026-08-13T01:28:03+00:00 | Vulnerability · Source |
| CVE-2026-68386 | suse_vex | SUSE CVE CVE-2026-68386 | known affected: 177 known not affected: 119 | 2026-08-13T01:28:02+00:00 | Vulnerability · Source |
| CVE-2026-68387 | suse_vex | SUSE CVE CVE-2026-68387 | known not affected: 296 | 2026-08-13T01:28:01+00:00 | Vulnerability · Source |
| CVE-2026-68429 | suse_vex | SUSE CVE CVE-2026-68429 | known affected: 30 known not affected: 266 | 2026-08-13T01:28:00+00:00 | Vulnerability · Source |
| CVE-2026-68430 | suse_vex | SUSE CVE CVE-2026-68430 | No product status | 2026-08-13T01:27:58+00:00 | Vulnerability · Source |
| CVE-2026-68431 | suse_vex | SUSE CVE CVE-2026-68431 | known affected: 129 known not affected: 167 | 2026-08-13T01:27:57+00:00 | Vulnerability · Source |
| CVE-2026-68432 | suse_vex | SUSE CVE CVE-2026-68432 | known affected: 290 known not affected: 6 | 2026-08-13T01:27:56+00:00 | Vulnerability · Source |
| CVE-2026-68433 | suse_vex | SUSE CVE CVE-2026-68433 | known affected: 292 known not affected: 4 | 2026-08-13T01:27:55+00:00 | Vulnerability · Source |
| CVE-2026-68434 | suse_vex | SUSE CVE CVE-2026-68434 | known not affected: 296 | 2026-08-13T01:27:53+00:00 | Vulnerability · Source |
| CVE-2026-68435 | suse_vex | SUSE CVE CVE-2026-68435 | known affected: 129 known not affected: 167 | 2026-08-13T01:27:52+00:00 | Vulnerability · Source |
| CVE-2026-68437 | suse_vex | SUSE CVE CVE-2026-68437 | known not affected: 296 | 2026-08-13T01:27:51+00:00 | Vulnerability · Source |
| CVE-2026-68438 | suse_vex | SUSE CVE CVE-2026-68438 | known not affected: 296 | 2026-08-13T01:27:50+00:00 | Vulnerability · Source |
| CVE-2026-68439 | suse_vex | SUSE CVE CVE-2026-68439 | known affected: 100 known not affected: 196 | 2026-08-13T01:27:48+00:00 | Vulnerability · Source |
| CVE-2026-68440 | suse_vex | SUSE CVE CVE-2026-68440 | known not affected: 296 | 2026-08-13T01:27:46+00:00 | Vulnerability · Source |
| CVE-2026-68441 | suse_vex | SUSE CVE CVE-2026-68441 | known affected: 292 known not affected: 4 | 2026-08-13T01:27:44+00:00 | Vulnerability · Source |
| CVE-2026-68442 | suse_vex | SUSE CVE CVE-2026-68442 | known affected: 29 known not affected: 267 | 2026-08-13T01:27:43+00:00 | Vulnerability · Source |
| CVE-2026-68443 | suse_vex | SUSE CVE CVE-2026-68443 | known not affected: 296 | 2026-08-13T01:27:41+00:00 | Vulnerability · Source |
| CVE-2026-68444 | suse_vex | SUSE CVE CVE-2026-68444 | known affected: 118 known not affected: 178 | 2026-08-13T01:27:40+00:00 | Vulnerability · Source |
| CVE-2026-68446 | suse_vex | SUSE CVE CVE-2026-68446 | known affected: 132 known not affected: 164 | 2026-08-13T01:27:38+00:00 | Vulnerability · Source |