VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292108 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-6199 | suse_vex | SUSE CVE CVE-2025-6199 | known affected: 444 known not affected: 83 recommended: 312 | 2026-07-25T01:09:47+00:00 | Vulnerability · Source |
| CVE-2025-6424 | suse_vex | SUSE CVE CVE-2025-6424 | known affected: 37 recommended: 361 | 2026-07-25T01:09:43+00:00 | Vulnerability · Source |
| CVE-2025-6425 | suse_vex | SUSE CVE CVE-2025-6425 | known affected: 37 recommended: 361 | 2026-07-25T01:09:42+00:00 | Vulnerability · Source |
| CVE-2025-6435 | suse_vex | SUSE CVE CVE-2025-6435 | known affected: 37 recommended: 342 | 2026-07-25T01:09:38+00:00 | Vulnerability · Source |
| CVE-2025-6494 | suse_vex | SUSE CVE CVE-2025-6494 | known not affected: 318 | 2026-07-25T01:09:34+00:00 | Vulnerability · Source |
| CVE-2025-7339 | suse_vex | SUSE CVE CVE-2025-7339 | known affected: 156 known not affected: 326 recommended: 1 | 2026-07-25T01:09:32+00:00 | Vulnerability · Source |
| CVE-2025-7394 | suse_vex | SUSE CVE CVE-2025-7394 | known not affected: 304 | 2026-07-25T01:09:29+00:00 | Vulnerability · Source |
| CVE-2025-7396 | suse_vex | SUSE CVE CVE-2025-7396 | known not affected: 304 | 2026-07-25T01:09:27+00:00 | Vulnerability · Source |
| CVE-2025-8033 | suse_vex | SUSE CVE CVE-2025-8033 | known affected: 37 recommended: 357 | 2026-07-25T01:09:22+00:00 | Vulnerability · Source |
| CVE-2025-8067 | suse_vex | SUSE CVE CVE-2025-8067 | known affected: 451 recommended: 259 | 2026-07-25T01:09:16+00:00 | Vulnerability · Source |
| CVE-2025-8114 | suse_vex | SUSE CVE CVE-2025-8114 | known affected: 497 recommended: 128 | 2026-07-25T01:09:15+00:00 | Vulnerability · Source |
| CVE-2025-8734 | suse_vex | SUSE CVE CVE-2025-8734 | known affected: 130 | 2026-07-25T01:09:07+00:00 | Vulnerability · Source |
| CVE-2025-9375 | suse_vex | SUSE CVE CVE-2025-9375 | known affected: 397 known not affected: 56 recommended: 25 | 2026-07-25T01:09:03+00:00 | Vulnerability · Source |
| CVE-2025-9403 | suse_vex | SUSE CVE CVE-2025-9403 | known affected: 444 known not affected: 11 recommended: 77 | 2026-07-25T01:09:02+00:00 | Vulnerability · Source |
| CVE-2025-9901 | suse_vex | SUSE CVE CVE-2025-9901 | known affected: 391 known not affected: 1 | 2026-07-25T01:08:59+00:00 | Vulnerability · Source |
| CVE-2025-10532 | suse_vex | SUSE CVE CVE-2025-10532 | known affected: 37 recommended: 187 | 2026-07-25T01:08:54+00:00 | Vulnerability · Source |
| CVE-2025-11713 | suse_vex | SUSE CVE CVE-2025-11713 | known affected: 70 recommended: 180 | 2026-07-25T01:08:46+00:00 | Vulnerability · Source |
| CVE-2025-11714 | suse_vex | SUSE CVE CVE-2025-11714 | known affected: 70 recommended: 185 | 2026-07-25T01:08:44+00:00 | Vulnerability · Source |
| CVE-2025-11715 | suse_vex | SUSE CVE CVE-2025-11715 | known affected: 70 recommended: 185 | 2026-07-25T01:08:43+00:00 | Vulnerability · Source |
| CVE-2025-11731 | suse_vex | SUSE CVE CVE-2025-11731 | known affected: 435 recommended: 143 | 2026-07-25T01:08:41+00:00 | Vulnerability · Source |
| CVE-2025-12199 | suse_vex | SUSE CVE CVE-2025-12199 | known not affected: 53 | 2026-07-25T01:08:38+00:00 | Vulnerability · Source |
| CVE-2025-12464 | suse_vex | SUSE CVE CVE-2025-12464 | known affected: 614 known not affected: 394 recommended: 1145 | 2026-07-25T01:08:36+00:00 | Vulnerability · Source |
| CVE-2025-12816 | suse_vex | SUSE CVE CVE-2025-12816 | known affected: 116 known not affected: 381 recommended: 115 | 2026-07-25T01:08:34+00:00 | Vulnerability · Source |
| CVE-2025-13945 | suse_vex | SUSE CVE CVE-2025-13945 | known not affected: 237 recommended: 201 | 2026-07-25T01:08:24+00:00 | Vulnerability · Source |
| CVE-2025-14575 | suse_vex | SUSE CVE CVE-2025-14575 | known affected: 1461 recommended: 37 | 2026-07-25T01:08:18+00:00 | Vulnerability · Source |
| CVE-2025-15224 | suse_vex | SUSE CVE CVE-2025-15224 | known affected: 497 known not affected: 9 recommended: 117 | 2026-07-25T01:08:14+00:00 | Vulnerability · Source |
| CVE-2025-21629 | suse_vex | SUSE CVE CVE-2025-21629 | known affected: 394 known not affected: 274 recommended: 407 | 2026-07-25T01:08:02+00:00 | Vulnerability · Source |
| CVE-2025-21645 | suse_vex | SUSE CVE CVE-2025-21645 | known affected: 451 known not affected: 229 recommended: 363 | 2026-07-25T01:07:52+00:00 | Vulnerability · Source |
| CVE-2025-21658 | suse_vex | SUSE CVE CVE-2025-21658 | known affected: 417 known not affected: 158 recommended: 603 | 2026-07-25T01:07:36+00:00 | Vulnerability · Source |
| CVE-2025-21665 | suse_vex | SUSE CVE CVE-2025-21665 | known affected: 552 known not affected: 200 recommended: 310 | 2026-07-25T01:07:30+00:00 | Vulnerability · Source |
| CVE-2025-21669 | suse_vex | SUSE CVE CVE-2025-21669 | known affected: 524 known not affected: 194 recommended: 406 | 2026-07-25T01:07:22+00:00 | Vulnerability · Source |
| CVE-2025-21670 | suse_vex | SUSE CVE CVE-2025-21670 | known affected: 410 known not affected: 308 recommended: 363 | 2026-07-25T01:07:21+00:00 | Vulnerability · Source |
| CVE-2025-21675 | suse_vex | SUSE CVE CVE-2025-21675 | known affected: 524 known not affected: 194 recommended: 363 | 2026-07-25T01:07:12+00:00 | Vulnerability · Source |
| CVE-2025-21679 | suse_vex | SUSE CVE CVE-2025-21679 | known not affected: 352 | 2026-07-25T01:07:08+00:00 | Vulnerability · Source |
| CVE-2025-21681 | suse_vex | SUSE CVE CVE-2025-21681 | known affected: 410 known not affected: 276 recommended: 400 | 2026-07-25T01:07:04+00:00 | Vulnerability · Source |
| CVE-2025-21684 | suse_vex | SUSE CVE CVE-2025-21684 | known affected: 506 known not affected: 174 recommended: 363 | 2026-07-25T01:07:00+00:00 | Vulnerability · Source |
| CVE-2025-21692 | suse_vex | SUSE CVE CVE-2025-21692 | known affected: 373 known not affected: 157 recommended: 715 | 2026-07-25T01:06:49+00:00 | Vulnerability · Source |
| CVE-2025-21705 | suse_vex | SUSE CVE CVE-2025-21705 | known affected: 394 known not affected: 308 recommended: 363 | 2026-07-25T01:06:35+00:00 | Vulnerability · Source |
| CVE-2025-21708 | suse_vex | SUSE CVE CVE-2025-21708 | known affected: 638 known not affected: 28 recommended: 402 | 2026-07-25T01:06:29+00:00 | Vulnerability · Source |
| CVE-2025-21716 | suse_vex | SUSE CVE CVE-2025-21716 | known affected: 394 known not affected: 308 recommended: 363 | 2026-07-25T01:06:20+00:00 | Vulnerability · Source |
| CVE-2025-21720 | suse_vex | SUSE CVE CVE-2025-21720 | known affected: 440 known not affected: 287 recommended: 407 | 2026-07-25T01:06:18+00:00 | Vulnerability · Source |
| CVE-2025-21725 | suse_vex | SUSE CVE CVE-2025-21725 | known affected: 394 known not affected: 308 recommended: 363 | 2026-07-25T01:06:15+00:00 | Vulnerability · Source |
| CVE-2025-21739 | suse_vex | SUSE CVE CVE-2025-21739 | known affected: 524 known not affected: 158 recommended: 436 | 2026-07-25T01:05:56+00:00 | Vulnerability · Source |
| CVE-2025-21740 | suse_vex | SUSE CVE CVE-2025-21740 | known not affected: 352 | 2026-07-25T01:05:54+00:00 | Vulnerability · Source |
| CVE-2025-21745 | suse_vex | SUSE CVE CVE-2025-21745 | known affected: 543 known not affected: 137 recommended: 403 | 2026-07-25T01:05:48+00:00 | Vulnerability · Source |
| CVE-2025-21749 | suse_vex | SUSE CVE CVE-2025-21749 | known affected: 645 known not affected: 109 recommended: 362 | 2026-07-25T01:05:46+00:00 | Vulnerability · Source |
| CVE-2025-21757 | suse_vex | SUSE CVE CVE-2025-21757 | known not affected: 352 | 2026-07-25T01:05:41+00:00 | Vulnerability · Source |
| CVE-2025-21762 | suse_vex | SUSE CVE CVE-2025-21762 | known affected: 648 known not affected: 6 recommended: 435 | 2026-07-25T01:05:34+00:00 | Vulnerability · Source |
| CVE-2025-21768 | suse_vex | SUSE CVE CVE-2025-21768 | known affected: 664 known not affected: 22 recommended: 444 | 2026-07-25T01:05:26+00:00 | Vulnerability · Source |
| CVE-2025-21772 | suse_vex | SUSE CVE CVE-2025-21772 | known affected: 461 recommended: 828 | 2026-07-25T01:05:24+00:00 | Vulnerability · Source |