VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
306222 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-39899 | suse_vex | SUSE CVE CVE-2025-39899 | known affected: 2 known not affected: 523 recommended: 154 | 2026-10-10T01:56:57+00:00 | Vulnerability · Source |
| CVE-2025-39902 | suse_vex | SUSE CVE CVE-2025-39902 | known affected: 604 known not affected: 187 recommended: 483 | 2026-10-10T01:56:55+00:00 | Vulnerability · Source |
| CVE-2025-39903 | suse_vex | SUSE CVE CVE-2025-39903 | known affected: 396 known not affected: 542 recommended: 154 | 2026-10-10T01:56:52+00:00 | Vulnerability · Source |
| CVE-2025-39905 | suse_vex | SUSE CVE CVE-2025-39905 | known not affected: 523 recommended: 42 | 2026-10-10T01:56:50+00:00 | Vulnerability · Source |
| CVE-2025-39911 | suse_vex | SUSE CVE CVE-2025-39911 | known affected: 731 recommended: 501 | 2026-10-10T01:56:47+00:00 | Vulnerability · Source |
| CVE-2025-39913 | suse_vex | SUSE CVE CVE-2025-39913 | known affected: 664 known not affected: 64 recommended: 407 | 2026-10-10T01:56:44+00:00 | Vulnerability · Source |
| CVE-2025-39920 | suse_vex | SUSE CVE CVE-2025-39920 | known affected: 400 known not affected: 387 recommended: 310 | 2026-10-10T01:56:41+00:00 | Vulnerability · Source |
| CVE-2025-39927 | suse_vex | SUSE CVE CVE-2025-39927 | known affected: 301 known not affected: 187 recommended: 172 | 2026-10-10T01:56:38+00:00 | Vulnerability · Source |
| CVE-2025-39930 | suse_vex | SUSE CVE CVE-2025-39930 | known not affected: 467 recommended: 27 | 2026-10-10T01:56:36+00:00 | Vulnerability · Source |
| CVE-2025-39934 | suse_vex | SUSE CVE CVE-2025-39934 | known affected: 396 known not affected: 387 recommended: 464 | 2026-10-10T01:56:34+00:00 | Vulnerability · Source |
| CVE-2025-39938 | suse_vex | SUSE CVE CVE-2025-39938 | known affected: 461 known not affected: 322 recommended: 464 | 2026-10-10T01:56:31+00:00 | Vulnerability · Source |
| CVE-2025-39944 | suse_vex | SUSE CVE CVE-2025-39944 | known affected: 529 known not affected: 262 recommended: 464 | 2026-10-10T01:56:28+00:00 | Vulnerability · Source |
| CVE-2025-39950 | suse_vex | SUSE CVE CVE-2025-39950 | known affected: 396 known not affected: 542 recommended: 154 | 2026-10-10T01:56:26+00:00 | Vulnerability · Source |
| CVE-2025-39955 | suse_vex | SUSE CVE CVE-2025-39955 | known affected: 725 known not affected: 6 recommended: 575 | 2026-10-10T01:56:23+00:00 | Vulnerability · Source |
| CVE-2025-39956 | suse_vex | SUSE CVE CVE-2025-39956 | known affected: 396 known not affected: 545 recommended: 154 | 2026-10-10T01:56:20+00:00 | Vulnerability · Source |
| CVE-2025-39959 | suse_vex | SUSE CVE CVE-2025-39959 | known not affected: 523 recommended: 27 | 2026-10-10T01:56:18+00:00 | Vulnerability · Source |
| CVE-2025-39963 | suse_vex | SUSE CVE CVE-2025-39963 | known affected: 401 known not affected: 540 recommended: 162 | 2026-10-10T01:56:16+00:00 | Vulnerability · Source |
| CVE-2025-39964 | suse_vex | SUSE CVE CVE-2025-39964 | known affected: 826 recommended: 525 | 2026-10-10T01:56:14+00:00 | Vulnerability · Source |
| CVE-2025-39967 | suse_vex | SUSE CVE CVE-2025-39967 | known affected: 431 known not affected: 132 recommended: 683 | 2026-10-10T01:56:12+00:00 | Vulnerability · Source |
| CVE-2025-39973 | suse_vex | SUSE CVE CVE-2025-39973 | known affected: 477 recommended: 1019 | 2026-10-10T01:56:10+00:00 | Vulnerability · Source |
| CVE-2025-39980 | suse_vex | SUSE CVE CVE-2025-39980 | known affected: 573 known not affected: 213 recommended: 464 | 2026-10-10T01:56:07+00:00 | Vulnerability · Source |
| CVE-2025-39981 | suse_vex | SUSE CVE CVE-2025-39981 | known affected: 376 known not affected: 323 recommended: 654 | 2026-10-10T01:56:05+00:00 | Vulnerability · Source |
| CVE-2025-39987 | suse_vex | SUSE CVE CVE-2025-39987 | known affected: 396 known not affected: 387 recommended: 464 | 2026-10-10T01:56:03+00:00 | Vulnerability · Source |
| CVE-2025-39989 | suse_vex | SUSE CVE CVE-2025-39989 | known affected: 143 known not affected: 256 recommended: 78 | 2026-10-10T01:56:01+00:00 | Vulnerability · Source |
| CVE-2025-39992 | suse_vex | SUSE CVE CVE-2025-39992 | known affected: 468 known not affected: 475 recommended: 160 | 2026-10-10T01:55:59+00:00 | Vulnerability · Source |
| CVE-2025-39993 | suse_vex | SUSE CVE CVE-2025-39993 | known affected: 396 known not affected: 387 recommended: 503 | 2026-10-10T01:55:57+00:00 | Vulnerability · Source |
| CVE-2025-39994 | suse_vex | SUSE CVE CVE-2025-39994 | known affected: 396 known not affected: 327 recommended: 490 | 2026-10-10T01:55:55+00:00 | Vulnerability · Source |
| CVE-2025-39997 | suse_vex | SUSE CVE CVE-2025-39997 | known affected: 401 known not affected: 330 recommended: 507 | 2026-10-10T01:55:53+00:00 | Vulnerability · Source |
| CVE-2025-39998 | suse_vex | SUSE CVE CVE-2025-39998 | known affected: 781 recommended: 354 | 2026-10-10T01:55:51+00:00 | Vulnerability · Source |
| CVE-2025-40000 | suse_vex | SUSE CVE CVE-2025-40000 | known affected: 468 known not affected: 323 recommended: 470 | 2026-10-10T01:55:49+00:00 | Vulnerability · Source |
| CVE-2025-40002 | suse_vex | SUSE CVE CVE-2025-40002 | known not affected: 523 recommended: 33 | 2026-10-10T01:55:47+00:00 | Vulnerability · Source |
| CVE-2025-40003 | suse_vex | SUSE CVE CVE-2025-40003 | known affected: 298 known not affected: 187 recommended: 160 | 2026-10-10T01:55:45+00:00 | Vulnerability · Source |
| CVE-2025-40005 | suse_vex | SUSE CVE CVE-2025-40005 | known affected: 697 known not affected: 94 recommended: 464 | 2026-10-10T01:55:43+00:00 | Vulnerability · Source |
| CVE-2025-40010 | suse_vex | SUSE CVE CVE-2025-40010 | known affected: 522 known not affected: 265 recommended: 310 | 2026-10-10T01:55:40+00:00 | Vulnerability · Source |
| CVE-2025-40011 | suse_vex | SUSE CVE CVE-2025-40011 | known affected: 645 known not affected: 135 recommended: 464 | 2026-10-10T01:55:38+00:00 | Vulnerability · Source |
| CVE-2025-40014 | suse_vex | SUSE CVE CVE-2025-40014 | known affected: 394 known not affected: 414 recommended: 396 | 2026-10-10T01:55:35+00:00 | Vulnerability · Source |
| CVE-2025-40019 | suse_vex | SUSE CVE CVE-2025-40019 | known affected: 399 known not affected: 225 recommended: 670 | 2026-10-10T01:55:33+00:00 | Vulnerability · Source |
| CVE-2025-40020 | suse_vex | SUSE CVE CVE-2025-40020 | known affected: 396 known not affected: 396 recommended: 464 | 2026-10-10T01:55:30+00:00 | Vulnerability · Source |
| CVE-2025-40022 | suse_vex | SUSE CVE CVE-2025-40022 | known affected: 71 known not affected: 411 recommended: 306 | 2026-10-10T01:55:27+00:00 | Vulnerability · Source |
| CVE-2025-40024 | suse_vex | SUSE CVE CVE-2025-40024 | known affected: 443 known not affected: 390 recommended: 366 | 2026-10-10T01:55:25+00:00 | Vulnerability · Source |
| CVE-2025-40026 | suse_vex | SUSE CVE CVE-2025-40026 | known affected: 336 recommended: 67 | 2026-10-10T01:55:23+00:00 | Vulnerability · Source |
| CVE-2025-40027 | suse_vex | SUSE CVE CVE-2025-40027 | known affected: 720 known not affected: 6 recommended: 507 | 2026-10-10T01:55:21+00:00 | Vulnerability · Source |
| CVE-2025-40029 | suse_vex | SUSE CVE CVE-2025-40029 | known affected: 557 known not affected: 235 recommended: 470 | 2026-10-10T01:55:19+00:00 | Vulnerability · Source |
| CVE-2025-40030 | suse_vex | SUSE CVE CVE-2025-40030 | known affected: 720 known not affected: 6 recommended: 525 | 2026-10-10T01:55:17+00:00 | Vulnerability · Source |
| CVE-2025-40031 | suse_vex | SUSE CVE CVE-2025-40031 | known affected: 2 known not affected: 540 recommended: 160 | 2026-10-10T01:55:15+00:00 | Vulnerability · Source |
| CVE-2025-40034 | suse_vex | SUSE CVE CVE-2025-40034 | known not affected: 514 recommended: 6 | 2026-10-10T01:55:13+00:00 | Vulnerability · Source |
| CVE-2025-40035 | suse_vex | SUSE CVE CVE-2025-40035 | known affected: 726 recommended: 507 | 2026-10-10T01:55:11+00:00 | Vulnerability · Source |
| CVE-2025-40042 | suse_vex | SUSE CVE CVE-2025-40042 | known affected: 773 recommended: 390 | 2026-10-10T01:55:09+00:00 | Vulnerability · Source |
| CVE-2025-40043 | suse_vex | SUSE CVE CVE-2025-40043 | known affected: 714 known not affected: 66 recommended: 470 | 2026-10-10T01:55:07+00:00 | Vulnerability · Source |
| CVE-2025-40049 | suse_vex | SUSE CVE CVE-2025-40049 | known affected: 726 recommended: 507 | 2026-10-10T01:55:05+00:00 | Vulnerability · Source |