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-98286 | redhat_vex | kernel: drop_monitor: use timer_shutdown_sync() to prevent timer rearming during teardown | known affected: 249 known not affected: 28 | 2026-10-16T00:42:54+00:00 | Vulnerability · Source |
| CVE-2026-18938 | suse_vex | SUSE CVE CVE-2026-18938 | known affected: 31 known not affected: 242 recommended: 9 | 2026-10-16T00:42:54+00:00 | Vulnerability · Source |
| CVE-2026-19032 | suse_vex | SUSE CVE CVE-2026-19032 | known affected: 28 recommended: 77 | 2026-10-16T00:42:52+00:00 | Vulnerability · Source |
| CVE-2026-19445 | suse_vex | SUSE CVE CVE-2026-19445 | known affected: 452 known not affected: 21 | 2026-10-16T00:42:44+00:00 | Vulnerability · Source |
| CVE-2026-19487 | suse_vex | SUSE CVE CVE-2026-19487 | known affected: 172 known not affected: 15 | 2026-10-16T00:42:41+00:00 | Vulnerability · Source |
| CVE-2026-19534 | suse_vex | SUSE CVE CVE-2026-19534 | known affected: 80 known not affected: 246 recommended: 33 | 2026-10-16T00:42:39+00:00 | Vulnerability · Source |
| CVE-2026-19553 | suse_vex | SUSE CVE CVE-2026-19553 | known affected: 169 known not affected: 304 | 2026-10-16T00:42:36+00:00 | Vulnerability · Source |
| CVE-2026-19685 | suse_vex | SUSE CVE CVE-2026-19685 | known affected: 442 known not affected: 82 recommended: 174 | 2026-10-16T00:42:19+00:00 | Vulnerability · Source |
| CVE-2026-19730 | suse_vex | SUSE CVE CVE-2026-19730 | known affected: 8 known not affected: 124 recommended: 9 | 2026-10-16T00:42:17+00:00 | Vulnerability · Source |
| CVE-2026-19931 | suse_vex | SUSE CVE CVE-2026-19931 | known affected: 168 known not affected: 18 recommended: 9 | 2026-10-16T00:42:15+00:00 | Vulnerability · Source |
| CVE-2026-20608 | suse_vex | SUSE CVE CVE-2026-20608 | known affected: 88 recommended: 528 | 2026-10-16T00:42:11+00:00 | Vulnerability · Source |
| CVE-2026-20635 | suse_vex | SUSE CVE CVE-2026-20635 | known affected: 88 recommended: 503 | 2026-10-16T00:42:09+00:00 | Vulnerability · Source |
| CVE-2026-20636 | suse_vex | SUSE CVE CVE-2026-20636 | known affected: 88 recommended: 503 | 2026-10-16T00:42:07+00:00 | Vulnerability · Source |
| CVE-2026-20643 | suse_vex | SUSE CVE CVE-2026-20643 | known affected: 122 recommended: 336 | 2026-10-16T00:42:05+00:00 | Vulnerability · Source |
| CVE-2026-20644 | suse_vex | SUSE CVE CVE-2026-20644 | known affected: 88 recommended: 503 | 2026-10-16T00:42:02+00:00 | Vulnerability · Source |
| CVE-2026-20652 | suse_vex | SUSE CVE CVE-2026-20652 | known affected: 88 recommended: 503 | 2026-10-16T00:42:00+00:00 | Vulnerability · Source |
| CVE-2026-20664 | suse_vex | SUSE CVE CVE-2026-20664 | known affected: 122 recommended: 311 | 2026-10-16T00:41:58+00:00 | Vulnerability · Source |
| CVE-2026-20665 | suse_vex | SUSE CVE CVE-2026-20665 | known affected: 122 recommended: 336 | 2026-10-16T00:41:55+00:00 | Vulnerability · Source |
| CVE-2026-20676 | suse_vex | SUSE CVE CVE-2026-20676 | known affected: 88 recommended: 503 | 2026-10-16T00:41:53+00:00 | Vulnerability · Source |
| CVE-2026-20691 | suse_vex | SUSE CVE CVE-2026-20691 | known affected: 122 recommended: 311 | 2026-10-16T00:41:50+00:00 | Vulnerability · Source |
| CVE-2026-20884 | suse_vex | SUSE CVE CVE-2026-20884 | known not affected: 9 recommended: 38 | 2026-10-16T00:41:48+00:00 | Vulnerability · Source |
| CVE-2026-20889 | suse_vex | SUSE CVE CVE-2026-20889 | known not affected: 9 recommended: 40 | 2026-10-16T00:41:46+00:00 | Vulnerability · Source |
| CVE-2026-20911 | suse_vex | SUSE CVE CVE-2026-20911 | known not affected: 15 recommended: 41 | 2026-10-16T00:41:44+00:00 | Vulnerability · Source |
| CVE-2026-21620 | suse_vex | SUSE CVE CVE-2026-21620 | known affected: 48 recommended: 94 | 2026-10-16T00:41:39+00:00 | Vulnerability · Source |
| CVE-2026-21637 | suse_vex | SUSE CVE CVE-2026-21637 | known affected: 168 recommended: 213 | 2026-10-16T00:41:37+00:00 | Vulnerability · Source |
| CVE-2026-21710 | suse_vex | SUSE CVE CVE-2026-21710 | known affected: 144 recommended: 198 | 2026-10-16T00:41:34+00:00 | Vulnerability · Source |
| CVE-2026-21712 | suse_vex | SUSE CVE CVE-2026-21712 | known not affected: 303 recommended: 67 | 2026-10-16T00:41:32+00:00 | Vulnerability · Source |
| CVE-2026-21713 | suse_vex | SUSE CVE CVE-2026-21713 | known affected: 144 recommended: 190 | 2026-10-16T00:41:30+00:00 | Vulnerability · Source |
| CVE-2026-21714 | suse_vex | SUSE CVE CVE-2026-21714 | known affected: 144 recommended: 190 | 2026-10-16T00:41:28+00:00 | Vulnerability · Source |
| CVE-2026-21715 | suse_vex | SUSE CVE CVE-2026-21715 | known not affected: 226 recommended: 126 | 2026-10-16T00:41:26+00:00 | Vulnerability · Source |
| CVE-2026-21716 | suse_vex | SUSE CVE CVE-2026-21716 | known not affected: 226 recommended: 126 | 2026-10-16T00:41:24+00:00 | Vulnerability · Source |
| CVE-2026-21717 | suse_vex | SUSE CVE CVE-2026-21717 | known affected: 133 known not affected: 32 recommended: 170 | 2026-10-16T00:41:21+00:00 | Vulnerability · Source |
| CVE-2026-22007 | suse_vex | SUSE CVE CVE-2026-22007 | known affected: 402 known not affected: 306 recommended: 877 | 2026-10-16T00:41:18+00:00 | Vulnerability · Source |
| CVE-2026-22008 | suse_vex | SUSE CVE CVE-2026-22008 | known not affected: 672 recommended: 110 | 2026-10-16T00:41:15+00:00 | Vulnerability · Source |
| CVE-2026-22013 | suse_vex | SUSE CVE CVE-2026-22013 | known affected: 608 known not affected: 70 recommended: 849 | 2026-10-16T00:41:12+00:00 | Vulnerability · Source |
| CVE-2026-22016 | suse_vex | SUSE CVE CVE-2026-22016 | known affected: 608 known not affected: 70 recommended: 870 | 2026-10-16T00:41:10+00:00 | Vulnerability · Source |
| CVE-2026-22018 | suse_vex | SUSE CVE CVE-2026-22018 | known affected: 608 known not affected: 70 recommended: 849 | 2026-10-16T00:41:07+00:00 | Vulnerability · Source |
| CVE-2026-22021 | suse_vex | SUSE CVE CVE-2026-22021 | known affected: 608 known not affected: 70 recommended: 870 | 2026-10-16T00:41:04+00:00 | Vulnerability · Source |
| CVE-2026-22693 | suse_vex | SUSE CVE CVE-2026-22693 | known affected: 447 known not affected: 237 recommended: 94 | 2026-10-16T00:41:01+00:00 | Vulnerability · Source |
| CVE-2026-22695 | suse_vex | SUSE CVE CVE-2026-22695 | known affected: 354 known not affected: 300 recommended: 479 | 2026-10-16T00:40:59+00:00 | Vulnerability · Source |
| CVE-2026-22701 | suse_vex | SUSE CVE CVE-2026-22701 | known affected: 25 recommended: 19 | 2026-10-16T00:40:56+00:00 | Vulnerability · Source |
| CVE-2026-22703 | suse_vex | SUSE CVE CVE-2026-22703 | known affected: 14 known not affected: 3 recommended: 31 | 2026-10-16T00:40:53+00:00 | Vulnerability · Source |
| CVE-2026-22770 | suse_vex | SUSE CVE CVE-2026-22770 | known not affected: 179 recommended: 160 | 2026-10-16T00:40:50+00:00 | Vulnerability · Source |
| CVE-2026-22772 | suse_vex | SUSE CVE CVE-2026-22772 | first fixed: 2 known affected: 14 known not affected: 258 recommended: 36 | 2026-10-16T00:40:48+00:00 | Vulnerability · Source |
| CVE-2026-22801 | suse_vex | SUSE CVE CVE-2026-22801 | known affected: 439 known not affected: 228 recommended: 471 | 2026-10-16T00:40:45+00:00 | Vulnerability · Source |
| CVE-2026-22851 | suse_vex | SUSE CVE CVE-2026-22851 | known not affected: 8 recommended: 117 | 2026-10-16T00:40:41+00:00 | Vulnerability · Source |
| CVE-2026-22852 | suse_vex | SUSE CVE CVE-2026-22852 | recommended: 193 | 2026-10-16T00:40:39+00:00 | Vulnerability · Source |
| CVE-2026-22853 | suse_vex | SUSE CVE CVE-2026-22853 | known not affected: 38 recommended: 123 | 2026-10-16T00:40:36+00:00 | Vulnerability · Source |
| CVE-2026-22854 | suse_vex | SUSE CVE CVE-2026-22854 | recommended: 182 | 2026-10-16T00:40:33+00:00 | Vulnerability · Source |
| CVE-2026-22855 | suse_vex | SUSE CVE CVE-2026-22855 | recommended: 193 | 2026-10-16T00:40:30+00:00 | Vulnerability · Source |