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-38348 | suse_vex | SUSE CVE CVE-2025-38348 | first fixed: 2 known affected: 639 known not affected: 46 recommended: 481 | 2026-07-23T01:40:35+00:00 | Vulnerability · Source |
| CVE-2025-38357 | suse_vex | SUSE CVE CVE-2025-38357 | known not affected: 345 | 2026-07-23T01:40:32+00:00 | Vulnerability · Source |
| CVE-2025-38360 | suse_vex | SUSE CVE CVE-2025-38360 | first fixed: 2 known affected: 418 known not affected: 318 recommended: 481 | 2026-07-23T01:40:31+00:00 | Vulnerability · Source |
| CVE-2025-38363 | suse_vex | SUSE CVE CVE-2025-38363 | first fixed: 2 known affected: 558 known not affected: 157 recommended: 508 | 2026-07-23T01:40:30+00:00 | Vulnerability · Source |
| CVE-2025-38371 | suse_vex | SUSE CVE CVE-2025-38371 | first fixed: 2 known affected: 605 known not affected: 110 recommended: 481 | 2026-07-23T01:40:28+00:00 | Vulnerability · Source |
| CVE-2025-38372 | suse_vex | SUSE CVE CVE-2025-38372 | first fixed: 2 known affected: 70 known not affected: 344 recommended: 154 | 2026-07-23T01:40:27+00:00 | Vulnerability · Source |
| CVE-2025-38384 | suse_vex | SUSE CVE CVE-2025-38384 | first fixed: 2 known affected: 572 known not affected: 143 recommended: 508 | 2026-07-23T01:40:26+00:00 | Vulnerability · Source |
| CVE-2025-38385 | suse_vex | SUSE CVE CVE-2025-38385 | first fixed: 2 known affected: 394 known not affected: 321 recommended: 508 | 2026-07-23T01:40:24+00:00 | Vulnerability · Source |
| CVE-2025-38394 | suse_vex | SUSE CVE CVE-2025-38394 | known not affected: 345 | 2026-07-23T01:40:23+00:00 | Vulnerability · Source |
| CVE-2025-38411 | suse_vex | SUSE CVE CVE-2025-38411 | known not affected: 345 | 2026-07-23T01:40:21+00:00 | Vulnerability · Source |
| CVE-2025-38414 | suse_vex | SUSE CVE CVE-2025-38414 | first fixed: 2 known affected: 410 known not affected: 305 recommended: 508 | 2026-07-23T01:40:18+00:00 | Vulnerability · Source |
| CVE-2025-38428 | suse_vex | SUSE CVE CVE-2025-38428 | first fixed: 2 known affected: 633 known not affected: 94 recommended: 481 | 2026-07-23T01:40:15+00:00 | Vulnerability · Source |
| CVE-2025-38431 | suse_vex | SUSE CVE CVE-2025-38431 | known not affected: 345 | 2026-07-23T01:40:14+00:00 | Vulnerability · Source |
| CVE-2025-38433 | suse_vex | SUSE CVE CVE-2025-38433 | known not affected: 345 | 2026-07-23T01:40:12+00:00 | Vulnerability · Source |
| CVE-2025-38435 | suse_vex | SUSE CVE CVE-2025-38435 | known not affected: 345 | 2026-07-23T01:40:11+00:00 | Vulnerability · Source |
| CVE-2025-38440 | suse_vex | SUSE CVE CVE-2025-38440 | first fixed: 2 known affected: 394 known not affected: 409 recommended: 265 | 2026-07-23T01:40:08+00:00 | Vulnerability · Source |
| CVE-2025-38454 | suse_vex | SUSE CVE CVE-2025-38454 | first fixed: 2 known not affected: 414 recommended: 154 | 2026-07-23T01:40:05+00:00 | Vulnerability · Source |
| CVE-2025-38467 | suse_vex | SUSE CVE CVE-2025-38467 | first fixed: 2 known affected: 605 known not affected: 110 recommended: 508 | 2026-07-23T01:40:01+00:00 | Vulnerability · Source |
| CVE-2025-38481 | suse_vex | SUSE CVE CVE-2025-38481 | first fixed: 2 known affected: 667 known not affected: 46 recommended: 481 | 2026-07-23T01:39:56+00:00 | Vulnerability · Source |
| CVE-2025-38482 | suse_vex | SUSE CVE CVE-2025-38482 | first fixed: 2 known affected: 633 known not affected: 52 recommended: 508 | 2026-07-23T01:39:54+00:00 | Vulnerability · Source |
| CVE-2025-38486 | suse_vex | SUSE CVE CVE-2025-38486 | known not affected: 414 | 2026-07-23T01:39:53+00:00 | Vulnerability · Source |
| CVE-2025-38490 | suse_vex | SUSE CVE CVE-2025-38490 | first fixed: 2 known affected: 394 known not affected: 309 recommended: 508 | 2026-07-23T01:39:51+00:00 | Vulnerability · Source |
| CVE-2025-38495 | suse_vex | SUSE CVE CVE-2025-38495 | first fixed: 2 known affected: 441 known not affected: 66 recommended: 910 | 2026-07-23T01:39:49+00:00 | Vulnerability · Source |
| CVE-2025-38502 | suse_vex | SUSE CVE CVE-2025-38502 | known affected: 142 known not affected: 64 | 2026-07-23T01:39:46+00:00 | Vulnerability · Source |
| CVE-2025-38505 | suse_vex | SUSE CVE CVE-2025-38505 | first fixed: 2 known not affected: 414 recommended: 172 | 2026-07-23T01:39:44+00:00 | Vulnerability · Source |
| CVE-2025-38510 | suse_vex | SUSE CVE CVE-2025-38510 | first fixed: 2 known affected: 394 known not affected: 347 recommended: 526 | 2026-07-23T01:39:43+00:00 | Vulnerability · Source |
| CVE-2025-38512 | suse_vex | SUSE CVE CVE-2025-38512 | first fixed: 2 known affected: 623 known not affected: 91 recommended: 556 | 2026-07-23T01:39:41+00:00 | Vulnerability · Source |
| CVE-2025-38513 | suse_vex | SUSE CVE CVE-2025-38513 | first fixed: 2 known affected: 649 known not affected: 73 recommended: 529 | 2026-07-23T01:39:40+00:00 | Vulnerability · Source |
| CVE-2025-38514 | suse_vex | SUSE CVE CVE-2025-38514 | first fixed: 2 known affected: 455 known not affected: 55 recommended: 508 | 2026-07-23T01:39:39+00:00 | Vulnerability · Source |
| CVE-2025-38531 | suse_vex | SUSE CVE CVE-2025-38531 | first fixed: 2 known affected: 646 known not affected: 102 recommended: 508 | 2026-07-23T01:39:37+00:00 | Vulnerability · Source |
| CVE-2025-38532 | suse_vex | SUSE CVE CVE-2025-38532 | known not affected: 358 | 2026-07-23T01:39:36+00:00 | Vulnerability · Source |
| CVE-2025-38542 | suse_vex | SUSE CVE CVE-2025-38542 | known affected: 6 known not affected: 387 | 2026-07-23T01:39:34+00:00 | Vulnerability · Source |
| CVE-2025-38545 | suse_vex | SUSE CVE CVE-2025-38545 | first fixed: 2 known not affected: 446 recommended: 127 | 2026-07-23T01:39:32+00:00 | Vulnerability · Source |
| CVE-2025-38550 | suse_vex | SUSE CVE CVE-2025-38550 | first fixed: 2 known affected: 521 known not affected: 208 recommended: 569 | 2026-07-23T01:39:31+00:00 | Vulnerability · Source |
| CVE-2025-38553 | suse_vex | SUSE CVE CVE-2025-38553 | first fixed: 2 known affected: 438 known not affected: 73 recommended: 796 | 2026-07-23T01:39:29+00:00 | Vulnerability · Source |
| 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 |