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-2025-21632 | suse_vex | SUSE CVE CVE-2025-21632 | known affected: 410 known not affected: 306 recommended: 363 | 2026-07-23T01:49:27+00:00 | Vulnerability · Source |
| CVE-2025-21643 | suse_vex | SUSE CVE CVE-2025-21643 | known not affected: 344 recommended: 53 | 2026-07-23T01:49:18+00:00 | Vulnerability · Source |
| CVE-2025-21651 | suse_vex | SUSE CVE CVE-2025-21651 | known affected: 575 known not affected: 141 recommended: 363 | 2026-07-23T01:49:15+00:00 | Vulnerability · Source |
| CVE-2025-21657 | suse_vex | SUSE CVE CVE-2025-21657 | known not affected: 273 | 2026-07-23T01:49:12+00:00 | Vulnerability · Source |
| CVE-2025-21678 | suse_vex | SUSE CVE CVE-2025-21678 | known affected: 634 known not affected: 58 recommended: 362 | 2026-07-23T01:49:05+00:00 | Vulnerability · Source |
| CVE-2025-21685 | suse_vex | SUSE CVE CVE-2025-21685 | known not affected: 350 recommended: 26 | 2026-07-23T01:49:04+00:00 | Vulnerability · Source |
| CVE-2025-21721 | suse_vex | SUSE CVE CVE-2025-21721 | known not affected: 293 | 2026-07-23T01:48:44+00:00 | Vulnerability · Source |
| CVE-2025-21722 | suse_vex | SUSE CVE CVE-2025-21722 | known not affected: 293 | 2026-07-23T01:48:43+00:00 | Vulnerability · Source |
| CVE-2025-21723 | suse_vex | SUSE CVE CVE-2025-21723 | known affected: 410 known not affected: 306 recommended: 335 | 2026-07-23T01:48:41+00:00 | Vulnerability · Source |
| CVE-2025-21729 | suse_vex | SUSE CVE CVE-2025-21729 | known affected: 440 known not affected: 270 recommended: 409 | 2026-07-23T01:48:37+00:00 | Vulnerability · Source |
| CVE-2025-21734 | suse_vex | SUSE CVE CVE-2025-21734 | known affected: 557 known not affected: 121 recommended: 335 | 2026-07-23T01:48:34+00:00 | Vulnerability · Source |
| CVE-2025-21736 | suse_vex | SUSE CVE CVE-2025-21736 | known affected: 671 known not affected: 86 recommended: 309 | 2026-07-23T01:48:32+00:00 | Vulnerability · Source |
| CVE-2025-21747 | suse_vex | SUSE CVE CVE-2025-21747 | known affected: 47 known not affected: 232 | 2026-07-23T01:48:28+00:00 | Vulnerability · Source |
| CVE-2025-21790 | suse_vex | SUSE CVE CVE-2025-21790 | known affected: 453 known not affected: 247 recommended: 446 | 2026-07-23T01:48:06+00:00 | Vulnerability · Source |
| CVE-2025-21794 | suse_vex | SUSE CVE CVE-2025-21794 | known affected: 451 known not affected: 227 recommended: 362 | 2026-07-23T01:48:03+00:00 | Vulnerability · Source |
| CVE-2025-21808 | suse_vex | SUSE CVE CVE-2025-21808 | known affected: 440 known not affected: 270 recommended: 368 | 2026-07-23T01:47:58+00:00 | Vulnerability · Source |
| CVE-2025-21809 | suse_vex | SUSE CVE CVE-2025-21809 | known not affected: 388 recommended: 26 | 2026-07-23T01:47:57+00:00 | Vulnerability · Source |
| CVE-2025-21823 | suse_vex | SUSE CVE CVE-2025-21823 | known affected: 596 known not affected: 120 recommended: 335 | 2026-07-23T01:47:54+00:00 | Vulnerability · Source |
| CVE-2025-21824 | suse_vex | SUSE CVE CVE-2025-21824 | known affected: 451 known not affected: 293 recommended: 137 | 2026-07-23T01:47:52+00:00 | Vulnerability · Source |
| CVE-2025-21832 | suse_vex | SUSE CVE CVE-2025-21832 | known affected: 469 known not affected: 211 recommended: 368 | 2026-07-23T01:47:51+00:00 | Vulnerability · Source |
| CVE-2025-21849 | suse_vex | SUSE CVE CVE-2025-21849 | known affected: 451 known not affected: 289 recommended: 164 | 2026-07-23T01:47:43+00:00 | Vulnerability · Source |
| CVE-2025-21869 | suse_vex | SUSE CVE CVE-2025-21869 | known affected: 451 known not affected: 219 recommended: 368 | 2026-07-23T01:47:36+00:00 | Vulnerability · Source |
| CVE-2025-21882 | suse_vex | SUSE CVE CVE-2025-21882 | known affected: 57 known not affected: 285 recommended: 145 | 2026-07-23T01:47:33+00:00 | Vulnerability · Source |
| CVE-2025-21885 | suse_vex | SUSE CVE CVE-2025-21885 | known affected: 557 known not affected: 113 recommended: 395 | 2026-07-23T01:47:31+00:00 | Vulnerability · Source |
| CVE-2025-21897 | suse_vex | SUSE CVE CVE-2025-21897 | known not affected: 330 | 2026-07-23T01:47:24+00:00 | Vulnerability · Source |
| CVE-2025-21903 | suse_vex | SUSE CVE CVE-2025-21903 | known not affected: 378 recommended: 26 | 2026-07-23T01:47:21+00:00 | Vulnerability · Source |
| CVE-2025-21904 | suse_vex | SUSE CVE CVE-2025-21904 | known affected: 664 known not affected: 36 recommended: 395 | 2026-07-23T01:47:20+00:00 | Vulnerability · Source |
| CVE-2025-21906 | suse_vex | SUSE CVE CVE-2025-21906 | known affected: 440 known not affected: 260 recommended: 395 | 2026-07-23T01:47:18+00:00 | Vulnerability · Source |
| CVE-2025-21942 | suse_vex | SUSE CVE CVE-2025-21942 | known not affected: 342 recommended: 53 | 2026-07-23T01:47:08+00:00 | Vulnerability · Source |
| CVE-2025-21950 | suse_vex | SUSE CVE CVE-2025-21950 | known affected: 506 known not affected: 164 recommended: 368 | 2026-07-23T01:47:05+00:00 | Vulnerability · Source |
| CVE-2025-21970 | suse_vex | SUSE CVE CVE-2025-21970 | known affected: 556 known not affected: 148 recommended: 368 | 2026-07-23T01:46:59+00:00 | Vulnerability · Source |
| CVE-2025-21978 | suse_vex | SUSE CVE CVE-2025-21978 | known affected: 506 known not affected: 164 recommended: 395 | 2026-07-23T01:46:56+00:00 | Vulnerability · Source |
| CVE-2025-21979 | suse_vex | SUSE CVE CVE-2025-21979 | known affected: 394 known not affected: 276 recommended: 411 | 2026-07-23T01:46:55+00:00 | Vulnerability · Source |
| CVE-2025-21993 | suse_vex | SUSE CVE CVE-2025-21993 | known affected: 674 recommended: 471 | 2026-07-23T01:46:46+00:00 | Vulnerability · Source |
| CVE-2025-22001 | suse_vex | SUSE CVE CVE-2025-22001 | known affected: 394 known not affected: 280 recommended: 395 | 2026-07-23T01:46:41+00:00 | Vulnerability · Source |
| CVE-2025-22006 | suse_vex | SUSE CVE CVE-2025-22006 | known not affected: 311 | 2026-07-23T01:46:39+00:00 | Vulnerability · Source |
| CVE-2025-22012 | suse_vex | SUSE CVE CVE-2025-22012 | known not affected: 273 | 2026-07-23T01:46:38+00:00 | Vulnerability · Source |
| CVE-2025-22021 | suse_vex | SUSE CVE CVE-2025-22021 | known affected: 668 known not affected: 6 recommended: 414 | 2026-07-23T01:46:35+00:00 | Vulnerability · Source |
| CVE-2025-22034 | suse_vex | SUSE CVE CVE-2025-22034 | first fixed: 2 known not affected: 378 recommended: 154 | 2026-07-23T01:46:29+00:00 | Vulnerability · Source |
| CVE-2025-22061 | suse_vex | SUSE CVE CVE-2025-22061 | known not affected: 273 | 2026-07-23T01:46:18+00:00 | Vulnerability · Source |
| CVE-2025-22077 | suse_vex | SUSE CVE CVE-2025-22077 | first fixed: 2 known affected: 127 known not affected: 275 recommended: 154 | 2026-07-23T01:46:17+00:00 | Vulnerability · Source |
| CVE-2025-22090 | suse_vex | SUSE CVE CVE-2025-22090 | known affected: 640 known not affected: 30 recommended: 395 | 2026-07-23T01:46:10+00:00 | Vulnerability · Source |
| CVE-2025-22099 | suse_vex | SUSE CVE CVE-2025-22099 | known not affected: 275 | 2026-07-23T01:46:05+00:00 | Vulnerability · Source |
| CVE-2025-22102 | suse_vex | SUSE CVE CVE-2025-22102 | known affected: 440 known not affected: 264 recommended: 391 | 2026-07-23T01:46:03+00:00 | Vulnerability · Source |
| CVE-2025-22109 | suse_vex | SUSE CVE CVE-2025-22109 | known affected: 640 known not affected: 60 recommended: 418 | 2026-07-23T01:46:01+00:00 | Vulnerability · Source |
| CVE-2025-22110 | suse_vex | SUSE CVE CVE-2025-22110 | known not affected: 275 | 2026-07-23T01:46:00+00:00 | Vulnerability · Source |
| CVE-2025-23048 | suse_vex | SUSE CVE CVE-2025-23048 | known affected: 424 known not affected: 49 recommended: 266 | 2026-07-23T01:45:51+00:00 | Vulnerability · Source |
| CVE-2025-23083 | suse_vex | SUSE CVE CVE-2025-23083 | known not affected: 187 recommended: 107 | 2026-07-23T01:45:50+00:00 | Vulnerability · Source |
| CVE-2025-23084 | suse_vex | SUSE CVE CVE-2025-23084 | known not affected: 185 | 2026-07-23T01:45:49+00:00 | Vulnerability · Source |
| CVE-2025-23133 | suse_vex | SUSE CVE CVE-2025-23133 | known affected: 552 known not affected: 152 recommended: 395 | 2026-07-23T01:45:44+00:00 | Vulnerability · Source |