VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
306231 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-21755 | suse_vex | SUSE CVE CVE-2025-21755 | known affected: 437 known not affected: 396 recommended: 404 | 2026-10-10T16:44:46+00:00 | Vulnerability · Source |
| CVE-2025-21757 | suse_vex | SUSE CVE CVE-2025-21757 | known not affected: 469 | 2026-10-10T16:44:44+00:00 | Vulnerability · Source |
| CVE-2025-21759 | suse_vex | SUSE CVE CVE-2025-21759 | known affected: 752 recommended: 530 | 2026-10-10T16:44:42+00:00 | Vulnerability · Source |
| CVE-2025-21760 | suse_vex | SUSE CVE CVE-2025-21760 | known affected: 632 known not affected: 2 recommended: 570 | 2026-10-10T16:44:40+00:00 | Vulnerability · Source |
| CVE-2025-21770 | suse_vex | SUSE CVE CVE-2025-21770 | known affected: 463 known not affected: 402 recommended: 171 | 2026-10-10T16:44:38+00:00 | Vulnerability · Source |
| CVE-2025-21777 | suse_vex | SUSE CVE CVE-2025-21777 | known affected: 69 known not affected: 449 recommended: 120 | 2026-10-10T16:44:35+00:00 | Vulnerability · Source |
| CVE-2025-21780 | suse_vex | SUSE CVE CVE-2025-21780 | known affected: 374 known not affected: 257 recommended: 662 | 2026-10-10T16:44:33+00:00 | Vulnerability · Source |
| CVE-2025-21781 | suse_vex | SUSE CVE CVE-2025-21781 | known affected: 658 known not affected: 172 recommended: 357 | 2026-10-10T16:44:30+00:00 | Vulnerability · Source |
| CVE-2025-21783 | suse_vex | SUSE CVE CVE-2025-21783 | known affected: 67 known not affected: 402 recommended: 78 | 2026-10-10T16:44:28+00:00 | Vulnerability · Source |
| CVE-2025-21786 | suse_vex | SUSE CVE CVE-2025-21786 | known affected: 67 known not affected: 402 recommended: 190 | 2026-10-10T16:44:26+00:00 | Vulnerability · Source |
| CVE-2025-21793 | suse_vex | SUSE CVE CVE-2025-21793 | known affected: 461 known not affected: 343 recommended: 357 | 2026-10-10T16:44:24+00:00 | Vulnerability · Source |
| CVE-2025-21796 | suse_vex | SUSE CVE CVE-2025-21796 | known affected: 752 recommended: 507 | 2026-10-10T16:44:22+00:00 | Vulnerability · Source |
| CVE-2025-21798 | suse_vex | SUSE CVE CVE-2025-21798 | known not affected: 469 recommended: 78 | 2026-10-10T16:44:20+00:00 | Vulnerability · Source |
| CVE-2025-21804 | suse_vex | SUSE CVE CVE-2025-21804 | known affected: 455 known not affected: 349 recommended: 357 | 2026-10-10T16:44:19+00:00 | Vulnerability · Source |
| CVE-2025-21831 | suse_vex | SUSE CVE CVE-2025-21831 | known affected: 702 known not affected: 52 recommended: 383 | 2026-10-10T16:44:15+00:00 | Vulnerability · Source |
| CVE-2025-21842 | suse_vex | SUSE CVE CVE-2025-21842 | known affected: 461 known not affected: 402 recommended: 171 | 2026-10-10T16:44:13+00:00 | Vulnerability · Source |
| CVE-2025-21844 | suse_vex | SUSE CVE CVE-2025-21844 | known affected: 607 known not affected: 195 recommended: 467 | 2026-10-10T16:44:11+00:00 | Vulnerability · Source |
| CVE-2025-21866 | suse_vex | SUSE CVE CVE-2025-21866 | known affected: 591 known not affected: 211 recommended: 384 | 2026-10-10T16:44:07+00:00 | Vulnerability · Source |
| CVE-2025-21868 | suse_vex | SUSE CVE CVE-2025-21868 | known affected: 504 known not affected: 332 recommended: 381 | 2026-10-10T16:44:05+00:00 | Vulnerability · Source |
| CVE-2025-21875 | suse_vex | SUSE CVE CVE-2025-21875 | known affected: 565 known not affected: 256 recommended: 384 | 2026-10-10T16:44:02+00:00 | Vulnerability · Source |
| CVE-2025-21882 | suse_vex | SUSE CVE CVE-2025-21882 | known affected: 67 known not affected: 392 recommended: 152 | 2026-10-10T16:43:59+00:00 | Vulnerability · Source |
| CVE-2025-21893 | suse_vex | SUSE CVE CVE-2025-21893 | known affected: 67 known not affected: 364 recommended: 152 | 2026-10-10T16:43:57+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-10T16:43:54+00:00 | Vulnerability · Source |
| CVE-2025-21915 | suse_vex | SUSE CVE CVE-2025-21915 | known affected: 394 known not affected: 400 recommended: 384 | 2026-10-10T16:43:52+00:00 | Vulnerability · Source |
| CVE-2025-21920 | suse_vex | SUSE CVE CVE-2025-21920 | known affected: 788 recommended: 519 | 2026-10-10T16:43:50+00:00 | Vulnerability · Source |
| CVE-2025-21922 | suse_vex | SUSE CVE CVE-2025-21922 | known affected: 739 known not affected: 34 recommended: 424 | 2026-10-10T16:43:48+00:00 | Vulnerability · Source |
| CVE-2025-21926 | suse_vex | SUSE CVE CVE-2025-21926 | known affected: 671 known not affected: 96 recommended: 496 | 2026-10-10T16:43:46+00:00 | Vulnerability · Source |
| CVE-2025-21940 | suse_vex | SUSE CVE CVE-2025-21940 | known affected: 394 known not affected: 459 recommended: 171 | 2026-10-10T16:43:44+00:00 | Vulnerability · Source |
| CVE-2025-21961 | suse_vex | SUSE CVE CVE-2025-21961 | known affected: 504 known not affected: 325 recommended: 470 | 2026-10-10T16:43:40+00:00 | Vulnerability · Source |
| CVE-2025-21964 | suse_vex | SUSE CVE CVE-2025-21964 | known affected: 634 known not affected: 141 recommended: 519 | 2026-10-10T16:43:39+00:00 | Vulnerability · Source |
| CVE-2025-21974 | suse_vex | SUSE CVE CVE-2025-21974 | known not affected: 459 recommended: 152 | 2026-10-10T16:43:37+00:00 | Vulnerability · Source |
| CVE-2025-21976 | suse_vex | SUSE CVE CVE-2025-21976 | known affected: 596 known not affected: 250 recommended: 160 | 2026-10-10T16:43:35+00:00 | Vulnerability · Source |
| CVE-2025-21978 | suse_vex | SUSE CVE CVE-2025-21978 | known affected: 522 known not affected: 272 recommended: 384 | 2026-10-10T16:43:33+00:00 | Vulnerability · Source |
| CVE-2025-21985 | suse_vex | SUSE CVE CVE-2025-21985 | known affected: 394 known not affected: 400 recommended: 384 | 2026-10-10T16:43:31+00:00 | Vulnerability · Source |
| CVE-2025-22004 | suse_vex | SUSE CVE CVE-2025-22004 | known affected: 460 recommended: 198 | 2026-10-10T16:43:29+00:00 | Vulnerability · Source |
| CVE-2025-22020 | suse_vex | SUSE CVE CVE-2025-22020 | known affected: 385 known not affected: 209 recommended: 155 | 2026-10-10T16:43:26+00:00 | Vulnerability · Source |
| CVE-2025-22062 | suse_vex | SUSE CVE CVE-2025-22062 | known affected: 538 known not affected: 256 recommended: 407 | 2026-10-10T16:43:22+00:00 | Vulnerability · Source |
| CVE-2025-22075 | suse_vex | SUSE CVE CVE-2025-22075 | known affected: 591 known not affected: 203 recommended: 407 | 2026-10-10T16:43:19+00:00 | Vulnerability · Source |
| CVE-2025-22080 | suse_vex | SUSE CVE CVE-2025-22080 | known affected: 437 known not affected: 384 recommended: 384 | 2026-10-10T16:43:17+00:00 | Vulnerability · Source |
| CVE-2025-22089 | suse_vex | SUSE CVE CVE-2025-22089 | known affected: 522 known not affected: 278 recommended: 479 | 2026-10-10T16:43:15+00:00 | Vulnerability · Source |
| CVE-2025-22090 | suse_vex | SUSE CVE CVE-2025-22090 | known affected: 734 known not affected: 27 recommended: 384 | 2026-10-10T16:43:13+00:00 | Vulnerability · Source |
| CVE-2025-22093 | suse_vex | SUSE CVE CVE-2025-22093 | known affected: 394 known not affected: 414 recommended: 407 | 2026-10-10T16:43:11+00:00 | Vulnerability · Source |
| CVE-2025-22095 | suse_vex | SUSE CVE CVE-2025-22095 | known affected: 394 known not affected: 408 recommended: 396 | 2026-10-10T16:43:09+00:00 | Vulnerability · Source |
| CVE-2025-22102 | suse_vex | SUSE CVE CVE-2025-22102 | known affected: 437 known not affected: 392 recommended: 407 | 2026-10-10T16:43:06+00:00 | Vulnerability · Source |
| CVE-2025-22107 | suse_vex | SUSE CVE CVE-2025-22107 | known affected: 607 known not affected: 187 recommended: 407 | 2026-10-10T16:43:04+00:00 | Vulnerability · Source |
| CVE-2025-22124 | suse_vex | SUSE CVE CVE-2025-22124 | known affected: 394 known not affected: 408 recommended: 396 | 2026-10-10T16:43:00+00:00 | Vulnerability · Source |
| CVE-2025-23131 | suse_vex | SUSE CVE CVE-2025-23131 | known affected: 730 known not affected: 49 recommended: 447 | 2026-10-10T16:42:52+00:00 | Vulnerability · Source |
| CVE-2025-23134 | suse_vex | SUSE CVE CVE-2025-23134 | known affected: 27 known not affected: 468 recommended: 175 | 2026-10-10T16:42:49+00:00 | Vulnerability · Source |
| CVE-2025-23136 | suse_vex | SUSE CVE CVE-2025-23136 | known affected: 739 known not affected: 49 recommended: 444 | 2026-10-10T16:42:47+00:00 | Vulnerability · Source |
| CVE-2025-23151 | suse_vex | SUSE CVE CVE-2025-23151 | known affected: 461 known not affected: 360 recommended: 396 | 2026-10-10T16:42:44+00:00 | Vulnerability · Source |