VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
307707 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-39772 | suse_vex | SUSE CVE CVE-2025-39772 | known affected: 637 known not affected: 96 recommended: 487 | 2026-10-11T16:49:56+00:00 | Vulnerability · Source |
| CVE-2025-39779 | suse_vex | SUSE CVE CVE-2025-39779 | known affected: 524 known not affected: 262 recommended: 154 | 2026-10-11T16:49:53+00:00 | Vulnerability · Source |
| CVE-2025-39782 | suse_vex | SUSE CVE CVE-2025-39782 | known affected: 725 known not affected: 6 recommended: 509 | 2026-10-11T16:49:51+00:00 | Vulnerability · Source |
| CVE-2025-39831 | suse_vex | SUSE CVE CVE-2025-39831 | known affected: 74 known not affected: 473 recommended: 154 | 2026-10-11T16:49:45+00:00 | Vulnerability · Source |
| CVE-2025-39841 | suse_vex | SUSE CVE CVE-2025-39841 | known affected: 635 known not affected: 96 recommended: 593 | 2026-10-11T16:49:43+00:00 | Vulnerability · Source |
| CVE-2025-39850 | suse_vex | SUSE CVE CVE-2025-39850 | known affected: 576 known not affected: 213 recommended: 464 | 2026-10-11T16:49:40+00:00 | Vulnerability · Source |
| CVE-2025-39866 | suse_vex | SUSE CVE CVE-2025-39866 | known affected: 731 recommended: 501 | 2026-10-11T16:49:34+00:00 | Vulnerability · Source |
| CVE-2025-39889 | suse_vex | SUSE CVE CVE-2025-39889 | known affected: 780 known not affected: 40 recommended: 464 | 2026-10-11T16:49:30+00:00 | Vulnerability · Source |
| CVE-2025-39916 | suse_vex | SUSE CVE CVE-2025-39916 | known affected: 2 known not affected: 517 recommended: 154 | 2026-10-11T16:49:24+00:00 | Vulnerability · Source |
| CVE-2025-39926 | suse_vex | SUSE CVE CVE-2025-39926 | known affected: 7 known not affected: 542 recommended: 154 | 2026-10-11T16:49:20+00:00 | Vulnerability · Source |
| CVE-2025-39931 | suse_vex | SUSE CVE CVE-2025-39931 | known affected: 731 recommended: 501 | 2026-10-11T16:49:18+00:00 | Vulnerability · Source |
| CVE-2025-39937 | suse_vex | SUSE CVE CVE-2025-39937 | known affected: 755 known not affected: 36 recommended: 464 | 2026-10-11T16:49:15+00:00 | Vulnerability · Source |
| CVE-2025-39939 | suse_vex | SUSE CVE CVE-2025-39939 | known affected: 394 known not affected: 503 recommended: 83 | 2026-10-11T16:49:13+00:00 | Vulnerability · Source |
| CVE-2025-39988 | suse_vex | SUSE CVE CVE-2025-39988 | known affected: 396 known not affected: 387 recommended: 464 | 2026-10-11T16:49:06+00:00 | Vulnerability · Source |
| CVE-2025-40015 | suse_vex | SUSE CVE CVE-2025-40015 | known not affected: 523 recommended: 6 | 2026-10-11T16:49:02+00:00 | Vulnerability · Source |
| CVE-2025-40016 | suse_vex | SUSE CVE CVE-2025-40016 | known affected: 402 known not affected: 399 recommended: 470 | 2026-10-11T16:49:00+00:00 | Vulnerability · Source |
| CVE-2025-40045 | suse_vex | SUSE CVE CVE-2025-40045 | known affected: 2 known not affected: 514 recommended: 178 | 2026-10-11T16:48:58+00:00 | Vulnerability · Source |
| CVE-2025-40047 | suse_vex | SUSE CVE CVE-2025-40047 | known affected: 396 known not affected: 490 recommended: 336 | 2026-10-11T16:48:56+00:00 | Vulnerability · Source |
| CVE-2025-40060 | suse_vex | SUSE CVE CVE-2025-40060 | known affected: 524 known not affected: 262 recommended: 470 | 2026-10-11T16:48:52+00:00 | Vulnerability · Source |
| CVE-2025-40077 | suse_vex | SUSE CVE CVE-2025-40077 | known not affected: 514 recommended: 6 | 2026-10-11T16:48:48+00:00 | Vulnerability · Source |
| CVE-2025-40089 | suse_vex | SUSE CVE CVE-2025-40089 | known not affected: 514 recommended: 6 | 2026-10-11T16:48:43+00:00 | Vulnerability · Source |
| CVE-2025-40093 | suse_vex | SUSE CVE CVE-2025-40093 | known affected: 24 known not affected: 512 recommended: 6 | 2026-10-11T16:48:41+00:00 | Vulnerability · Source |
| CVE-2025-40106 | suse_vex | SUSE CVE CVE-2025-40106 | known affected: 868 known not affected: 6 recommended: 295 | 2026-10-11T16:48:36+00:00 | Vulnerability · Source |
| CVE-2025-40132 | suse_vex | SUSE CVE CVE-2025-40132 | known affected: 396 known not affected: 462 recommended: 247 | 2026-10-11T16:48:31+00:00 | Vulnerability · Source |
| CVE-2025-40134 | suse_vex | SUSE CVE CVE-2025-40134 | known affected: 644 known not affected: 187 recommended: 366 | 2026-10-11T16:48:29+00:00 | Vulnerability · Source |
| CVE-2025-40157 | suse_vex | SUSE CVE CVE-2025-40157 | known affected: 396 known not affected: 388 recommended: 464 | 2026-10-11T16:48:25+00:00 | Vulnerability · Source |
| CVE-2025-40158 | suse_vex | SUSE CVE CVE-2025-40158 | known affected: 737 known not affected: 36 recommended: 492 | 2026-10-11T16:48:23+00:00 | Vulnerability · Source |
| CVE-2025-40179 | suse_vex | SUSE CVE CVE-2025-40179 | known affected: 443 known not affected: 388 recommended: 384 | 2026-10-11T16:48:20+00:00 | Vulnerability · Source |
| CVE-2025-40202 | suse_vex | SUSE CVE CVE-2025-40202 | known affected: 443 known not affected: 388 recommended: 366 | 2026-10-11T16:48:12+00:00 | Vulnerability · Source |
| CVE-2025-40213 | suse_vex | SUSE CVE CVE-2025-40213 | known affected: 551 known not affected: 321 recommended: 287 | 2026-10-11T16:48:08+00:00 | Vulnerability · Source |
| CVE-2025-40220 | suse_vex | SUSE CVE CVE-2025-40220 | known affected: 596 recommended: 621 | 2026-10-11T16:48:05+00:00 | Vulnerability · Source |
| CVE-2025-40237 | suse_vex | SUSE CVE CVE-2025-40237 | known affected: 396 known not affected: 538 recommended: 214 | 2026-10-11T16:48:02+00:00 | Vulnerability · Source |
| CVE-2025-40246 | suse_vex | SUSE CVE CVE-2025-40246 | known affected: 396 known not affected: 538 recommended: 172 | 2026-10-11T16:47:59+00:00 | Vulnerability · Source |
| CVE-2025-40252 | suse_vex | SUSE CVE CVE-2025-40252 | known affected: 806 known not affected: 6 recommended: 346 | 2026-10-11T16:47:56+00:00 | Vulnerability · Source |
| CVE-2025-40261 | suse_vex | SUSE CVE CVE-2025-40261 | known affected: 685 known not affected: 129 recommended: 312 | 2026-10-11T16:47:53+00:00 | Vulnerability · Source |
| CVE-2025-40275 | suse_vex | SUSE CVE CVE-2025-40275 | known affected: 630 known not affected: 143 recommended: 407 | 2026-10-11T16:47:47+00:00 | Vulnerability · Source |
| CVE-2025-40293 | suse_vex | SUSE CVE CVE-2025-40293 | known affected: 484 known not affected: 388 recommended: 289 | 2026-10-11T16:47:44+00:00 | Vulnerability · Source |
| CVE-2025-40302 | suse_vex | SUSE CVE CVE-2025-40302 | known affected: 396 known not affected: 468 recommended: 265 | 2026-10-11T16:47:41+00:00 | Vulnerability · Source |
| CVE-2025-40319 | suse_vex | SUSE CVE CVE-2025-40319 | known affected: 659 known not affected: 213 recommended: 289 | 2026-10-11T16:47:38+00:00 | Vulnerability · Source |
| CVE-2025-40329 | suse_vex | SUSE CVE CVE-2025-40329 | known affected: 396 known not affected: 429 recommended: 384 | 2026-10-11T16:47:34+00:00 | Vulnerability · Source |
| CVE-2025-40332 | suse_vex | SUSE CVE CVE-2025-40332 | known affected: 396 known not affected: 510 recommended: 265 | 2026-10-11T16:47:32+00:00 | Vulnerability · Source |
| CVE-2025-40355 | suse_vex | SUSE CVE CVE-2025-40355 | known affected: 612 known not affected: 260 recommended: 289 | 2026-10-11T16:47:29+00:00 | Vulnerability · Source |
| CVE-2025-40779 | suse_vex | SUSE CVE CVE-2025-40779 | known not affected: 375 recommended: 150 | 2026-10-11T16:47:26+00:00 | Vulnerability · Source |
| CVE-2025-43212 | suse_vex | SUSE CVE CVE-2025-43212 | known affected: 179 known not affected: 105 recommended: 562 | 2026-10-11T16:47:22+00:00 | Vulnerability · Source |
| CVE-2025-43458 | suse_vex | SUSE CVE CVE-2025-43458 | known affected: 237 recommended: 588 | 2026-10-11T16:47:20+00:00 | Vulnerability · Source |
| CVE-2025-44001 | suse_vex | SUSE CVE CVE-2025-44001 | recommended: 1 | 2026-10-11T16:47:16+00:00 | Vulnerability · Source |
| CVE-2025-46404 | suse_vex | SUSE CVE CVE-2025-46404 | known affected: 12 recommended: 54 | 2026-10-11T16:47:14+00:00 | Vulnerability · Source |
| CVE-2025-46599 | suse_vex | SUSE CVE CVE-2025-46599 | recommended: 4 | 2026-10-11T16:47:12+00:00 | Vulnerability · Source |
| CVE-2025-46702 | suse_vex | SUSE CVE CVE-2025-46702 | recommended: 4 | 2026-10-11T16:47:10+00:00 | Vulnerability · Source |
| CVE-2025-46705 | suse_vex | SUSE CVE CVE-2025-46705 | known affected: 12 recommended: 54 | 2026-10-11T16:47:08+00:00 | Vulnerability · Source |