VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
305868 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2026-98223 | suse_vex | SUSE CVE CVE-2026-98223 | known not affected: 347 | 2026-10-08T16:50:02+00:00 | Vulnerability · Source |
| CVE-2026-98224 | suse_vex | SUSE CVE CVE-2026-98224 | known not affected: 347 | 2026-10-08T16:49:59+00:00 | Vulnerability · Source |
| CVE-2026-98225 | suse_vex | SUSE CVE CVE-2026-98225 | known not affected: 347 | 2026-10-08T16:49:56+00:00 | Vulnerability · Source |
| CVE-2026-98226 | suse_vex | SUSE CVE CVE-2026-98226 | known not affected: 347 | 2026-10-08T16:49:54+00:00 | Vulnerability · Source |
| CVE-2026-98227 | suse_vex | SUSE CVE CVE-2026-98227 | known affected: 297 known not affected: 50 | 2026-10-08T16:49:52+00:00 | Vulnerability · Source |
| CVE-2026-98228 | suse_vex | SUSE CVE CVE-2026-98228 | known affected: 29 known not affected: 318 | 2026-10-08T16:49:50+00:00 | Vulnerability · Source |
| CVE-2026-98229 | suse_vex | SUSE CVE CVE-2026-98229 | known affected: 338 known not affected: 9 | 2026-10-08T16:49:47+00:00 | Vulnerability · Source |
| CVE-2026-98231 | suse_vex | SUSE CVE CVE-2026-98231 | known not affected: 347 | 2026-10-08T16:49:45+00:00 | Vulnerability · Source |
| CVE-2026-98232 | suse_vex | SUSE CVE CVE-2026-98232 | known not affected: 347 | 2026-10-08T16:49:42+00:00 | Vulnerability · Source |
| CVE-2026-98233 | suse_vex | SUSE CVE CVE-2026-98233 | known affected: 208 known not affected: 139 | 2026-10-08T16:49:40+00:00 | Vulnerability · Source |
| CVE-2026-98234 | suse_vex | SUSE CVE CVE-2026-98234 | known affected: 343 known not affected: 4 | 2026-10-08T16:49:38+00:00 | Vulnerability · Source |
| CVE-2026-98235 | suse_vex | SUSE CVE CVE-2026-98235 | known affected: 29 known not affected: 318 | 2026-10-08T16:49:36+00:00 | Vulnerability · Source |
| CVE-2026-98241 | suse_vex | SUSE CVE CVE-2026-98241 | known affected: 297 known not affected: 50 | 2026-10-08T16:49:34+00:00 | Vulnerability · Source |
| CVE-2026-98242 | suse_vex | SUSE CVE CVE-2026-98242 | known not affected: 347 | 2026-10-08T16:49:31+00:00 | Vulnerability · Source |
| CVE-2026-98243 | suse_vex | SUSE CVE CVE-2026-98243 | known not affected: 347 | 2026-10-08T16:49:29+00:00 | Vulnerability · Source |
| CVE-2026-98244 | suse_vex | SUSE CVE CVE-2026-98244 | known not affected: 347 | 2026-10-08T16:49:26+00:00 | Vulnerability · Source |
| CVE-2026-98245 | suse_vex | SUSE CVE CVE-2026-98245 | known affected: 158 known not affected: 189 | 2026-10-08T16:49:24+00:00 | Vulnerability · Source |
| CVE-2026-98246 | suse_vex | SUSE CVE CVE-2026-98246 | known affected: 62 known not affected: 285 | 2026-10-08T16:49:21+00:00 | Vulnerability · Source |
| CVE-2026-98247 | suse_vex | SUSE CVE CVE-2026-98247 | known affected: 62 known not affected: 285 | 2026-10-08T16:49:18+00:00 | Vulnerability · Source |
| CVE-2026-98249 | suse_vex | SUSE CVE CVE-2026-98249 | known affected: 62 known not affected: 285 | 2026-10-08T16:49:16+00:00 | Vulnerability · Source |
| CVE-2026-98250 | suse_vex | SUSE CVE CVE-2026-98250 | known not affected: 347 | 2026-10-08T16:49:15+00:00 | Vulnerability · Source |
| CVE-2026-98252 | suse_vex | SUSE CVE CVE-2026-98252 | known affected: 297 known not affected: 50 | 2026-10-08T16:49:13+00:00 | Vulnerability · Source |
| CVE-2026-98254 | suse_vex | SUSE CVE CVE-2026-98254 | known affected: 158 known not affected: 189 | 2026-10-08T16:49:11+00:00 | Vulnerability · Source |
| CVE-2026-98255 | suse_vex | SUSE CVE CVE-2026-98255 | known affected: 254 known not affected: 93 | 2026-10-08T16:49:10+00:00 | Vulnerability · Source |
| CVE-2026-98256 | suse_vex | SUSE CVE CVE-2026-98256 | known not affected: 347 | 2026-10-08T16:49:08+00:00 | Vulnerability · Source |
| CVE-2026-98258 | suse_vex | SUSE CVE CVE-2026-98258 | known not affected: 347 | 2026-10-08T16:49:06+00:00 | Vulnerability · Source |
| CVE-2026-98261 | suse_vex | SUSE CVE CVE-2026-98261 | known not affected: 347 | 2026-10-08T16:49:03+00:00 | Vulnerability · Source |
| CVE-2026-98262 | suse_vex | SUSE CVE CVE-2026-98262 | known affected: 301 known not affected: 46 | 2026-10-08T16:49:01+00:00 | Vulnerability · Source |
| CVE-2026-98266 | suse_vex | SUSE CVE CVE-2026-98266 | known affected: 301 known not affected: 46 | 2026-10-08T16:48:58+00:00 | Vulnerability · Source |
| CVE-2026-98267 | suse_vex | SUSE CVE CVE-2026-98267 | known not affected: 347 | 2026-10-08T16:48:56+00:00 | Vulnerability · Source |
| CVE-2026-98269 | suse_vex | SUSE CVE CVE-2026-98269 | known affected: 297 known not affected: 50 | 2026-10-08T16:48:54+00:00 | Vulnerability · Source |
| CVE-2026-98272 | suse_vex | SUSE CVE CVE-2026-98272 | known affected: 158 known not affected: 189 | 2026-10-08T16:48:52+00:00 | Vulnerability · Source |
| CVE-2026-98274 | suse_vex | SUSE CVE CVE-2026-98274 | known not affected: 347 | 2026-10-08T16:48:51+00:00 | Vulnerability · Source |
| CVE-2026-98275 | suse_vex | SUSE CVE CVE-2026-98275 | known affected: 241 known not affected: 106 | 2026-10-08T16:48:49+00:00 | Vulnerability · Source |
| CVE-2026-98276 | suse_vex | SUSE CVE CVE-2026-98276 | known affected: 301 known not affected: 46 | 2026-10-08T16:48:47+00:00 | Vulnerability · Source |
| CVE-2026-98279 | suse_vex | SUSE CVE CVE-2026-98279 | known affected: 108 known not affected: 239 | 2026-10-08T16:48:46+00:00 | Vulnerability · Source |