VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291864 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-22867 | suse_vex | SUSE CVE CVE-2025-22867 | known affected: 39 known not affected: 275 recommended: 56 | 2026-08-12T17:01:21+00:00 | Vulnerability · Source |
| CVE-2025-23167 | suse_vex | SUSE CVE CVE-2025-23167 | known affected: 25 known not affected: 200 recommended: 53 | 2026-08-12T17:01:10+00:00 | Vulnerability · Source |
| CVE-2025-23244 | suse_vex | SUSE CVE CVE-2025-23244 | known not affected: 66 | 2026-08-12T17:01:09+00:00 | Vulnerability · Source |
| CVE-2025-23259 | suse_vex | SUSE CVE CVE-2025-23259 | known not affected: 145 recommended: 155 | 2026-08-12T17:01:07+00:00 | Vulnerability · Source |
| CVE-2025-23309 | suse_vex | SUSE CVE CVE-2025-23309 | known not affected: 177 | 2026-08-12T17:01:05+00:00 | Vulnerability · Source |
| CVE-2025-25193 | suse_vex | SUSE CVE CVE-2025-25193 | known affected: 1 recommended: 40 | 2026-08-12T17:00:56+00:00 | Vulnerability · Source |
| CVE-2025-25468 | suse_vex | SUSE CVE CVE-2025-25468 | known not affected: 502 | 2026-08-12T17:00:55+00:00 | Vulnerability · Source |
| CVE-2025-25471 | suse_vex | SUSE CVE CVE-2025-25471 | known not affected: 502 | 2026-08-12T17:00:53+00:00 | Vulnerability · Source |
| CVE-2025-27219 | suse_vex | SUSE CVE CVE-2025-27219 | known affected: 448 known not affected: 82 recommended: 224 | 2026-08-12T17:00:45+00:00 | Vulnerability · Source |
| CVE-2025-27462 | suse_vex | SUSE CVE CVE-2025-27462 | known not affected: 218 | 2026-08-12T17:00:43+00:00 | Vulnerability · Source |
| CVE-2025-27465 | suse_vex | SUSE CVE CVE-2025-27465 | known affected: 405 known not affected: 13 recommended: 251 | 2026-08-12T17:00:41+00:00 | Vulnerability · Source |
| CVE-2025-27833 | suse_vex | SUSE CVE CVE-2025-27833 | known not affected: 106 recommended: 8 | 2026-08-12T17:00:32+00:00 | Vulnerability · Source |
| CVE-2025-27836 | suse_vex | SUSE CVE CVE-2025-27836 | known affected: 29 recommended: 104 | 2026-08-12T17:00:29+00:00 | Vulnerability · Source |
| CVE-2025-30189 | suse_vex | SUSE CVE CVE-2025-30189 | known not affected: 352 recommended: 37 | 2026-08-12T17:00:26+00:00 | Vulnerability · Source |
| CVE-2025-30348 | suse_vex | SUSE CVE CVE-2025-30348 | known affected: 1824 recommended: 794 | 2026-08-12T17:00:22+00:00 | Vulnerability · Source |
| CVE-2025-31206 | suse_vex | SUSE CVE CVE-2025-31206 | known affected: 88 recommended: 592 | 2026-08-12T17:00:17+00:00 | Vulnerability · Source |
| CVE-2025-31223 | suse_vex | SUSE CVE CVE-2025-31223 | known affected: 88 recommended: 528 | 2026-08-12T17:00:13+00:00 | Vulnerability · Source |
| CVE-2025-31936 | suse_vex | SUSE CVE CVE-2025-31936 | No product status | 2026-08-12T17:00:06+00:00 | Vulnerability · Source |
| CVE-2025-32049 | suse_vex | SUSE CVE CVE-2025-32049 | known affected: 126 recommended: 231 | 2026-08-12T17:00:02+00:00 | Vulnerability · Source |
| CVE-2025-32386 | suse_vex | SUSE CVE CVE-2025-32386 | known affected: 21 known not affected: 92 recommended: 133 | 2026-08-12T17:00:01+00:00 | Vulnerability · Source |
| CVE-2025-37821 | suse_vex | SUSE CVE CVE-2025-37821 | first fixed: 2 known affected: 62 known not affected: 387 recommended: 196 | 2026-08-12T16:59:34+00:00 | Vulnerability · Source |
| CVE-2025-37866 | suse_vex | SUSE CVE CVE-2025-37866 | known not affected: 397 | 2026-08-12T16:59:14+00:00 | Vulnerability · Source |
| CVE-2025-37868 | suse_vex | SUSE CVE CVE-2025-37868 | known affected: 394 known not affected: 352 recommended: 164 | 2026-08-12T16:59:11+00:00 | Vulnerability · Source |
| CVE-2025-37934 | suse_vex | SUSE CVE CVE-2025-37934 | known affected: 441 known not affected: 296 recommended: 164 | 2026-08-12T16:58:57+00:00 | Vulnerability · Source |
| CVE-2025-37940 | suse_vex | SUSE CVE CVE-2025-37940 | known affected: 225 known not affected: 22 | 2026-08-12T16:58:55+00:00 | Vulnerability · Source |
| CVE-2025-37948 | suse_vex | SUSE CVE CVE-2025-37948 | known affected: 462 known not affected: 54 recommended: 644 | 2026-08-12T16:58:51+00:00 | Vulnerability · Source |
| CVE-2025-37955 | suse_vex | SUSE CVE CVE-2025-37955 | first fixed: 2 known affected: 47 known not affected: 328 recommended: 174 | 2026-08-12T16:58:47+00:00 | Vulnerability · Source |
| CVE-2025-38032 | suse_vex | SUSE CVE CVE-2025-38032 | known not affected: 401 | 2026-08-12T16:58:31+00:00 | Vulnerability · Source |
| CVE-2025-38038 | suse_vex | SUSE CVE CVE-2025-38038 | first fixed: 2 known not affected: 416 recommended: 154 | 2026-08-12T16:58:29+00:00 | Vulnerability · Source |
| CVE-2025-38144 | suse_vex | SUSE CVE CVE-2025-38144 | known not affected: 416 | 2026-08-12T16:58:06+00:00 | Vulnerability · Source |
| CVE-2025-38148 | suse_vex | SUSE CVE CVE-2025-38148 | first fixed: 2 known affected: 394 known not affected: 323 recommended: 550 | 2026-08-12T16:58:03+00:00 | Vulnerability · Source |
| CVE-2025-38159 | suse_vex | SUSE CVE CVE-2025-38159 | first fixed: 2 known affected: 399 known not affected: 159 recommended: 817 | 2026-08-12T16:57:59+00:00 | Vulnerability · Source |
| CVE-2025-38178 | suse_vex | SUSE CVE CVE-2025-38178 | known not affected: 416 | 2026-08-12T16:57:52+00:00 | Vulnerability · Source |
| CVE-2025-38180 | suse_vex | SUSE CVE CVE-2025-38180 | first fixed: 2 known affected: 405 known not affected: 318 recommended: 892 | 2026-08-12T16:57:48+00:00 | Vulnerability · Source |
| CVE-2025-38186 | suse_vex | SUSE CVE CVE-2025-38186 | first fixed: 2 known affected: 394 known not affected: 367 recommended: 265 | 2026-08-12T16:57:43+00:00 | Vulnerability · Source |
| CVE-2025-38189 | suse_vex | SUSE CVE CVE-2025-38189 | first fixed: 2 known affected: 394 known not affected: 370 recommended: 265 | 2026-08-12T16:57:41+00:00 | Vulnerability · Source |
| CVE-2025-38195 | suse_vex | SUSE CVE CVE-2025-38195 | known not affected: 416 | 2026-08-12T16:57:36+00:00 | Vulnerability · Source |
| CVE-2025-38220 | suse_vex | SUSE CVE CVE-2025-38220 | first fixed: 2 known affected: 445 known not affected: 283 recommended: 550 | 2026-08-12T16:57:24+00:00 | Vulnerability · Source |
| CVE-2025-38247 | suse_vex | SUSE CVE CVE-2025-38247 | known not affected: 416 | 2026-08-12T16:57:14+00:00 | Vulnerability · Source |
| CVE-2025-38299 | suse_vex | SUSE CVE CVE-2025-38299 | first fixed: 2 known affected: 394 known not affected: 370 recommended: 265 | 2026-08-12T16:57:02+00:00 | Vulnerability · Source |
| CVE-2025-38317 | suse_vex | SUSE CVE CVE-2025-38317 | first fixed: 2 known affected: 394 known not affected: 383 recommended: 265 | 2026-08-12T16:56:57+00:00 | Vulnerability · Source |
| CVE-2025-38327 | suse_vex | SUSE CVE CVE-2025-38327 | known not affected: 416 | 2026-08-12T16:56:54+00:00 | Vulnerability · Source |
| CVE-2025-38336 | suse_vex | SUSE CVE CVE-2025-38336 | first fixed: 2 known affected: 645 known not affected: 78 recommended: 545 | 2026-08-12T16:56:51+00:00 | Vulnerability · Source |
| CVE-2025-38374 | suse_vex | SUSE CVE CVE-2025-38374 | first fixed: 2 known affected: 5 known not affected: 448 recommended: 154 | 2026-08-12T16:56:39+00:00 | Vulnerability · Source |
| CVE-2025-38375 | suse_vex | SUSE CVE CVE-2025-38375 | first fixed: 2 known affected: 496 known not affected: 36 recommended: 782 | 2026-08-12T16:56:37+00:00 | Vulnerability · Source |
| CVE-2025-38390 | suse_vex | SUSE CVE CVE-2025-38390 | first fixed: 2 known not affected: 416 recommended: 154 | 2026-08-12T16:56:33+00:00 | Vulnerability · Source |
| CVE-2025-38397 | suse_vex | SUSE CVE CVE-2025-38397 | first fixed: 2 known not affected: 416 recommended: 154 | 2026-08-12T16:56:30+00:00 | Vulnerability · Source |
| CVE-2025-38403 | suse_vex | SUSE CVE CVE-2025-38403 | first fixed: 2 known affected: 683 known not affected: 6 recommended: 648 | 2026-08-12T16:56:28+00:00 | Vulnerability · Source |
| CVE-2025-38415 | suse_vex | SUSE CVE CVE-2025-38415 | first fixed: 2 known affected: 643 known not affected: 46 recommended: 661 | 2026-08-12T16:56:25+00:00 | Vulnerability · Source |
| CVE-2025-38417 | suse_vex | SUSE CVE CVE-2025-38417 | first fixed: 2 known affected: 394 known not affected: 375 recommended: 308 | 2026-08-12T16:56:23+00:00 | Vulnerability · Source |