VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-73086 | suse_vex | SUSE CVE CVE-2026-73086 | known affected: 265 known not affected: 334 recommended: 1 | 2026-10-16T00:07:37+00:00 | Vulnerability · Source |
| CVE-2026-73088 | suse_vex | SUSE CVE CVE-2026-73088 | known affected: 109 known not affected: 334 recommended: 5 | 2026-10-16T00:07:35+00:00 | Vulnerability · Source |
| CVE-2026-73089 | suse_vex | SUSE CVE CVE-2026-73089 | known affected: 109 known not affected: 334 recommended: 2 | 2026-10-16T00:07:33+00:00 | Vulnerability · Source |
| CVE-2026-73490 | suse_vex | SUSE CVE CVE-2026-73490 | known affected: 74 known not affected: 22 | 2026-10-16T00:07:26+00:00 | Vulnerability · Source |
| CVE-2026-73491 | suse_vex | SUSE CVE CVE-2026-73491 | known affected: 7 known not affected: 91 | 2026-10-16T00:07:25+00:00 | Vulnerability · Source |
| CVE-2026-73492 | suse_vex | SUSE CVE CVE-2026-73492 | known affected: 7 known not affected: 91 | 2026-10-16T00:07:23+00:00 | Vulnerability · Source |
| CVE-2026-73643 | suse_vex | SUSE CVE CVE-2026-73643 | known not affected: 590 | 2026-10-16T00:07:19+00:00 | Vulnerability · Source |
| CVE-2026-73646 | suse_vex | SUSE CVE CVE-2026-73646 | known affected: 256 known not affected: 332 | 2026-10-16T00:07:17+00:00 | Vulnerability · Source |
| CVE-2026-73650 | suse_vex | SUSE CVE CVE-2026-73650 | known affected: 76 known not affected: 356 recommended: 1 | 2026-10-16T00:07:14+00:00 | Vulnerability · Source |
| CVE-2026-74394 | suse_vex | SUSE CVE CVE-2026-74394 | known affected: 498 known not affected: 129 recommended: 603 | 2026-10-16T00:06:00+00:00 | Vulnerability · Source |
| CVE-2026-74556 | suse_vex | SUSE CVE CVE-2026-74556 | known affected: 583 recommended: 482 | 2026-10-16T00:04:54+00:00 | Vulnerability · Source |
| CVE-2026-75803 | suse_vex | SUSE CVE CVE-2026-75803 | known affected: 394 known not affected: 499 recommended: 117 | 2026-10-16T00:02:55+00:00 | Vulnerability · Source |
| CVE-2026-75889 | suse_vex | SUSE CVE CVE-2026-75889 | known affected: 4 recommended: 5 | 2026-10-16T00:02:48+00:00 | Vulnerability · Source |
| CVE-2026-75899 | suse_vex | SUSE CVE CVE-2026-75899 | known affected: 9 known not affected: 147 | 2026-10-16T00:02:46+00:00 | Vulnerability · Source |
| CVE-2026-75900 | suse_vex | SUSE CVE CVE-2026-75900 | known affected: 49 recommended: 13 | 2026-10-16T00:02:44+00:00 | Vulnerability · Source |
| CVE-2026-75931 | suse_vex | SUSE CVE CVE-2026-75931 | known affected: 9 known not affected: 147 | 2026-10-16T00:02:42+00:00 | Vulnerability · Source |
| CVE-2026-75975 | suse_vex | SUSE CVE CVE-2026-75975 | known affected: 9 known not affected: 147 | 2026-10-16T00:02:40+00:00 | Vulnerability · Source |
| CVE-2026-76172 | suse_vex | SUSE CVE CVE-2026-76172 | known affected: 9 known not affected: 147 | 2026-10-16T00:02:35+00:00 | Vulnerability · Source |
| CVE-2026-76642 | suse_vex | SUSE CVE CVE-2026-76642 | known affected: 642 recommended: 109 | 2026-10-16T00:02:31+00:00 | Vulnerability · Source |
| CVE-2026-77214 | suse_vex | SUSE CVE CVE-2026-77214 | known affected: 345 known not affected: 7169 | 2026-10-16T00:02:21+00:00 | Vulnerability · Source |
| CVE-2026-77219 | suse_vex | SUSE CVE CVE-2026-77219 | known affected: 72 recommended: 136 | 2026-10-16T00:02:19+00:00 | Vulnerability · Source |
| CVE-2026-78254 | suse_vex | SUSE CVE CVE-2026-78254 | known affected: 133 recommended: 76 | 2026-10-16T00:02:13+00:00 | Vulnerability · Source |
| CVE-2026-78367 | suse_vex | SUSE CVE CVE-2026-78367 | known affected: 24 known not affected: 155 | 2026-10-16T00:02:09+00:00 | Vulnerability · Source |
| CVE-2026-78409 | suse_vex | SUSE CVE CVE-2026-78409 | known affected: 34 known not affected: 649 | 2026-10-16T00:02:05+00:00 | Vulnerability · Source |
| CVE-2026-78410 | suse_vex | SUSE CVE CVE-2026-78410 | known affected: 642 recommended: 109 | 2026-10-16T00:02:03+00:00 | Vulnerability · Source |
| CVE-2026-78807 | suse_vex | SUSE CVE CVE-2026-78807 | known affected: 20 recommended: 25 | 2026-10-16T00:01:57+00:00 | Vulnerability · Source |
| CVE-2026-79699 | suse_vex | SUSE CVE CVE-2026-79699 | known affected: 231 | 2026-10-16T00:01:38+00:00 | Vulnerability · Source |
| CVE-2026-79705 | suse_vex | SUSE CVE CVE-2026-79705 | known affected: 166 | 2026-10-16T00:01:35+00:00 | Vulnerability · Source |
| CVE-2026-79769 | suse_vex | SUSE CVE CVE-2026-79769 | known affected: 77 known not affected: 287 | 2026-10-16T00:01:33+00:00 | Vulnerability · Source |
| CVE-2026-79770 | suse_vex | SUSE CVE CVE-2026-79770 | known affected: 120 known not affected: 244 | 2026-10-16T00:01:31+00:00 | Vulnerability · Source |
| CVE-2026-80229 | suse_vex | SUSE CVE CVE-2026-80229 | known affected: 492 known not affected: 34 recommended: 69 | 2026-10-16T00:01:25+00:00 | Vulnerability · Source |
| CVE-2026-80230 | suse_vex | SUSE CVE CVE-2026-80230 | known affected: 526 recommended: 69 | 2026-10-16T00:01:23+00:00 | Vulnerability · Source |
| CVE-2026-80255 | suse_vex | SUSE CVE CVE-2026-80255 | known affected: 148 known not affected: 38 recommended: 9 | 2026-10-16T00:01:21+00:00 | Vulnerability · Source |
| CVE-2026-80521 | suse_vex | SUSE CVE CVE-2026-80521 | known affected: 29 known not affected: 324 | 2026-10-16T00:01:13+00:00 | Vulnerability · Source |
| CVE-2026-81521 | suse_vex | SUSE CVE CVE-2026-81521 | known affected: 5 recommended: 5 | 2026-10-15T23:59:04+00:00 | Vulnerability · Source |
| CVE-2026-82209 | suse_vex | SUSE CVE CVE-2026-82209 | known affected: 172 known not affected: 2 recommended: 9 | 2026-10-15T23:58:53+00:00 | Vulnerability · Source |
| CVE-2026-82328 | suse_vex | SUSE CVE CVE-2026-82328 | known affected: 26 | 2026-10-15T23:58:50+00:00 | Vulnerability · Source |
| CVE-2026-82343 | suse_vex | SUSE CVE CVE-2026-82343 | known affected: 26 | 2026-10-15T23:58:48+00:00 | Vulnerability · Source |
| CVE-2026-82474 | suse_vex | SUSE CVE CVE-2026-82474 | known affected: 86 known not affected: 57 recommended: 4 | 2026-10-15T23:58:43+00:00 | Vulnerability · Source |
| CVE-2026-83557 | suse_vex | SUSE CVE CVE-2026-83557 | known affected: 28 recommended: 83 | 2026-10-15T23:58:41+00:00 | Vulnerability · Source |
| CVE-2026-84233 | suse_vex | SUSE CVE CVE-2026-84233 | known affected: 44 known not affected: 155 | 2026-10-15T23:58:37+00:00 | Vulnerability · Source |
| CVE-2026-84369 | suse_vex | SUSE CVE CVE-2026-84369 | known affected: 232 known not affected: 326 | 2026-10-15T23:58:31+00:00 | Vulnerability · Source |
| CVE-2026-84370 | suse_vex | SUSE CVE CVE-2026-84370 | known affected: 230 known not affected: 332 | 2026-10-15T23:58:29+00:00 | Vulnerability · Source |
| CVE-2026-84451 | suse_vex | SUSE CVE CVE-2026-84451 | known not affected: 27 recommended: 64 | 2026-10-15T23:58:25+00:00 | Vulnerability · Source |
| CVE-2026-84837 | suse_vex | SUSE CVE CVE-2026-84837 | known affected: 187 | 2026-10-15T23:58:16+00:00 | Vulnerability · Source |
| CVE-2026-84838 | suse_vex | SUSE CVE CVE-2026-84838 | known affected: 187 | 2026-10-15T23:58:14+00:00 | Vulnerability · Source |
| CVE-2026-85644 | suse_vex | SUSE CVE CVE-2026-85644 | known affected: 5 recommended: 1 | 2026-10-15T23:58:10+00:00 | Vulnerability · Source |
| CVE-2026-86472 | suse_vex | SUSE CVE CVE-2026-86472 | known affected: 9 known not affected: 147 | 2026-10-15T23:58:03+00:00 | Vulnerability · Source |
| CVE-2026-86537 | suse_vex | SUSE CVE CVE-2026-86537 | No product status | 2026-10-15T23:58:01+00:00 | Vulnerability · Source |
| CVE-2026-86793 | suse_vex | SUSE CVE CVE-2026-86793 | No product status | 2026-10-15T23:57:49+00:00 | Vulnerability · Source |