VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
78331 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-31689 | suse_vex | SUSE CVE CVE-2026-31689 | known affected: 125 known not affected: 284 | 2026-10-03T23:57:29+00:00 | Vulnerability · Source |
| CVE-2026-39919 | suse_vex | SUSE CVE CVE-2026-39919 | known affected: 130 recommended: 18 | 2026-10-03T23:57:24+00:00 | Vulnerability · Source |
| CVE-2026-64475 | suse_vex | SUSE CVE CVE-2026-64475 | known affected: 183 known not affected: 193 recommended: 4 | 2026-10-03T23:56:58+00:00 | Vulnerability · Source |
| CVE-2026-72129 | suse_vex | SUSE CVE CVE-2026-72129 | known affected: 356 known not affected: 6 recommended: 103 | 2026-10-03T23:56:50+00:00 | Vulnerability · Source |
| CVE-2026-75140 | suse_vex | SUSE CVE CVE-2026-75140 | known affected: 17 recommended: 25 | 2026-10-03T23:56:42+00:00 | Vulnerability · Source |
| CVE-2026-75874 | suse_vex | SUSE CVE CVE-2026-75874 | known affected: 65 recommended: 115 | 2026-10-03T23:56:39+00:00 | Vulnerability · Source |
| CVE-2026-80840 | suse_vex | SUSE CVE CVE-2026-80840 | known affected: 260 known not affected: 93 recommended: 4 | 2026-10-03T23:56:35+00:00 | Vulnerability · Source |
| CVE-2026-80976 | suse_vex | SUSE CVE CVE-2026-80976 | known affected: 293 known not affected: 60 recommended: 4 | 2026-10-03T23:56:33+00:00 | Vulnerability · Source |
| CVE-2026-80983 | suse_vex | SUSE CVE CVE-2026-80983 | known affected: 210 known not affected: 143 recommended: 4 | 2026-10-03T23:56:31+00:00 | Vulnerability · Source |
| CVE-2026-84119 | suse_vex | SUSE CVE CVE-2026-84119 | known affected: 80 recommended: 109 | 2026-10-03T23:56:29+00:00 | Vulnerability · Source |
| CVE-2026-84120 | suse_vex | SUSE CVE CVE-2026-84120 | known affected: 80 recommended: 109 | 2026-10-03T23:56:27+00:00 | Vulnerability · Source |
| CVE-2026-84121 | suse_vex | SUSE CVE CVE-2026-84121 | known affected: 80 recommended: 109 | 2026-10-03T23:56:25+00:00 | Vulnerability · Source |
| CVE-2026-84122 | suse_vex | SUSE CVE CVE-2026-84122 | known affected: 80 recommended: 109 | 2026-10-03T23:56:23+00:00 | Vulnerability · Source |
| CVE-2026-84124 | suse_vex | SUSE CVE CVE-2026-84124 | known affected: 80 recommended: 109 | 2026-10-03T23:56:22+00:00 | Vulnerability · Source |
| CVE-2026-84131 | suse_vex | SUSE CVE CVE-2026-84131 | known affected: 80 recommended: 109 | 2026-10-03T23:56:21+00:00 | Vulnerability · Source |
| CVE-2026-84143 | suse_vex | SUSE CVE CVE-2026-84143 | known affected: 80 recommended: 109 | 2026-10-03T23:56:19+00:00 | Vulnerability · Source |
| CVE-2026-84145 | suse_vex | SUSE CVE CVE-2026-84145 | known affected: 80 recommended: 109 | 2026-10-03T23:56:18+00:00 | Vulnerability · Source |
| CVE-2026-84639 | suse_vex | SUSE CVE CVE-2026-84639 | known affected: 80 recommended: 22 | 2026-10-03T23:56:16+00:00 | Vulnerability · Source |
| CVE-2026-84640 | suse_vex | SUSE CVE CVE-2026-84640 | known affected: 80 recommended: 22 | 2026-10-03T23:56:15+00:00 | Vulnerability · Source |
| CVE-2026-84641 | suse_vex | SUSE CVE CVE-2026-84641 | known affected: 80 recommended: 22 | 2026-10-03T23:56:13+00:00 | Vulnerability · Source |
| CVE-2026-89479 | suse_vex | SUSE CVE CVE-2026-89479 | known affected: 353 recommended: 4 | 2026-10-03T23:56:10+00:00 | Vulnerability · Source |
| CVE-2026-89569 | suse_vex | SUSE CVE CVE-2026-89569 | known affected: 265 known not affected: 88 recommended: 4 | 2026-10-03T23:56:05+00:00 | Vulnerability · Source |
| CVE-2026-89603 | suse_vex | SUSE CVE CVE-2026-89603 | known affected: 210 known not affected: 143 recommended: 4 | 2026-10-03T23:56:03+00:00 | Vulnerability · Source |
| CVE-2026-89631 | suse_vex | SUSE CVE CVE-2026-89631 | known affected: 353 recommended: 4 | 2026-10-03T23:56:01+00:00 | Vulnerability · Source |
| CVE-2026-89636 | suse_vex | SUSE CVE CVE-2026-89636 | known affected: 347 known not affected: 6 recommended: 4 | 2026-10-03T23:56:00+00:00 | Vulnerability · Source |
| CVE-2026-89638 | suse_vex | SUSE CVE CVE-2026-89638 | known affected: 353 recommended: 4 | 2026-10-03T23:55:58+00:00 | Vulnerability · Source |
| CVE-2026-89777 | suse_vex | SUSE CVE CVE-2026-89777 | known affected: 254 known not affected: 93 recommended: 4 | 2026-10-03T23:55:56+00:00 | Vulnerability · Source |
| CVE-2026-89984 | suse_vex | SUSE CVE CVE-2026-89984 | known affected: 204 known not affected: 143 recommended: 4 | 2026-10-03T23:55:52+00:00 | Vulnerability · Source |
| CVE-2026-92005 | suse_vex | SUSE CVE CVE-2026-92005 | known affected: 71 recommended: 99 | 2026-10-03T23:55:48+00:00 | Vulnerability · Source |
| CVE-2026-92006 | suse_vex | SUSE CVE CVE-2026-92006 | known affected: 71 recommended: 99 | 2026-10-03T23:55:46+00:00 | Vulnerability · Source |
| CVE-2026-92007 | suse_vex | SUSE CVE CVE-2026-92007 | known affected: 71 recommended: 99 | 2026-10-03T23:55:45+00:00 | Vulnerability · Source |
| CVE-2026-92008 | suse_vex | SUSE CVE CVE-2026-92008 | known affected: 71 recommended: 99 | 2026-10-03T23:55:43+00:00 | Vulnerability · Source |
| CVE-2026-92009 | suse_vex | SUSE CVE CVE-2026-92009 | known affected: 71 recommended: 99 | 2026-10-03T23:55:41+00:00 | Vulnerability · Source |
| CVE-2026-92010 | suse_vex | SUSE CVE CVE-2026-92010 | known affected: 71 recommended: 99 | 2026-10-03T23:55:38+00:00 | Vulnerability · Source |
| CVE-2026-92011 | suse_vex | SUSE CVE CVE-2026-92011 | known affected: 71 recommended: 99 | 2026-10-03T23:55:37+00:00 | Vulnerability · Source |
| CVE-2026-92012 | suse_vex | SUSE CVE CVE-2026-92012 | known affected: 71 recommended: 99 | 2026-10-03T23:55:35+00:00 | Vulnerability · Source |
| CVE-2026-92013 | suse_vex | SUSE CVE CVE-2026-92013 | known affected: 71 recommended: 99 | 2026-10-03T23:55:33+00:00 | Vulnerability · Source |
| CVE-2026-92014 | suse_vex | SUSE CVE CVE-2026-92014 | known affected: 71 recommended: 11 | 2026-10-03T23:55:32+00:00 | Vulnerability · Source |
| CVE-2026-92015 | suse_vex | SUSE CVE CVE-2026-92015 | known affected: 71 recommended: 99 | 2026-10-03T23:55:30+00:00 | Vulnerability · Source |
| CVE-2026-92016 | suse_vex | SUSE CVE CVE-2026-92016 | known affected: 71 recommended: 99 | 2026-10-03T23:55:28+00:00 | Vulnerability · Source |
| CVE-2026-92017 | suse_vex | SUSE CVE CVE-2026-92017 | known affected: 71 recommended: 99 | 2026-10-03T23:55:26+00:00 | Vulnerability · Source |
| CVE-2026-92018 | suse_vex | SUSE CVE CVE-2026-92018 | known affected: 71 recommended: 99 | 2026-10-03T23:55:24+00:00 | Vulnerability · Source |
| CVE-2026-92019 | suse_vex | SUSE CVE CVE-2026-92019 | known affected: 71 recommended: 99 | 2026-10-03T23:55:23+00:00 | Vulnerability · Source |
| CVE-2026-92020 | suse_vex | SUSE CVE CVE-2026-92020 | known affected: 71 recommended: 99 | 2026-10-03T23:55:21+00:00 | Vulnerability · Source |
| CVE-2026-92021 | suse_vex | SUSE CVE CVE-2026-92021 | known affected: 71 recommended: 11 | 2026-10-03T23:55:18+00:00 | Vulnerability · Source |
| CVE-2026-92022 | suse_vex | SUSE CVE CVE-2026-92022 | known affected: 71 recommended: 99 | 2026-10-03T23:55:17+00:00 | Vulnerability · Source |
| CVE-2026-92023 | suse_vex | SUSE CVE CVE-2026-92023 | known affected: 71 recommended: 99 | 2026-10-03T23:55:15+00:00 | Vulnerability · Source |
| CVE-2026-92024 | suse_vex | SUSE CVE CVE-2026-92024 | known affected: 71 recommended: 99 | 2026-10-03T23:55:13+00:00 | Vulnerability · Source |
| CVE-2026-92025 | suse_vex | SUSE CVE CVE-2026-92025 | known affected: 71 recommended: 99 | 2026-10-03T23:55:12+00:00 | Vulnerability · Source |
| CVE-2026-92026 | suse_vex | SUSE CVE CVE-2026-92026 | known affected: 71 recommended: 99 | 2026-10-03T23:55:10+00:00 | Vulnerability · Source |