VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
306114 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-97574 | suse_vex | SUSE CVE CVE-2026-97574 | known not affected: 347 recommended: 4 | 2026-10-08T16:52:05+00:00 | Vulnerability · Source |
| CVE-2026-97605 | suse_vex | SUSE CVE CVE-2026-97605 | known affected: 108 known not affected: 239 recommended: 4 | 2026-10-08T16:52:02+00:00 | Vulnerability · Source |
| CVE-2026-97902 | suse_vex | SUSE CVE CVE-2026-97902 | known affected: 29 known not affected: 318 recommended: 4 | 2026-10-08T16:52:00+00:00 | Vulnerability · Source |
| CVE-2026-97934 | suse_vex | SUSE CVE CVE-2026-97934 | known affected: 149 known not affected: 239 recommended: 4 | 2026-10-08T16:51:57+00:00 | Vulnerability · Source |
| CVE-2026-97940 | suse_vex | SUSE CVE CVE-2026-97940 | known affected: 386 known not affected: 4 recommended: 4 | 2026-10-08T16:51:55+00:00 | Vulnerability · Source |
| CVE-2026-97947 | suse_vex | SUSE CVE CVE-2026-97947 | known affected: 102 known not affected: 286 recommended: 4 | 2026-10-08T16:51:52+00:00 | Vulnerability · Source |
| CVE-2026-97957 | suse_vex | SUSE CVE CVE-2026-97957 | known affected: 230 known not affected: 117 recommended: 4 | 2026-10-08T16:51:50+00:00 | Vulnerability · Source |
| CVE-2026-98003 | suse_vex | SUSE CVE CVE-2026-98003 | known affected: 271 known not affected: 117 recommended: 4 | 2026-10-08T16:51:48+00:00 | Vulnerability · Source |
| CVE-2026-98028 | suse_vex | SUSE CVE CVE-2026-98028 | known not affected: 347 recommended: 4 | 2026-10-08T16:51:45+00:00 | Vulnerability · Source |
| CVE-2026-98029 | suse_vex | SUSE CVE CVE-2026-98029 | known not affected: 347 recommended: 4 | 2026-10-08T16:51:43+00:00 | Vulnerability · Source |
| CVE-2026-98030 | suse_vex | SUSE CVE CVE-2026-98030 | known affected: 341 known not affected: 47 recommended: 4 | 2026-10-08T16:51:41+00:00 | Vulnerability · Source |
| CVE-2026-98091 | suse_vex | SUSE CVE CVE-2026-98091 | known affected: 323 known not affected: 65 recommended: 4 | 2026-10-08T16:51:38+00:00 | Vulnerability · Source |
| CVE-2026-98176 | suse_vex | SUSE CVE CVE-2026-98176 | known affected: 254 known not affected: 93 | 2026-10-08T16:51:35+00:00 | Vulnerability · Source |
| CVE-2026-98177 | suse_vex | SUSE CVE CVE-2026-98177 | known affected: 343 known not affected: 4 | 2026-10-08T16:51:31+00:00 | Vulnerability · Source |
| CVE-2026-98178 | suse_vex | SUSE CVE CVE-2026-98178 | known not affected: 347 | 2026-10-08T16:51:29+00:00 | Vulnerability · Source |
| CVE-2026-98179 | suse_vex | SUSE CVE CVE-2026-98179 | known affected: 62 known not affected: 285 | 2026-10-08T16:51:27+00:00 | Vulnerability · Source |
| CVE-2026-98180 | suse_vex | SUSE CVE CVE-2026-98180 | known affected: 108 known not affected: 239 | 2026-10-08T16:51:24+00:00 | Vulnerability · Source |
| CVE-2026-98181 | suse_vex | SUSE CVE CVE-2026-98181 | known affected: 158 known not affected: 189 | 2026-10-08T16:51:20+00:00 | Vulnerability · Source |
| CVE-2026-98182 | suse_vex | SUSE CVE CVE-2026-98182 | known affected: 208 known not affected: 139 | 2026-10-08T16:51:18+00:00 | Vulnerability · Source |
| CVE-2026-98183 | suse_vex | SUSE CVE CVE-2026-98183 | known not affected: 347 | 2026-10-08T16:51:16+00:00 | Vulnerability · Source |
| CVE-2026-98184 | suse_vex | SUSE CVE CVE-2026-98184 | known not affected: 347 | 2026-10-08T16:51:14+00:00 | Vulnerability · Source |
| CVE-2026-98186 | suse_vex | SUSE CVE CVE-2026-98186 | known affected: 301 known not affected: 46 | 2026-10-08T16:51:11+00:00 | Vulnerability · Source |
| CVE-2026-98188 | suse_vex | SUSE CVE CVE-2026-98188 | known affected: 301 known not affected: 46 | 2026-10-08T16:51:09+00:00 | Vulnerability · Source |
| CVE-2026-98189 | suse_vex | SUSE CVE CVE-2026-98189 | known affected: 297 known not affected: 50 | 2026-10-08T16:51:07+00:00 | Vulnerability · Source |
| CVE-2026-98191 | suse_vex | SUSE CVE CVE-2026-98191 | known affected: 208 known not affected: 139 | 2026-10-08T16:51:04+00:00 | Vulnerability · Source |
| CVE-2026-98192 | suse_vex | SUSE CVE CVE-2026-98192 | known affected: 158 known not affected: 189 | 2026-10-08T16:51:02+00:00 | Vulnerability · Source |
| CVE-2026-98194 | suse_vex | SUSE CVE CVE-2026-98194 | known affected: 301 known not affected: 46 | 2026-10-08T16:51:00+00:00 | Vulnerability · Source |
| CVE-2026-98195 | suse_vex | SUSE CVE CVE-2026-98195 | known affected: 295 known not affected: 52 | 2026-10-08T16:50:58+00:00 | Vulnerability · Source |
| CVE-2026-98196 | suse_vex | SUSE CVE CVE-2026-98196 | known affected: 297 known not affected: 50 | 2026-10-08T16:50:56+00:00 | Vulnerability · Source |
| CVE-2026-98197 | suse_vex | SUSE CVE CVE-2026-98197 | known affected: 269 known not affected: 78 | 2026-10-08T16:50:54+00:00 | Vulnerability · Source |
| CVE-2026-98198 | suse_vex | SUSE CVE CVE-2026-98198 | known affected: 158 known not affected: 189 | 2026-10-08T16:50:52+00:00 | Vulnerability · Source |
| CVE-2026-98199 | suse_vex | SUSE CVE CVE-2026-98199 | known affected: 158 known not affected: 189 | 2026-10-08T16:50:50+00:00 | Vulnerability · Source |
| CVE-2026-98200 | suse_vex | SUSE CVE CVE-2026-98200 | known not affected: 347 | 2026-10-08T16:50:47+00:00 | Vulnerability · Source |
| CVE-2026-98201 | suse_vex | SUSE CVE CVE-2026-98201 | known affected: 269 known not affected: 78 | 2026-10-08T16:50:45+00:00 | Vulnerability · Source |
| CVE-2026-98203 | suse_vex | SUSE CVE CVE-2026-98203 | known affected: 263 known not affected: 84 | 2026-10-08T16:50:41+00:00 | Vulnerability · Source |
| CVE-2026-98205 | suse_vex | SUSE CVE CVE-2026-98205 | known affected: 301 known not affected: 46 | 2026-10-08T16:50:39+00:00 | Vulnerability · Source |
| CVE-2026-98208 | suse_vex | SUSE CVE CVE-2026-98208 | known affected: 269 known not affected: 78 | 2026-10-08T16:50:36+00:00 | Vulnerability · Source |
| CVE-2026-98209 | suse_vex | SUSE CVE CVE-2026-98209 | known affected: 158 known not affected: 189 | 2026-10-08T16:50:33+00:00 | Vulnerability · Source |
| CVE-2026-98210 | suse_vex | SUSE CVE CVE-2026-98210 | known affected: 297 known not affected: 50 | 2026-10-08T16:50:30+00:00 | Vulnerability · Source |
| CVE-2026-98211 | suse_vex | SUSE CVE CVE-2026-98211 | known not affected: 347 | 2026-10-08T16:50:27+00:00 | Vulnerability · Source |
| CVE-2026-98212 | suse_vex | SUSE CVE CVE-2026-98212 | known affected: 158 known not affected: 189 | 2026-10-08T16:50:24+00:00 | Vulnerability · Source |
| CVE-2026-98213 | suse_vex | SUSE CVE CVE-2026-98213 | known affected: 176 known not affected: 171 | 2026-10-08T16:50:22+00:00 | Vulnerability · Source |
| CVE-2026-98214 | suse_vex | SUSE CVE CVE-2026-98214 | known not affected: 347 | 2026-10-08T16:50:20+00:00 | Vulnerability · Source |
| CVE-2026-98215 | suse_vex | SUSE CVE CVE-2026-98215 | known not affected: 347 | 2026-10-08T16:50:18+00:00 | Vulnerability · Source |
| CVE-2026-98216 | suse_vex | SUSE CVE CVE-2026-98216 | known affected: 62 known not affected: 285 | 2026-10-08T16:50:16+00:00 | Vulnerability · Source |
| CVE-2026-98217 | suse_vex | SUSE CVE CVE-2026-98217 | known affected: 297 known not affected: 50 | 2026-10-08T16:50:14+00:00 | Vulnerability · Source |
| CVE-2026-98218 | suse_vex | SUSE CVE CVE-2026-98218 | known not affected: 347 | 2026-10-08T16:50:12+00:00 | Vulnerability · Source |
| CVE-2026-98219 | suse_vex | SUSE CVE CVE-2026-98219 | known not affected: 347 | 2026-10-08T16:50:09+00:00 | Vulnerability · Source |
| CVE-2026-98221 | suse_vex | SUSE CVE CVE-2026-98221 | known affected: 126 known not affected: 221 | 2026-10-08T16:50:07+00:00 | Vulnerability · Source |
| CVE-2026-98222 | suse_vex | SUSE CVE CVE-2026-98222 | known affected: 301 known not affected: 46 | 2026-10-08T16:50:04+00:00 | Vulnerability · Source |