VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291864 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-40339 | suse_vex | SUSE CVE CVE-2025-40339 | first fixed: 2 known affected: 394 known not affected: 333 recommended: 330 | 2026-08-12T16:51:27+00:00 | Vulnerability · Source |
| CVE-2025-40353 | suse_vex | SUSE CVE CVE-2025-40353 | first fixed: 2 known affected: 394 known not affected: 436 recommended: 172 | 2026-08-12T16:51:24+00:00 | Vulnerability · Source |
| CVE-2025-40911 | suse_vex | SUSE CVE CVE-2025-40911 | known not affected: 27 | 2026-08-12T16:51:17+00:00 | Vulnerability · Source |
| CVE-2025-43214 | suse_vex | SUSE CVE CVE-2025-43214 | known affected: 88 recommended: 528 | 2026-08-12T16:51:12+00:00 | Vulnerability · Source |
| CVE-2025-43356 | suse_vex | SUSE CVE CVE-2025-43356 | known affected: 132 recommended: 608 | 2026-08-12T16:51:09+00:00 | Vulnerability · Source |
| CVE-2025-43421 | suse_vex | SUSE CVE CVE-2025-43421 | known affected: 124 recommended: 632 | 2026-08-12T16:51:06+00:00 | Vulnerability · Source |
| CVE-2025-43431 | suse_vex | SUSE CVE CVE-2025-43431 | known affected: 132 recommended: 632 | 2026-08-12T16:51:05+00:00 | Vulnerability · Source |
| CVE-2025-43432 | suse_vex | SUSE CVE CVE-2025-43432 | known affected: 132 recommended: 632 | 2026-08-12T16:51:03+00:00 | Vulnerability · Source |
| CVE-2025-43433 | suse_vex | SUSE CVE CVE-2025-43433 | known affected: 88 recommended: 528 | 2026-08-12T16:51:02+00:00 | Vulnerability · Source |
| CVE-2025-43441 | suse_vex | SUSE CVE CVE-2025-43441 | known affected: 88 recommended: 528 | 2026-08-12T16:51:00+00:00 | Vulnerability · Source |
| CVE-2025-43443 | suse_vex | SUSE CVE CVE-2025-43443 | known affected: 124 known not affected: 8 recommended: 632 | 2026-08-12T16:50:58+00:00 | Vulnerability · Source |
| CVE-2025-43535 | suse_vex | SUSE CVE CVE-2025-43535 | known affected: 133 recommended: 624 | 2026-08-12T16:50:55+00:00 | Vulnerability · Source |
| CVE-2025-43536 | suse_vex | SUSE CVE CVE-2025-43536 | known affected: 133 recommended: 624 | 2026-08-12T16:50:53+00:00 | Vulnerability · Source |
| CVE-2025-43963 | suse_vex | SUSE CVE CVE-2025-43963 | known affected: 18 known not affected: 8 recommended: 47 | 2026-08-12T16:50:49+00:00 | Vulnerability · Source |
| CVE-2025-43966 | suse_vex | SUSE CVE CVE-2025-43966 | known not affected: 37 | 2026-08-12T16:50:47+00:00 | Vulnerability · Source |
| CVE-2025-45512 | suse_vex | SUSE CVE CVE-2025-45512 | known not affected: 66 | 2026-08-12T16:50:44+00:00 | Vulnerability · Source |
| CVE-2025-46646 | suse_vex | SUSE CVE CVE-2025-46646 | known not affected: 131 recommended: 14 | 2026-08-12T16:50:38+00:00 | Vulnerability · Source |
| CVE-2025-46727 | suse_vex | SUSE CVE CVE-2025-46727 | known affected: 416 known not affected: 8 recommended: 97 | 2026-08-12T16:50:36+00:00 | Vulnerability · Source |
| CVE-2025-46784 | suse_vex | SUSE CVE CVE-2025-46784 | known affected: 6 known not affected: 28 recommended: 32 | 2026-08-12T16:50:34+00:00 | Vulnerability · Source |
| CVE-2025-46818 | suse_vex | SUSE CVE CVE-2025-46818 | known affected: 2 known not affected: 7 recommended: 85 | 2026-08-12T16:50:32+00:00 | Vulnerability · Source |
| CVE-2025-46819 | suse_vex | SUSE CVE CVE-2025-46819 | known affected: 2 known not affected: 7 recommended: 85 | 2026-08-12T16:50:29+00:00 | Vulnerability · Source |
| CVE-2025-47806 | suse_vex | SUSE CVE CVE-2025-47806 | known affected: 689 known not affected: 28 recommended: 591 | 2026-08-12T16:50:21+00:00 | Vulnerability · Source |
| CVE-2025-47807 | suse_vex | SUSE CVE CVE-2025-47807 | known affected: 689 known not affected: 28 recommended: 591 | 2026-08-12T16:50:19+00:00 | Vulnerability · Source |
| CVE-2025-47808 | suse_vex | SUSE CVE CVE-2025-47808 | known affected: 689 known not affected: 28 recommended: 591 | 2026-08-12T16:50:17+00:00 | Vulnerability · Source |
| CVE-2025-48071 | suse_vex | SUSE CVE CVE-2025-48071 | known not affected: 143 recommended: 30 | 2026-08-12T16:50:11+00:00 | Vulnerability · Source |
| CVE-2025-49124 | suse_vex | SUSE CVE CVE-2025-49124 | known not affected: 369 | 2026-08-12T16:50:07+00:00 | Vulnerability · Source |
| CVE-2025-50063 | suse_vex | SUSE CVE CVE-2025-50063 | known not affected: 662 | 2026-08-12T16:50:02+00:00 | Vulnerability · Source |
| CVE-2025-50182 | suse_vex | SUSE CVE CVE-2025-50182 | known not affected: 153 recommended: 5 | 2026-08-12T16:50:00+00:00 | Vulnerability · Source |
| CVE-2025-53057 | suse_vex | SUSE CVE CVE-2025-53057 | known affected: 394 known not affected: 104 recommended: 937 | 2026-08-12T16:49:55+00:00 | Vulnerability · Source |
| CVE-2025-53103 | suse_vex | SUSE CVE CVE-2025-53103 | known not affected: 40 | 2026-08-12T16:49:54+00:00 | Vulnerability · Source |
| CVE-2025-53506 | suse_vex | SUSE CVE CVE-2025-53506 | known affected: 461 known not affected: 20 recommended: 467 | 2026-08-12T16:49:52+00:00 | Vulnerability · Source |
| CVE-2025-54314 | suse_vex | SUSE CVE CVE-2025-54314 | known not affected: 132 recommended: 2 | 2026-08-12T16:49:49+00:00 | Vulnerability · Source |
| CVE-2025-54574 | suse_vex | SUSE CVE CVE-2025-54574 | known affected: 5 known not affected: 9 recommended: 1 | 2026-08-12T16:49:43+00:00 | Vulnerability · Source |
| CVE-2025-55132 | suse_vex | SUSE CVE CVE-2025-55132 | known affected: 32 known not affected: 132 recommended: 126 | 2026-08-12T16:49:41+00:00 | Vulnerability · Source |
| CVE-2025-55754 | suse_vex | SUSE CVE CVE-2025-55754 | known affected: 473 recommended: 535 | 2026-08-12T16:49:34+00:00 | Vulnerability · Source |
| CVE-2025-56225 | suse_vex | SUSE CVE CVE-2025-56225 | recommended: 14 | 2026-08-12T16:49:32+00:00 | Vulnerability · Source |
| CVE-2025-57803 | suse_vex | SUSE CVE CVE-2025-57803 | known affected: 75 known not affected: 24 recommended: 366 | 2026-08-12T16:49:31+00:00 | Vulnerability · Source |
| CVE-2025-57807 | suse_vex | SUSE CVE CVE-2025-57807 | known affected: 172 known not affected: 38 recommended: 229 | 2026-08-12T16:49:29+00:00 | Vulnerability · Source |
| CVE-2025-58144 | suse_vex | SUSE CVE CVE-2025-58144 | known not affected: 264 | 2026-08-12T16:49:26+00:00 | Vulnerability · Source |
| CVE-2025-58145 | suse_vex | SUSE CVE CVE-2025-58145 | known not affected: 264 | 2026-08-12T16:49:25+00:00 | Vulnerability · Source |
| CVE-2025-58146 | suse_vex | SUSE CVE CVE-2025-58146 | known not affected: 264 | 2026-08-12T16:49:23+00:00 | Vulnerability · Source |
| CVE-2025-59032 | suse_vex | SUSE CVE CVE-2025-59032 | known affected: 215 known not affected: 35 recommended: 70 | 2026-08-12T16:49:19+00:00 | Vulnerability · Source |
| CVE-2025-59438 | suse_vex | SUSE CVE CVE-2025-59438 | known not affected: 1651 recommended: 99 | 2026-08-12T16:49:16+00:00 | Vulnerability · Source |
| CVE-2025-59465 | suse_vex | SUSE CVE CVE-2025-59465 | known affected: 164 recommended: 126 | 2026-08-12T16:49:14+00:00 | Vulnerability · Source |
| CVE-2025-60019 | suse_vex | SUSE CVE CVE-2025-60019 | known not affected: 94 | 2026-08-12T16:49:09+00:00 | Vulnerability · Source |
| CVE-2025-61102 | suse_vex | SUSE CVE CVE-2025-61102 | known affected: 233 known not affected: 238 recommended: 112 | 2026-08-12T16:49:06+00:00 | Vulnerability · Source |
| CVE-2025-61728 | suse_vex | SUSE CVE CVE-2025-61728 | known affected: 24 known not affected: 54 recommended: 352 | 2026-08-12T16:49:01+00:00 | Vulnerability · Source |
| CVE-2025-61730 | suse_vex | SUSE CVE CVE-2025-61730 | known affected: 24 known not affected: 108 recommended: 264 | 2026-08-12T16:48:59+00:00 | Vulnerability · Source |
| CVE-2025-61795 | suse_vex | SUSE CVE CVE-2025-61795 | known affected: 473 recommended: 543 | 2026-08-12T16:48:56+00:00 | Vulnerability · Source |
| CVE-2025-61921 | suse_vex | SUSE CVE CVE-2025-61921 | known not affected: 93 | 2026-08-12T16:48:53+00:00 | Vulnerability · Source |