VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292116 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-46703 | suse_vex | SUSE CVE CVE-2024-46703 | known not affected: 324 recommended: 59 | 2026-07-23T02:00:10+00:00 | Vulnerability · Source |
| CVE-2024-46715 | suse_vex | SUSE CVE CVE-2024-46715 | known affected: 505 known not affected: 52 recommended: 729 | 2026-07-23T02:00:05+00:00 | Vulnerability · Source |
| CVE-2024-46719 | suse_vex | SUSE CVE CVE-2024-46719 | known affected: 369 known not affected: 386 recommended: 628 | 2026-07-23T02:00:02+00:00 | Vulnerability · Source |
| CVE-2024-46723 | suse_vex | SUSE CVE CVE-2024-46723 | known affected: 536 known not affected: 21 recommended: 772 | 2026-07-23T01:59:59+00:00 | Vulnerability · Source |
| CVE-2024-46731 | suse_vex | SUSE CVE CVE-2024-46731 | known affected: 401 known not affected: 156 recommended: 729 | 2026-07-23T01:59:56+00:00 | Vulnerability · Source |
| CVE-2024-46739 | suse_vex | SUSE CVE CVE-2024-46739 | known affected: 453 known not affected: 77 recommended: 715 | 2026-07-23T01:59:51+00:00 | Vulnerability · Source |
| CVE-2024-46740 | suse_vex | SUSE CVE CVE-2024-46740 | known not affected: 324 | 2026-07-23T01:59:50+00:00 | Vulnerability · Source |
| CVE-2024-46773 | suse_vex | SUSE CVE CVE-2024-46773 | known affected: 343 known not affected: 232 recommended: 657 | 2026-07-23T01:59:41+00:00 | Vulnerability · Source |
| CVE-2024-46780 | suse_vex | SUSE CVE CVE-2024-46780 | known affected: 456 known not affected: 186 recommended: 645 | 2026-07-23T01:59:39+00:00 | Vulnerability · Source |
| CVE-2024-46793 | suse_vex | SUSE CVE CVE-2024-46793 | known not affected: 324 recommended: 59 | 2026-07-23T01:59:34+00:00 | Vulnerability · Source |
| CVE-2024-46801 | suse_vex | SUSE CVE CVE-2024-46801 | known not affected: 325 | 2026-07-23T01:59:32+00:00 | Vulnerability · Source |
| CVE-2024-46808 | suse_vex | SUSE CVE CVE-2024-46808 | known not affected: 235 recommended: 59 | 2026-07-23T01:59:29+00:00 | Vulnerability · Source |
| CVE-2024-46866 | suse_vex | SUSE CVE CVE-2024-46866 | known not affected: 324 recommended: 59 | 2026-07-23T01:59:15+00:00 | Vulnerability · Source |
| CVE-2024-46868 | suse_vex | SUSE CVE CVE-2024-46868 | known not affected: 324 | 2026-07-23T01:59:13+00:00 | Vulnerability · Source |
| CVE-2024-46901 | suse_vex | SUSE CVE CVE-2024-46901 | known affected: 168 recommended: 143 | 2026-07-23T01:59:12+00:00 | Vulnerability · Source |
| CVE-2024-47176 | suse_vex | SUSE CVE CVE-2024-47176 | known affected: 40 recommended: 99 | 2026-07-23T01:59:09+00:00 | Vulnerability · Source |
| CVE-2024-47220 | suse_vex | SUSE CVE CVE-2024-47220 | known affected: 490 known not affected: 105 recommended: 157 | 2026-07-23T01:59:07+00:00 | Vulnerability · Source |
| CVE-2024-47252 | suse_vex | SUSE CVE CVE-2024-47252 | known affected: 472 known not affected: 1 recommended: 280 | 2026-07-23T01:59:06+00:00 | Vulnerability · Source |
| CVE-2024-47401 | suse_vex | SUSE CVE CVE-2024-47401 | recommended: 3 | 2026-07-23T01:59:05+00:00 | Vulnerability · Source |
| CVE-2024-47541 | suse_vex | SUSE CVE CVE-2024-47541 | known affected: 412 recommended: 952 | 2026-07-23T01:59:02+00:00 | Vulnerability · Source |
| CVE-2024-47596 | suse_vex | SUSE CVE CVE-2024-47596 | known affected: 35 recommended: 99 | 2026-07-23T01:58:59+00:00 | Vulnerability · Source |
| CVE-2024-47603 | suse_vex | SUSE CVE CVE-2024-47603 | known affected: 34 known not affected: 1 recommended: 99 | 2026-07-23T01:58:56+00:00 | Vulnerability · Source |
| CVE-2024-47613 | suse_vex | SUSE CVE CVE-2024-47613 | known affected: 34 known not affected: 1 recommended: 203 | 2026-07-23T01:58:55+00:00 | Vulnerability · Source |
| CVE-2024-47680 | suse_vex | SUSE CVE CVE-2024-47680 | known not affected: 379 recommended: 6 | 2026-07-23T01:58:49+00:00 | Vulnerability · Source |
| CVE-2024-47683 | suse_vex | SUSE CVE CVE-2024-47683 | known not affected: 379 recommended: 6 | 2026-07-23T01:58:48+00:00 | Vulnerability · Source |
| CVE-2024-47686 | suse_vex | SUSE CVE CVE-2024-47686 | known affected: 394 known not affected: 321 recommended: 372 | 2026-07-23T01:58:46+00:00 | Vulnerability · Source |
| CVE-2024-47688 | suse_vex | SUSE CVE CVE-2024-47688 | known affected: 394 known not affected: 321 recommended: 372 | 2026-07-23T01:58:45+00:00 | Vulnerability · Source |
| CVE-2024-47693 | suse_vex | SUSE CVE CVE-2024-47693 | known affected: 479 known not affected: 138 recommended: 641 | 2026-07-23T01:58:43+00:00 | Vulnerability · Source |
| CVE-2024-47700 | suse_vex | SUSE CVE CVE-2024-47700 | known not affected: 402 recommended: 49 | 2026-07-23T01:58:40+00:00 | Vulnerability · Source |
| CVE-2024-47721 | suse_vex | SUSE CVE CVE-2024-47721 | known not affected: 402 recommended: 6 | 2026-07-23T01:58:35+00:00 | Vulnerability · Source |
| CVE-2024-47729 | suse_vex | SUSE CVE CVE-2024-47729 | known not affected: 402 recommended: 65 | 2026-07-23T01:58:33+00:00 | Vulnerability · Source |
| CVE-2024-47814 | suse_vex | SUSE CVE CVE-2024-47814 | known affected: 392 known not affected: 121 recommended: 167 | 2026-07-23T01:58:21+00:00 | Vulnerability · Source |
| CVE-2024-49393 | suse_vex | SUSE CVE CVE-2024-49393 | known affected: 1 recommended: 4 | 2026-07-23T01:58:20+00:00 | Vulnerability · Source |
| CVE-2024-49394 | suse_vex | SUSE CVE CVE-2024-49394 | known affected: 1 recommended: 4 | 2026-07-23T01:58:19+00:00 | Vulnerability · Source |
| CVE-2024-49761 | suse_vex | SUSE CVE CVE-2024-49761 | known affected: 609 known not affected: 94 recommended: 214 | 2026-07-23T01:58:14+00:00 | Vulnerability · Source |
| CVE-2024-49857 | suse_vex | SUSE CVE CVE-2024-49857 | known not affected: 402 recommended: 65 | 2026-07-23T01:58:13+00:00 | Vulnerability · Source |
| CVE-2024-49864 | suse_vex | SUSE CVE CVE-2024-49864 | known affected: 398 known not affected: 373 recommended: 413 | 2026-07-23T01:58:11+00:00 | Vulnerability · Source |
| CVE-2024-49868 | suse_vex | SUSE CVE CVE-2024-49868 | known affected: 588 known not affected: 36 recommended: 625 | 2026-07-23T01:58:10+00:00 | Vulnerability · Source |
| CVE-2024-49869 | suse_vex | SUSE CVE CVE-2024-49869 | known not affected: 379 recommended: 6 | 2026-07-23T01:58:09+00:00 | Vulnerability · Source |
| CVE-2024-49881 | suse_vex | SUSE CVE CVE-2024-49881 | known affected: 582 known not affected: 42 recommended: 725 | 2026-07-23T01:58:04+00:00 | Vulnerability · Source |
| CVE-2024-49887 | suse_vex | SUSE CVE CVE-2024-49887 | known not affected: 402 recommended: 6 | 2026-07-23T01:58:00+00:00 | Vulnerability · Source |
| CVE-2024-49903 | suse_vex | SUSE CVE CVE-2024-49903 | known affected: 354 known not affected: 165 recommended: 641 | 2026-07-23T01:57:54+00:00 | Vulnerability · Source |
| CVE-2024-49941 | suse_vex | SUSE CVE CVE-2024-49941 | known not affected: 379 recommended: 6 | 2026-07-23T01:57:43+00:00 | Vulnerability · Source |
| CVE-2024-49947 | suse_vex | SUSE CVE CVE-2024-49947 | known affected: 354 known not affected: 263 recommended: 641 | 2026-07-23T01:57:41+00:00 | Vulnerability · Source |
| CVE-2024-49952 | suse_vex | SUSE CVE CVE-2024-49952 | known affected: 633 known not affected: 42 recommended: 466 | 2026-07-23T01:57:40+00:00 | Vulnerability · Source |
| CVE-2024-49966 | suse_vex | SUSE CVE CVE-2024-49966 | known affected: 577 known not affected: 11 recommended: 681 | 2026-07-23T01:57:34+00:00 | Vulnerability · Source |
| CVE-2024-49970 | suse_vex | SUSE CVE CVE-2024-49970 | known not affected: 379 recommended: 65 | 2026-07-23T01:57:33+00:00 | Vulnerability · Source |
| CVE-2024-49977 | suse_vex | SUSE CVE CVE-2024-49977 | known not affected: 379 recommended: 49 | 2026-07-23T01:57:31+00:00 | Vulnerability · Source |
| CVE-2024-49979 | suse_vex | SUSE CVE CVE-2024-49979 | known not affected: 379 recommended: 6 | 2026-07-23T01:57:30+00:00 | Vulnerability · Source |
| 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 |