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-49221 | suse_vex | SUSE CVE CVE-2025-49221 | recommended: 3 | 2026-10-17T00:54:47+00:00 | Vulnerability · Source |
| CVE-2025-50949 | suse_vex | SUSE CVE CVE-2025-50949 | known affected: 21 recommended: 30 | 2026-10-17T00:54:45+00:00 | Vulnerability · Source |
| CVE-2025-51471 | suse_vex | SUSE CVE CVE-2025-51471 | recommended: 5 | 2026-10-17T00:54:43+00:00 | Vulnerability · Source |
| CVE-2025-52890 | suse_vex | SUSE CVE CVE-2025-52890 | recommended: 10 | 2026-10-17T00:54:42+00:00 | Vulnerability · Source |
| CVE-2025-53057 | suse_vex | SUSE CVE CVE-2025-53057 | known affected: 394 known not affected: 208 recommended: 1010 | 2026-10-17T00:54:40+00:00 | Vulnerability · Source |
| CVE-2025-53816 | suse_vex | SUSE CVE CVE-2025-53816 | known affected: 0 known not affected: 19 recommended: 7 | 2026-10-17T00:54:39+00:00 | Vulnerability · Source |
| CVE-2025-54090 | suse_vex | SUSE CVE CVE-2025-54090 | known affected: 0 known not affected: 307 recommended: 1 | 2026-10-17T00:54:37+00:00 | Vulnerability · Source |
| CVE-2025-54386 | suse_vex | SUSE CVE CVE-2025-54386 | recommended: 6 | 2026-10-17T00:54:36+00:00 | Vulnerability · Source |
| CVE-2025-54463 | suse_vex | SUSE CVE CVE-2025-54463 | recommended: 3 | 2026-10-17T00:54:34+00:00 | Vulnerability · Source |
| CVE-2025-54576 | suse_vex | SUSE CVE CVE-2025-54576 | recommended: 5 | 2026-10-17T00:54:33+00:00 | Vulnerability · Source |
| CVE-2025-58158 | suse_vex | SUSE CVE CVE-2025-58158 | recommended: 3 | 2026-10-17T00:54:30+00:00 | Vulnerability · Source |
| CVE-2025-58266 | suse_vex | SUSE CVE CVE-2025-58266 | recommended: 16 | 2026-10-17T00:54:28+00:00 | Vulnerability · Source |
| CVE-2025-58355 | suse_vex | SUSE CVE CVE-2025-58355 | recommended: 3 | 2026-10-17T00:54:26+00:00 | Vulnerability · Source |
| CVE-2025-58364 | suse_vex | SUSE CVE CVE-2025-58364 | known affected: 533 known not affected: 1 recommended: 421 | 2026-10-17T00:54:25+00:00 | Vulnerability · Source |
| CVE-2025-58437 | suse_vex | SUSE CVE CVE-2025-58437 | recommended: 3 | 2026-10-17T00:54:24+00:00 | Vulnerability · Source |
| CVE-2025-59351 | suse_vex | SUSE CVE CVE-2025-59351 | recommended: 3 | 2026-10-17T00:54:23+00:00 | Vulnerability · Source |
| CVE-2025-59362 | suse_vex | SUSE CVE CVE-2025-59362 | known affected: 415 recommended: 34 | 2026-10-17T00:54:21+00:00 | Vulnerability · Source |
| CVE-2025-59432 | suse_vex | SUSE CVE CVE-2025-59432 | known affected: 432 recommended: 136 | 2026-10-17T00:54:19+00:00 | Vulnerability · Source |
| CVE-2025-60632 | suse_vex | SUSE CVE CVE-2025-60632 | recommended: 2 | 2026-10-17T00:54:18+00:00 | Vulnerability · Source |
| CVE-2025-60638 | suse_vex | SUSE CVE CVE-2025-60638 | recommended: 2 | 2026-10-17T00:54:17+00:00 | Vulnerability · Source |
| CVE-2025-60876 | suse_vex | SUSE CVE CVE-2025-60876 | known affected: 35 recommended: 118 | 2026-10-17T00:54:15+00:00 | Vulnerability · Source |
| CVE-2025-61723 | suse_vex | SUSE CVE CVE-2025-61723 | known affected: 30 known not affected: 99 recommended: 281 | 2026-10-17T00:54:12+00:00 | Vulnerability · Source |
| CVE-2025-61730 | suse_vex | SUSE CVE CVE-2025-61730 | known affected: 48 known not affected: 109 recommended: 240 | 2026-10-17T00:54:11+00:00 | Vulnerability · Source |
| CVE-2025-62157 | suse_vex | SUSE CVE CVE-2025-62157 | recommended: 3 | 2026-10-17T00:54:09+00:00 | Vulnerability · Source |
| CVE-2025-62171 | suse_vex | SUSE CVE CVE-2025-62171 | known affected: 322 known not affected: 24 recommended: 231 | 2026-10-17T00:54:07+00:00 | Vulnerability · Source |
| CVE-2025-64505 | suse_vex | SUSE CVE CVE-2025-64505 | known affected: 497 known not affected: 139 recommended: 248 | 2026-10-17T00:54:04+00:00 | Vulnerability · Source |
| CVE-2025-65082 | suse_vex | SUSE CVE CVE-2025-65082 | known affected: 554 known not affected: 1 recommended: 221 | 2026-10-17T00:54:02+00:00 | Vulnerability · Source |
| CVE-2025-65111 | suse_vex | SUSE CVE CVE-2025-65111 | recommended: 2 | 2026-10-17T00:54:01+00:00 | Vulnerability · Source |
| CVE-2025-66506 | suse_vex | SUSE CVE CVE-2025-66506 | recommended: 2 | 2026-10-17T00:53:59+00:00 | Vulnerability · Source |
| CVE-2025-66614 | suse_vex | SUSE CVE CVE-2025-66614 | known affected: 157 recommended: 484 | 2026-10-17T00:53:57+00:00 | Vulnerability · Source |
| CVE-2025-67725 | suse_vex | SUSE CVE CVE-2025-67725 | known affected: 456 known not affected: 8 recommended: 469 | 2026-10-17T00:53:55+00:00 | Vulnerability · Source |
| CVE-2025-67860 | suse_vex | SUSE CVE CVE-2025-67860 | recommended: 2 | 2026-10-17T00:53:54+00:00 | Vulnerability · Source |
| CVE-2025-68173 | suse_vex | SUSE CVE CVE-2025-68173 | known affected: 471 known not affected: 68 recommended: 203 | 2026-10-17T00:53:52+00:00 | Vulnerability · Source |
| CVE-2025-68214 | suse_vex | SUSE CVE CVE-2025-68214 | known affected: 733 known not affected: 96 recommended: 389 | 2026-10-17T00:53:48+00:00 | Vulnerability · Source |
| CVE-2025-68252 | suse_vex | SUSE CVE CVE-2025-68252 | known affected: 396 known not affected: 432 recommended: 415 | 2026-10-17T00:53:46+00:00 | Vulnerability · Source |
| CVE-2025-68307 | suse_vex | SUSE CVE CVE-2025-68307 | known affected: 396 known not affected: 437 recommended: 415 | 2026-10-17T00:53:43+00:00 | Vulnerability · Source |
| CVE-2025-68321 | suse_vex | SUSE CVE CVE-2025-68321 | known affected: 322 known not affected: 96 | 2026-10-17T00:53:41+00:00 | Vulnerability · Source |
| CVE-2025-68340 | suse_vex | SUSE CVE CVE-2025-68340 | known affected: 803 known not affected: 6 recommended: 357 | 2026-10-17T00:53:37+00:00 | Vulnerability · Source |
| CVE-2025-68344 | suse_vex | SUSE CVE CVE-2025-68344 | known affected: 396 known not affected: 497 recommended: 209 | 2026-10-17T00:53:36+00:00 | Vulnerability · Source |
| CVE-2025-68347 | suse_vex | SUSE CVE CVE-2025-68347 | known affected: 396 known not affected: 437 recommended: 441 | 2026-10-17T00:53:34+00:00 | Vulnerability · Source |
| CVE-2025-68360 | suse_vex | SUSE CVE CVE-2025-68360 | known affected: 7 known not affected: 535 recommended: 209 | 2026-10-17T00:53:32+00:00 | Vulnerability · Source |
| CVE-2025-68362 | suse_vex | SUSE CVE CVE-2025-68362 | known affected: 726 known not affected: 49 recommended: 444 | 2026-10-17T00:53:30+00:00 | Vulnerability · Source |
| CVE-2025-68379 | suse_vex | SUSE CVE CVE-2025-68379 | known affected: 780 known not affected: 34 recommended: 363 | 2026-10-17T00:53:28+00:00 | Vulnerability · Source |
| CVE-2025-68383 | suse_vex | SUSE CVE CVE-2025-68383 | recommended: 2 | 2026-10-17T00:53:27+00:00 | Vulnerability · Source |
| CVE-2025-68730 | suse_vex | SUSE CVE CVE-2025-68730 | known affected: 74 known not affected: 486 recommended: 6 | 2026-10-17T00:53:25+00:00 | Vulnerability · Source |
| CVE-2025-68736 | suse_vex | SUSE CVE CVE-2025-68736 | known affected: 614 known not affected: 263 recommended: 317 | 2026-10-17T00:53:23+00:00 | Vulnerability · Source |
| CVE-2025-68748 | suse_vex | SUSE CVE CVE-2025-68748 | known affected: 448 known not affected: 490 recommended: 209 | 2026-10-17T00:53:20+00:00 | Vulnerability · Source |
| CVE-2025-68775 | suse_vex | SUSE CVE CVE-2025-68775 | known affected: 421 known not affected: 312 recommended: 415 | 2026-10-17T00:53:17+00:00 | Vulnerability · Source |
| CVE-2025-68789 | suse_vex | SUSE CVE CVE-2025-68789 | known affected: 617 known not affected: 170 recommended: 320 | 2026-10-17T00:53:14+00:00 | Vulnerability · Source |
| CVE-2025-68792 | suse_vex | SUSE CVE CVE-2025-68792 | known affected: 2 known not affected: 453 recommended: 203 | 2026-10-17T00:53:13+00:00 | Vulnerability · Source |