VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
288105 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-22068 | suse_vex | SUSE CVE CVE-2025-22068 | known not affected: 344 recommended: 95 | 2026-07-31T01:17:46+00:00 | Vulnerability · Source |
| CVE-2025-22071 | suse_vex | SUSE CVE CVE-2025-22071 | known not affected: 455 | 2026-07-31T01:17:43+00:00 | Vulnerability · Source |
| CVE-2025-22072 | suse_vex | SUSE CVE CVE-2025-22072 | known affected: 230 known not affected: 219 | 2026-07-31T01:17:40+00:00 | Vulnerability · Source |
| CVE-2025-22073 | suse_vex | SUSE CVE CVE-2025-22073 | known not affected: 455 | 2026-07-31T01:17:38+00:00 | Vulnerability · Source |
| CVE-2025-22074 | suse_vex | SUSE CVE CVE-2025-22074 | known not affected: 344 | 2026-07-31T01:17:35+00:00 | Vulnerability · Source |
| CVE-2025-22079 | suse_vex | SUSE CVE CVE-2025-22079 | known affected: 249 known not affected: 93 | 2026-07-31T01:17:32+00:00 | Vulnerability · Source |
| CVE-2025-22081 | suse_vex | SUSE CVE CVE-2025-22081 | known not affected: 421 | 2026-07-31T01:17:29+00:00 | Vulnerability · Source |
| CVE-2025-22085 | suse_vex | SUSE CVE CVE-2025-22085 | known not affected: 344 recommended: 211 | 2026-07-31T01:17:25+00:00 | Vulnerability · Source |
| CVE-2025-22086 | suse_vex | SUSE CVE CVE-2025-22086 | known affected: 632 known not affected: 46 recommended: 541 | 2026-07-31T01:17:23+00:00 | Vulnerability · Source |
| CVE-2025-22087 | suse_vex | SUSE CVE CVE-2025-22087 | known not affected: 348 recommended: 96 | 2026-07-31T01:17:22+00:00 | Vulnerability · Source |
| CVE-2025-22114 | suse_vex | SUSE CVE CVE-2025-22114 | known not affected: 348 | 2026-07-31T01:17:15+00:00 | Vulnerability · Source |
| CVE-2025-22117 | suse_vex | SUSE CVE CVE-2025-22117 | known not affected: 397 recommended: 132 | 2026-07-31T01:17:13+00:00 | Vulnerability · Source |
| CVE-2025-22118 | suse_vex | SUSE CVE CVE-2025-22118 | known not affected: 393 recommended: 132 | 2026-07-31T01:17:11+00:00 | Vulnerability · Source |
| CVE-2025-22123 | suse_vex | SUSE CVE CVE-2025-22123 | known not affected: 455 | 2026-07-31T01:17:08+00:00 | Vulnerability · Source |
| CVE-2025-22127 | suse_vex | SUSE CVE CVE-2025-22127 | known affected: 6 known not affected: 445 | 2026-07-31T01:17:06+00:00 | Vulnerability · Source |
| CVE-2025-23130 | suse_vex | SUSE CVE CVE-2025-23130 | known not affected: 459 | 2026-07-31T01:16:59+00:00 | Vulnerability · Source |
| CVE-2025-23132 | suse_vex | SUSE CVE CVE-2025-23132 | known not affected: 455 | 2026-07-31T01:16:57+00:00 | Vulnerability · Source |
| CVE-2025-23135 | suse_vex | SUSE CVE CVE-2025-23135 | known not affected: 455 | 2026-07-31T01:16:55+00:00 | Vulnerability · Source |
| CVE-2025-23143 | suse_vex | SUSE CVE CVE-2025-23143 | known affected: 245 known not affected: 68 | 2026-07-31T01:16:52+00:00 | Vulnerability · Source |
| CVE-2025-24531 | suse_vex | SUSE CVE CVE-2025-24531 | known not affected: 80 recommended: 8 | 2026-07-31T01:16:46+00:00 | Vulnerability · Source |
| CVE-2025-30204 | suse_vex | SUSE CVE CVE-2025-30204 | first fixed: 2 known affected: 55 known not affected: 521 recommended: 184 | 2026-07-31T01:16:36+00:00 | Vulnerability · Source |
| CVE-2025-37739 | suse_vex | SUSE CVE CVE-2025-37739 | known not affected: 460 | 2026-07-31T01:16:32+00:00 | Vulnerability · Source |
| CVE-2025-37740 | suse_vex | SUSE CVE CVE-2025-37740 | known affected: 625 known not affected: 153 recommended: 354 | 2026-07-31T01:16:30+00:00 | Vulnerability · Source |
| CVE-2025-37741 | suse_vex | SUSE CVE CVE-2025-37741 | known affected: 394 known not affected: 370 recommended: 354 | 2026-07-31T01:16:27+00:00 | Vulnerability · Source |
| CVE-2025-37742 | suse_vex | SUSE CVE CVE-2025-37742 | known affected: 564 known not affected: 219 recommended: 354 | 2026-07-31T01:16:24+00:00 | Vulnerability · Source |
| CVE-2025-37749 | suse_vex | SUSE CVE CVE-2025-37749 | known affected: 624 recommended: 533 | 2026-07-31T01:16:22+00:00 | Vulnerability · Source |
| CVE-2025-37751 | suse_vex | SUSE CVE CVE-2025-37751 | first fixed: 2 known affected: 394 known not affected: 344 recommended: 283 | 2026-07-31T01:16:19+00:00 | Vulnerability · Source |
| CVE-2025-37775 | suse_vex | SUSE CVE CVE-2025-37775 | known affected: 16 known not affected: 433 | 2026-07-31T01:16:11+00:00 | Vulnerability · Source |
| CVE-2025-37776 | suse_vex | SUSE CVE CVE-2025-37776 | known not affected: 456 | 2026-07-31T01:16:08+00:00 | Vulnerability · Source |
| CVE-2025-37777 | suse_vex | SUSE CVE CVE-2025-37777 | known not affected: 456 | 2026-07-31T01:16:06+00:00 | Vulnerability · Source |
| CVE-2025-37791 | suse_vex | SUSE CVE CVE-2025-37791 | known affected: 424 known not affected: 359 recommended: 164 | 2026-07-31T01:16:02+00:00 | Vulnerability · Source |
| CVE-2025-37802 | suse_vex | SUSE CVE CVE-2025-37802 | known not affected: 456 | 2026-07-31T01:15:57+00:00 | Vulnerability · Source |
| CVE-2025-37806 | suse_vex | SUSE CVE CVE-2025-37806 | known not affected: 449 | 2026-07-31T01:15:54+00:00 | Vulnerability · Source |
| CVE-2025-37817 | suse_vex | SUSE CVE CVE-2025-37817 | known affected: 224 known not affected: 225 | 2026-07-31T01:15:46+00:00 | Vulnerability · Source |
| CVE-2025-37818 | suse_vex | SUSE CVE CVE-2025-37818 | known not affected: 449 | 2026-07-31T01:15:44+00:00 | Vulnerability · Source |
| CVE-2025-37822 | suse_vex | SUSE CVE CVE-2025-37822 | known not affected: 468 | 2026-07-31T01:15:41+00:00 | Vulnerability · Source |
| CVE-2025-37834 | suse_vex | SUSE CVE CVE-2025-37834 | known not affected: 456 | 2026-07-31T01:15:38+00:00 | Vulnerability · Source |
| CVE-2025-37838 | suse_vex | SUSE CVE CVE-2025-37838 | known not affected: 348 recommended: 53 | 2026-07-31T01:15:36+00:00 | Vulnerability · Source |
| CVE-2025-37845 | suse_vex | SUSE CVE CVE-2025-37845 | first fixed: 2 known not affected: 397 recommended: 172 | 2026-07-31T01:15:33+00:00 | Vulnerability · Source |
| CVE-2025-37849 | suse_vex | SUSE CVE CVE-2025-37849 | first fixed: 2 known affected: 506 known not affected: 196 recommended: 591 | 2026-07-31T01:15:30+00:00 | Vulnerability · Source |
| CVE-2025-37857 | suse_vex | SUSE CVE CVE-2025-37857 | known affected: 275 known not affected: 68 | 2026-07-31T01:15:26+00:00 | Vulnerability · Source |
| CVE-2025-37858 | suse_vex | SUSE CVE CVE-2025-37858 | known affected: 394 known not affected: 208 recommended: 354 | 2026-07-31T01:15:23+00:00 | Vulnerability · Source |
| CVE-2025-37869 | suse_vex | SUSE CVE CVE-2025-37869 | known affected: 451 known not affected: 317 recommended: 164 | 2026-07-31T01:15:20+00:00 | Vulnerability · Source |
| CVE-2025-37876 | suse_vex | SUSE CVE CVE-2025-37876 | known not affected: 455 | 2026-07-31T01:15:16+00:00 | Vulnerability · Source |
| CVE-2025-37880 | suse_vex | SUSE CVE CVE-2025-37880 | known not affected: 449 | 2026-07-31T01:15:12+00:00 | Vulnerability · Source |
| CVE-2025-37883 | suse_vex | SUSE CVE CVE-2025-37883 | known affected: 180 known not affected: 120 | 2026-07-31T01:15:09+00:00 | Vulnerability · Source |
| CVE-2025-37894 | suse_vex | SUSE CVE CVE-2025-37894 | known not affected: 375 recommended: 53 | 2026-07-31T01:15:01+00:00 | Vulnerability · Source |
| CVE-2025-37906 | suse_vex | SUSE CVE CVE-2025-37906 | known not affected: 455 | 2026-07-31T01:14:56+00:00 | Vulnerability · Source |
| CVE-2025-37908 | suse_vex | SUSE CVE CVE-2025-37908 | known not affected: 375 recommended: 53 | 2026-07-31T01:14:54+00:00 | Vulnerability · Source |
| CVE-2025-37926 | suse_vex | SUSE CVE CVE-2025-37926 | known not affected: 449 | 2026-07-31T01:14:42+00:00 | Vulnerability · Source |