VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
78249 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-53127 | suse_vex | SUSE CVE CVE-2024-53127 | known affected: 364 known not affected: 397 recommended: 381 | 2026-10-03T23:59:27+00:00 | Vulnerability · Source |
| CVE-2024-53148 | suse_vex | SUSE CVE CVE-2024-53148 | known affected: 396 known not affected: 244 recommended: 459 | 2026-10-03T23:59:25+00:00 | Vulnerability · Source |
| CVE-2024-53170 | suse_vex | SUSE CVE CVE-2024-53170 | known affected: 410 known not affected: 511 recommended: 399 | 2026-10-03T23:59:23+00:00 | Vulnerability · Source |
| CVE-2024-53239 | suse_vex | SUSE CVE CVE-2024-53239 | known affected: 517 known not affected: 73 recommended: 758 | 2026-10-03T23:59:20+00:00 | Vulnerability · Source |
| CVE-2024-56575 | suse_vex | SUSE CVE CVE-2024-56575 | known affected: 481 known not affected: 305 recommended: 468 | 2026-10-03T23:59:17+00:00 | Vulnerability · Source |
| CVE-2024-56576 | suse_vex | SUSE CVE CVE-2024-56576 | known affected: 666 known not affected: 221 recommended: 358 | 2026-10-03T23:59:16+00:00 | Vulnerability · Source |
| CVE-2024-56617 | suse_vex | SUSE CVE CVE-2024-56617 | known affected: 410 known not affected: 512 recommended: 358 | 2026-10-03T23:59:14+00:00 | Vulnerability · Source |
| CVE-2024-56677 | suse_vex | SUSE CVE CVE-2024-56677 | known affected: 394 known not affected: 481 recommended: 358 | 2026-10-03T23:59:11+00:00 | Vulnerability · Source |
| CVE-2024-56701 | suse_vex | SUSE CVE CVE-2024-56701 | known affected: 515 known not affected: 260 recommended: 459 | 2026-10-03T23:59:09+00:00 | Vulnerability · Source |
| CVE-2024-56763 | suse_vex | SUSE CVE CVE-2024-56763 | known affected: 782 known not affected: 32 recommended: 398 | 2026-10-03T23:59:07+00:00 | Vulnerability · Source |
| CVE-2024-56778 | suse_vex | SUSE CVE CVE-2024-56778 | known affected: 587 known not affected: 157 recommended: 459 | 2026-10-03T23:59:05+00:00 | Vulnerability · Source |
| CVE-2025-7424 | suse_vex | SUSE CVE CVE-2025-7424 | known affected: 394 known not affected: 249 recommended: 29 | 2026-10-03T23:58:58+00:00 | Vulnerability · Source |
| CVE-2025-8534 | suse_vex | SUSE CVE CVE-2025-8534 | known affected: 572 recommended: 88 | 2026-10-03T23:58:56+00:00 | Vulnerability · Source |
| CVE-2025-9900 | suse_vex | SUSE CVE CVE-2025-9900 | known affected: 467 known not affected: 548 recommended: 150 | 2026-10-03T23:58:54+00:00 | Vulnerability · Source |
| CVE-2025-21650 | suse_vex | SUSE CVE CVE-2025-21650 | known affected: 410 known not affected: 428 recommended: 358 | 2026-10-03T23:58:50+00:00 | Vulnerability · Source |
| CVE-2025-21910 | suse_vex | SUSE CVE CVE-2025-21910 | known affected: 722 known not affected: 43 recommended: 424 | 2026-10-03T23:58:45+00:00 | Vulnerability · Source |
| CVE-2025-54518 | suse_vex | SUSE CVE CVE-2025-54518 | known affected: 603 recommended: 878 | 2026-10-03T23:58:19+00:00 | Vulnerability · Source |
| CVE-2025-69421 | suse_vex | SUSE CVE CVE-2025-69421 | known affected: 554 known not affected: 116 recommended: 426 | 2026-10-03T23:58:13+00:00 | Vulnerability · Source |
| CVE-2026-0799 | suse_vex | SUSE CVE CVE-2026-0799 | known affected: 430 recommended: 59 | 2026-10-03T23:58:09+00:00 | Vulnerability · Source |
| CVE-2026-13877 | suse_vex | SUSE CVE CVE-2026-13877 | recommended: 14 | 2026-10-03T23:57:59+00:00 | Vulnerability · Source |
| CVE-2026-16365 | suse_vex | SUSE CVE CVE-2026-16365 | known affected: 48 recommended: 111 | 2026-10-03T23:57:41+00:00 | Vulnerability · Source |
| CVE-2026-17615 | suse_vex | SUSE CVE CVE-2026-17615 | recommended: 4 | 2026-10-03T23:57:39+00:00 | Vulnerability · Source |
| CVE-2026-31689 | suse_vex | SUSE CVE CVE-2026-31689 | known affected: 125 known not affected: 284 | 2026-10-03T23:57:29+00:00 | Vulnerability · Source |
| CVE-2026-39919 | suse_vex | SUSE CVE CVE-2026-39919 | known affected: 130 recommended: 18 | 2026-10-03T23:57:24+00:00 | Vulnerability · Source |
| CVE-2026-64475 | suse_vex | SUSE CVE CVE-2026-64475 | known affected: 183 known not affected: 193 recommended: 4 | 2026-10-03T23:56:58+00:00 | Vulnerability · Source |
| CVE-2026-72129 | suse_vex | SUSE CVE CVE-2026-72129 | known affected: 356 known not affected: 6 recommended: 103 | 2026-10-03T23:56:50+00:00 | Vulnerability · Source |
| CVE-2026-75140 | suse_vex | SUSE CVE CVE-2026-75140 | known affected: 17 recommended: 25 | 2026-10-03T23:56:42+00:00 | Vulnerability · Source |
| CVE-2026-75874 | suse_vex | SUSE CVE CVE-2026-75874 | known affected: 65 recommended: 115 | 2026-10-03T23:56:39+00:00 | Vulnerability · Source |
| CVE-2026-80840 | suse_vex | SUSE CVE CVE-2026-80840 | known affected: 260 known not affected: 93 recommended: 4 | 2026-10-03T23:56:35+00:00 | Vulnerability · Source |
| CVE-2026-80976 | suse_vex | SUSE CVE CVE-2026-80976 | known affected: 293 known not affected: 60 recommended: 4 | 2026-10-03T23:56:33+00:00 | Vulnerability · Source |
| CVE-2026-80983 | suse_vex | SUSE CVE CVE-2026-80983 | known affected: 210 known not affected: 143 recommended: 4 | 2026-10-03T23:56:31+00:00 | Vulnerability · Source |
| CVE-2026-84119 | suse_vex | SUSE CVE CVE-2026-84119 | known affected: 80 recommended: 109 | 2026-10-03T23:56:29+00:00 | Vulnerability · Source |
| CVE-2026-84120 | suse_vex | SUSE CVE CVE-2026-84120 | known affected: 80 recommended: 109 | 2026-10-03T23:56:27+00:00 | Vulnerability · Source |
| CVE-2026-84121 | suse_vex | SUSE CVE CVE-2026-84121 | known affected: 80 recommended: 109 | 2026-10-03T23:56:25+00:00 | Vulnerability · Source |
| CVE-2026-84122 | suse_vex | SUSE CVE CVE-2026-84122 | known affected: 80 recommended: 109 | 2026-10-03T23:56:23+00:00 | Vulnerability · Source |
| CVE-2026-84124 | suse_vex | SUSE CVE CVE-2026-84124 | known affected: 80 recommended: 109 | 2026-10-03T23:56:22+00:00 | Vulnerability · Source |
| CVE-2026-84131 | suse_vex | SUSE CVE CVE-2026-84131 | known affected: 80 recommended: 109 | 2026-10-03T23:56:21+00:00 | Vulnerability · Source |
| CVE-2026-84143 | suse_vex | SUSE CVE CVE-2026-84143 | known affected: 80 recommended: 109 | 2026-10-03T23:56:19+00:00 | Vulnerability · Source |
| CVE-2026-84145 | suse_vex | SUSE CVE CVE-2026-84145 | known affected: 80 recommended: 109 | 2026-10-03T23:56:18+00:00 | Vulnerability · Source |
| CVE-2026-84639 | suse_vex | SUSE CVE CVE-2026-84639 | known affected: 80 recommended: 22 | 2026-10-03T23:56:16+00:00 | Vulnerability · Source |
| CVE-2026-84640 | suse_vex | SUSE CVE CVE-2026-84640 | known affected: 80 recommended: 22 | 2026-10-03T23:56:15+00:00 | Vulnerability · Source |
| CVE-2026-84641 | suse_vex | SUSE CVE CVE-2026-84641 | known affected: 80 recommended: 22 | 2026-10-03T23:56:13+00:00 | Vulnerability · Source |
| CVE-2026-89479 | suse_vex | SUSE CVE CVE-2026-89479 | known affected: 353 recommended: 4 | 2026-10-03T23:56:10+00:00 | Vulnerability · Source |
| CVE-2026-89569 | suse_vex | SUSE CVE CVE-2026-89569 | known affected: 265 known not affected: 88 recommended: 4 | 2026-10-03T23:56:05+00:00 | Vulnerability · Source |
| CVE-2026-89603 | suse_vex | SUSE CVE CVE-2026-89603 | known affected: 210 known not affected: 143 recommended: 4 | 2026-10-03T23:56:03+00:00 | Vulnerability · Source |
| CVE-2026-89631 | suse_vex | SUSE CVE CVE-2026-89631 | known affected: 353 recommended: 4 | 2026-10-03T23:56:01+00:00 | Vulnerability · Source |
| CVE-2026-89636 | suse_vex | SUSE CVE CVE-2026-89636 | known affected: 347 known not affected: 6 recommended: 4 | 2026-10-03T23:56:00+00:00 | Vulnerability · Source |
| CVE-2026-89638 | suse_vex | SUSE CVE CVE-2026-89638 | known affected: 353 recommended: 4 | 2026-10-03T23:55:58+00:00 | Vulnerability · Source |
| CVE-2026-89777 | suse_vex | SUSE CVE CVE-2026-89777 | known affected: 254 known not affected: 93 recommended: 4 | 2026-10-03T23:55:56+00:00 | Vulnerability · Source |
| CVE-2026-89984 | suse_vex | SUSE CVE CVE-2026-89984 | known affected: 204 known not affected: 143 recommended: 4 | 2026-10-03T23:55:52+00:00 | Vulnerability · Source |