VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291877 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-22858 | suse_vex | SUSE CVE CVE-2026-22858 | known not affected: 38 recommended: 133 | 2026-08-12T00:01:31+00:00 | Vulnerability · Source |
| CVE-2026-23392 | suse_vex | SUSE CVE CVE-2026-23392 | first fixed: 2 known affected: 446 known not affected: 81 recommended: 595 | 2026-08-12T00:01:07+00:00 | Vulnerability · Source |
| CVE-2026-24515 | suse_vex | SUSE CVE CVE-2026-24515 | known affected: 442 known not affected: 5810 recommended: 103 | 2026-08-12T00:00:57+00:00 | Vulnerability · Source |
| CVE-2026-28374 | suse_vex | SUSE CVE CVE-2026-28374 | first fixed: 1 known affected: 2 recommended: 65 | 2026-08-12T00:00:46+00:00 | Vulnerability · Source |
| CVE-2026-28376 | suse_vex | SUSE CVE CVE-2026-28376 | first fixed: 1 known affected: 2 recommended: 65 | 2026-08-12T00:00:44+00:00 | Vulnerability · Source |
| CVE-2026-28379 | suse_vex | SUSE CVE CVE-2026-28379 | first fixed: 1 known affected: 2 recommended: 65 | 2026-08-12T00:00:43+00:00 | Vulnerability · Source |
| CVE-2026-28380 | suse_vex | SUSE CVE CVE-2026-28380 | first fixed: 1 known affected: 2 recommended: 65 | 2026-08-12T00:00:41+00:00 | Vulnerability · Source |
| CVE-2026-28383 | suse_vex | SUSE CVE CVE-2026-28383 | first fixed: 1 known affected: 2 recommended: 65 | 2026-08-12T00:00:40+00:00 | Vulnerability · Source |
| CVE-2026-31404 | suse_vex | SUSE CVE CVE-2026-31404 | known affected: 462 known not affected: 186 recommended: 123 | 2026-08-12T00:00:35+00:00 | Vulnerability · Source |
| CVE-2026-31580 | suse_vex | SUSE CVE CVE-2026-31580 | first fixed: 2 known affected: 593 known not affected: 4 recommended: 308 | 2026-08-12T00:00:17+00:00 | Vulnerability · Source |
| CVE-2026-32952 | suse_vex | SUSE CVE CVE-2026-32952 | recommended: 19 | 2026-08-11T23:59:53+00:00 | Vulnerability · Source |
| CVE-2026-33173 | suse_vex | SUSE CVE CVE-2026-33173 | known not affected: 98 | 2026-08-11T23:59:51+00:00 | Vulnerability · Source |
| CVE-2026-33202 | suse_vex | SUSE CVE CVE-2026-33202 | known not affected: 98 | 2026-08-11T23:59:48+00:00 | Vulnerability · Source |
| CVE-2026-33378 | suse_vex | SUSE CVE CVE-2026-33378 | first fixed: 1 known affected: 2 recommended: 65 | 2026-08-11T23:59:42+00:00 | Vulnerability · Source |
| CVE-2026-33380 | suse_vex | SUSE CVE CVE-2026-33380 | first fixed: 1 known affected: 2 recommended: 65 | 2026-08-11T23:59:40+00:00 | Vulnerability · Source |
| CVE-2026-33381 | suse_vex | SUSE CVE CVE-2026-33381 | first fixed: 1 known affected: 2 recommended: 65 | 2026-08-11T23:59:37+00:00 | Vulnerability · Source |
| CVE-2026-33636 | suse_vex | SUSE CVE CVE-2026-33636 | known affected: 394 known not affected: 218 recommended: 221 | 2026-08-11T23:59:29+00:00 | Vulnerability · Source |
| CVE-2026-33986 | suse_vex | SUSE CVE CVE-2026-33986 | known affected: 48 recommended: 117 | 2026-08-11T23:59:24+00:00 | Vulnerability · Source |
| CVE-2026-33995 | suse_vex | SUSE CVE CVE-2026-33995 | known affected: 48 recommended: 117 | 2026-08-11T23:59:22+00:00 | Vulnerability · Source |
| CVE-2026-35172 | suse_vex | SUSE CVE CVE-2026-35172 | known not affected: 71 recommended: 5 | 2026-08-11T23:59:09+00:00 | Vulnerability · Source |
| CVE-2026-37459 | suse_vex | SUSE CVE CVE-2026-37459 | known not affected: 363 recommended: 26 | 2026-08-11T23:59:05+00:00 | Vulnerability · Source |
| CVE-2026-39883 | suse_vex | SUSE CVE CVE-2026-39883 | recommended: 7 | 2026-08-11T23:58:54+00:00 | Vulnerability · Source |
| CVE-2026-40033 | suse_vex | SUSE CVE CVE-2026-40033 | known affected: 38 recommended: 123 | 2026-08-11T23:58:52+00:00 | Vulnerability · Source |
| CVE-2026-42945 | suse_vex | SUSE CVE CVE-2026-42945 | known affected: 406 recommended: 75 | 2026-08-11T23:58:03+00:00 | Vulnerability · Source |
| CVE-2026-45022 | suse_vex | SUSE CVE CVE-2026-45022 | recommended: 4 | 2026-08-11T23:56:44+00:00 | Vulnerability · Source |
| CVE-2026-45571 | suse_vex | SUSE CVE CVE-2026-45571 | recommended: 4 | 2026-08-11T23:56:39+00:00 | Vulnerability · Source |
| CVE-2026-46194 | suse_vex | SUSE CVE CVE-2026-46194 | known not affected: 293 recommended: 4 | 2026-08-11T23:55:49+00:00 | Vulnerability · Source |
| CVE-2026-47783 | suse_vex | SUSE CVE CVE-2026-47783 | known affected: 19 recommended: 57 | 2026-08-11T23:55:18+00:00 | Vulnerability · Source |
| CVE-2026-48790 | suse_vex | SUSE CVE CVE-2026-48790 | No product status | 2026-08-11T23:55:12+00:00 | Vulnerability · Source |
| CVE-2026-52718 | suse_vex | SUSE CVE CVE-2026-52718 | known affected: 365 known not affected: 181 recommended: 309 | 2026-08-11T23:54:46+00:00 | Vulnerability · Source |
| CVE-2026-53462 | suse_vex | SUSE CVE CVE-2026-53462 | known not affected: 288 recommended: 15 | 2026-08-11T23:53:25+00:00 | Vulnerability · Source |
| CVE-2026-55510 | suse_vex | SUSE CVE CVE-2026-55510 | known not affected: 278 recommended: 15 | 2026-08-11T23:53:15+00:00 | Vulnerability · Source |
| CVE-2026-55577 | suse_vex | SUSE CVE CVE-2026-55577 | known not affected: 278 recommended: 15 | 2026-08-11T23:53:13+00:00 | Vulnerability · Source |
| CVE-2026-56113 | suse_vex | SUSE CVE CVE-2026-56113 | known affected: 4 recommended: 1 | 2026-08-11T23:52:59+00:00 | Vulnerability · Source |
| CVE-2026-56115 | suse_vex | SUSE CVE CVE-2026-56115 | known affected: 4 recommended: 1 | 2026-08-11T23:52:56+00:00 | Vulnerability · Source |
| CVE-2026-56116 | suse_vex | SUSE CVE CVE-2026-56116 | known affected: 4 recommended: 1 | 2026-08-11T23:52:54+00:00 | Vulnerability · Source |
| CVE-2026-56117 | suse_vex | SUSE CVE CVE-2026-56117 | known affected: 4 recommended: 1 | 2026-08-11T23:52:52+00:00 | Vulnerability · Source |
| CVE-2026-57158 | suse_vex | SUSE CVE CVE-2026-57158 | known affected: 65 recommended: 65 | 2026-08-11T23:52:31+00:00 | Vulnerability · Source |
| CVE-2026-57235 | suse_vex | SUSE CVE CVE-2026-57235 | known affected: 103 known not affected: 5 | 2026-08-11T23:52:29+00:00 | Vulnerability · Source |
| CVE-2026-57434 | suse_vex | SUSE CVE CVE-2026-57434 | known affected: 103 known not affected: 5 | 2026-08-11T23:52:27+00:00 | Vulnerability · Source |
| CVE-2026-57435 | suse_vex | SUSE CVE CVE-2026-57435 | known affected: 103 known not affected: 5 | 2026-08-11T23:52:25+00:00 | Vulnerability · Source |
| CVE-2026-57436 | suse_vex | SUSE CVE CVE-2026-57436 | known affected: 103 known not affected: 5 | 2026-08-11T23:52:23+00:00 | Vulnerability · Source |
| CVE-2026-57437 | suse_vex | SUSE CVE CVE-2026-57437 | known affected: 103 known not affected: 5 | 2026-08-11T23:52:21+00:00 | Vulnerability · Source |
| CVE-2026-57438 | suse_vex | SUSE CVE CVE-2026-57438 | known affected: 103 known not affected: 5 | 2026-08-11T23:52:19+00:00 | Vulnerability · Source |
| CVE-2026-57965 | suse_vex | SUSE CVE CVE-2026-57965 | first fixed: 2 known affected: 8 known not affected: 3 recommended: 23 | 2026-08-11T23:52:16+00:00 | Vulnerability · Source |
| CVE-2026-57966 | suse_vex | SUSE CVE CVE-2026-57966 | first fixed: 2 known affected: 8 known not affected: 3 recommended: 23 | 2026-08-11T23:52:14+00:00 | Vulnerability · Source |
| CVE-2026-59881 | suse_vex | SUSE CVE CVE-2026-59881 | first fixed: 33 known affected: 66 recommended: 2 | 2026-08-11T23:51:08+00:00 | Vulnerability · Source |
| CVE-2026-63872 | suse_vex | SUSE CVE CVE-2026-63872 | known affected: 292 known not affected: 6 | 2026-08-11T23:50:34+00:00 | Vulnerability · Source |
| CVE-2026-64165 | suse_vex | SUSE CVE CVE-2026-64165 | known not affected: 298 | 2026-08-11T23:49:42+00:00 | Vulnerability · Source |
| CVE-2026-67215 | suse_vex | SUSE CVE CVE-2026-67215 | known affected: 17 | 2026-08-11T23:49:02+00:00 | Vulnerability · Source |