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-39812 | suse_vex | SUSE CVE CVE-2025-39812 | first fixed: 2 known affected: 630 known not affected: 5 recommended: 503 | 2026-07-23T01:37:20+00:00 | Vulnerability · Source |
| CVE-2025-39823 | suse_vex | SUSE CVE CVE-2025-39823 | first fixed: 2 known affected: 361 known not affected: 97 recommended: 758 | 2026-07-23T01:37:16+00:00 | Vulnerability · Source |
| CVE-2025-39826 | suse_vex | SUSE CVE CVE-2025-39826 | first fixed: 2 known affected: 394 known not affected: 263 recommended: 500 | 2026-07-23T01:37:13+00:00 | Vulnerability · Source |
| CVE-2025-39827 | suse_vex | SUSE CVE CVE-2025-39827 | first fixed: 2 known affected: 394 known not affected: 263 recommended: 500 | 2026-07-23T01:37:12+00:00 | Vulnerability · Source |
| CVE-2025-39836 | suse_vex | SUSE CVE CVE-2025-39836 | first fixed: 2 known affected: 394 known not affected: 351 recommended: 238 | 2026-07-23T01:37:09+00:00 | Vulnerability · Source |
| CVE-2025-39844 | suse_vex | SUSE CVE CVE-2025-39844 | first fixed: 2 known affected: 509 known not affected: 154 recommended: 500 | 2026-07-23T01:37:07+00:00 | Vulnerability · Source |
| CVE-2025-39845 | suse_vex | SUSE CVE CVE-2025-39845 | first fixed: 2 known affected: 394 known not affected: 263 recommended: 500 | 2026-07-23T01:37:05+00:00 | Vulnerability · Source |
| CVE-2025-39848 | suse_vex | SUSE CVE CVE-2025-39848 | first fixed: 2 known affected: 394 known not affected: 263 recommended: 500 | 2026-07-23T01:37:04+00:00 | Vulnerability · Source |
| CVE-2025-39851 | suse_vex | SUSE CVE CVE-2025-39851 | first fixed: 2 known affected: 552 known not affected: 111 recommended: 500 | 2026-07-23T01:37:02+00:00 | Vulnerability · Source |
| CVE-2025-39855 | suse_vex | SUSE CVE CVE-2025-39855 | known not affected: 345 | 2026-07-23T01:37:01+00:00 | Vulnerability · Source |
| CVE-2025-39856 | suse_vex | SUSE CVE CVE-2025-39856 | known not affected: 345 | 2026-07-23T01:36:59+00:00 | Vulnerability · Source |
| CVE-2025-39858 | suse_vex | SUSE CVE CVE-2025-39858 | known not affected: 345 | 2026-07-23T01:36:58+00:00 | Vulnerability · Source |
| CVE-2025-39859 | suse_vex | SUSE CVE CVE-2025-39859 | first fixed: 2 known affected: 511 known not affected: 154 recommended: 473 | 2026-07-23T01:36:56+00:00 | Vulnerability · Source |
| CVE-2025-39863 | suse_vex | SUSE CVE CVE-2025-39863 | first fixed: 2 known affected: 629 known not affected: 6 recommended: 530 | 2026-07-23T01:36:55+00:00 | Vulnerability · Source |
| CVE-2025-39882 | suse_vex | SUSE CVE CVE-2025-39882 | first fixed: 2 known affected: 394 known not affected: 263 recommended: 500 | 2026-07-23T01:36:51+00:00 | Vulnerability · Source |
| CVE-2025-39884 | suse_vex | SUSE CVE CVE-2025-39884 | first fixed: 2 known affected: 57 known not affected: 351 recommended: 127 | 2026-07-23T01:36:49+00:00 | Vulnerability · Source |
| CVE-2025-39886 | suse_vex | SUSE CVE CVE-2025-39886 | known affected: 57 known not affected: 203 | 2026-07-23T01:36:48+00:00 | Vulnerability · Source |
| CVE-2025-39887 | suse_vex | SUSE CVE CVE-2025-39887 | known not affected: 345 | 2026-07-23T01:36:47+00:00 | Vulnerability · Source |
| CVE-2025-39888 | suse_vex | SUSE CVE CVE-2025-39888 | known not affected: 345 | 2026-07-23T01:36:45+00:00 | Vulnerability · Source |
| CVE-2025-39897 | suse_vex | SUSE CVE CVE-2025-39897 | first fixed: 2 known not affected: 433 recommended: 154 | 2026-07-23T01:36:43+00:00 | Vulnerability · Source |
| CVE-2025-39899 | suse_vex | SUSE CVE CVE-2025-39899 | first fixed: 2 known not affected: 414 recommended: 154 | 2026-07-23T01:36:42+00:00 | Vulnerability · Source |
| CVE-2025-39910 | suse_vex | SUSE CVE CVE-2025-39910 | known not affected: 376 | 2026-07-23T01:36:39+00:00 | Vulnerability · Source |
| CVE-2025-39911 | suse_vex | SUSE CVE CVE-2025-39911 | first fixed: 2 known affected: 635 recommended: 530 | 2026-07-23T01:36:38+00:00 | Vulnerability · Source |
| CVE-2025-39915 | suse_vex | SUSE CVE CVE-2025-39915 | known not affected: 343 | 2026-07-23T01:36:36+00:00 | Vulnerability · Source |
| CVE-2025-39916 | suse_vex | SUSE CVE CVE-2025-39916 | first fixed: 2 known not affected: 408 recommended: 154 | 2026-07-23T01:36:35+00:00 | Vulnerability · Source |
| CVE-2025-39917 | suse_vex | SUSE CVE CVE-2025-39917 | first fixed: 2 known affected: 5 known not affected: 433 recommended: 127 | 2026-07-23T01:36:33+00:00 | Vulnerability · Source |
| CVE-2025-39919 | suse_vex | SUSE CVE CVE-2025-39919 | known not affected: 343 | 2026-07-23T01:36:32+00:00 | Vulnerability · Source |
| CVE-2025-39922 | suse_vex | SUSE CVE CVE-2025-39922 | first fixed: 2 known affected: 394 known not affected: 351 recommended: 238 | 2026-07-23T01:36:31+00:00 | Vulnerability · Source |
| CVE-2025-39924 | suse_vex | SUSE CVE CVE-2025-39924 | known not affected: 345 | 2026-07-23T01:36:29+00:00 | Vulnerability · Source |
| CVE-2025-39927 | suse_vex | SUSE CVE CVE-2025-39927 | first fixed: 2 known affected: 341 known not affected: 97 recommended: 145 | 2026-07-23T01:36:28+00:00 | Vulnerability · Source |
| CVE-2025-39930 | suse_vex | SUSE CVE CVE-2025-39930 | known not affected: 346 recommended: 27 | 2026-07-23T01:36:27+00:00 | Vulnerability · Source |
| CVE-2025-39932 | suse_vex | SUSE CVE CVE-2025-39932 | known not affected: 345 | 2026-07-23T01:36:25+00:00 | Vulnerability · Source |
| CVE-2025-39934 | suse_vex | SUSE CVE CVE-2025-39934 | first fixed: 2 known affected: 394 known not affected: 263 recommended: 500 | 2026-07-23T01:36:23+00:00 | Vulnerability · Source |
| CVE-2025-39935 | suse_vex | SUSE CVE CVE-2025-39935 | known affected: 57 known not affected: 357 recommended: 27 | 2026-07-23T01:36:22+00:00 | Vulnerability · Source |
| CVE-2025-39936 | suse_vex | SUSE CVE CVE-2025-39936 | known not affected: 343 | 2026-07-23T01:36:21+00:00 | Vulnerability · Source |
| CVE-2025-39938 | suse_vex | SUSE CVE CVE-2025-39938 | first fixed: 2 known affected: 449 known not affected: 208 recommended: 500 | 2026-07-23T01:36:19+00:00 | Vulnerability · Source |
| CVE-2025-39939 | suse_vex | SUSE CVE CVE-2025-39939 | known not affected: 345 | 2026-07-23T01:36:18+00:00 | Vulnerability · Source |
| CVE-2025-39953 | suse_vex | SUSE CVE CVE-2025-39953 | known affected: 216 known not affected: 22 | 2026-07-23T01:36:15+00:00 | Vulnerability · Source |
| CVE-2025-39954 | suse_vex | SUSE CVE CVE-2025-39954 | known not affected: 345 | 2026-07-23T01:36:14+00:00 | Vulnerability · Source |
| CVE-2025-39956 | suse_vex | SUSE CVE CVE-2025-39956 | first fixed: 2 known affected: 394 known not affected: 436 recommended: 154 | 2026-07-23T01:36:13+00:00 | Vulnerability · Source |
| CVE-2025-39958 | suse_vex | SUSE CVE CVE-2025-39958 | known affected: 198 known not affected: 2 | 2026-07-23T01:36:11+00:00 | Vulnerability · Source |
| CVE-2025-39976 | suse_vex | SUSE CVE CVE-2025-39976 | known not affected: 345 | 2026-07-23T01:36:07+00:00 | Vulnerability · Source |
| CVE-2025-39978 | suse_vex | SUSE CVE CVE-2025-39978 | first fixed: 2 known affected: 354 known not affected: 154 recommended: 696 | 2026-07-23T01:36:06+00:00 | Vulnerability · Source |
| CVE-2025-39986 | suse_vex | SUSE CVE CVE-2025-39986 | first fixed: 2 known affected: 394 known not affected: 263 recommended: 500 | 2026-07-23T01:36:03+00:00 | Vulnerability · Source |
| CVE-2025-39994 | suse_vex | SUSE CVE CVE-2025-39994 | first fixed: 2 known affected: 394 known not affected: 233 recommended: 479 | 2026-07-23T01:36:01+00:00 | Vulnerability · Source |
| CVE-2025-39995 | suse_vex | SUSE CVE CVE-2025-39995 | first fixed: 2 known affected: 394 known not affected: 263 recommended: 506 | 2026-07-23T01:36:00+00:00 | Vulnerability · Source |
| CVE-2025-39997 | suse_vex | SUSE CVE CVE-2025-39997 | first fixed: 2 known affected: 399 known not affected: 236 recommended: 536 | 2026-07-23T01:35:58+00:00 | Vulnerability · Source |
| CVE-2025-39999 | suse_vex | SUSE CVE CVE-2025-39999 | known not affected: 345 recommended: 6 | 2026-07-23T01:35:56+00:00 | Vulnerability · Source |
| CVE-2025-40002 | suse_vex | SUSE CVE CVE-2025-40002 | known not affected: 414 recommended: 33 | 2026-07-23T01:35:54+00:00 | Vulnerability · Source |
| CVE-2025-40005 | suse_vex | SUSE CVE CVE-2025-40005 | first fixed: 2 known affected: 615 known not affected: 50 recommended: 500 | 2026-07-23T01:35:53+00:00 | Vulnerability · Source |