VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
304407 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-42014 | suse_vex | SUSE CVE CVE-2026-42014 | known affected: 529 recommended: 236 | 2026-10-02T16:52:45+00:00 | Vulnerability · Source |
| CVE-2026-42015 | suse_vex | SUSE CVE CVE-2026-42015 | known affected: 529 recommended: 236 | 2026-10-02T16:52:43+00:00 | Vulnerability · Source |
| CVE-2026-42258 | suse_vex | SUSE CVE CVE-2026-42258 | known affected: 278 known not affected: 104 recommended: 139 | 2026-10-02T16:52:40+00:00 | Vulnerability · Source |
| CVE-2026-42356 | suse_vex | SUSE CVE CVE-2026-42356 | known affected: 183 | 2026-10-02T16:52:37+00:00 | Vulnerability · Source |
| CVE-2026-42504 | suse_vex | SUSE CVE CVE-2026-42504 | known affected: 24 known not affected: 93 recommended: 278 | 2026-10-02T16:52:35+00:00 | Vulnerability · Source |
| CVE-2026-42528 | suse_vex | SUSE CVE CVE-2026-42528 | known affected: 183 | 2026-10-02T16:52:33+00:00 | Vulnerability · Source |
| CVE-2026-43392 | suse_vex | SUSE CVE CVE-2026-43392 | known affected: 17 known not affected: 370 | 2026-10-02T16:52:26+00:00 | Vulnerability · Source |
| CVE-2026-46600 | suse_vex | SUSE CVE CVE-2026-46600 | known affected: 270 known not affected: 389 recommended: 53 | 2026-10-02T16:52:12+00:00 | Vulnerability · Source |
| CVE-2026-46729 | suse_vex | SUSE CVE CVE-2026-46729 | known affected: 183 | 2026-10-02T16:52:10+00:00 | Vulnerability · Source |
| CVE-2026-47360 | suse_vex | SUSE CVE CVE-2026-47360 | known affected: 183 | 2026-10-02T16:52:06+00:00 | Vulnerability · Source |
| CVE-2026-47519 | suse_vex | SUSE CVE CVE-2026-47519 | known affected: 156 | 2026-10-02T16:51:55+00:00 | Vulnerability · Source |
| CVE-2026-47574 | suse_vex | SUSE CVE CVE-2026-47574 | known affected: 156 | 2026-10-02T16:51:36+00:00 | Vulnerability · Source |
| CVE-2026-48005 | suse_vex | SUSE CVE CVE-2026-48005 | known affected: 183 | 2026-10-02T16:51:27+00:00 | Vulnerability · Source |
| CVE-2026-50229 | suse_vex | SUSE CVE CVE-2026-50229 | known affected: 324 known not affected: 69 recommended: 235 | 2026-10-02T16:51:25+00:00 | Vulnerability · Source |
| CVE-2026-54875 | suse_vex | SUSE CVE CVE-2026-54875 | known affected: 40 known not affected: 553 recommended: 24 | 2026-10-02T16:51:16+00:00 | Vulnerability · Source |
| CVE-2026-55252 | suse_vex | SUSE CVE CVE-2026-55252 | No product status | 2026-10-02T16:51:12+00:00 | Vulnerability · Source |
| CVE-2026-55443 | suse_vex | SUSE CVE CVE-2026-55443 | recommended: 2 | 2026-10-02T16:51:10+00:00 | Vulnerability · Source |
| CVE-2026-56153 | suse_vex | SUSE CVE CVE-2026-56153 | known affected: 183 | 2026-10-02T16:51:07+00:00 | Vulnerability · Source |
| CVE-2026-56154 | suse_vex | SUSE CVE CVE-2026-56154 | known affected: 183 | 2026-10-02T16:51:05+00:00 | Vulnerability · Source |
| CVE-2026-56209 | suse_vex | SUSE CVE CVE-2026-56209 | known not affected: 16 recommended: 119 | 2026-10-02T16:51:02+00:00 | Vulnerability · Source |
| CVE-2026-56210 | suse_vex | SUSE CVE CVE-2026-56210 | known not affected: 16 recommended: 119 | 2026-10-02T16:50:59+00:00 | Vulnerability · Source |
| CVE-2026-56211 | suse_vex | SUSE CVE CVE-2026-56211 | known not affected: 16 recommended: 119 | 2026-10-02T16:50:57+00:00 | Vulnerability · Source |
| CVE-2026-56852 | suse_vex | SUSE CVE CVE-2026-56852 | known affected: 1587 known not affected: 461 recommended: 544 | 2026-10-02T16:50:47+00:00 | Vulnerability · Source |
| CVE-2026-80844 | redhat_vex | kernel: xfrm: ah6: validate routing header segments_left | fixed: 2336 known affected: 24 | 2026-10-02T16:50:44+00:00 | Vulnerability · Source |
| CVE-2026-56860 | suse_vex | SUSE CVE CVE-2026-56860 | known affected: 12 known not affected: 147 recommended: 380 | 2026-10-02T16:50:44+00:00 | Vulnerability · Source |
| CVE-2026-57941 | suse_vex | SUSE CVE CVE-2026-57941 | known affected: 183 | 2026-10-02T16:50:40+00:00 | Vulnerability · Source |
| CVE-2026-58415 | suse_vex | SUSE CVE CVE-2026-58415 | known affected: 183 | 2026-10-02T16:50:35+00:00 | Vulnerability · Source |
| CVE-2026-59685 | suse_vex | SUSE CVE CVE-2026-59685 | known not affected: 183 | 2026-10-02T16:50:32+00:00 | Vulnerability · Source |
| CVE-2026-59797 | suse_vex | SUSE CVE CVE-2026-59797 | known affected: 183 | 2026-10-02T16:50:30+00:00 | Vulnerability · Source |
| CVE-2026-63045 | suse_vex | SUSE CVE CVE-2026-63045 | known affected: 183 | 2026-10-02T16:50:28+00:00 | Vulnerability · Source |
| CVE-2026-63292 | suse_vex | SUSE CVE CVE-2026-63292 | known affected: 183 | 2026-10-02T16:50:25+00:00 | Vulnerability · Source |
| CVE-2026-63374 | suse_vex | SUSE CVE CVE-2026-63374 | known affected: 15 recommended: 26 | 2026-10-02T16:50:23+00:00 | Vulnerability · Source |
| CVE-2026-63622 | suse_vex | SUSE CVE CVE-2026-63622 | known affected: 782 known not affected: 1 recommended: 882 | 2026-10-02T16:50:21+00:00 | Vulnerability · Source |
| CVE-2026-63686 | suse_vex | SUSE CVE CVE-2026-63686 | known affected: 183 | 2026-10-02T16:50:19+00:00 | Vulnerability · Source |
| CVE-2026-63718 | suse_vex | SUSE CVE CVE-2026-63718 | known affected: 183 | 2026-10-02T16:50:17+00:00 | Vulnerability · Source |
| CVE-2026-63802 | suse_vex | SUSE CVE CVE-2026-63802 | known affected: 475 known not affected: 251 recommended: 360 | 2026-10-02T16:50:15+00:00 | Vulnerability · Source |
| CVE-2026-63912 | suse_vex | SUSE CVE CVE-2026-63912 | known affected: 605 known not affected: 121 recommended: 295 | 2026-10-02T16:50:10+00:00 | Vulnerability · Source |
| CVE-2026-63917 | suse_vex | SUSE CVE CVE-2026-63917 | known affected: 670 known not affected: 6 recommended: 559 | 2026-10-02T16:50:08+00:00 | Vulnerability · Source |
| CVE-2026-63921 | suse_vex | SUSE CVE CVE-2026-63921 | known affected: 655 known not affected: 21 recommended: 559 | 2026-10-02T16:50:03+00:00 | Vulnerability · Source |
| CVE-2026-63944 | suse_vex | SUSE CVE CVE-2026-63944 | known affected: 437 known not affected: 309 recommended: 378 | 2026-10-02T16:50:00+00:00 | Vulnerability · Source |
| CVE-2026-63971 | suse_vex | SUSE CVE CVE-2026-63971 | known affected: 658 recommended: 517 | 2026-10-02T16:49:58+00:00 | Vulnerability · Source |
| CVE-2026-63994 | suse_vex | SUSE CVE CVE-2026-63994 | known affected: 553 known not affected: 121 recommended: 456 | 2026-10-02T16:49:55+00:00 | Vulnerability · Source |
| CVE-2026-64038 | suse_vex | SUSE CVE CVE-2026-64038 | known affected: 123 known not affected: 251 | 2026-10-02T16:49:48+00:00 | Vulnerability · Source |
| CVE-2026-64121 | suse_vex | SUSE CVE CVE-2026-64121 | known affected: 496 known not affected: 251 recommended: 298 | 2026-10-02T16:49:43+00:00 | Vulnerability · Source |
| CVE-2026-64189 | suse_vex | SUSE CVE CVE-2026-64189 | known affected: 561 known not affected: 97 recommended: 563 | 2026-10-02T16:49:40+00:00 | Vulnerability · Source |
| CVE-2026-64847 | suse_vex | SUSE CVE CVE-2026-64847 | known affected: 15 recommended: 26 | 2026-10-02T16:49:36+00:00 | Vulnerability · Source |
| CVE-2026-71973 | suse_vex | SUSE CVE CVE-2026-71973 | known affected: 5 known not affected: 55 | 2026-10-02T16:49:25+00:00 | Vulnerability · Source |
| CVE-2026-72217 | suse_vex | SUSE CVE CVE-2026-72217 | known affected: 36 known not affected: 333 recommended: 145 | 2026-10-02T16:49:22+00:00 | Vulnerability · Source |
| CVE-2026-72897 | suse_vex | SUSE CVE CVE-2026-72897 | known affected: 40 known not affected: 553 recommended: 24 | 2026-10-02T16:49:18+00:00 | Vulnerability · Source |
| CVE-2026-73636 | suse_vex | SUSE CVE CVE-2026-73636 | known affected: 183 | 2026-10-02T16:49:15+00:00 | Vulnerability · Source |