VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292442 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-38559 | suse_vex | SUSE CVE CVE-2025-38559 | first fixed: 2 known affected: 5 known not affected: 448 recommended: 127 | 2026-07-23T01:39:27+00:00 | Vulnerability · Source |
| CVE-2025-38567 | suse_vex | SUSE CVE CVE-2025-38567 | known not affected: 345 | 2026-07-23T01:39:25+00:00 | Vulnerability · Source |
| CVE-2025-38580 | suse_vex | SUSE CVE CVE-2025-38580 | known not affected: 345 | 2026-07-23T01:39:22+00:00 | Vulnerability · Source |
| CVE-2025-38582 | suse_vex | SUSE CVE CVE-2025-38582 | first fixed: 2 known affected: 394 known not affected: 347 recommended: 508 | 2026-07-23T01:39:20+00:00 | Vulnerability · Source |
| CVE-2025-38599 | suse_vex | SUSE CVE CVE-2025-38599 | known not affected: 345 | 2026-07-23T01:39:17+00:00 | Vulnerability · Source |
| CVE-2025-38600 | suse_vex | SUSE CVE CVE-2025-38600 | known not affected: 345 | 2026-07-23T01:39:16+00:00 | Vulnerability · Source |
| CVE-2025-38603 | suse_vex | SUSE CVE CVE-2025-38603 | known not affected: 345 | 2026-07-23T01:39:14+00:00 | Vulnerability · Source |
| CVE-2025-38605 | suse_vex | SUSE CVE CVE-2025-38605 | first fixed: 2 known affected: 394 known not affected: 278 recommended: 508 | 2026-07-23T01:39:13+00:00 | Vulnerability · Source |
| CVE-2025-38610 | suse_vex | SUSE CVE CVE-2025-38610 | first fixed: 2 known affected: 394 known not affected: 335 recommended: 508 | 2026-07-23T01:39:11+00:00 | Vulnerability · Source |
| CVE-2025-38614 | suse_vex | SUSE CVE CVE-2025-38614 | first fixed: 2 known affected: 645 recommended: 524 | 2026-07-23T01:39:09+00:00 | Vulnerability · Source |
| CVE-2025-38616 | suse_vex | SUSE CVE CVE-2025-38616 | first fixed: 2 known affected: 399 known not affected: 281 recommended: 571 | 2026-07-23T01:39:07+00:00 | Vulnerability · Source |
| CVE-2025-38633 | suse_vex | SUSE CVE CVE-2025-38633 | known not affected: 345 | 2026-07-23T01:39:00+00:00 | Vulnerability · Source |
| CVE-2025-38636 | suse_vex | SUSE CVE CVE-2025-38636 | known not affected: 206 | 2026-07-23T01:38:58+00:00 | Vulnerability · Source |
| CVE-2025-38642 | suse_vex | SUSE CVE CVE-2025-38642 | known not affected: 345 | 2026-07-23T01:38:56+00:00 | Vulnerability · Source |
| CVE-2025-38646 | suse_vex | SUSE CVE CVE-2025-38646 | first fixed: 2 known affected: 394 known not affected: 335 recommended: 481 | 2026-07-23T01:38:54+00:00 | Vulnerability · Source |
| CVE-2025-38656 | suse_vex | SUSE CVE CVE-2025-38656 | first fixed: 2 known affected: 394 known not affected: 305 recommended: 538 | 2026-07-23T01:38:52+00:00 | Vulnerability · Source |
| CVE-2025-38662 | suse_vex | SUSE CVE CVE-2025-38662 | first fixed: 2 known not affected: 414 recommended: 127 | 2026-07-23T01:38:50+00:00 | Vulnerability · Source |
| CVE-2025-38663 | suse_vex | SUSE CVE CVE-2025-38663 | known affected: 697 known not affected: 68 recommended: 354 | 2026-07-23T01:38:48+00:00 | Vulnerability · Source |
| CVE-2025-38665 | suse_vex | SUSE CVE CVE-2025-38665 | first fixed: 2 known affected: 645 known not affected: 73 recommended: 531 | 2026-07-23T01:38:47+00:00 | Vulnerability · Source |
| CVE-2025-38670 | suse_vex | SUSE CVE CVE-2025-38670 | first fixed: 2 known affected: 521 known not affected: 208 recommended: 508 | 2026-07-23T01:38:45+00:00 | Vulnerability · Source |
| CVE-2025-38672 | suse_vex | SUSE CVE CVE-2025-38672 | known not affected: 345 | 2026-07-23T01:38:44+00:00 | Vulnerability · Source |
| CVE-2025-38673 | suse_vex | SUSE CVE CVE-2025-38673 | known not affected: 345 | 2026-07-23T01:38:43+00:00 | Vulnerability · Source |
| CVE-2025-38681 | suse_vex | SUSE CVE CVE-2025-38681 | first fixed: 2 known affected: 506 known not affected: 169 recommended: 500 | 2026-07-23T01:38:41+00:00 | Vulnerability · Source |
| CVE-2025-38687 | suse_vex | SUSE CVE CVE-2025-38687 | first fixed: 2 known affected: 648 known not affected: 6 recommended: 500 | 2026-07-23T01:38:38+00:00 | Vulnerability · Source |
| CVE-2025-38688 | suse_vex | SUSE CVE CVE-2025-38688 | known affected: 186 known not affected: 144 | 2026-07-23T01:38:37+00:00 | Vulnerability · Source |
| CVE-2025-38692 | suse_vex | SUSE CVE CVE-2025-38692 | first fixed: 2 known affected: 557 known not affected: 118 recommended: 473 | 2026-07-23T01:38:36+00:00 | Vulnerability · Source |
| CVE-2025-38693 | suse_vex | SUSE CVE CVE-2025-38693 | first fixed: 2 known affected: 590 known not affected: 9 recommended: 500 | 2026-07-23T01:38:34+00:00 | Vulnerability · Source |
| CVE-2025-38696 | suse_vex | SUSE CVE CVE-2025-38696 | known not affected: 345 | 2026-07-23T01:38:33+00:00 | Vulnerability · Source |
| CVE-2025-38698 | suse_vex | SUSE CVE CVE-2025-38698 | known affected: 394 known not affected: 269 recommended: 346 | 2026-07-23T01:38:32+00:00 | Vulnerability · Source |
| CVE-2025-38700 | suse_vex | SUSE CVE CVE-2025-38700 | first fixed: 2 known affected: 635 recommended: 530 | 2026-07-23T01:38:31+00:00 | Vulnerability · Source |
| CVE-2025-38708 | suse_vex | SUSE CVE CVE-2025-38708 | known not affected: 414 | 2026-07-23T01:38:29+00:00 | Vulnerability · Source |
| CVE-2025-38710 | suse_vex | SUSE CVE CVE-2025-38710 | first fixed: 2 known affected: 397 known not affected: 374 recommended: 265 | 2026-07-23T01:38:27+00:00 | Vulnerability · Source |
| CVE-2025-38716 | suse_vex | SUSE CVE CVE-2025-38716 | known affected: 6 known not affected: 339 | 2026-07-23T01:38:25+00:00 | Vulnerability · Source |
| CVE-2025-38719 | suse_vex | SUSE CVE CVE-2025-38719 | known affected: 47 known not affected: 283 | 2026-07-23T01:38:24+00:00 | Vulnerability · Source |
| CVE-2025-38720 | suse_vex | SUSE CVE CVE-2025-38720 | known not affected: 330 | 2026-07-23T01:38:22+00:00 | Vulnerability · Source |
| CVE-2025-38722 | suse_vex | SUSE CVE CVE-2025-38722 | first fixed: 2 known affected: 451 known not affected: 203 recommended: 481 | 2026-07-23T01:38:20+00:00 | Vulnerability · Source |
| CVE-2025-38732 | suse_vex | SUSE CVE CVE-2025-38732 | first fixed: 2 known affected: 552 known not affected: 111 recommended: 508 | 2026-07-23T01:38:15+00:00 | Vulnerability · Source |
| CVE-2025-38733 | suse_vex | SUSE CVE CVE-2025-38733 | first fixed: 2 known affected: 62 known not affected: 376 recommended: 154 | 2026-07-23T01:38:13+00:00 | Vulnerability · Source |
| CVE-2025-38735 | suse_vex | SUSE CVE CVE-2025-38735 | first fixed: 2 known affected: 585 known not affected: 52 recommended: 523 | 2026-07-23T01:38:11+00:00 | Vulnerability · Source |
| CVE-2025-39673 | suse_vex | SUSE CVE CVE-2025-39673 | first fixed: 2 known affected: 511 known not affected: 154 recommended: 500 | 2026-07-23T01:38:09+00:00 | Vulnerability · Source |
| CVE-2025-39675 | suse_vex | SUSE CVE CVE-2025-39675 | first fixed: 2 known affected: 543 known not affected: 114 recommended: 473 | 2026-07-23T01:38:07+00:00 | Vulnerability · Source |
| CVE-2025-39703 | suse_vex | SUSE CVE CVE-2025-39703 | first fixed: 2 known affected: 349 known not affected: 154 recommended: 714 | 2026-07-23T01:38:01+00:00 | Vulnerability · Source |
| CVE-2025-39704 | suse_vex | SUSE CVE CVE-2025-39704 | known affected: 79 known not affected: 376 | 2026-07-23T01:38:00+00:00 | Vulnerability · Source |
| CVE-2025-39708 | suse_vex | SUSE CVE CVE-2025-39708 | known not affected: 345 | 2026-07-23T01:37:59+00:00 | Vulnerability · Source |
| CVE-2025-39711 | suse_vex | SUSE CVE CVE-2025-39711 | first fixed: 2 known affected: 451 known not affected: 294 recommended: 238 | 2026-07-23T01:37:57+00:00 | Vulnerability · Source |
| CVE-2025-39714 | suse_vex | SUSE CVE CVE-2025-39714 | first fixed: 2 known affected: 618 known not affected: 9 recommended: 500 | 2026-07-23T01:37:56+00:00 | Vulnerability · Source |
| CVE-2025-39717 | suse_vex | SUSE CVE CVE-2025-39717 | known not affected: 345 | 2026-07-23T01:37:54+00:00 | Vulnerability · Source |
| CVE-2025-39721 | suse_vex | SUSE CVE CVE-2025-39721 | first fixed: 2 known affected: 506 known not affected: 151 recommended: 500 | 2026-07-23T01:37:51+00:00 | Vulnerability · Source |
| CVE-2025-39725 | suse_vex | SUSE CVE CVE-2025-39725 | known not affected: 345 | 2026-07-23T01:37:50+00:00 | Vulnerability · Source |
| CVE-2025-39729 | suse_vex | SUSE CVE CVE-2025-39729 | known not affected: 336 | 2026-07-23T01:37:48+00:00 | Vulnerability · Source |