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-37865 | suse_vex | SUSE CVE CVE-2025-37865 | known affected: 497 known not affected: 220 recommended: 392 | 2026-07-25T00:55:38+00:00 | Vulnerability · Source |
| CVE-2025-37875 | suse_vex | SUSE CVE CVE-2025-37875 | known affected: 506 known not affected: 196 recommended: 407 | 2026-07-25T00:55:26+00:00 | Vulnerability · Source |
| CVE-2025-37879 | suse_vex | SUSE CVE CVE-2025-37879 | known affected: 687 known not affected: 6 recommended: 448 | 2026-07-25T00:55:24+00:00 | Vulnerability · Source |
| CVE-2025-37881 | suse_vex | SUSE CVE CVE-2025-37881 | known affected: 506 known not affected: 196 recommended: 407 | 2026-07-25T00:55:21+00:00 | Vulnerability · Source |
| CVE-2025-37891 | suse_vex | SUSE CVE CVE-2025-37891 | known affected: 410 known not affected: 307 recommended: 407 | 2026-07-25T00:55:08+00:00 | Vulnerability · Source |
| CVE-2025-37892 | suse_vex | SUSE CVE CVE-2025-37892 | known affected: 643 known not affected: 46 recommended: 444 | 2026-07-25T00:55:07+00:00 | Vulnerability · Source |
| CVE-2025-37896 | suse_vex | SUSE CVE CVE-2025-37896 | known not affected: 375 | 2026-07-25T00:55:01+00:00 | Vulnerability · Source |
| CVE-2025-37897 | suse_vex | SUSE CVE CVE-2025-37897 | known affected: 394 known not affected: 286 recommended: 407 | 2026-07-25T00:54:59+00:00 | Vulnerability · Source |
| CVE-2025-37899 | suse_vex | SUSE CVE CVE-2025-37899 | known not affected: 451 | 2026-07-25T00:54:57+00:00 | Vulnerability · Source |
| CVE-2025-37905 | suse_vex | SUSE CVE CVE-2025-37905 | known affected: 490 known not affected: 190 recommended: 407 | 2026-07-25T00:54:52+00:00 | Vulnerability · Source |
| CVE-2025-37912 | suse_vex | SUSE CVE CVE-2025-37912 | known affected: 481 known not affected: 236 recommended: 407 | 2026-07-25T00:54:47+00:00 | Vulnerability · Source |
| CVE-2025-37913 | suse_vex | SUSE CVE CVE-2025-37913 | known affected: 535 known not affected: 113 recommended: 444 | 2026-07-25T00:54:45+00:00 | Vulnerability · Source |
| CVE-2025-37917 | suse_vex | SUSE CVE CVE-2025-37917 | known affected: 440 known not affected: 277 recommended: 392 | 2026-07-25T00:54:39+00:00 | Vulnerability · Source |
| CVE-2025-37929 | suse_vex | SUSE CVE CVE-2025-37929 | known affected: 394 known not affected: 286 recommended: 407 | 2026-07-25T00:54:28+00:00 | Vulnerability · Source |
| CVE-2025-37932 | suse_vex | SUSE CVE CVE-2025-37932 | known affected: 115 known not affected: 50 recommended: 679 | 2026-07-25T00:54:22+00:00 | Vulnerability · Source |
| CVE-2025-37935 | suse_vex | SUSE CVE CVE-2025-37935 | known affected: 57 known not affected: 355 recommended: 53 | 2026-07-25T00:54:18+00:00 | Vulnerability · Source |
| CVE-2025-37936 | suse_vex | SUSE CVE CVE-2025-37936 | known affected: 497 known not affected: 220 recommended: 392 | 2026-07-25T00:54:17+00:00 | Vulnerability · Source |
| CVE-2025-37937 | suse_vex | SUSE CVE CVE-2025-37937 | known affected: 618 known not affected: 84 recommended: 407 | 2026-07-25T00:54:15+00:00 | Vulnerability · Source |
| CVE-2025-37941 | suse_vex | SUSE CVE CVE-2025-37941 | known affected: 47 known not affected: 328 recommended: 53 | 2026-07-25T00:54:12+00:00 | Vulnerability · Source |
| CVE-2025-37946 | suse_vex | SUSE CVE CVE-2025-37946 | known affected: 441 known not affected: 239 recommended: 407 | 2026-07-25T00:54:06+00:00 | Vulnerability · Source |
| CVE-2025-37950 | suse_vex | SUSE CVE CVE-2025-37950 | known not affected: 375 | 2026-07-25T00:54:01+00:00 | Vulnerability · Source |
| CVE-2025-37951 | suse_vex | SUSE CVE CVE-2025-37951 | known affected: 535 known not affected: 145 recommended: 407 | 2026-07-25T00:53:59+00:00 | Vulnerability · Source |
| CVE-2025-37957 | suse_vex | SUSE CVE CVE-2025-37957 | known affected: 567 known not affected: 150 recommended: 411 | 2026-07-25T00:53:57+00:00 | Vulnerability · Source |
| CVE-2025-37959 | suse_vex | SUSE CVE CVE-2025-37959 | known affected: 490 known not affected: 190 recommended: 407 | 2026-07-25T00:53:55+00:00 | Vulnerability · Source |
| CVE-2025-37966 | suse_vex | SUSE CVE CVE-2025-37966 | known affected: 47 known not affected: 328 | 2026-07-25T00:53:52+00:00 | Vulnerability · Source |
| CVE-2025-37967 | suse_vex | SUSE CVE CVE-2025-37967 | known affected: 618 known not affected: 99 recommended: 392 | 2026-07-25T00:53:50+00:00 | Vulnerability · Source |
| CVE-2025-37970 | suse_vex | SUSE CVE CVE-2025-37970 | known affected: 604 known not affected: 98 recommended: 407 | 2026-07-25T00:53:45+00:00 | Vulnerability · Source |
| CVE-2025-37971 | suse_vex | SUSE CVE CVE-2025-37971 | known affected: 47 known not affected: 328 recommended: 53 | 2026-07-25T00:53:43+00:00 | Vulnerability · Source |
| CVE-2025-37977 | suse_vex | SUSE CVE CVE-2025-37977 | known affected: 57 known not affected: 226 | 2026-07-25T00:53:36+00:00 | Vulnerability · Source |
| CVE-2025-37979 | suse_vex | SUSE CVE CVE-2025-37979 | known affected: 441 known not affected: 239 recommended: 407 | 2026-07-25T00:53:33+00:00 | Vulnerability · Source |
| CVE-2025-37980 | suse_vex | SUSE CVE CVE-2025-37980 | known affected: 637 known not affected: 52 recommended: 444 | 2026-07-25T00:53:32+00:00 | Vulnerability · Source |
| CVE-2025-37986 | suse_vex | SUSE CVE CVE-2025-37986 | known affected: 441 known not affected: 239 recommended: 407 | 2026-07-25T00:53:25+00:00 | Vulnerability · Source |
| CVE-2025-37987 | suse_vex | SUSE CVE CVE-2025-37987 | known affected: 497 known not affected: 220 recommended: 392 | 2026-07-25T00:53:23+00:00 | Vulnerability · Source |
| CVE-2025-37990 | suse_vex | SUSE CVE CVE-2025-37990 | known affected: 639 known not affected: 82 recommended: 421 | 2026-07-25T00:53:21+00:00 | Vulnerability · Source |
| CVE-2025-37995 | suse_vex | SUSE CVE CVE-2025-37995 | known affected: 683 known not affected: 6 recommended: 444 | 2026-07-25T00:53:15+00:00 | Vulnerability · Source |
| CVE-2025-38006 | suse_vex | SUSE CVE CVE-2025-38006 | first fixed: 2 known affected: 448 known not affected: 283 recommended: 508 | 2026-07-25T00:53:01+00:00 | Vulnerability · Source |
| CVE-2025-38009 | suse_vex | SUSE CVE CVE-2025-38009 | known affected: 557 known not affected: 145 recommended: 407 | 2026-07-25T00:52:58+00:00 | Vulnerability · Source |
| CVE-2025-38019 | suse_vex | SUSE CVE CVE-2025-38019 | first fixed: 2 known affected: 5 known not affected: 448 recommended: 154 | 2026-07-25T00:52:49+00:00 | Vulnerability · Source |
| CVE-2025-38031 | suse_vex | SUSE CVE CVE-2025-38031 | known affected: 557 known not affected: 145 recommended: 407 | 2026-07-25T00:52:37+00:00 | Vulnerability · Source |
| CVE-2025-38034 | suse_vex | SUSE CVE CVE-2025-38034 | first fixed: 2 known affected: 689 known not affected: 6 recommended: 545 | 2026-07-25T00:52:35+00:00 | Vulnerability · Source |
| CVE-2025-38036 | suse_vex | SUSE CVE CVE-2025-38036 | known affected: 93 known not affected: 379 | 2026-07-25T00:52:33+00:00 | Vulnerability · Source |
| CVE-2025-38047 | suse_vex | SUSE CVE CVE-2025-38047 | known affected: 720 known not affected: 95 recommended: 164 | 2026-07-25T00:52:24+00:00 | Vulnerability · Source |
| CVE-2025-38051 | suse_vex | SUSE CVE CVE-2025-38051 | known affected: 689 recommended: 493 | 2026-07-25T00:52:21+00:00 | Vulnerability · Source |
| CVE-2025-38053 | suse_vex | SUSE CVE CVE-2025-38053 | known affected: 567 known not affected: 150 recommended: 456 | 2026-07-25T00:52:18+00:00 | Vulnerability · Source |
| CVE-2025-38058 | suse_vex | SUSE CVE CVE-2025-38058 | first fixed: 2 known affected: 675 known not affected: 20 recommended: 545 | 2026-07-25T00:52:13+00:00 | Vulnerability · Source |
| CVE-2025-38059 | suse_vex | SUSE CVE CVE-2025-38059 | known affected: 394 known not affected: 308 recommended: 407 | 2026-07-25T00:52:11+00:00 | Vulnerability · Source |
| CVE-2025-38067 | suse_vex | SUSE CVE CVE-2025-38067 | known affected: 66 known not affected: 46 recommended: 42 | 2026-07-25T00:52:03+00:00 | Vulnerability · Source |
| CVE-2025-38077 | suse_vex | SUSE CVE CVE-2025-38077 | known affected: 506 known not affected: 196 recommended: 407 | 2026-07-25T00:51:58+00:00 | Vulnerability · Source |
| CVE-2025-38080 | suse_vex | SUSE CVE CVE-2025-38080 | known affected: 394 known not affected: 308 recommended: 407 | 2026-07-25T00:51:54+00:00 | Vulnerability · Source |
| CVE-2025-38084 | suse_vex | SUSE CVE CVE-2025-38084 | first fixed: 2 known affected: 513 known not affected: 46 recommended: 732 | 2026-07-25T00:51:52+00:00 | Vulnerability · Source |