VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-27836 | suse_vex | SUSE CVE CVE-2025-27836 | known affected: 57 known not affected: 7 recommended: 103 | 2026-10-15T16:53:38+00:00 | Vulnerability · Source |
| CVE-2025-27837 | suse_vex | SUSE CVE CVE-2025-27837 | known affected: 0 known not affected: 147 recommended: 13 | 2026-10-15T16:53:36+00:00 | Vulnerability · Source |
| CVE-2025-27933 | suse_vex | SUSE CVE CVE-2025-27933 | recommended: 5 | 2026-10-15T16:53:34+00:00 | Vulnerability · Source |
| CVE-2025-27936 | suse_vex | SUSE CVE CVE-2025-27936 | recommended: 5 | 2026-10-15T16:53:33+00:00 | Vulnerability · Source |
| CVE-2025-29072 | suse_vex | SUSE CVE CVE-2025-29072 | recommended: 5 | 2026-10-15T16:53:30+00:00 | Vulnerability · Source |
| CVE-2025-29087 | suse_vex | SUSE CVE CVE-2025-29087 | known affected: 426 known not affected: 1 recommended: 252 | 2026-10-15T16:53:28+00:00 | Vulnerability · Source |
| CVE-2025-29088 | suse_vex | SUSE CVE CVE-2025-29088 | known affected: 427 known not affected: 11 recommended: 252 | 2026-10-15T16:53:26+00:00 | Vulnerability · Source |
| CVE-2025-29768 | suse_vex | SUSE CVE CVE-2025-29768 | known affected: 439 known not affected: 6 recommended: 248 | 2026-10-15T16:53:23+00:00 | Vulnerability · Source |
| CVE-2025-29778 | suse_vex | SUSE CVE CVE-2025-29778 | recommended: 5 | 2026-10-15T16:53:21+00:00 | Vulnerability · Source |
| CVE-2025-29785 | suse_vex | SUSE CVE CVE-2025-29785 | known affected: 0 known not affected: 441 recommended: 5 | 2026-10-15T16:53:19+00:00 | Vulnerability · Source |
| CVE-2025-29914 | suse_vex | SUSE CVE CVE-2025-29914 | recommended: 5 | 2026-10-15T16:53:17+00:00 | Vulnerability · Source |
| CVE-2025-29923 | suse_vex | SUSE CVE CVE-2025-29923 | known affected: 22 known not affected: 6 recommended: 93 | 2026-10-15T16:53:15+00:00 | Vulnerability · Source |
| CVE-2025-30153 | suse_vex | SUSE CVE CVE-2025-30153 | recommended: 19 | 2026-10-15T16:53:14+00:00 | Vulnerability · Source |
| CVE-2025-30163 | suse_vex | SUSE CVE CVE-2025-30163 | recommended: 5 | 2026-10-15T16:53:12+00:00 | Vulnerability · Source |
| CVE-2025-30179 | suse_vex | SUSE CVE CVE-2025-30179 | recommended: 5 | 2026-10-15T16:53:10+00:00 | Vulnerability · Source |
| CVE-2025-30204 | suse_vex | SUSE CVE CVE-2025-30204 | known affected: 76 known not affected: 585 recommended: 196 | 2026-10-15T16:53:08+00:00 | Vulnerability · Source |
| CVE-2025-30206 | suse_vex | SUSE CVE CVE-2025-30206 | recommended: 5 | 2026-10-15T16:53:06+00:00 | Vulnerability · Source |
| CVE-2025-30215 | suse_vex | SUSE CVE CVE-2025-30215 | recommended: 5 | 2026-10-15T16:53:05+00:00 | Vulnerability · Source |
| CVE-2025-30223 | suse_vex | SUSE CVE CVE-2025-30223 | recommended: 5 | 2026-10-15T16:53:03+00:00 | Vulnerability · Source |
| CVE-2025-30258 | suse_vex | SUSE CVE CVE-2025-30258 | known affected: 446 known not affected: 28 recommended: 97 | 2026-10-15T16:53:00+00:00 | Vulnerability · Source |
| CVE-2025-30348 | suse_vex | SUSE CVE CVE-2025-30348 | known affected: 2440 recommended: 682 | 2026-10-15T16:52:58+00:00 | Vulnerability · Source |
| CVE-2025-30472 | suse_vex | SUSE CVE CVE-2025-30472 | known affected: 394 known not affected: 12 recommended: 90 | 2026-10-15T16:52:56+00:00 | Vulnerability · Source |
| CVE-2025-30698 | suse_vex | SUSE CVE CVE-2025-30698 | known affected: 522 known not affected: 139 recommended: 916 | 2026-10-15T16:52:54+00:00 | Vulnerability · Source |
| CVE-2025-30749 | suse_vex | SUSE CVE CVE-2025-30749 | known affected: 626 recommended: 964 | 2026-10-15T16:52:51+00:00 | Vulnerability · Source |
| CVE-2025-30754 | suse_vex | SUSE CVE CVE-2025-30754 | known affected: 626 recommended: 936 | 2026-10-15T16:52:49+00:00 | Vulnerability · Source |
| CVE-2025-31115 | suse_vex | SUSE CVE CVE-2025-31115 | known affected: 394 known not affected: 257 recommended: 90 | 2026-10-15T16:52:47+00:00 | Vulnerability · Source |
| CVE-2025-31133 | suse_vex | SUSE CVE CVE-2025-31133 | known affected: 397 known not affected: 1291 recommended: 231 | 2026-10-15T16:52:45+00:00 | Vulnerability · Source |
| CVE-2025-31277 | suse_vex | SUSE CVE CVE-2025-31277 | known affected: 176 recommended: 504 | 2026-10-15T16:52:44+00:00 | Vulnerability · Source |
| CVE-2025-31335 | suse_vex | SUSE CVE CVE-2025-31335 | known affected: 177 recommended: 47 | 2026-10-15T16:52:42+00:00 | Vulnerability · Source |
| CVE-2025-31363 | suse_vex | SUSE CVE CVE-2025-31363 | recommended: 5 | 2026-10-15T16:52:40+00:00 | Vulnerability · Source |
| CVE-2025-31489 | suse_vex | SUSE CVE CVE-2025-31489 | recommended: 5 | 2026-10-15T16:52:38+00:00 | Vulnerability · Source |
| CVE-2025-31648 | suse_vex | SUSE CVE CVE-2025-31648 | known affected: 20 recommended: 36 | 2026-10-15T16:52:37+00:00 | Vulnerability · Source |
| CVE-2024-24784 | redhat_vex | golang: net/mail: comments in display names are incorrectly handled | fixed: 1678 known affected: 56 known not affected: 714 | 2026-10-15T16:52:36+00:00 | Vulnerability · Source |
| CVE-2025-31650 | suse_vex | SUSE CVE CVE-2025-31650 | known affected: 422 known not affected: 228 recommended: 373 | 2026-10-15T16:52:35+00:00 | Vulnerability · Source |
| CVE-2025-31936 | suse_vex | SUSE CVE CVE-2025-31936 | known affected: 12 recommended: 36 | 2026-10-15T16:52:33+00:00 | Vulnerability · Source |
| CVE-2025-31938 | suse_vex | SUSE CVE CVE-2025-31938 | known affected: 12 recommended: 33 | 2026-10-15T16:52:32+00:00 | Vulnerability · Source |
| CVE-2025-31947 | suse_vex | SUSE CVE CVE-2025-31947 | recommended: 5 | 2026-10-15T16:52:30+00:00 | Vulnerability · Source |
| CVE-2025-32025 | suse_vex | SUSE CVE CVE-2025-32025 | recommended: 5 | 2026-10-15T16:52:28+00:00 | Vulnerability · Source |
| CVE-2025-32086 | suse_vex | SUSE CVE CVE-2025-32086 | known affected: 24 recommended: 43 | 2026-10-15T16:52:26+00:00 | Vulnerability · Source |
| CVE-2025-32093 | suse_vex | SUSE CVE CVE-2025-32093 | recommended: 5 | 2026-10-15T16:52:24+00:00 | Vulnerability · Source |
| CVE-2025-32365 | suse_vex | SUSE CVE CVE-2025-32365 | known affected: 284 known not affected: 40 recommended: 188 | 2026-10-15T16:52:22+00:00 | Vulnerability · Source |
| CVE-2025-32386 | suse_vex | SUSE CVE CVE-2025-32386 | known affected: 30 known not affected: 95 recommended: 133 | 2026-10-15T16:52:20+00:00 | Vulnerability · Source |
| CVE-2025-32414 | suse_vex | SUSE CVE CVE-2025-32414 | known affected: 567 known not affected: 21 recommended: 196 | 2026-10-15T16:52:18+00:00 | Vulnerability · Source |
| CVE-2025-32415 | suse_vex | SUSE CVE CVE-2025-32415 | known affected: 592 known not affected: 21 recommended: 196 | 2026-10-15T16:52:16+00:00 | Vulnerability · Source |
| CVE-2025-32431 | suse_vex | SUSE CVE CVE-2025-32431 | recommended: 6 | 2026-10-15T16:52:15+00:00 | Vulnerability · Source |
| CVE-2025-32441 | suse_vex | SUSE CVE CVE-2025-32441 | known affected: 428 known not affected: 10 recommended: 91 | 2026-10-15T16:52:13+00:00 | Vulnerability · Source |
| CVE-2025-32462 | suse_vex | SUSE CVE CVE-2025-32462 | known affected: 380 known not affected: 1 recommended: 211 | 2026-10-15T16:52:11+00:00 | Vulnerability · Source |
| CVE-2025-32463 | suse_vex | SUSE CVE CVE-2025-32463 | known affected: 394 known not affected: 117 recommended: 88 | 2026-10-15T16:52:10+00:00 | Vulnerability · Source |
| CVE-2025-32728 | suse_vex | SUSE CVE CVE-2025-32728 | known affected: 376 known not affected: 95 recommended: 295 | 2026-10-15T16:52:08+00:00 | Vulnerability · Source |
| CVE-2025-32777 | suse_vex | SUSE CVE CVE-2025-32777 | recommended: 5 | 2026-10-15T16:52:06+00:00 | Vulnerability · Source |