VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104648 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-38066 | suse_vex | SUSE CVE CVE-2025-38066 | known affected: 339 recommended: 109 | 2026-10-17T00:59:07+00:00 | Vulnerability · Source |
| CVE-2025-38099 | suse_vex | SUSE CVE CVE-2025-38099 | known affected: 778 known not affected: 60 recommended: 503 | 2026-10-17T00:59:02+00:00 | Vulnerability · Source |
| CVE-2025-38123 | suse_vex | SUSE CVE CVE-2025-38123 | known affected: 396 known not affected: 442 recommended: 503 | 2026-10-17T00:58:58+00:00 | Vulnerability · Source |
| CVE-2025-38135 | suse_vex | SUSE CVE CVE-2025-38135 | known affected: 608 known not affected: 243 recommended: 503 | 2026-10-17T00:58:55+00:00 | Vulnerability · Source |
| CVE-2025-38147 | suse_vex | SUSE CVE CVE-2025-38147 | known affected: 746 known not affected: 36 recommended: 450 | 2026-10-17T00:58:52+00:00 | Vulnerability · Source |
| CVE-2025-38149 | suse_vex | SUSE CVE CVE-2025-38149 | known affected: 396 known not affected: 442 recommended: 503 | 2026-10-17T00:58:50+00:00 | Vulnerability · Source |
| CVE-2025-38172 | suse_vex | SUSE CVE CVE-2025-38172 | known affected: 2 known not affected: 521 recommended: 227 | 2026-10-17T00:58:47+00:00 | Vulnerability · Source |
| CVE-2025-38173 | suse_vex | SUSE CVE CVE-2025-38173 | known affected: 705 known not affected: 80 recommended: 540 | 2026-10-17T00:58:46+00:00 | Vulnerability · Source |
| CVE-2025-38183 | suse_vex | SUSE CVE CVE-2025-38183 | known affected: 437 known not affected: 399 recommended: 427 | 2026-10-17T00:58:44+00:00 | Vulnerability · Source |
| CVE-2025-38200 | suse_vex | SUSE CVE CVE-2025-38200 | known affected: 571 recommended: 925 | 2026-10-17T00:58:41+00:00 | Vulnerability · Source |
| CVE-2025-38205 | suse_vex | SUSE CVE CVE-2025-38205 | known affected: 457 known not affected: 405 recommended: 503 | 2026-10-17T00:58:39+00:00 | Vulnerability · Source |
| CVE-2025-38220 | suse_vex | SUSE CVE CVE-2025-38220 | known affected: 444 known not affected: 405 recommended: 545 | 2026-10-17T00:58:36+00:00 | Vulnerability · Source |
| CVE-2025-38225 | suse_vex | SUSE CVE CVE-2025-38225 | known affected: 539 known not affected: 299 recommended: 503 | 2026-10-17T00:58:34+00:00 | Vulnerability · Source |
| CVE-2025-38240 | suse_vex | SUSE CVE CVE-2025-38240 | known affected: 394 known not affected: 404 recommended: 427 | 2026-10-17T00:58:32+00:00 | Vulnerability · Source |
| CVE-2025-38279 | suse_vex | SUSE CVE CVE-2025-38279 | known affected: 504 known not affected: 332 recommended: 427 | 2026-10-17T00:58:27+00:00 | Vulnerability · Source |
| CVE-2025-38301 | suse_vex | SUSE CVE CVE-2025-38301 | known affected: 5 known not affected: 526 recommended: 185 | 2026-10-17T00:58:23+00:00 | Vulnerability · Source |
| CVE-2025-38331 | suse_vex | SUSE CVE CVE-2025-38331 | known affected: 0 known not affected: 575 | 2026-10-17T00:58:20+00:00 | Vulnerability · Source |
| CVE-2025-38335 | suse_vex | SUSE CVE CVE-2025-38335 | known affected: 402 known not affected: 436 recommended: 503 | 2026-10-17T00:58:18+00:00 | Vulnerability · Source |
| CVE-2025-38352 | suse_vex | SUSE CVE CVE-2025-38352 | known affected: 467 known not affected: 306 recommended: 1025 | 2026-10-17T00:58:15+00:00 | Vulnerability · Source |
| CVE-2025-38359 | suse_vex | SUSE CVE CVE-2025-38359 | known affected: 588 known not affected: 218 recommended: 495 | 2026-10-17T00:58:13+00:00 | Vulnerability · Source |
| CVE-2025-38381 | suse_vex | SUSE CVE CVE-2025-38381 | known affected: 2 known not affected: 521 recommended: 185 | 2026-10-17T00:58:07+00:00 | Vulnerability · Source |
| CVE-2025-38406 | suse_vex | SUSE CVE CVE-2025-38406 | known affected: 735 known not affected: 54 recommended: 503 | 2026-10-17T00:58:02+00:00 | Vulnerability · Source |
| CVE-2025-38414 | suse_vex | SUSE CVE CVE-2025-38414 | known affected: 412 known not affected: 426 recommended: 503 | 2026-10-17T00:58:00+00:00 | Vulnerability · Source |
| CVE-2025-38420 | suse_vex | SUSE CVE CVE-2025-38420 | known affected: 739 known not affected: 43 recommended: 526 | 2026-10-17T00:57:58+00:00 | Vulnerability · Source |
| CVE-2025-38428 | suse_vex | SUSE CVE CVE-2025-38428 | known affected: 729 known not affected: 121 recommended: 503 | 2026-10-17T00:57:57+00:00 | Vulnerability · Source |
| CVE-2025-38441 | suse_vex | SUSE CVE CVE-2025-38441 | known affected: 524 known not affected: 338 recommended: 503 | 2026-10-17T00:57:55+00:00 | Vulnerability · Source |
| CVE-2025-38445 | suse_vex | SUSE CVE CVE-2025-38445 | known affected: 675 known not affected: 187 recommended: 503 | 2026-10-17T00:57:53+00:00 | Vulnerability · Source |
| CVE-2025-38485 | suse_vex | SUSE CVE CVE-2025-38485 | known affected: 396 known not affected: 442 recommended: 503 | 2026-10-17T00:57:49+00:00 | Vulnerability · Source |
| CVE-2025-38507 | suse_vex | SUSE CVE CVE-2025-38507 | known affected: 2 known not affected: 399 recommended: 203 | 2026-10-17T00:57:46+00:00 | Vulnerability · Source |
| CVE-2025-38529 | suse_vex | SUSE CVE CVE-2025-38529 | known affected: 729 known not affected: 117 recommended: 521 | 2026-10-17T00:57:44+00:00 | Vulnerability · Source |
| CVE-2025-38545 | suse_vex | SUSE CVE CVE-2025-38545 | known affected: 2 known not affected: 552 recommended: 185 | 2026-10-17T00:57:41+00:00 | Vulnerability · Source |
| CVE-2025-38548 | suse_vex | SUSE CVE CVE-2025-38548 | known affected: 539 known not affected: 307 recommended: 521 | 2026-10-17T00:57:39+00:00 | Vulnerability · Source |
| CVE-2025-38565 | suse_vex | SUSE CVE CVE-2025-38565 | known affected: 259 known not affected: 6 recommended: 700 | 2026-10-17T00:57:36+00:00 | Vulnerability · Source |
| CVE-2025-38568 | suse_vex | SUSE CVE CVE-2025-38568 | known affected: 396 known not affected: 450 recommended: 615 | 2026-10-17T00:57:34+00:00 | Vulnerability · Source |
| CVE-2025-38569 | suse_vex | SUSE CVE CVE-2025-38569 | known affected: 2 known not affected: 552 recommended: 203 | 2026-10-17T00:57:33+00:00 | Vulnerability · Source |
| CVE-2025-38580 | suse_vex | SUSE CVE CVE-2025-38580 | known affected: 0 known not affected: 521 | 2026-10-17T00:57:31+00:00 | Vulnerability · Source |
| CVE-2025-38583 | suse_vex | SUSE CVE CVE-2025-38583 | known affected: 539 known not affected: 319 recommended: 503 | 2026-10-17T00:57:30+00:00 | Vulnerability · Source |
| CVE-2025-38602 | suse_vex | SUSE CVE CVE-2025-38602 | known affected: 741 known not affected: 61 recommended: 540 | 2026-10-17T00:57:26+00:00 | Vulnerability · Source |
| CVE-2025-38620 | suse_vex | SUSE CVE CVE-2025-38620 | known affected: 0 known not affected: 521 | 2026-10-17T00:57:24+00:00 | Vulnerability · Source |
| CVE-2025-38622 | suse_vex | SUSE CVE CVE-2025-38622 | known affected: 619 known not affected: 187 recommended: 503 | 2026-10-17T00:57:22+00:00 | Vulnerability · Source |
| CVE-2025-38625 | suse_vex | SUSE CVE CVE-2025-38625 | known affected: 2 known not affected: 535 recommended: 203 | 2026-10-17T00:57:21+00:00 | Vulnerability · Source |
| CVE-2025-38633 | suse_vex | SUSE CVE CVE-2025-38633 | known affected: 0 known not affected: 521 | 2026-10-17T00:57:19+00:00 | Vulnerability · Source |
| CVE-2025-38637 | suse_vex | SUSE CVE CVE-2025-38637 | known affected: 671 known not affected: 96 recommended: 454 | 2026-10-17T00:57:17+00:00 | Vulnerability · Source |
| CVE-2025-38641 | suse_vex | SUSE CVE CVE-2025-38641 | known affected: 0 known not affected: 521 recommended: 58 | 2026-10-17T00:57:15+00:00 | Vulnerability · Source |
| CVE-2025-38663 | suse_vex | SUSE CVE CVE-2025-38663 | known affected: 822 known not affected: 56 recommended: 318 | 2026-10-17T00:57:13+00:00 | Vulnerability · Source |
| CVE-2025-38683 | suse_vex | SUSE CVE CVE-2025-38683 | known affected: 371 known not affected: 317 recommended: 629 | 2026-10-17T00:57:11+00:00 | Vulnerability · Source |
| CVE-2025-38684 | suse_vex | SUSE CVE CVE-2025-38684 | known affected: 399 known not affected: 213 recommended: 797 | 2026-10-17T00:57:09+00:00 | Vulnerability · Source |
| CVE-2025-38696 | suse_vex | SUSE CVE CVE-2025-38696 | known affected: 0 known not affected: 520 | 2026-10-17T00:57:07+00:00 | Vulnerability · Source |
| CVE-2025-38697 | suse_vex | SUSE CVE CVE-2025-38697 | known affected: 394 known not affected: 393 recommended: 310 | 2026-10-17T00:57:06+00:00 | Vulnerability · Source |
| CVE-2025-38711 | suse_vex | SUSE CVE CVE-2025-38711 | known affected: 0 known not affected: 520 | 2026-10-17T00:57:04+00:00 | Vulnerability · Source |