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-22013 | suse_vex | SUSE CVE CVE-2025-22013 | known affected: 394 known not affected: 400 recommended: 415 | 2026-10-15T16:57:58+00:00 | Vulnerability · Source |
| CVE-2025-22014 | suse_vex | SUSE CVE CVE-2025-22014 | known affected: 522 known not affected: 272 recommended: 415 | 2026-10-15T16:57:56+00:00 | Vulnerability · Source |
| CVE-2025-22015 | suse_vex | SUSE CVE CVE-2025-22015 | known affected: 437 known not affected: 384 recommended: 415 | 2026-10-15T16:57:55+00:00 | Vulnerability · Source |
| CVE-2025-22017 | suse_vex | SUSE CVE CVE-2025-22017 | known affected: 437 known not affected: 384 recommended: 415 | 2026-10-15T16:57:53+00:00 | Vulnerability · Source |
| CVE-2025-22018 | suse_vex | SUSE CVE CVE-2025-22018 | known affected: 769 recommended: 478 | 2026-10-15T16:57:51+00:00 | Vulnerability · Source |
| CVE-2025-22019 | suse_vex | SUSE CVE CVE-2025-22019 | known affected: 0 known not affected: 561 | 2026-10-15T16:57:48+00:00 | Vulnerability · Source |
| CVE-2025-22020 | suse_vex | SUSE CVE CVE-2025-22020 | known affected: 385 known not affected: 209 recommended: 186 | 2026-10-15T16:57:46+00:00 | Vulnerability · Source |
| CVE-2025-22021 | suse_vex | SUSE CVE CVE-2025-22021 | known affected: 759 known not affected: 6 recommended: 468 | 2026-10-15T16:57:44+00:00 | Vulnerability · Source |
| CVE-2025-22022 | suse_vex | SUSE CVE CVE-2025-22022 | known affected: 743 recommended: 464 | 2026-10-15T16:57:42+00:00 | Vulnerability · Source |
| CVE-2025-22024 | suse_vex | SUSE CVE CVE-2025-22024 | known affected: 0 known not affected: 460 recommended: 109 | 2026-10-15T16:57:40+00:00 | Vulnerability · Source |
| CVE-2025-22025 | suse_vex | SUSE CVE CVE-2025-22025 | known affected: 394 known not affected: 350 recommended: 517 | 2026-10-15T16:57:39+00:00 | Vulnerability · Source |
| CVE-2025-22026 | suse_vex | SUSE CVE CVE-2025-22026 | known affected: 0 known not affected: 540 recommended: 119 | 2026-10-15T16:57:37+00:00 | Vulnerability · Source |
| CVE-2025-22027 | suse_vex | SUSE CVE CVE-2025-22027 | known affected: 722 known not affected: 49 recommended: 475 | 2026-10-15T16:57:35+00:00 | Vulnerability · Source |
| CVE-2025-22032 | suse_vex | SUSE CVE CVE-2025-22032 | known affected: 0 known not affected: 456 recommended: 109 | 2026-10-15T16:57:33+00:00 | Vulnerability · Source |
| CVE-2025-22033 | suse_vex | SUSE CVE CVE-2025-22033 | known affected: 394 known not affected: 400 recommended: 438 | 2026-10-15T16:57:31+00:00 | Vulnerability · Source |
| CVE-2025-22035 | suse_vex | SUSE CVE CVE-2025-22035 | known affected: 584 known not affected: 198 recommended: 450 | 2026-10-15T16:57:29+00:00 | Vulnerability · Source |
| CVE-2025-22038 | suse_vex | SUSE CVE CVE-2025-22038 | known affected: 0 known not affected: 559 | 2026-10-15T16:57:27+00:00 | Vulnerability · Source |
| CVE-2025-22039 | suse_vex | SUSE CVE CVE-2025-22039 | known affected: 0 known not affected: 559 | 2026-10-15T16:57:25+00:00 | Vulnerability · Source |
| CVE-2025-22040 | suse_vex | SUSE CVE CVE-2025-22040 | known affected: 0 known not affected: 559 | 2026-10-15T16:57:23+00:00 | Vulnerability · Source |
| CVE-2025-22042 | suse_vex | SUSE CVE CVE-2025-22042 | known affected: 0 known not affected: 557 | 2026-10-15T16:57:21+00:00 | Vulnerability · Source |
| CVE-2025-22043 | suse_vex | SUSE CVE CVE-2025-22043 | known affected: 0 known not affected: 557 | 2026-10-15T16:57:20+00:00 | Vulnerability · Source |
| CVE-2025-22044 | suse_vex | SUSE CVE CVE-2025-22044 | known affected: 565 known not affected: 229 recommended: 438 | 2026-10-15T16:57:18+00:00 | Vulnerability · Source |
| CVE-2025-22045 | suse_vex | SUSE CVE CVE-2025-22045 | known affected: 429 known not affected: 187 recommended: 731 | 2026-10-15T16:57:16+00:00 | Vulnerability · Source |
| CVE-2025-22049 | suse_vex | SUSE CVE CVE-2025-22049 | known affected: 0 known not affected: 557 | 2026-10-15T16:57:14+00:00 | Vulnerability · Source |
| CVE-2025-22052 | suse_vex | SUSE CVE CVE-2025-22052 | known affected: 0 known not affected: 460 | 2026-10-15T16:57:13+00:00 | Vulnerability · Source |
| CVE-2025-22054 | suse_vex | SUSE CVE CVE-2025-22054 | known affected: 0 known not affected: 561 | 2026-10-15T16:57:11+00:00 | Vulnerability · Source |
| CVE-2025-22055 | suse_vex | SUSE CVE CVE-2025-22055 | known affected: 439 known not affected: 139 recommended: 814 | 2026-10-15T16:57:09+00:00 | Vulnerability · Source |
| CVE-2025-22056 | suse_vex | SUSE CVE CVE-2025-22056 | known affected: 432 known not affected: 217 recommended: 771 | 2026-10-15T16:57:08+00:00 | Vulnerability · Source |
| CVE-2025-22060 | suse_vex | SUSE CVE CVE-2025-22060 | known affected: 480 known not affected: 206 recommended: 563 | 2026-10-15T16:57:06+00:00 | Vulnerability · Source |
| CVE-2025-22061 | suse_vex | SUSE CVE CVE-2025-22061 | known affected: 0 known not affected: 456 | 2026-10-15T16:57:04+00:00 | Vulnerability · Source |
| CVE-2025-22062 | suse_vex | SUSE CVE CVE-2025-22062 | known affected: 538 known not affected: 256 recommended: 438 | 2026-10-15T16:57:03+00:00 | Vulnerability · Source |
| CVE-2025-22070 | suse_vex | SUSE CVE CVE-2025-22070 | known affected: 410 known not affected: 384 recommended: 431 | 2026-10-15T16:57:01+00:00 | Vulnerability · Source |
| CVE-2025-22075 | suse_vex | SUSE CVE CVE-2025-22075 | known affected: 591 known not affected: 203 recommended: 438 | 2026-10-15T16:56:59+00:00 | Vulnerability · Source |
| CVE-2025-22077 | suse_vex | SUSE CVE CVE-2025-22077 | known affected: 145 known not affected: 368 recommended: 185 | 2026-10-15T16:56:58+00:00 | Vulnerability · Source |
| CVE-2025-22078 | suse_vex | SUSE CVE CVE-2025-22078 | known affected: 0 known not affected: 456 recommended: 109 | 2026-10-15T16:56:56+00:00 | Vulnerability · Source |
| CVE-2025-22081 | suse_vex | SUSE CVE CVE-2025-22081 | known affected: 0 known not affected: 528 | 2026-10-15T16:56:54+00:00 | Vulnerability · Source |
| CVE-2025-22082 | suse_vex | SUSE CVE CVE-2025-22082 | known affected: 0 known not affected: 460 recommended: 109 | 2026-10-15T16:56:53+00:00 | Vulnerability · Source |
| CVE-2025-22083 | suse_vex | SUSE CVE CVE-2025-22083 | known affected: 712 known not affected: 6 recommended: 464 | 2026-10-15T16:56:51+00:00 | Vulnerability · Source |
| CVE-2025-22085 | suse_vex | SUSE CVE CVE-2025-22085 | known affected: 0 known not affected: 456 recommended: 292 | 2026-10-15T16:56:49+00:00 | Vulnerability · Source |
| CVE-2025-22088 | suse_vex | SUSE CVE CVE-2025-22088 | known affected: 437 known not affected: 388 recommended: 438 | 2026-10-15T16:56:47+00:00 | Vulnerability · Source |
| CVE-2025-22090 | suse_vex | SUSE CVE CVE-2025-22090 | known affected: 734 known not affected: 27 recommended: 415 | 2026-10-15T16:56:46+00:00 | Vulnerability · Source |
| CVE-2025-22091 | suse_vex | SUSE CVE CVE-2025-22091 | known affected: 0 known not affected: 460 recommended: 292 | 2026-10-15T16:56:44+00:00 | Vulnerability · Source |
| CVE-2025-22092 | suse_vex | SUSE CVE CVE-2025-22092 | known affected: 0 known not affected: 460 recommended: 141 | 2026-10-15T16:56:43+00:00 | Vulnerability · Source |
| CVE-2025-22093 | suse_vex | SUSE CVE CVE-2025-22093 | known affected: 394 known not affected: 410 recommended: 438 | 2026-10-15T16:56:41+00:00 | Vulnerability · Source |
| CVE-2025-22094 | suse_vex | SUSE CVE CVE-2025-22094 | known affected: 0 known not affected: 460 recommended: 206 | 2026-10-15T16:56:40+00:00 | Vulnerability · Source |
| CVE-2025-22095 | suse_vex | SUSE CVE CVE-2025-22095 | known affected: 394 known not affected: 404 recommended: 427 | 2026-10-15T16:56:38+00:00 | Vulnerability · Source |
| CVE-2025-22098 | suse_vex | SUSE CVE CVE-2025-22098 | known affected: 0 known not affected: 460 recommended: 58 | 2026-10-15T16:56:37+00:00 | Vulnerability · Source |
| CVE-2025-22099 | suse_vex | SUSE CVE CVE-2025-22099 | known affected: 0 known not affected: 460 recommended: 58 | 2026-10-15T16:56:36+00:00 | Vulnerability · Source |
| CVE-2025-22105 | suse_vex | SUSE CVE CVE-2025-22105 | known affected: 502 known not affected: 323 recommended: 457 | 2026-10-15T16:56:34+00:00 | Vulnerability · Source |
| CVE-2025-22106 | suse_vex | SUSE CVE CVE-2025-22106 | known affected: 437 known not affected: 388 recommended: 415 | 2026-10-15T16:56:33+00:00 | Vulnerability · Source |