VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292225 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-21898 | suse_vex | SUSE CVE CVE-2025-21898 | known affected: 673 known not affected: 22 recommended: 430 | 2026-07-16T18:50:56+00:00 | Vulnerability · Source |
| CVE-2025-21956 | suse_vex | SUSE CVE CVE-2025-21956 | known affected: 402 known not affected: 248 recommended: 421 | 2026-07-16T18:50:46+00:00 | Vulnerability · Source |
| CVE-2025-21964 | suse_vex | SUSE CVE CVE-2025-21964 | known affected: 603 known not affected: 77 recommended: 487 | 2026-07-16T18:50:40+00:00 | Vulnerability · Source |
| CVE-2025-22035 | suse_vex | SUSE CVE CVE-2025-22035 | known affected: 571 known not affected: 120 recommended: 430 | 2026-07-16T18:50:09+00:00 | Vulnerability · Source |
| CVE-2025-22053 | suse_vex | SUSE CVE CVE-2025-22053 | known affected: 674 known not affected: 2 recommended: 421 | 2026-07-16T18:50:02+00:00 | Vulnerability · Source |
| CVE-2025-22063 | suse_vex | SUSE CVE CVE-2025-22063 | known affected: 654 known not affected: 22 recommended: 434 | 2026-07-16T18:49:55+00:00 | Vulnerability · Source |
| CVE-2025-22237 | suse_vex | SUSE CVE CVE-2025-22237 | known affected: 527 recommended: 375 | 2026-07-16T18:49:21+00:00 | Vulnerability · Source |
| CVE-2025-22239 | suse_vex | SUSE CVE CVE-2025-22239 | known affected: 496 recommended: 375 | 2026-07-16T18:49:20+00:00 | Vulnerability · Source |
| CVE-2025-22240 | suse_vex | SUSE CVE CVE-2025-22240 | known affected: 527 recommended: 375 | 2026-07-16T18:49:18+00:00 | Vulnerability · Source |
| CVE-2025-22865 | suse_vex | SUSE CVE CVE-2025-22865 | known not affected: 275 recommended: 92 | 2026-07-16T18:49:15+00:00 | Vulnerability · Source |
| CVE-2025-22921 | suse_vex | SUSE CVE CVE-2025-22921 | known not affected: 138 recommended: 542 | 2026-07-16T18:49:04+00:00 | Vulnerability · Source |
| CVE-2025-23278 | suse_vex | SUSE CVE CVE-2025-23278 | known affected: 17 known not affected: 6 recommended: 231 | 2026-07-16T18:48:35+00:00 | Vulnerability · Source |
| CVE-2025-24030 | suse_vex | SUSE CVE CVE-2025-24030 | recommended: 3 | 2026-07-16T18:48:32+00:00 | Vulnerability · Source |
| CVE-2025-24354 | suse_vex | SUSE CVE CVE-2025-24354 | recommended: 3 | 2026-07-16T18:48:24+00:00 | Vulnerability · Source |
| CVE-2025-24526 | suse_vex | SUSE CVE CVE-2025-24526 | recommended: 3 | 2026-07-16T18:48:20+00:00 | Vulnerability · Source |
| CVE-2025-24866 | suse_vex | SUSE CVE CVE-2025-24866 | recommended: 3 | 2026-07-16T18:48:12+00:00 | Vulnerability · Source |
| CVE-2025-24884 | suse_vex | SUSE CVE CVE-2025-24884 | recommended: 3 | 2026-07-16T18:48:09+00:00 | Vulnerability · Source |
| CVE-2025-24976 | suse_vex | SUSE CVE CVE-2025-24976 | known not affected: 29 recommended: 3 | 2026-07-16T18:48:06+00:00 | Vulnerability · Source |
| CVE-2025-25196 | suse_vex | SUSE CVE CVE-2025-25196 | recommended: 3 | 2026-07-16T18:48:05+00:00 | Vulnerability · Source |
| CVE-2025-25204 | suse_vex | SUSE CVE CVE-2025-25204 | recommended: 3 | 2026-07-16T18:48:03+00:00 | Vulnerability · Source |
| CVE-2025-25208 | suse_vex | SUSE CVE CVE-2025-25208 | recommended: 3 | 2026-07-16T18:48:01+00:00 | Vulnerability · Source |
| CVE-2025-25274 | suse_vex | SUSE CVE CVE-2025-25274 | recommended: 3 | 2026-07-16T18:48:00+00:00 | Vulnerability · Source |
| CVE-2025-25294 | suse_vex | SUSE CVE CVE-2025-25294 | recommended: 3 | 2026-07-16T18:47:58+00:00 | Vulnerability · Source |
| CVE-2025-25473 | suse_vex | SUSE CVE CVE-2025-25473 | known not affected: 400 recommended: 273 | 2026-07-16T18:47:57+00:00 | Vulnerability · Source |
| CVE-2025-27155 | suse_vex | SUSE CVE CVE-2025-27155 | recommended: 3 | 2026-07-16T18:47:40+00:00 | Vulnerability · Source |
| CVE-2025-27421 | suse_vex | SUSE CVE CVE-2025-27421 | recommended: 3 | 2026-07-16T18:47:36+00:00 | Vulnerability · Source |
| CVE-2025-27936 | suse_vex | SUSE CVE CVE-2025-27936 | recommended: 3 | 2026-07-16T18:47:25+00:00 | Vulnerability · Source |
| CVE-2025-29778 | suse_vex | SUSE CVE CVE-2025-29778 | recommended: 3 | 2026-07-16T18:47:23+00:00 | Vulnerability · Source |
| CVE-2025-29785 | suse_vex | SUSE CVE CVE-2025-29785 | known not affected: 397 recommended: 3 | 2026-07-16T18:47:22+00:00 | Vulnerability · Source |
| CVE-2025-30219 | suse_vex | SUSE CVE CVE-2025-30219 | known affected: 55 recommended: 90 | 2026-07-16T18:47:16+00:00 | Vulnerability · Source |
| CVE-2025-30223 | suse_vex | SUSE CVE CVE-2025-30223 | recommended: 3 | 2026-07-16T18:47:14+00:00 | Vulnerability · Source |
| CVE-2025-31489 | suse_vex | SUSE CVE CVE-2025-31489 | recommended: 3 | 2026-07-16T18:47:06+00:00 | Vulnerability · Source |
| CVE-2025-31498 | suse_vex | SUSE CVE CVE-2025-31498 | known not affected: 102 recommended: 30 | 2026-07-16T18:47:04+00:00 | Vulnerability · Source |
| CVE-2025-32801 | suse_vex | SUSE CVE CVE-2025-32801 | known affected: 112 recommended: 285 | 2026-07-16T18:46:52+00:00 | Vulnerability · Source |
| CVE-2025-37852 | suse_vex | SUSE CVE CVE-2025-37852 | known affected: 506 known not affected: 170 recommended: 430 | 2026-07-16T18:45:55+00:00 | Vulnerability · Source |
| CVE-2025-37922 | suse_vex | SUSE CVE CVE-2025-37922 | known not affected: 373 recommended: 53 | 2026-07-16T18:45:10+00:00 | Vulnerability · Source |
| CVE-2025-37942 | suse_vex | SUSE CVE CVE-2025-37942 | known affected: 444 known not affected: 17 recommended: 53 | 2026-07-16T18:44:51+00:00 | Vulnerability · Source |
| CVE-2025-37989 | suse_vex | SUSE CVE CVE-2025-37989 | known affected: 608 known not affected: 68 recommended: 430 | 2026-07-16T18:44:25+00:00 | Vulnerability · Source |
| CVE-2025-38074 | suse_vex | SUSE CVE CVE-2025-38074 | known affected: 440 known not affected: 251 recommended: 430 | 2026-07-16T18:43:56+00:00 | Vulnerability · Source |
| CVE-2025-38383 | suse_vex | SUSE CVE CVE-2025-38383 | first fixed: 2 known affected: 453 recommended: 196 | 2026-07-16T18:41:20+00:00 | Vulnerability · Source |
| CVE-2025-38628 | suse_vex | SUSE CVE CVE-2025-38628 | first fixed: 2 known affected: 399 known not affected: 389 recommended: 265 | 2026-07-16T18:39:06+00:00 | Vulnerability · Source |
| CVE-2025-39753 | suse_vex | SUSE CVE CVE-2025-39753 | first fixed: 2 known not affected: 408 recommended: 172 | 2026-07-16T18:37:16+00:00 | Vulnerability · Source |
| CVE-2025-39814 | suse_vex | SUSE CVE CVE-2025-39814 | first fixed: 2 known not affected: 408 recommended: 172 | 2026-07-16T18:36:34+00:00 | Vulnerability · Source |
| CVE-2025-39830 | suse_vex | SUSE CVE CVE-2025-39830 | first fixed: 2 known affected: 456 known not affected: 317 recommended: 265 | 2026-07-16T18:36:18+00:00 | Vulnerability · Source |
| CVE-2025-43541 | suse_vex | SUSE CVE CVE-2025-43541 | known affected: 133 recommended: 617 | 2026-07-16T18:13:55+00:00 | Vulnerability · Source |
| CVE-2025-43962 | suse_vex | SUSE CVE CVE-2025-43962 | known affected: 24 recommended: 49 | 2026-07-16T18:13:53+00:00 | Vulnerability · Source |
| CVE-2025-46331 | suse_vex | SUSE CVE CVE-2025-46331 | recommended: 3 | 2026-07-16T18:13:50+00:00 | Vulnerability · Source |
| CVE-2025-46342 | suse_vex | SUSE CVE CVE-2025-46342 | recommended: 3 | 2026-07-16T18:13:49+00:00 | Vulnerability · Source |
| CVE-2025-46394 | suse_vex | SUSE CVE CVE-2025-46394 | known affected: 32 recommended: 116 | 2026-07-16T18:13:48+00:00 | Vulnerability · Source |
| CVE-2025-46404 | suse_vex | SUSE CVE CVE-2025-46404 | known affected: 6 recommended: 56 | 2026-07-16T18:13:47+00:00 | Vulnerability · Source |