VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-38422 | suse_vex | SUSE CVE CVE-2025-38422 | known affected: 212 known not affected: 251 | 2026-10-16T12:57:03+00:00 | Vulnerability · Source |
| CVE-2025-38424 | suse_vex | SUSE CVE CVE-2025-38424 | known affected: 739 known not affected: 54 recommended: 540 | 2026-10-16T12:57:01+00:00 | Vulnerability · Source |
| CVE-2025-38433 | suse_vex | SUSE CVE CVE-2025-38433 | known affected: 0 known not affected: 521 | 2026-10-16T12:56:58+00:00 | Vulnerability · Source |
| CVE-2025-38438 | suse_vex | SUSE CVE CVE-2025-38438 | known affected: 214 known not affected: 309 recommended: 268 | 2026-10-16T12:56:56+00:00 | Vulnerability · Source |
| CVE-2025-38454 | suse_vex | SUSE CVE CVE-2025-38454 | known affected: 2 known not affected: 521 recommended: 185 | 2026-10-16T12:56:53+00:00 | Vulnerability · Source |
| CVE-2025-38460 | suse_vex | SUSE CVE CVE-2025-38460 | known affected: 583 recommended: 825 | 2026-10-16T12:56:50+00:00 | Vulnerability · Source |
| CVE-2025-38469 | suse_vex | SUSE CVE CVE-2025-38469 | known affected: 396 known not affected: 489 recommended: 341 | 2026-10-16T12:56:49+00:00 | Vulnerability · Source |
| CVE-2025-38475 | suse_vex | SUSE CVE CVE-2025-38475 | known affected: 423 known not affected: 502 recommended: 278 | 2026-10-16T12:56:46+00:00 | Vulnerability · Source |
| CVE-2025-38491 | suse_vex | SUSE CVE CVE-2025-38491 | known affected: 457 known not affected: 405 recommended: 503 | 2026-10-16T12:56:43+00:00 | Vulnerability · Source |
| CVE-2025-38508 | suse_vex | SUSE CVE CVE-2025-38508 | known affected: 7 known not affected: 552 recommended: 185 | 2026-10-16T12:56:39+00:00 | Vulnerability · Source |
| CVE-2025-38511 | suse_vex | SUSE CVE CVE-2025-38511 | known affected: 396 known not affected: 498 recommended: 302 | 2026-10-16T12:56:36+00:00 | Vulnerability · Source |
| CVE-2025-38515 | suse_vex | SUSE CVE CVE-2025-38515 | known affected: 645 known not affected: 155 recommended: 544 | 2026-10-16T12:56:33+00:00 | Vulnerability · Source |
| CVE-2025-38528 | suse_vex | SUSE CVE CVE-2025-38528 | known affected: 592 known not affected: 270 recommended: 503 | 2026-10-16T12:56:28+00:00 | Vulnerability · Source |
| CVE-2025-38531 | suse_vex | SUSE CVE CVE-2025-38531 | known affected: 670 known not affected: 192 recommended: 503 | 2026-10-16T12:56:25+00:00 | Vulnerability · Source |
| CVE-2025-38539 | suse_vex | SUSE CVE CVE-2025-38539 | known affected: 746 recommended: 582 | 2026-10-16T12:56:22+00:00 | Vulnerability · Source |
| CVE-2025-38541 | suse_vex | SUSE CVE CVE-2025-38541 | known affected: 396 known not affected: 450 recommended: 521 | 2026-10-16T12:56:21+00:00 | Vulnerability · Source |
| CVE-2025-38544 | suse_vex | SUSE CVE CVE-2025-38544 | known affected: 712 known not affected: 94 recommended: 503 | 2026-10-16T12:56:19+00:00 | Vulnerability · Source |
| CVE-2025-38546 | suse_vex | SUSE CVE CVE-2025-38546 | known affected: 595 known not affected: 6 recommended: 811 | 2026-10-16T12:56:16+00:00 | Vulnerability · Source |
| CVE-2025-38560 | suse_vex | SUSE CVE CVE-2025-38560 | known affected: 420 known not affected: 262 recommended: 709 | 2026-10-16T12:56:13+00:00 | Vulnerability · Source |
| CVE-2025-38564 | suse_vex | SUSE CVE CVE-2025-38564 | known affected: 2 known not affected: 529 recommended: 185 | 2026-10-16T12:56:11+00:00 | Vulnerability · Source |
| CVE-2025-38571 | suse_vex | SUSE CVE CVE-2025-38571 | known affected: 396 known not affected: 450 recommended: 589 | 2026-10-16T12:56:08+00:00 | Vulnerability · Source |
| CVE-2025-38574 | suse_vex | SUSE CVE CVE-2025-38574 | known affected: 746 recommended: 540 | 2026-10-16T12:56:06+00:00 | Vulnerability · Source |
| CVE-2025-38576 | suse_vex | SUSE CVE CVE-2025-38576 | known affected: 729 known not affected: 67 recommended: 503 | 2026-10-16T12:56:04+00:00 | Vulnerability · Source |
| CVE-2025-38582 | suse_vex | SUSE CVE CVE-2025-38582 | known affected: 396 known not affected: 462 recommended: 503 | 2026-10-16T12:56:01+00:00 | Vulnerability · Source |
| CVE-2025-38586 | suse_vex | SUSE CVE CVE-2025-38586 | known affected: 2 known not affected: 521 recommended: 185 | 2026-10-16T12:55:59+00:00 | Vulnerability · Source |
| CVE-2025-38587 | suse_vex | SUSE CVE CVE-2025-38587 | known affected: 396 known not affected: 462 recommended: 503 | 2026-10-16T12:55:57+00:00 | Vulnerability · Source |
| CVE-2025-38588 | suse_vex | SUSE CVE CVE-2025-38588 | known affected: 396 known not affected: 450 recommended: 547 | 2026-10-16T12:55:55+00:00 | Vulnerability · Source |
| CVE-2025-38592 | suse_vex | SUSE CVE CVE-2025-38592 | known affected: 0 known not affected: 521 recommended: 58 | 2026-10-16T12:55:53+00:00 | Vulnerability · Source |
| CVE-2025-38601 | suse_vex | SUSE CVE CVE-2025-38601 | known affected: 539 known not affected: 319 recommended: 503 | 2026-10-16T12:55:50+00:00 | Vulnerability · Source |
| CVE-2025-38617 | suse_vex | SUSE CVE CVE-2025-38617 | known affected: 346 known not affected: 485 recommended: 944 | 2026-10-16T12:55:44+00:00 | Vulnerability · Source |
| CVE-2025-38632 | suse_vex | SUSE CVE CVE-2025-38632 | known affected: 396 known not affected: 390 recommended: 540 | 2026-10-16T12:55:42+00:00 | Vulnerability · Source |
| CVE-2025-38639 | suse_vex | SUSE CVE CVE-2025-38639 | known affected: 735 known not affected: 11 recommended: 540 | 2026-10-16T12:55:40+00:00 | Vulnerability · Source |
| CVE-2025-38647 | suse_vex | SUSE CVE CVE-2025-38647 | known affected: 0 known not affected: 521 recommended: 58 | 2026-10-16T12:55:36+00:00 | Vulnerability · Source |
| CVE-2025-38657 | suse_vex | SUSE CVE CVE-2025-38657 | known affected: 0 known not affected: 521 recommended: 58 | 2026-10-16T12:55:34+00:00 | Vulnerability · Source |
| CVE-2025-38662 | suse_vex | SUSE CVE CVE-2025-38662 | known affected: 2 known not affected: 521 recommended: 185 | 2026-10-16T12:55:31+00:00 | Vulnerability · Source |
| CVE-2025-38679 | suse_vex | SUSE CVE CVE-2025-38679 | known affected: 422 known not affected: 192 recommended: 503 | 2026-10-16T12:55:27+00:00 | Vulnerability · Source |
| CVE-2025-38688 | suse_vex | SUSE CVE CVE-2025-38688 | known affected: 189 known not affected: 317 | 2026-10-16T12:55:25+00:00 | Vulnerability · Source |
| CVE-2025-38709 | suse_vex | SUSE CVE CVE-2025-38709 | known affected: 694 known not affected: 97 recommended: 503 | 2026-10-16T12:55:22+00:00 | Vulnerability · Source |
| CVE-2025-38710 | suse_vex | SUSE CVE CVE-2025-38710 | known affected: 399 known not affected: 487 recommended: 278 | 2026-10-16T12:55:21+00:00 | Vulnerability · Source |
| CVE-2025-38722 | suse_vex | SUSE CVE CVE-2025-38722 | known affected: 463 known not affected: 317 recommended: 503 | 2026-10-16T12:55:18+00:00 | Vulnerability · Source |
| CVE-2025-38733 | suse_vex | SUSE CVE CVE-2025-38733 | known affected: 74 known not affected: 472 recommended: 185 | 2026-10-16T12:55:15+00:00 | Vulnerability · Source |
| CVE-2025-39673 | suse_vex | SUSE CVE CVE-2025-39673 | known affected: 529 known not affected: 262 recommended: 495 | 2026-10-16T12:55:12+00:00 | Vulnerability · Source |
| CVE-2025-39677 | suse_vex | SUSE CVE CVE-2025-39677 | known affected: 725 known not affected: 6 recommended: 532 | 2026-10-16T12:55:10+00:00 | Vulnerability · Source |
| CVE-2025-39678 | suse_vex | SUSE CVE CVE-2025-39678 | known affected: 468 known not affected: 323 recommended: 503 | 2026-10-16T12:55:08+00:00 | Vulnerability · Source |
| CVE-2025-39711 | suse_vex | SUSE CVE CVE-2025-39711 | known affected: 463 known not affected: 397 recommended: 278 | 2026-10-16T12:55:02+00:00 | Vulnerability · Source |
| CVE-2025-39713 | suse_vex | SUSE CVE CVE-2025-39713 | known affected: 686 known not affected: 39 recommended: 495 | 2026-10-16T12:55:00+00:00 | Vulnerability · Source |
| CVE-2025-39718 | suse_vex | SUSE CVE CVE-2025-39718 | known affected: 463 known not affected: 317 recommended: 652 | 2026-10-16T12:54:58+00:00 | Vulnerability · Source |
| CVE-2025-39726 | suse_vex | SUSE CVE CVE-2025-39726 | known affected: 479 known not affected: 68 recommended: 724 | 2026-10-16T12:54:56+00:00 | Vulnerability · Source |
| CVE-2025-39732 | suse_vex | SUSE CVE CVE-2025-39732 | known affected: 524 known not affected: 259 recommended: 495 | 2026-10-16T12:54:54+00:00 | Vulnerability · Source |
| CVE-2025-39776 | suse_vex | SUSE CVE CVE-2025-39776 | known affected: 239 known not affected: 323 | 2026-10-16T12:54:47+00:00 | Vulnerability · Source |