VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292117 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-49981 | suse_vex | SUSE CVE CVE-2024-49981 | known affected: 381 known not affected: 138 recommended: 641 | 2026-07-23T01:57:28+00:00 | Vulnerability · Source |
| CVE-2024-49990 | suse_vex | SUSE CVE CVE-2024-49990 | known not affected: 379 recommended: 65 | 2026-07-23T01:57:24+00:00 | Vulnerability · Source |
| CVE-2024-49992 | suse_vex | SUSE CVE CVE-2024-49992 | known not affected: 402 recommended: 65 | 2026-07-23T01:57:22+00:00 | Vulnerability · Source |
| CVE-2024-50010 | suse_vex | SUSE CVE CVE-2024-50010 | known not affected: 230 recommended: 6 | 2026-07-23T01:57:17+00:00 | Vulnerability · Source |
| CVE-2024-50059 | suse_vex | SUSE CVE CVE-2024-50059 | known affected: 365 known not affected: 294 recommended: 643 | 2026-07-23T01:57:07+00:00 | Vulnerability · Source |
| CVE-2024-50070 | suse_vex | SUSE CVE CVE-2024-50070 | known not affected: 379 recommended: 6 | 2026-07-23T01:57:03+00:00 | Vulnerability · Source |
| CVE-2024-50078 | suse_vex | SUSE CVE CVE-2024-50078 | known affected: 354 known not affected: 263 recommended: 684 | 2026-07-23T01:57:00+00:00 | Vulnerability · Source |
| CVE-2024-50083 | suse_vex | SUSE CVE CVE-2024-50083 | known affected: 523 known not affected: 215 recommended: 371 | 2026-07-23T01:56:57+00:00 | Vulnerability · Source |
| CVE-2024-50093 | suse_vex | SUSE CVE CVE-2024-50093 | known affected: 450 known not affected: 224 recommended: 628 | 2026-07-23T01:56:56+00:00 | Vulnerability · Source |
| CVE-2024-50098 | suse_vex | SUSE CVE CVE-2024-50098 | known affected: 450 known not affected: 224 recommended: 585 | 2026-07-23T01:56:54+00:00 | Vulnerability · Source |
| CVE-2024-50113 | suse_vex | SUSE CVE CVE-2024-50113 | known not affected: 370 recommended: 6 | 2026-07-23T01:56:51+00:00 | Vulnerability · Source |
| CVE-2024-50120 | suse_vex | SUSE CVE CVE-2024-50120 | known not affected: 370 recommended: 49 | 2026-07-23T01:56:50+00:00 | Vulnerability · Source |
| CVE-2024-50126 | suse_vex | SUSE CVE CVE-2024-50126 | known affected: 419 known not affected: 347 recommended: 391 | 2026-07-23T01:56:48+00:00 | Vulnerability · Source |
| CVE-2024-50136 | suse_vex | SUSE CVE CVE-2024-50136 | known affected: 364 known not affected: 290 recommended: 417 | 2026-07-23T01:56:47+00:00 | Vulnerability · Source |
| CVE-2024-50137 | suse_vex | SUSE CVE CVE-2024-50137 | known not affected: 370 recommended: 6 | 2026-07-23T01:56:45+00:00 | Vulnerability · Source |
| CVE-2024-50144 | suse_vex | SUSE CVE CVE-2024-50144 | known not affected: 379 recommended: 65 | 2026-07-23T01:56:44+00:00 | Vulnerability · Source |
| CVE-2024-50145 | suse_vex | SUSE CVE CVE-2024-50145 | known affected: 398 known not affected: 396 recommended: 316 | 2026-07-23T01:56:43+00:00 | Vulnerability · Source |
| CVE-2024-50156 | suse_vex | SUSE CVE CVE-2024-50156 | known affected: 354 known not affected: 254 recommended: 585 | 2026-07-23T01:56:41+00:00 | Vulnerability · Source |
| CVE-2024-50157 | suse_vex | SUSE CVE CVE-2024-50157 | known affected: 394 known not affected: 298 recommended: 316 | 2026-07-23T01:56:40+00:00 | Vulnerability · Source |
| CVE-2024-50170 | suse_vex | SUSE CVE CVE-2024-50170 | known not affected: 378 recommended: 6 | 2026-07-23T01:56:38+00:00 | Vulnerability · Source |
| CVE-2024-50176 | suse_vex | SUSE CVE CVE-2024-50176 | known affected: 394 known not affected: 316 recommended: 316 | 2026-07-23T01:56:36+00:00 | Vulnerability · Source |
| CVE-2024-50183 | suse_vex | SUSE CVE CVE-2024-50183 | known affected: 578 known not affected: 49 recommended: 611 | 2026-07-23T01:56:35+00:00 | Vulnerability · Source |
| CVE-2024-50186 | suse_vex | SUSE CVE CVE-2024-50186 | known affected: 426 known not affected: 224 recommended: 628 | 2026-07-23T01:56:33+00:00 | Vulnerability · Source |
| CVE-2024-50192 | suse_vex | SUSE CVE CVE-2024-50192 | known affected: 463 known not affected: 187 recommended: 658 | 2026-07-23T01:56:32+00:00 | Vulnerability · Source |
| CVE-2024-50195 | suse_vex | SUSE CVE CVE-2024-50195 | known affected: 593 known not affected: 36 recommended: 730 | 2026-07-23T01:56:30+00:00 | Vulnerability · Source |
| CVE-2024-50197 | suse_vex | SUSE CVE CVE-2024-50197 | known not affected: 378 recommended: 108 | 2026-07-23T01:56:29+00:00 | Vulnerability · Source |
| CVE-2024-50200 | suse_vex | SUSE CVE CVE-2024-50200 | known affected: 394 known not affected: 316 recommended: 359 | 2026-07-23T01:56:27+00:00 | Vulnerability · Source |
| CVE-2024-50204 | suse_vex | SUSE CVE CVE-2024-50204 | known not affected: 378 | 2026-07-23T01:56:26+00:00 | Vulnerability · Source |
| CVE-2024-50210 | suse_vex | SUSE CVE CVE-2024-50210 | known not affected: 269 recommended: 420 | 2026-07-23T01:56:23+00:00 | Vulnerability · Source |
| CVE-2024-50211 | suse_vex | SUSE CVE CVE-2024-50211 | known affected: 358 known not affected: 322 recommended: 459 | 2026-07-23T01:56:22+00:00 | Vulnerability · Source |
| CVE-2024-50214 | suse_vex | SUSE CVE CVE-2024-50214 | known not affected: 320 recommended: 65 | 2026-07-23T01:56:20+00:00 | Vulnerability · Source |
| CVE-2024-50218 | suse_vex | SUSE CVE CVE-2024-50218 | known affected: 579 known not affected: 47 recommended: 618 | 2026-07-23T01:56:19+00:00 | Vulnerability · Source |
| CVE-2024-50227 | suse_vex | SUSE CVE CVE-2024-50227 | known not affected: 320 recommended: 6 | 2026-07-23T01:56:17+00:00 | Vulnerability · Source |
| CVE-2024-50233 | suse_vex | SUSE CVE CVE-2024-50233 | known affected: 354 known not affected: 249 recommended: 585 | 2026-07-23T01:56:14+00:00 | Vulnerability · Source |
| CVE-2024-50247 | suse_vex | SUSE CVE CVE-2024-50247 | known not affected: 321 recommended: 6 | 2026-07-23T01:56:13+00:00 | Vulnerability · Source |
| CVE-2024-50260 | suse_vex | SUSE CVE CVE-2024-50260 | known not affected: 320 recommended: 6 | 2026-07-23T01:56:11+00:00 | Vulnerability · Source |
| CVE-2024-50266 | suse_vex | SUSE CVE CVE-2024-50266 | known not affected: 308 | 2026-07-23T01:56:09+00:00 | Vulnerability · Source |
| CVE-2024-50277 | suse_vex | SUSE CVE CVE-2024-50277 | known not affected: 308 | 2026-07-23T01:56:07+00:00 | Vulnerability · Source |
| CVE-2024-50279 | suse_vex | SUSE CVE CVE-2024-50279 | known affected: 431 known not affected: 42 recommended: 973 | 2026-07-23T01:56:05+00:00 | Vulnerability · Source |
| CVE-2024-50280 | suse_vex | SUSE CVE CVE-2024-50280 | known affected: 4 known not affected: 312 recommended: 413 | 2026-07-23T01:56:04+00:00 | Vulnerability · Source |
| CVE-2024-50281 | suse_vex | SUSE CVE CVE-2024-50281 | known not affected: 308 | 2026-07-23T01:56:03+00:00 | Vulnerability · Source |
| CVE-2024-50283 | suse_vex | SUSE CVE CVE-2024-50283 | known not affected: 370 | 2026-07-23T01:56:01+00:00 | Vulnerability · Source |
| CVE-2024-50285 | suse_vex | SUSE CVE CVE-2024-50285 | known not affected: 305 | 2026-07-23T01:56:00+00:00 | Vulnerability · Source |
| CVE-2024-50289 | suse_vex | SUSE CVE CVE-2024-50289 | known affected: 579 known not affected: 36 recommended: 612 | 2026-07-23T01:55:59+00:00 | Vulnerability · Source |
| CVE-2024-50295 | suse_vex | SUSE CVE CVE-2024-50295 | known affected: 354 known not affected: 245 recommended: 579 | 2026-07-23T01:55:57+00:00 | Vulnerability · Source |
| CVE-2024-50300 | suse_vex | SUSE CVE CVE-2024-50300 | known not affected: 308 | 2026-07-23T01:55:56+00:00 | Vulnerability · Source |
| CVE-2024-50382 | suse_vex | SUSE CVE CVE-2024-50382 | known not affected: 60 recommended: 41 | 2026-07-23T01:55:55+00:00 | Vulnerability · Source |
| CVE-2024-50613 | suse_vex | SUSE CVE CVE-2024-50613 | known not affected: 113 | 2026-07-23T01:55:53+00:00 | Vulnerability · Source |
| CVE-2024-53047 | suse_vex | SUSE CVE CVE-2024-53047 | known not affected: 308 recommended: 43 | 2026-07-23T01:55:50+00:00 | Vulnerability · Source |
| CVE-2024-53055 | suse_vex | SUSE CVE CVE-2024-53055 | known affected: 475 known not affected: 182 recommended: 463 | 2026-07-23T01:55:48+00:00 | Vulnerability · Source |