VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
81558 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2026-98280 | suse_vex | SUSE CVE CVE-2026-98280 | known not affected: 347 | 2026-10-08T16:48:43+00:00 | Vulnerability · Source |
| CVE-2026-98281 | suse_vex | SUSE CVE CVE-2026-98281 | known not affected: 347 | 2026-10-08T16:48:41+00:00 | Vulnerability · Source |
| CVE-2026-98283 | suse_vex | SUSE CVE CVE-2026-98283 | known affected: 208 known not affected: 139 | 2026-10-08T16:48:39+00:00 | Vulnerability · Source |
| CVE-2026-98286 | suse_vex | SUSE CVE CVE-2026-98286 | known affected: 204 known not affected: 143 | 2026-10-08T16:48:36+00:00 | Vulnerability · Source |
| CVE-2026-98287 | suse_vex | SUSE CVE CVE-2026-98287 | known affected: 158 known not affected: 189 | 2026-10-08T16:48:34+00:00 | Vulnerability · Source |
| CVE-2026-98288 | suse_vex | SUSE CVE CVE-2026-98288 | known affected: 254 known not affected: 93 | 2026-10-08T16:48:32+00:00 | Vulnerability · Source |
| CVE-2026-98289 | suse_vex | SUSE CVE CVE-2026-98289 | known affected: 108 known not affected: 239 | 2026-10-08T16:48:30+00:00 | Vulnerability · Source |
| CVE-2026-98291 | suse_vex | SUSE CVE CVE-2026-98291 | known not affected: 347 | 2026-10-08T16:48:28+00:00 | Vulnerability · Source |
| CVE-2026-98292 | suse_vex | SUSE CVE CVE-2026-98292 | known affected: 254 known not affected: 93 | 2026-10-08T16:48:26+00:00 | Vulnerability · Source |
| CVE-2026-98293 | suse_vex | SUSE CVE CVE-2026-98293 | known not affected: 347 | 2026-10-08T16:48:24+00:00 | Vulnerability · Source |
| CVE-2026-98297 | suse_vex | SUSE CVE CVE-2026-98297 | known not affected: 347 | 2026-10-08T16:48:22+00:00 | Vulnerability · Source |
| CVE-2026-98298 | suse_vex | SUSE CVE CVE-2026-98298 | known affected: 297 known not affected: 50 | 2026-10-08T16:48:20+00:00 | Vulnerability · Source |
| CVE-2026-98300 | suse_vex | SUSE CVE CVE-2026-98300 | known affected: 297 known not affected: 50 | 2026-10-08T16:48:17+00:00 | Vulnerability · Source |
| CVE-2026-98301 | suse_vex | SUSE CVE CVE-2026-98301 | known affected: 62 known not affected: 285 | 2026-10-08T16:48:15+00:00 | Vulnerability · Source |
| CVE-2026-98303 | suse_vex | SUSE CVE CVE-2026-98303 | known affected: 301 known not affected: 46 | 2026-10-08T16:48:12+00:00 | Vulnerability · Source |
| CVE-2026-98304 | suse_vex | SUSE CVE CVE-2026-98304 | known affected: 204 known not affected: 143 | 2026-10-08T16:48:09+00:00 | Vulnerability · Source |
| CVE-2026-98305 | suse_vex | SUSE CVE CVE-2026-98305 | known not affected: 347 | 2026-10-08T16:48:06+00:00 | Vulnerability · Source |
| CVE-2026-98308 | suse_vex | SUSE CVE CVE-2026-98308 | known affected: 297 known not affected: 50 | 2026-10-08T16:48:03+00:00 | Vulnerability · Source |
| CVE-2026-98309 | suse_vex | SUSE CVE CVE-2026-98309 | known affected: 297 known not affected: 50 | 2026-10-08T16:48:00+00:00 | Vulnerability · Source |
| CVE-2026-98310 | suse_vex | SUSE CVE CVE-2026-98310 | known not affected: 347 | 2026-10-08T16:47:57+00:00 | Vulnerability · Source |
| CVE-2026-98311 | suse_vex | SUSE CVE CVE-2026-98311 | known affected: 208 known not affected: 139 | 2026-10-08T16:47:55+00:00 | Vulnerability · Source |
| CVE-2026-98312 | suse_vex | SUSE CVE CVE-2026-98312 | known affected: 301 known not affected: 46 | 2026-10-08T16:47:52+00:00 | Vulnerability · Source |
| CVE-2026-98315 | suse_vex | SUSE CVE CVE-2026-98315 | known not affected: 347 | 2026-10-08T16:47:49+00:00 | Vulnerability · Source |
| CVE-2026-98316 | suse_vex | SUSE CVE CVE-2026-98316 | known affected: 220 known not affected: 127 | 2026-10-08T16:47:47+00:00 | Vulnerability · Source |
| CVE-2026-98317 | suse_vex | SUSE CVE CVE-2026-98317 | known affected: 110 known not affected: 237 | 2026-10-08T16:47:44+00:00 | Vulnerability · Source |
| CVE-2026-98319 | suse_vex | SUSE CVE CVE-2026-98319 | known affected: 208 known not affected: 139 | 2026-10-08T16:47:42+00:00 | Vulnerability · Source |
| CVE-2026-98320 | suse_vex | SUSE CVE CVE-2026-98320 | known affected: 208 known not affected: 137 | 2026-10-08T16:47:39+00:00 | Vulnerability · Source |
| CVE-2026-98323 | suse_vex | SUSE CVE CVE-2026-98323 | known affected: 230 known not affected: 117 | 2026-10-08T16:47:36+00:00 | Vulnerability · Source |
| CVE-2026-98324 | suse_vex | SUSE CVE CVE-2026-98324 | known not affected: 347 | 2026-10-08T16:47:33+00:00 | Vulnerability · Source |
| CVE-2026-98326 | suse_vex | SUSE CVE CVE-2026-98326 | known affected: 297 known not affected: 50 | 2026-10-08T16:47:30+00:00 | Vulnerability · Source |
| CVE-2026-98328 | suse_vex | SUSE CVE CVE-2026-98328 | known affected: 158 known not affected: 189 | 2026-10-08T16:47:28+00:00 | Vulnerability · Source |
| CVE-2026-98329 | suse_vex | SUSE CVE CVE-2026-98329 | known affected: 295 known not affected: 52 | 2026-10-08T16:47:25+00:00 | Vulnerability · Source |
| CVE-2026-98330 | suse_vex | SUSE CVE CVE-2026-98330 | known affected: 347 | 2026-10-08T16:47:23+00:00 | Vulnerability · Source |
| CVE-2026-98333 | suse_vex | SUSE CVE CVE-2026-98333 | known affected: 347 | 2026-10-08T16:47:20+00:00 | Vulnerability · Source |
| CVE-2026-98336 | suse_vex | SUSE CVE CVE-2026-98336 | known affected: 62 known not affected: 285 | 2026-10-08T16:47:18+00:00 | Vulnerability · Source |
| CVE-2026-98337 | suse_vex | SUSE CVE CVE-2026-98337 | known affected: 295 known not affected: 52 | 2026-10-08T16:47:16+00:00 | Vulnerability · Source |