VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-65637 | suse_vex | SUSE CVE CVE-2025-65637 | recommended: 34 | 2026-10-15T15:59:53+00:00 | Vulnerability · Source |
| CVE-2025-65754 | suse_vex | SUSE CVE CVE-2025-65754 | No product status | 2026-10-15T15:59:52+00:00 | Vulnerability · Source |
| CVE-2025-65795 | suse_vex | SUSE CVE CVE-2025-65795 | No product status | 2026-10-15T15:59:50+00:00 | Vulnerability · Source |
| CVE-2025-65796 | suse_vex | SUSE CVE CVE-2025-65796 | No product status | 2026-10-15T15:59:49+00:00 | Vulnerability · Source |
| CVE-2025-65798 | suse_vex | SUSE CVE CVE-2025-65798 | No product status | 2026-10-15T15:59:47+00:00 | Vulnerability · Source |
| CVE-2025-65942 | suse_vex | SUSE CVE CVE-2025-65942 | No product status | 2026-10-15T15:59:45+00:00 | Vulnerability · Source |
| CVE-2025-65955 | suse_vex | SUSE CVE CVE-2025-65955 | known affected: 161 known not affected: 101 recommended: 294 | 2026-10-15T15:59:44+00:00 | Vulnerability · Source |
| CVE-2025-65965 | suse_vex | SUSE CVE CVE-2025-65965 | No product status | 2026-10-15T15:59:42+00:00 | Vulnerability · Source |
| CVE-2025-66037 | suse_vex | SUSE CVE CVE-2025-66037 | known affected: 406 known not affected: 14 recommended: 33 | 2026-10-15T15:59:40+00:00 | Vulnerability · Source |
| CVE-2025-66200 | suse_vex | SUSE CVE CVE-2025-66200 | known affected: 554 known not affected: 1 recommended: 214 | 2026-10-15T15:59:39+00:00 | Vulnerability · Source |
| CVE-2025-66215 | suse_vex | SUSE CVE CVE-2025-66215 | known affected: 414 recommended: 37 | 2026-10-15T15:59:37+00:00 | Vulnerability · Source |
| CVE-2025-66286 | suse_vex | SUSE CVE CVE-2025-66286 | known affected: 226 | 2026-10-15T15:59:35+00:00 | Vulnerability · Source |
| CVE-2025-66287 | suse_vex | SUSE CVE CVE-2025-66287 | known affected: 237 recommended: 588 | 2026-10-15T15:59:34+00:00 | Vulnerability · Source |
| CVE-2025-66292 | suse_vex | SUSE CVE CVE-2025-66292 | No product status | 2026-10-15T15:59:32+00:00 | Vulnerability · Source |
| CVE-2025-66382 | suse_vex | SUSE CVE CVE-2025-66382 | known affected: 273 known not affected: 433 recommended: 2 | 2026-10-15T15:59:30+00:00 | Vulnerability · Source |
| CVE-2025-66411 | suse_vex | SUSE CVE CVE-2025-66411 | No product status | 2026-10-15T15:59:29+00:00 | Vulnerability · Source |
| CVE-2025-66490 | suse_vex | SUSE CVE CVE-2025-66490 | recommended: 2 | 2026-10-15T15:59:25+00:00 | Vulnerability · Source |
| CVE-2025-66508 | suse_vex | SUSE CVE CVE-2025-66508 | No product status | 2026-10-15T15:59:23+00:00 | Vulnerability · Source |
| CVE-2025-66565 | suse_vex | SUSE CVE CVE-2025-66565 | No product status | 2026-10-15T15:59:22+00:00 | Vulnerability · Source |
| CVE-2025-66570 | suse_vex | SUSE CVE CVE-2025-66570 | recommended: 7 | 2026-10-15T15:59:20+00:00 | Vulnerability · Source |
| CVE-2025-66577 | suse_vex | SUSE CVE CVE-2025-66577 | recommended: 7 | 2026-10-15T15:59:19+00:00 | Vulnerability · Source |
| CVE-2025-66626 | suse_vex | SUSE CVE CVE-2025-66626 | No product status | 2026-10-15T15:59:17+00:00 | Vulnerability · Source |
| CVE-2025-66628 | suse_vex | SUSE CVE CVE-2025-66628 | known affected: 202 known not affected: 24 recommended: 314 | 2026-10-15T15:59:15+00:00 | Vulnerability · Source |
| CVE-2025-66630 | suse_vex | SUSE CVE CVE-2025-66630 | No product status | 2026-10-15T15:59:13+00:00 | Vulnerability · Source |
| CVE-2025-66719 | suse_vex | SUSE CVE CVE-2025-66719 | No product status | 2026-10-15T15:59:10+00:00 | Vulnerability · Source |
| CVE-2025-66866 | suse_vex | SUSE CVE CVE-2025-66866 | known affected: 273 | 2026-10-15T15:59:08+00:00 | Vulnerability · Source |
| CVE-2025-67030 | suse_vex | SUSE CVE CVE-2025-67030 | known affected: 8 recommended: 609 | 2026-10-15T15:59:06+00:00 | Vulnerability · Source |
| CVE-2025-67221 | suse_vex | SUSE CVE CVE-2025-67221 | recommended: 7 | 2026-10-15T15:59:05+00:00 | Vulnerability · Source |
| CVE-2025-67268 | suse_vex | SUSE CVE CVE-2025-67268 | recommended: 13 | 2026-10-15T15:59:03+00:00 | Vulnerability · Source |
| CVE-2025-67269 | suse_vex | SUSE CVE CVE-2025-67269 | recommended: 13 | 2026-10-15T15:59:01+00:00 | Vulnerability · Source |
| CVE-2025-67488 | suse_vex | SUSE CVE CVE-2025-67488 | No product status | 2026-10-15T15:58:59+00:00 | Vulnerability · Source |
| CVE-2025-67494 | suse_vex | SUSE CVE CVE-2025-67494 | No product status | 2026-10-15T15:58:57+00:00 | Vulnerability · Source |
| CVE-2025-67495 | suse_vex | SUSE CVE CVE-2025-67495 | No product status | 2026-10-15T15:58:55+00:00 | Vulnerability · Source |
| CVE-2025-67499 | suse_vex | SUSE CVE CVE-2025-67499 | known not affected: 179 recommended: 12 | 2026-10-15T15:58:53+00:00 | Vulnerability · Source |
| CVE-2025-67601 | suse_vex | SUSE CVE CVE-2025-67601 | No product status | 2026-10-15T15:58:50+00:00 | Vulnerability · Source |
| CVE-2025-67717 | suse_vex | SUSE CVE CVE-2025-67717 | No product status | 2026-10-15T15:58:48+00:00 | Vulnerability · Source |
| CVE-2025-67726 | suse_vex | SUSE CVE CVE-2025-67726 | known affected: 456 known not affected: 11 recommended: 468 | 2026-10-15T15:58:47+00:00 | Vulnerability · Source |
| CVE-2025-67733 | suse_vex | SUSE CVE CVE-2025-67733 | known affected: 9 recommended: 31 | 2026-10-15T15:58:45+00:00 | Vulnerability · Source |
| CVE-2025-67746 | suse_vex | SUSE CVE CVE-2025-67746 | known affected: 3 recommended: 21 | 2026-10-15T15:58:43+00:00 | Vulnerability · Source |
| CVE-2025-67819 | suse_vex | SUSE CVE CVE-2025-67819 | No product status | 2026-10-15T15:58:42+00:00 | Vulnerability · Source |
| CVE-2025-68120 | suse_vex | SUSE CVE CVE-2025-68120 | No product status | 2026-10-15T15:58:40+00:00 | Vulnerability · Source |
| CVE-2025-68151 | suse_vex | SUSE CVE CVE-2025-68151 | No product status | 2026-10-15T15:58:38+00:00 | Vulnerability · Source |
| CVE-2025-68156 | suse_vex | SUSE CVE CVE-2025-68156 | known affected: 2 recommended: 113 | 2026-10-15T15:58:37+00:00 | Vulnerability · Source |
| CVE-2025-68160 | suse_vex | SUSE CVE CVE-2025-68160 | known affected: 562 known not affected: 108 recommended: 426 | 2026-10-15T15:58:35+00:00 | Vulnerability · Source |
| CVE-2025-68167 | suse_vex | SUSE CVE CVE-2025-68167 | known affected: 396 known not affected: 522 recommended: 172 | 2026-10-15T15:58:33+00:00 | Vulnerability · Source |
| CVE-2025-68170 | suse_vex | SUSE CVE CVE-2025-68170 | known affected: 396 known not affected: 472 recommended: 265 | 2026-10-15T15:58:31+00:00 | Vulnerability · Source |
| CVE-2025-68174 | suse_vex | SUSE CVE CVE-2025-68174 | known affected: 612 known not affected: 260 recommended: 289 | 2026-10-15T15:58:29+00:00 | Vulnerability · Source |
| CVE-2025-68175 | suse_vex | SUSE CVE CVE-2025-68175 | known affected: 169 known not affected: 388 | 2026-10-15T15:58:28+00:00 | Vulnerability · Source |
| CVE-2025-68176 | suse_vex | SUSE CVE CVE-2025-68176 | known affected: 524 known not affected: 307 recommended: 384 | 2026-10-15T15:58:26+00:00 | Vulnerability · Source |
| CVE-2025-68179 | suse_vex | SUSE CVE CVE-2025-68179 | known affected: 481 known not affected: 388 recommended: 326 | 2026-10-15T15:58:24+00:00 | Vulnerability · Source |