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-25942 | suse_vex | SUSE CVE CVE-2026-25942 | recommended: 167 | 2026-10-16T00:31:51+00:00 | Vulnerability · Source |
| CVE-2026-25952 | suse_vex | SUSE CVE CVE-2026-25952 | recommended: 183 | 2026-10-16T00:31:49+00:00 | Vulnerability · Source |
| CVE-2026-25953 | suse_vex | SUSE CVE CVE-2026-25953 | recommended: 160 | 2026-10-16T00:31:47+00:00 | Vulnerability · Source |
| CVE-2026-25954 | suse_vex | SUSE CVE CVE-2026-25954 | recommended: 167 | 2026-10-16T00:31:45+00:00 | Vulnerability · Source |
| CVE-2026-25955 | suse_vex | SUSE CVE CVE-2026-25955 | known affected: 75 recommended: 117 | 2026-10-16T00:31:42+00:00 | Vulnerability · Source |
| CVE-2026-25959 | suse_vex | SUSE CVE CVE-2026-25959 | known affected: 75 recommended: 117 | 2026-10-16T00:31:39+00:00 | Vulnerability · Source |
| CVE-2026-25965 | suse_vex | SUSE CVE CVE-2026-25965 | known affected: 166 known not affected: 92 recommended: 249 | 2026-10-16T00:31:36+00:00 | Vulnerability · Source |
| CVE-2026-25966 | suse_vex | SUSE CVE CVE-2026-25966 | known affected: 88 known not affected: 16 recommended: 258 | 2026-10-16T00:31:34+00:00 | Vulnerability · Source |
| CVE-2026-25967 | suse_vex | SUSE CVE CVE-2026-25967 | known affected: 19 known not affected: 330 recommended: 162 | 2026-10-16T00:31:31+00:00 | Vulnerability · Source |
| CVE-2026-25968 | suse_vex | SUSE CVE CVE-2026-25968 | known affected: 19 known not affected: 330 recommended: 162 | 2026-10-16T00:31:28+00:00 | Vulnerability · Source |
| CVE-2026-25969 | suse_vex | SUSE CVE CVE-2026-25969 | known affected: 19 known not affected: 330 recommended: 162 | 2026-10-16T00:31:25+00:00 | Vulnerability · Source |
| CVE-2026-25970 | suse_vex | SUSE CVE CVE-2026-25970 | known affected: 58 known not affected: 200 recommended: 249 | 2026-10-16T00:31:22+00:00 | Vulnerability · Source |
| CVE-2026-25971 | suse_vex | SUSE CVE CVE-2026-25971 | known affected: 58 known not affected: 200 recommended: 249 | 2026-10-16T00:31:19+00:00 | Vulnerability · Source |
| CVE-2026-25982 | suse_vex | SUSE CVE CVE-2026-25982 | known not affected: 349 recommended: 119 | 2026-10-16T00:31:16+00:00 | Vulnerability · Source |
| CVE-2026-25983 | suse_vex | SUSE CVE CVE-2026-25983 | known affected: 166 known not affected: 16 recommended: 263 | 2026-10-16T00:31:14+00:00 | Vulnerability · Source |
| CVE-2026-25985 | suse_vex | SUSE CVE CVE-2026-25985 | known affected: 55 known not affected: 294 recommended: 162 | 2026-10-16T00:31:12+00:00 | Vulnerability · Source |
| CVE-2026-25986 | suse_vex | SUSE CVE CVE-2026-25986 | known affected: 166 known not affected: 92 recommended: 249 | 2026-10-16T00:31:09+00:00 | Vulnerability · Source |
| CVE-2026-25987 | suse_vex | SUSE CVE CVE-2026-25987 | known affected: 166 known not affected: 16 recommended: 263 | 2026-10-16T00:31:07+00:00 | Vulnerability · Source |
| CVE-2026-25988 | suse_vex | SUSE CVE CVE-2026-25988 | known affected: 166 recommended: 263 | 2026-10-16T00:31:04+00:00 | Vulnerability · Source |
| CVE-2026-25989 | suse_vex | SUSE CVE CVE-2026-25989 | known affected: 166 known not affected: 92 recommended: 249 | 2026-10-16T00:31:02+00:00 | Vulnerability · Source |
| CVE-2026-25990 | suse_vex | SUSE CVE CVE-2026-25990 | known not affected: 57 recommended: 14 | 2026-10-16T00:30:59+00:00 | Vulnerability · Source |
| CVE-2026-25997 | suse_vex | SUSE CVE CVE-2026-25997 | recommended: 173 | 2026-10-16T00:30:57+00:00 | Vulnerability · Source |
| CVE-2026-26007 | suse_vex | SUSE CVE CVE-2026-26007 | known affected: 394 known not affected: 106 recommended: 113 | 2026-10-16T00:30:54+00:00 | Vulnerability · Source |
| CVE-2026-26066 | suse_vex | SUSE CVE CVE-2026-26066 | known affected: 166 known not affected: 16 recommended: 263 | 2026-10-16T00:30:52+00:00 | Vulnerability · Source |
| CVE-2026-26080 | suse_vex | SUSE CVE CVE-2026-26080 | known not affected: 11 recommended: 5 | 2026-10-16T00:30:49+00:00 | Vulnerability · Source |
| CVE-2026-26081 | suse_vex | SUSE CVE CVE-2026-26081 | known not affected: 11 recommended: 6 | 2026-10-16T00:30:46+00:00 | Vulnerability · Source |
| CVE-2026-26157 | suse_vex | SUSE CVE CVE-2026-26157 | known affected: 20 recommended: 115 | 2026-10-16T00:30:44+00:00 | Vulnerability · Source |
| CVE-2026-26158 | suse_vex | SUSE CVE CVE-2026-26158 | known affected: 20 recommended: 115 | 2026-10-16T00:30:42+00:00 | Vulnerability · Source |
| CVE-2026-26269 | suse_vex | SUSE CVE CVE-2026-26269 | first fixed: 2 known affected: 446 recommended: 186 | 2026-10-16T00:30:39+00:00 | Vulnerability · Source |
| CVE-2026-26271 | suse_vex | SUSE CVE CVE-2026-26271 | recommended: 177 | 2026-10-16T00:30:36+00:00 | Vulnerability · Source |
| CVE-2026-26283 | suse_vex | SUSE CVE CVE-2026-26283 | known not affected: 349 recommended: 119 | 2026-10-16T00:30:34+00:00 | Vulnerability · Source |
| CVE-2026-26284 | suse_vex | SUSE CVE CVE-2026-26284 | known affected: 166 recommended: 287 | 2026-10-16T00:30:32+00:00 | Vulnerability · Source |
| CVE-2026-26955 | suse_vex | SUSE CVE CVE-2026-26955 | recommended: 193 | 2026-10-16T00:30:30+00:00 | Vulnerability · Source |
| CVE-2026-26958 | suse_vex | SUSE CVE CVE-2026-26958 | known affected: 42 recommended: 131 | 2026-10-16T00:30:28+00:00 | Vulnerability · Source |
| CVE-2026-26961 | suse_vex | SUSE CVE CVE-2026-26961 | known affected: 14 known not affected: 40 recommended: 63 | 2026-10-16T00:30:26+00:00 | Vulnerability · Source |
| CVE-2026-26962 | suse_vex | SUSE CVE CVE-2026-26962 | known affected: 14 known not affected: 37 recommended: 62 | 2026-10-16T00:30:24+00:00 | Vulnerability · Source |
| CVE-2026-26965 | suse_vex | SUSE CVE CVE-2026-26965 | known not affected: 27 recommended: 193 | 2026-10-16T00:30:23+00:00 | Vulnerability · Source |
| CVE-2026-26983 | suse_vex | SUSE CVE CVE-2026-26983 | known affected: 166 known not affected: 16 recommended: 263 | 2026-10-16T00:30:21+00:00 | Vulnerability · Source |
| CVE-2026-26996 | suse_vex | SUSE CVE CVE-2026-26996 | known affected: 532 known not affected: 344 recommended: 224 | 2026-10-16T00:30:19+00:00 | Vulnerability · Source |
| CVE-2026-27137 | suse_vex | SUSE CVE CVE-2026-27137 | known not affected: 202 recommended: 154 | 2026-10-16T00:30:14+00:00 | Vulnerability · Source |
| CVE-2026-27138 | suse_vex | SUSE CVE CVE-2026-27138 | known not affected: 202 recommended: 127 | 2026-10-16T00:30:13+00:00 | Vulnerability · Source |
| CVE-2026-27139 | suse_vex | SUSE CVE CVE-2026-27139 | known affected: 24 known not affected: 24 recommended: 249 | 2026-10-16T00:30:11+00:00 | Vulnerability · Source |
| CVE-2026-27141 | suse_vex | SUSE CVE CVE-2026-27141 | known not affected: 588 recommended: 17 | 2026-10-16T00:30:09+00:00 | Vulnerability · Source |
| CVE-2026-27142 | suse_vex | SUSE CVE CVE-2026-27142 | known affected: 24 known not affected: 85 recommended: 249 | 2026-10-16T00:30:07+00:00 | Vulnerability · Source |
| CVE-2026-27606 | suse_vex | SUSE CVE CVE-2026-27606 | known affected: 108 known not affected: 432 recommended: 121 | 2026-10-16T00:30:03+00:00 | Vulnerability · Source |
| CVE-2026-27798 | suse_vex | SUSE CVE CVE-2026-27798 | known affected: 54 known not affected: 52 recommended: 248 | 2026-10-16T00:30:02+00:00 | Vulnerability · Source |
| CVE-2026-27799 | suse_vex | SUSE CVE CVE-2026-27799 | first fixed: 14 known affected: 88 known not affected: 16 recommended: 243 | 2026-10-16T00:29:59+00:00 | Vulnerability · Source |
| CVE-2026-27820 | suse_vex | SUSE CVE CVE-2026-27820 | known affected: 572 known not affected: 114 recommended: 120 | 2026-10-16T00:29:57+00:00 | Vulnerability · Source |
| CVE-2026-27904 | suse_vex | SUSE CVE CVE-2026-27904 | known affected: 551 known not affected: 400 recommended: 182 | 2026-10-16T00:29:55+00:00 | Vulnerability · Source |
| CVE-2026-28295 | suse_vex | SUSE CVE CVE-2026-28295 | known affected: 62 recommended: 174 | 2026-10-16T00:29:53+00:00 | Vulnerability · Source |