VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
306200 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-38372 | suse_vex | SUSE CVE CVE-2025-38372 | known affected: 78 known not affected: 448 recommended: 154 | 2026-10-10T02:05:10+00:00 | Vulnerability · Source |
| CVE-2025-38373 | suse_vex | SUSE CVE CVE-2025-38373 | known affected: 472 known not affected: 366 recommended: 472 | 2026-10-10T02:05:08+00:00 | Vulnerability · Source |
| CVE-2025-38375 | suse_vex | SUSE CVE CVE-2025-38375 | known affected: 545 known not affected: 64 recommended: 746 | 2026-10-10T02:05:06+00:00 | Vulnerability · Source |
| CVE-2025-38376 | suse_vex | SUSE CVE CVE-2025-38376 | known affected: 396 known not affected: 442 recommended: 472 | 2026-10-10T02:05:04+00:00 | Vulnerability · Source |
| CVE-2025-38379 | suse_vex | SUSE CVE CVE-2025-38379 | known affected: 396 known not affected: 441 recommended: 384 | 2026-10-10T02:05:02+00:00 | Vulnerability · Source |
| CVE-2025-38383 | suse_vex | SUSE CVE CVE-2025-38383 | known affected: 564 recommended: 196 | 2026-10-10T02:05:01+00:00 | Vulnerability · Source |
| CVE-2025-38391 | suse_vex | SUSE CVE CVE-2025-38391 | known affected: 645 known not affected: 139 recommended: 495 | 2026-10-10T02:04:58+00:00 | Vulnerability · Source |
| CVE-2025-38399 | suse_vex | SUSE CVE CVE-2025-38399 | known affected: 668 known not affected: 181 recommended: 472 | 2026-10-10T02:04:56+00:00 | Vulnerability · Source |
| CVE-2025-38400 | suse_vex | SUSE CVE CVE-2025-38400 | known affected: 463 known not affected: 375 recommended: 514 | 2026-10-10T02:04:54+00:00 | Vulnerability · Source |
| CVE-2025-38401 | suse_vex | SUSE CVE CVE-2025-38401 | known affected: 406 known not affected: 444 recommended: 472 | 2026-10-10T02:04:52+00:00 | Vulnerability · Source |
| CVE-2025-38403 | suse_vex | SUSE CVE CVE-2025-38403 | known affected: 776 known not affected: 6 recommended: 612 | 2026-10-10T02:04:50+00:00 | Vulnerability · Source |
| CVE-2025-38405 | suse_vex | SUSE CVE CVE-2025-38405 | known affected: 2 known not affected: 524 recommended: 154 | 2026-10-10T02:04:49+00:00 | Vulnerability · Source |
| CVE-2025-38406 | suse_vex | SUSE CVE CVE-2025-38406 | known affected: 735 known not affected: 54 recommended: 472 | 2026-10-10T02:04:46+00:00 | Vulnerability · Source |
| CVE-2025-38408 | suse_vex | SUSE CVE CVE-2025-38408 | known affected: 539 known not affected: 262 recommended: 472 | 2026-10-10T02:04:44+00:00 | Vulnerability · Source |
| CVE-2025-38409 | suse_vex | SUSE CVE CVE-2025-38409 | known affected: 660 known not affected: 120 recommended: 472 | 2026-10-10T02:04:42+00:00 | Vulnerability · Source |
| CVE-2025-38410 | suse_vex | SUSE CVE CVE-2025-38410 | known affected: 729 known not affected: 109 recommended: 472 | 2026-10-10T02:04:40+00:00 | Vulnerability · Source |
| CVE-2025-38414 | suse_vex | SUSE CVE CVE-2025-38414 | known affected: 412 known not affected: 426 recommended: 472 | 2026-10-10T02:04:38+00:00 | Vulnerability · Source |
| CVE-2025-38416 | suse_vex | SUSE CVE CVE-2025-38416 | known affected: 729 known not affected: 49 recommended: 472 | 2026-10-10T02:04:36+00:00 | Vulnerability · Source |
| CVE-2025-38417 | suse_vex | SUSE CVE CVE-2025-38417 | known affected: 396 known not affected: 489 recommended: 333 | 2026-10-10T02:04:35+00:00 | Vulnerability · Source |
| CVE-2025-38420 | suse_vex | SUSE CVE CVE-2025-38420 | known affected: 739 known not affected: 43 recommended: 495 | 2026-10-10T02:04:33+00:00 | Vulnerability · Source |
| CVE-2025-38424 | suse_vex | SUSE CVE CVE-2025-38424 | known affected: 739 known not affected: 54 recommended: 509 | 2026-10-10T02:04:31+00:00 | Vulnerability · Source |
| CVE-2025-38425 | suse_vex | SUSE CVE CVE-2025-38425 | known affected: 539 known not affected: 299 recommended: 515 | 2026-10-10T02:04:29+00:00 | Vulnerability · Source |
| CVE-2025-38426 | suse_vex | SUSE CVE CVE-2025-38426 | known affected: 636 known not affected: 213 recommended: 472 | 2026-10-10T02:04:27+00:00 | Vulnerability · Source |
| CVE-2025-38428 | suse_vex | SUSE CVE CVE-2025-38428 | known affected: 729 known not affected: 121 recommended: 472 | 2026-10-10T02:04:25+00:00 | Vulnerability · Source |
| CVE-2025-38443 | suse_vex | SUSE CVE CVE-2025-38443 | known affected: 539 known not affected: 299 recommended: 472 | 2026-10-10T02:04:22+00:00 | Vulnerability · Source |
| CVE-2025-38445 | suse_vex | SUSE CVE CVE-2025-38445 | known affected: 678 known not affected: 187 recommended: 472 | 2026-10-10T02:04:19+00:00 | Vulnerability · Source |
| CVE-2025-38449 | suse_vex | SUSE CVE CVE-2025-38449 | known affected: 705 known not affected: 100 recommended: 601 | 2026-10-10T02:04:17+00:00 | Vulnerability · Source |
| CVE-2025-38451 | suse_vex | SUSE CVE CVE-2025-38451 | known affected: 7 known not affected: 557 recommended: 154 | 2026-10-10T02:04:15+00:00 | Vulnerability · Source |
| CVE-2025-38453 | suse_vex | SUSE CVE CVE-2025-38453 | known affected: 428 known not affected: 505 recommended: 295 | 2026-10-10T02:04:13+00:00 | Vulnerability · Source |
| CVE-2025-38455 | suse_vex | SUSE CVE CVE-2025-38455 | known affected: 582 known not affected: 256 recommended: 472 | 2026-10-10T02:04:11+00:00 | Vulnerability · Source |
| CVE-2025-38457 | suse_vex | SUSE CVE CVE-2025-38457 | known affected: 793 recommended: 509 | 2026-10-10T02:04:09+00:00 | Vulnerability · Source |
| CVE-2025-38459 | suse_vex | SUSE CVE CVE-2025-38459 | known affected: 460 known not affected: 405 recommended: 546 | 2026-10-10T02:04:07+00:00 | Vulnerability · Source |
| CVE-2025-38460 | suse_vex | SUSE CVE CVE-2025-38460 | known affected: 584 recommended: 794 | 2026-10-10T02:04:05+00:00 | Vulnerability · Source |
| CVE-2025-38463 | suse_vex | SUSE CVE CVE-2025-38463 | known affected: 444 known not affected: 405 recommended: 472 | 2026-10-10T02:04:03+00:00 | Vulnerability · Source |
| CVE-2025-38465 | suse_vex | SUSE CVE CVE-2025-38465 | known affected: 746 recommended: 511 | 2026-10-10T02:04:01+00:00 | Vulnerability · Source |
| CVE-2025-38466 | suse_vex | SUSE CVE CVE-2025-38466 | known affected: 539 known not affected: 265 recommended: 472 | 2026-10-10T02:03:58+00:00 | Vulnerability · Source |
| CVE-2025-38469 | suse_vex | SUSE CVE CVE-2025-38469 | known affected: 396 known not affected: 492 recommended: 283 | 2026-10-10T02:03:56+00:00 | Vulnerability · Source |
| CVE-2025-38470 | suse_vex | SUSE CVE CVE-2025-38470 | known affected: 702 recommended: 623 | 2026-10-10T02:03:53+00:00 | Vulnerability · Source |
| CVE-2025-38471 | suse_vex | SUSE CVE CVE-2025-38471 | known affected: 437 known not affected: 407 recommended: 528 | 2026-10-10T02:03:51+00:00 | Vulnerability · Source |
| CVE-2025-38472 | suse_vex | SUSE CVE CVE-2025-38472 | known affected: 444 known not affected: 405 recommended: 558 | 2026-10-10T02:03:49+00:00 | Vulnerability · Source |
| CVE-2025-38473 | suse_vex | SUSE CVE CVE-2025-38473 | known affected: 739 known not affected: 54 recommended: 509 | 2026-10-10T02:03:47+00:00 | Vulnerability · Source |
| CVE-2025-38474 | suse_vex | SUSE CVE CVE-2025-38474 | known affected: 745 known not affected: 48 recommended: 509 | 2026-10-10T02:03:45+00:00 | Vulnerability · Source |
| CVE-2025-38480 | suse_vex | SUSE CVE CVE-2025-38480 | known affected: 735 known not affected: 43 recommended: 472 | 2026-10-10T02:03:43+00:00 | Vulnerability · Source |
| CVE-2025-38481 | suse_vex | SUSE CVE CVE-2025-38481 | known affected: 793 known not affected: 43 recommended: 472 | 2026-10-10T02:03:40+00:00 | Vulnerability · Source |
| CVE-2025-38482 | suse_vex | SUSE CVE CVE-2025-38482 | known affected: 729 known not affected: 49 recommended: 472 | 2026-10-10T02:03:37+00:00 | Vulnerability · Source |
| CVE-2025-38483 | suse_vex | SUSE CVE CVE-2025-38483 | known affected: 729 known not affected: 49 recommended: 472 | 2026-10-10T02:03:35+00:00 | Vulnerability · Source |
| CVE-2025-38484 | suse_vex | SUSE CVE CVE-2025-38484 | known affected: 2 known not affected: 524 recommended: 154 | 2026-10-10T02:03:33+00:00 | Vulnerability · Source |
| CVE-2025-38489 | suse_vex | SUSE CVE CVE-2025-38489 | known affected: 396 known not affected: 442 recommended: 472 | 2026-10-10T02:03:31+00:00 | Vulnerability · Source |
| CVE-2025-38490 | suse_vex | SUSE CVE CVE-2025-38490 | known affected: 396 known not affected: 429 recommended: 472 | 2026-10-10T02:03:29+00:00 | Vulnerability · Source |
| CVE-2025-38491 | suse_vex | SUSE CVE CVE-2025-38491 | known affected: 460 known not affected: 405 recommended: 472 | 2026-10-10T02:03:27+00:00 | Vulnerability · Source |