VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291900 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-44941 | suse_vex | SUSE CVE CVE-2026-44941 | first fixed: 54 known affected: 407 known not affected: 15 recommended: 338 | 2026-08-11T00:07:01+00:00 | Vulnerability · Source |
| CVE-2026-44942 | suse_vex | SUSE CVE CVE-2026-44942 | first fixed: 54 known affected: 411 known not affected: 2 recommended: 348 | 2026-08-11T00:07:00+00:00 | Vulnerability · Source |
| CVE-2026-45031 | suse_vex | SUSE CVE CVE-2026-45031 | known affected: 85 known not affected: 8 recommended: 249 | 2026-08-11T00:06:57+00:00 | Vulnerability · Source |
| CVE-2026-45045 | suse_vex | SUSE CVE CVE-2026-45045 | No product status | 2026-08-11T00:06:55+00:00 | Vulnerability · Source |
| CVE-2026-45134 | suse_vex | SUSE CVE CVE-2026-45134 | recommended: 2 | 2026-08-11T00:06:54+00:00 | Vulnerability · Source |
| CVE-2026-45135 | suse_vex | SUSE CVE CVE-2026-45135 | known not affected: 245 | 2026-08-11T00:06:52+00:00 | Vulnerability · Source |
| CVE-2026-45447 | suse_vex | SUSE CVE CVE-2026-45447 | known affected: 507 known not affected: 75 recommended: 380 | 2026-08-11T00:06:50+00:00 | Vulnerability · Source |
| CVE-2026-46384 | suse_vex | SUSE CVE CVE-2026-46384 | No product status | 2026-08-11T00:06:26+00:00 | Vulnerability · Source |
| CVE-2026-46385 | suse_vex | SUSE CVE CVE-2026-46385 | No product status | 2026-08-11T00:06:24+00:00 | Vulnerability · Source |
| CVE-2026-47265 | suse_vex | SUSE CVE CVE-2026-47265 | known affected: 399 recommended: 46 | 2026-08-11T00:06:18+00:00 | Vulnerability · Source |
| CVE-2026-48522 | suse_vex | SUSE CVE CVE-2026-48522 | known affected: 399 known not affected: 24 recommended: 55 | 2026-08-11T00:06:14+00:00 | Vulnerability · Source |
| CVE-2026-48523 | suse_vex | SUSE CVE CVE-2026-48523 | known affected: 399 known not affected: 24 recommended: 55 | 2026-08-11T00:06:13+00:00 | Vulnerability · Source |
| CVE-2026-48524 | suse_vex | SUSE CVE CVE-2026-48524 | known affected: 391 known not affected: 24 recommended: 35 | 2026-08-11T00:06:12+00:00 | Vulnerability · Source |
| CVE-2026-48525 | suse_vex | SUSE CVE CVE-2026-48525 | known affected: 399 known not affected: 24 recommended: 55 | 2026-08-11T00:06:10+00:00 | Vulnerability · Source |
| CVE-2026-48779 | suse_vex | SUSE CVE CVE-2026-48779 | known affected: 92 known not affected: 326 recommended: 22 | 2026-08-11T00:06:08+00:00 | Vulnerability · Source |
| CVE-2026-48863 | suse_vex | SUSE CVE CVE-2026-48863 | first fixed: 36 known affected: 447 known not affected: 23 recommended: 140 | 2026-08-11T00:06:07+00:00 | Vulnerability · Source |
| CVE-2026-48913 | suse_vex | SUSE CVE CVE-2026-48913 | known affected: 445 recommended: 173 | 2026-08-11T00:06:05+00:00 | Vulnerability · Source |
| CVE-2026-49219 | suse_vex | SUSE CVE CVE-2026-49219 | known not affected: 288 recommended: 15 | 2026-08-11T00:06:03+00:00 | Vulnerability · Source |
| CVE-2026-50265 | suse_vex | SUSE CVE CVE-2026-50265 | known affected: 405 known not affected: 43 recommended: 93 | 2026-08-11T00:05:57+00:00 | Vulnerability · Source |
| CVE-2026-50269 | suse_vex | SUSE CVE CVE-2026-50269 | known affected: 399 recommended: 48 | 2026-08-11T00:05:55+00:00 | Vulnerability · Source |
| CVE-2026-50292 | suse_vex | SUSE CVE CVE-2026-50292 | known affected: 11 known not affected: 43 recommended: 96 | 2026-08-11T00:05:54+00:00 | Vulnerability · Source |
| CVE-2026-52844 | suse_vex | SUSE CVE CVE-2026-52844 | No product status | 2026-08-11T00:05:49+00:00 | Vulnerability · Source |
| CVE-2026-52845 | suse_vex | SUSE CVE CVE-2026-52845 | No product status | 2026-08-11T00:05:48+00:00 | Vulnerability · Source |
| CVE-2026-52846 | suse_vex | SUSE CVE CVE-2026-52846 | known affected: 6 known not affected: 223 | 2026-08-11T00:05:46+00:00 | Vulnerability · Source |
| CVE-2026-52858 | suse_vex | SUSE CVE CVE-2026-52858 | known affected: 170 recommended: 17 | 2026-08-11T00:05:45+00:00 | Vulnerability · Source |
| CVE-2026-53465 | suse_vex | SUSE CVE CVE-2026-53465 | known not affected: 288 recommended: 15 | 2026-08-11T00:05:19+00:00 | Vulnerability · Source |
| CVE-2026-53550 | suse_vex | SUSE CVE CVE-2026-53550 | known affected: 318 known not affected: 111 recommended: 9 | 2026-08-11T00:05:17+00:00 | Vulnerability · Source |
| CVE-2026-53624 | suse_vex | SUSE CVE CVE-2026-53624 | No product status | 2026-08-11T00:05:14+00:00 | Vulnerability · Source |
| CVE-2026-53632 | suse_vex | SUSE CVE CVE-2026-53632 | known not affected: 9 recommended: 1 | 2026-08-11T00:05:12+00:00 | Vulnerability · Source |
| CVE-2026-54058 | suse_vex | SUSE CVE CVE-2026-54058 | first fixed: 4 recommended: 41 | 2026-08-11T00:05:10+00:00 | Vulnerability · Source |
| CVE-2026-54272 | suse_vex | SUSE CVE CVE-2026-54272 | first fixed: 20 known not affected: 235 recommended: 40 | 2026-08-11T00:05:08+00:00 | Vulnerability · Source |
| CVE-2026-54273 | suse_vex | SUSE CVE CVE-2026-54273 | known affected: 399 recommended: 48 | 2026-08-11T00:05:06+00:00 | Vulnerability · Source |
| CVE-2026-54274 | suse_vex | SUSE CVE CVE-2026-54274 | known affected: 399 recommended: 45 | 2026-08-11T00:05:05+00:00 | Vulnerability · Source |
| CVE-2026-54275 | suse_vex | SUSE CVE CVE-2026-54275 | known affected: 399 recommended: 48 | 2026-08-11T00:05:03+00:00 | Vulnerability · Source |
| CVE-2026-54277 | suse_vex | SUSE CVE CVE-2026-54277 | known affected: 399 recommended: 48 | 2026-08-11T00:05:02+00:00 | Vulnerability · Source |
| CVE-2026-54278 | suse_vex | SUSE CVE CVE-2026-54278 | known affected: 399 recommended: 45 | 2026-08-11T00:05:00+00:00 | Vulnerability · Source |
| CVE-2026-54279 | suse_vex | SUSE CVE CVE-2026-54279 | known affected: 394 known not affected: 5 recommended: 48 | 2026-08-11T00:04:59+00:00 | Vulnerability · Source |
| CVE-2026-54280 | suse_vex | SUSE CVE CVE-2026-54280 | known affected: 394 known not affected: 5 recommended: 45 | 2026-08-11T00:04:57+00:00 | Vulnerability · Source |
| CVE-2026-55827 | suse_vex | SUSE CVE CVE-2026-55827 | known affected: 118 recommended: 21 | 2026-08-11T00:04:51+00:00 | Vulnerability · Source |
| CVE-2026-55999 | suse_vex | SUSE CVE CVE-2026-55999 | known affected: 417 recommended: 118 | 2026-08-11T00:04:43+00:00 | Vulnerability · Source |
| CVE-2026-56000 | suse_vex | SUSE CVE CVE-2026-56000 | known affected: 424 recommended: 93 | 2026-08-11T00:04:42+00:00 | Vulnerability · Source |
| CVE-2026-56001 | suse_vex | SUSE CVE CVE-2026-56001 | known affected: 423 recommended: 56 | 2026-08-11T00:04:40+00:00 | Vulnerability · Source |
| CVE-2026-56002 | suse_vex | SUSE CVE CVE-2026-56002 | known affected: 423 recommended: 56 | 2026-08-11T00:04:38+00:00 | Vulnerability · Source |
| CVE-2026-56003 | suse_vex | SUSE CVE CVE-2026-56003 | known affected: 423 recommended: 54 | 2026-08-11T00:04:36+00:00 | Vulnerability · Source |
| CVE-2026-56369 | suse_vex | SUSE CVE CVE-2026-56369 | known not affected: 8 | 2026-08-11T00:04:32+00:00 | Vulnerability · Source |
| CVE-2026-57234 | suse_vex | SUSE CVE CVE-2026-57234 | known affected: 66 known not affected: 42 | 2026-08-11T00:04:14+00:00 | Vulnerability · Source |
| CVE-2026-57236 | suse_vex | SUSE CVE CVE-2026-57236 | known affected: 103 known not affected: 5 | 2026-08-11T00:04:12+00:00 | Vulnerability · Source |
| CVE-2026-58059 | suse_vex | SUSE CVE CVE-2026-58059 | first fixed: 16 known affected: 16 recommended: 80 | 2026-08-11T00:03:53+00:00 | Vulnerability · Source |
| CVE-2026-58060 | suse_vex | SUSE CVE CVE-2026-58060 | first fixed: 16 known affected: 16 recommended: 80 | 2026-08-11T00:03:51+00:00 | Vulnerability · Source |
| CVE-2026-58061 | suse_vex | SUSE CVE CVE-2026-58061 | first fixed: 16 known affected: 16 recommended: 80 | 2026-08-11T00:03:50+00:00 | Vulnerability · Source |