VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292108 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-21784 | suse_vex | SUSE CVE CVE-2025-21784 | known affected: 451 known not affected: 229 recommended: 362 | 2026-07-25T01:05:09+00:00 | Vulnerability · Source |
| CVE-2025-21793 | suse_vex | SUSE CVE CVE-2025-21793 | known affected: 451 known not affected: 229 recommended: 362 | 2026-07-25T01:05:05+00:00 | Vulnerability · Source |
| CVE-2025-21813 | suse_vex | SUSE CVE CVE-2025-21813 | known affected: 57 known not affected: 295 | 2026-07-25T01:04:50+00:00 | Vulnerability · Source |
| CVE-2025-21814 | suse_vex | SUSE CVE CVE-2025-21814 | known affected: 699 recommended: 448 | 2026-07-25T01:04:48+00:00 | Vulnerability · Source |
| CVE-2025-21815 | suse_vex | SUSE CVE CVE-2025-21815 | known affected: 451 known not affected: 229 recommended: 362 | 2026-07-25T01:04:46+00:00 | Vulnerability · Source |
| CVE-2025-21819 | suse_vex | SUSE CVE CVE-2025-21819 | known affected: 451 known not affected: 229 recommended: 362 | 2026-07-25T01:04:42+00:00 | Vulnerability · Source |
| CVE-2025-21822 | suse_vex | SUSE CVE CVE-2025-21822 | known affected: 57 known not affected: 295 | 2026-07-25T01:04:38+00:00 | Vulnerability · Source |
| CVE-2025-21829 | suse_vex | SUSE CVE CVE-2025-21829 | known affected: 410 known not affected: 308 recommended: 403 | 2026-07-25T01:04:31+00:00 | Vulnerability · Source |
| CVE-2025-21838 | suse_vex | SUSE CVE CVE-2025-21838 | known affected: 408 known not affected: 344 recommended: 362 | 2026-07-25T01:04:24+00:00 | Vulnerability · Source |
| CVE-2025-21841 | suse_vex | SUSE CVE CVE-2025-21841 | known affected: 59 known not affected: 331 recommended: 53 | 2026-07-25T01:04:21+00:00 | Vulnerability · Source |
| CVE-2025-21850 | suse_vex | SUSE CVE CVE-2025-21850 | known affected: 451 known not affected: 225 recommended: 395 | 2026-07-25T01:04:16+00:00 | Vulnerability · Source |
| CVE-2025-21852 | suse_vex | SUSE CVE CVE-2025-21852 | known affected: 57 known not affected: 255 recommended: 418 | 2026-07-25T01:04:12+00:00 | Vulnerability · Source |
| CVE-2025-21858 | suse_vex | SUSE CVE CVE-2025-21858 | known affected: 642 known not affected: 6 recommended: 455 | 2026-07-25T01:04:03+00:00 | Vulnerability · Source |
| CVE-2025-21861 | suse_vex | SUSE CVE CVE-2025-21861 | known affected: 573 known not affected: 103 recommended: 478 | 2026-07-25T01:03:59+00:00 | Vulnerability · Source |
| CVE-2025-21866 | suse_vex | SUSE CVE CVE-2025-21866 | known affected: 557 known not affected: 119 recommended: 395 | 2026-07-25T01:03:52+00:00 | Vulnerability · Source |
| CVE-2025-21867 | suse_vex | SUSE CVE CVE-2025-21867 | known affected: 497 known not affected: 205 recommended: 439 | 2026-07-25T01:03:50+00:00 | Vulnerability · Source |
| CVE-2025-21872 | suse_vex | SUSE CVE CVE-2025-21872 | known affected: 604 known not affected: 113 recommended: 407 | 2026-07-25T01:03:44+00:00 | Vulnerability · Source |
| CVE-2025-21875 | suse_vex | SUSE CVE CVE-2025-21875 | known affected: 552 known not affected: 150 recommended: 395 | 2026-07-25T01:03:38+00:00 | Vulnerability · Source |
| CVE-2025-21876 | suse_vex | SUSE CVE CVE-2025-21876 | known affected: 451 known not affected: 221 recommended: 395 | 2026-07-25T01:03:36+00:00 | Vulnerability · Source |
| CVE-2025-21879 | suse_vex | SUSE CVE CVE-2025-21879 | known affected: 57 known not affected: 287 | 2026-07-25T01:03:31+00:00 | Vulnerability · Source |
| CVE-2025-21895 | suse_vex | SUSE CVE CVE-2025-21895 | known affected: 440 known not affected: 262 recommended: 395 | 2026-07-25T01:03:11+00:00 | Vulnerability · Source |
| CVE-2025-21899 | suse_vex | SUSE CVE CVE-2025-21899 | known affected: 618 known not affected: 99 recommended: 407 | 2026-07-25T01:03:08+00:00 | Vulnerability · Source |
| CVE-2025-21905 | suse_vex | SUSE CVE CVE-2025-21905 | known affected: 557 known not affected: 115 recommended: 458 | 2026-07-25T01:03:04+00:00 | Vulnerability · Source |
| CVE-2025-21918 | suse_vex | SUSE CVE CVE-2025-21918 | known affected: 451 known not affected: 221 recommended: 395 | 2026-07-25T01:02:48+00:00 | Vulnerability · Source |
| CVE-2025-21919 | suse_vex | SUSE CVE CVE-2025-21919 | known affected: 552 known not affected: 150 recommended: 474 | 2026-07-25T01:02:46+00:00 | Vulnerability · Source |
| CVE-2025-21924 | suse_vex | SUSE CVE CVE-2025-21924 | known affected: 552 known not affected: 150 recommended: 395 | 2026-07-25T01:02:40+00:00 | Vulnerability · Source |
| CVE-2025-21925 | suse_vex | SUSE CVE CVE-2025-21925 | known affected: 589 known not affected: 113 recommended: 395 | 2026-07-25T01:02:38+00:00 | Vulnerability · Source |
| CVE-2025-21937 | suse_vex | SUSE CVE CVE-2025-21937 | known affected: 451 known not affected: 225 recommended: 395 | 2026-07-25T01:02:26+00:00 | Vulnerability · Source |
| CVE-2025-21938 | suse_vex | SUSE CVE CVE-2025-21938 | known affected: 440 known not affected: 277 recommended: 392 | 2026-07-25T01:02:24+00:00 | Vulnerability · Source |
| CVE-2025-21948 | suse_vex | SUSE CVE CVE-2025-21948 | known affected: 622 known not affected: 52 recommended: 435 | 2026-07-25T01:02:12+00:00 | Vulnerability · Source |
| CVE-2025-21960 | suse_vex | SUSE CVE CVE-2025-21960 | known affected: 497 known not affected: 209 recommended: 395 | 2026-07-25T01:02:05+00:00 | Vulnerability · Source |
| CVE-2025-21965 | suse_vex | SUSE CVE CVE-2025-21965 | known not affected: 384 | 2026-07-25T01:01:58+00:00 | Vulnerability · Source |
| CVE-2025-21985 | suse_vex | SUSE CVE CVE-2025-21985 | known affected: 394 known not affected: 278 recommended: 395 | 2026-07-25T01:01:39+00:00 | Vulnerability · Source |
| CVE-2025-21989 | suse_vex | SUSE CVE CVE-2025-21989 | known not affected: 344 recommended: 145 | 2026-07-25T01:01:35+00:00 | Vulnerability · Source |
| CVE-2025-22002 | suse_vex | SUSE CVE CVE-2025-22002 | known not affected: 348 recommended: 53 | 2026-07-25T01:01:25+00:00 | Vulnerability · Source |
| CVE-2025-22005 | suse_vex | SUSE CVE CVE-2025-22005 | known affected: 618 known not affected: 103 recommended: 407 | 2026-07-25T01:01:21+00:00 | Vulnerability · Source |
| CVE-2025-22007 | suse_vex | SUSE CVE CVE-2025-22007 | known affected: 626 known not affected: 22 recommended: 435 | 2026-07-25T01:01:19+00:00 | Vulnerability · Source |
| CVE-2025-22015 | suse_vex | SUSE CVE CVE-2025-22015 | known affected: 440 known not affected: 262 recommended: 395 | 2026-07-25T01:01:08+00:00 | Vulnerability · Source |
| CVE-2025-22016 | suse_vex | SUSE CVE CVE-2025-22016 | known affected: 440 known not affected: 266 recommended: 395 | 2026-07-25T01:01:06+00:00 | Vulnerability · Source |
| CVE-2025-22017 | suse_vex | SUSE CVE CVE-2025-22017 | known affected: 440 known not affected: 262 recommended: 395 | 2026-07-25T01:01:04+00:00 | Vulnerability · Source |
| CVE-2025-22030 | suse_vex | SUSE CVE CVE-2025-22030 | known affected: 552 known not affected: 150 recommended: 411 | 2026-07-25T01:00:50+00:00 | Vulnerability · Source |
| CVE-2025-22047 | suse_vex | SUSE CVE CVE-2025-22047 | known affected: 394 known not affected: 311 recommended: 283 | 2026-07-25T01:00:38+00:00 | Vulnerability · Source |
| CVE-2025-22050 | suse_vex | SUSE CVE CVE-2025-22050 | known affected: 455 known not affected: 221 recommended: 441 | 2026-07-25T01:00:36+00:00 | Vulnerability · Source |
| CVE-2025-22052 | suse_vex | SUSE CVE CVE-2025-22052 | known not affected: 348 | 2026-07-25T01:00:34+00:00 | Vulnerability · Source |
| CVE-2025-22057 | suse_vex | SUSE CVE CVE-2025-22057 | known affected: 669 known not affected: 52 recommended: 411 | 2026-07-25T01:00:28+00:00 | Vulnerability · Source |
| CVE-2025-22060 | suse_vex | SUSE CVE CVE-2025-22060 | known affected: 473 known not affected: 128 recommended: 543 | 2026-07-25T01:00:25+00:00 | Vulnerability · Source |
| CVE-2025-22064 | suse_vex | SUSE CVE CVE-2025-22064 | known affected: 440 known not affected: 262 recommended: 418 | 2026-07-25T01:00:21+00:00 | Vulnerability · Source |
| CVE-2025-22065 | suse_vex | SUSE CVE CVE-2025-22065 | known affected: 506 known not affected: 200 recommended: 418 | 2026-07-25T01:00:19+00:00 | Vulnerability · Source |
| CVE-2025-22069 | suse_vex | SUSE CVE CVE-2025-22069 | known not affected: 344 | 2026-07-25T01:00:16+00:00 | Vulnerability · Source |
| CVE-2025-22083 | suse_vex | SUSE CVE CVE-2025-22083 | known affected: 618 known not affected: 6 recommended: 444 | 2026-07-25T01:00:08+00:00 | Vulnerability · Source |