VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
306232 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-37884 | suse_vex | SUSE CVE CVE-2025-37884 | known affected: 502 known not affected: 334 recommended: 396 | 2026-10-10T16:40:36+00:00 | Vulnerability · Source |
| CVE-2025-37908 | suse_vex | SUSE CVE CVE-2025-37908 | known not affected: 505 recommended: 78 | 2026-10-10T16:40:33+00:00 | Vulnerability · Source |
| CVE-2025-37910 | suse_vex | SUSE CVE CVE-2025-37910 | known not affected: 520 recommended: 78 | 2026-10-10T16:40:30+00:00 | Vulnerability · Source |
| CVE-2025-37917 | suse_vex | SUSE CVE CVE-2025-37917 | known affected: 437 known not affected: 399 recommended: 381 | 2026-10-10T16:40:26+00:00 | Vulnerability · Source |
| CVE-2025-37918 | suse_vex | SUSE CVE CVE-2025-37918 | known affected: 394 known not affected: 427 recommended: 396 | 2026-10-10T16:40:24+00:00 | Vulnerability · Source |
| CVE-2025-37929 | suse_vex | SUSE CVE CVE-2025-37929 | known affected: 394 known not affected: 427 recommended: 396 | 2026-10-10T16:40:21+00:00 | Vulnerability · Source |
| CVE-2025-37935 | suse_vex | SUSE CVE CVE-2025-37935 | known affected: 67 known not affected: 453 recommended: 78 | 2026-10-10T16:40:19+00:00 | Vulnerability · Source |
| CVE-2025-37936 | suse_vex | SUSE CVE CVE-2025-37936 | known affected: 504 known not affected: 332 recommended: 381 | 2026-10-10T16:40:16+00:00 | Vulnerability · Source |
| CVE-2025-37937 | suse_vex | SUSE CVE CVE-2025-37937 | known affected: 712 known not affected: 109 recommended: 396 | 2026-10-10T16:40:15+00:00 | Vulnerability · Source |
| CVE-2025-37954 | suse_vex | SUSE CVE CVE-2025-37954 | known affected: 580 known not affected: 256 recommended: 396 | 2026-10-10T16:40:12+00:00 | Vulnerability · Source |
| CVE-2025-37955 | suse_vex | SUSE CVE CVE-2025-37955 | known affected: 69 known not affected: 438 recommended: 176 | 2026-10-10T16:40:10+00:00 | Vulnerability · Source |
| CVE-2025-37957 | suse_vex | SUSE CVE CVE-2025-37957 | known affected: 580 known not affected: 256 recommended: 400 | 2026-10-10T16:40:08+00:00 | Vulnerability · Source |
| CVE-2025-37958 | suse_vex | SUSE CVE CVE-2025-37958 | known affected: 471 known not affected: 187 recommended: 692 | 2026-10-10T16:40:06+00:00 | Vulnerability · Source |
| CVE-2025-37968 | suse_vex | SUSE CVE CVE-2025-37968 | known affected: 770 known not affected: 66 recommended: 381 | 2026-10-10T16:40:03+00:00 | Vulnerability · Source |
| CVE-2025-37978 | suse_vex | SUSE CVE CVE-2025-37978 | known affected: 461 known not affected: 360 recommended: 396 | 2026-10-10T16:40:00+00:00 | Vulnerability · Source |
| CVE-2025-37980 | suse_vex | SUSE CVE CVE-2025-37980 | known affected: 731 known not affected: 49 recommended: 433 | 2026-10-10T16:39:58+00:00 | Vulnerability · Source |
| CVE-2025-37981 | suse_vex | SUSE CVE CVE-2025-37981 | known affected: 461 known not affected: 414 recommended: 171 | 2026-10-10T16:39:56+00:00 | Vulnerability · Source |
| CVE-2025-37983 | suse_vex | SUSE CVE CVE-2025-37983 | known affected: 716 known not affected: 43 recommended: 396 | 2026-10-10T16:39:54+00:00 | Vulnerability · Source |
| CVE-2025-37989 | suse_vex | SUSE CVE CVE-2025-37989 | known affected: 688 known not affected: 79 recommended: 419 | 2026-10-10T16:39:52+00:00 | Vulnerability · Source |
| CVE-2025-37997 | suse_vex | SUSE CVE CVE-2025-37997 | known affected: 387 known not affected: 276 recommended: 669 | 2026-10-10T16:39:50+00:00 | Vulnerability · Source |
| CVE-2025-38005 | suse_vex | SUSE CVE CVE-2025-38005 | known affected: 522 known not affected: 299 recommended: 396 | 2026-10-10T16:39:47+00:00 | Vulnerability · Source |
| CVE-2025-38025 | suse_vex | SUSE CVE CVE-2025-38025 | known not affected: 509 | 2026-10-10T16:39:44+00:00 | Vulnerability · Source |
| CVE-2025-38037 | suse_vex | SUSE CVE CVE-2025-38037 | known affected: 391 known not affected: 70 | 2026-10-10T16:39:43+00:00 | Vulnerability · Source |
| CVE-2025-38043 | suse_vex | SUSE CVE CVE-2025-38043 | known affected: 522 known not affected: 299 recommended: 396 | 2026-10-10T16:39:40+00:00 | Vulnerability · Source |
| CVE-2025-38045 | suse_vex | SUSE CVE CVE-2025-38045 | known affected: 516 known not affected: 317 recommended: 396 | 2026-10-10T16:39:38+00:00 | Vulnerability · Source |
| CVE-2025-38055 | suse_vex | SUSE CVE CVE-2025-38055 | known affected: 488 known not affected: 407 recommended: 171 | 2026-10-10T16:39:35+00:00 | Vulnerability · Source |
| CVE-2025-38058 | suse_vex | SUSE CVE CVE-2025-38058 | known affected: 754 known not affected: 34 recommended: 509 | 2026-10-10T16:39:32+00:00 | Vulnerability · Source |
| CVE-2025-38060 | suse_vex | SUSE CVE CVE-2025-38060 | known affected: 415 known not affected: 332 recommended: 488 | 2026-10-10T16:39:29+00:00 | Vulnerability · Source |
| CVE-2025-38064 | suse_vex | SUSE CVE CVE-2025-38064 | known affected: 786 known not affected: 2 recommended: 419 | 2026-10-10T16:39:26+00:00 | Vulnerability · Source |
| CVE-2025-38068 | suse_vex | SUSE CVE CVE-2025-38068 | known affected: 528 known not affected: 77 recommended: 633 | 2026-10-10T16:39:23+00:00 | Vulnerability · Source |
| CVE-2025-38072 | suse_vex | SUSE CVE CVE-2025-38072 | known affected: 746 known not affected: 36 recommended: 419 | 2026-10-10T16:39:20+00:00 | Vulnerability · Source |
| CVE-2025-38077 | suse_vex | SUSE CVE CVE-2025-38077 | known affected: 522 known not affected: 299 recommended: 396 | 2026-10-10T16:39:18+00:00 | Vulnerability · Source |
| CVE-2025-38081 | suse_vex | SUSE CVE CVE-2025-38081 | known affected: 394 known not affected: 427 recommended: 396 | 2026-10-10T16:39:15+00:00 | Vulnerability · Source |
| CVE-2025-38083 | suse_vex | SUSE CVE CVE-2025-38083 | known affected: 454 known not affected: 112 recommended: 807 | 2026-10-10T16:39:12+00:00 | Vulnerability · Source |
| CVE-2025-38087 | suse_vex | SUSE CVE CVE-2025-38087 | known affected: 396 known not affected: 442 recommended: 612 | 2026-10-10T16:39:09+00:00 | Vulnerability · Source |
| CVE-2025-38090 | suse_vex | SUSE CVE CVE-2025-38090 | known affected: 396 known not affected: 442 recommended: 472 | 2026-10-10T16:39:07+00:00 | Vulnerability · Source |
| CVE-2025-38104 | suse_vex | SUSE CVE CVE-2025-38104 | known affected: 461 known not affected: 339 recommended: 396 | 2026-10-10T16:39:04+00:00 | Vulnerability · Source |
| CVE-2025-38107 | suse_vex | SUSE CVE CVE-2025-38107 | known affected: 463 known not affected: 375 recommended: 472 | 2026-10-10T16:39:01+00:00 | Vulnerability · Source |
| CVE-2025-38108 | suse_vex | SUSE CVE CVE-2025-38108 | known affected: 645 known not affected: 139 recommended: 495 | 2026-10-10T16:38:59+00:00 | Vulnerability · Source |
| CVE-2025-38126 | suse_vex | SUSE CVE CVE-2025-38126 | known affected: 746 known not affected: 36 recommended: 419 | 2026-10-10T16:38:56+00:00 | Vulnerability · Source |
| CVE-2025-38132 | suse_vex | SUSE CVE CVE-2025-38132 | known affected: 437 known not affected: 399 recommended: 396 | 2026-10-10T16:38:54+00:00 | Vulnerability · Source |
| CVE-2025-38146 | suse_vex | SUSE CVE CVE-2025-38146 | known affected: 587 known not affected: 262 recommended: 472 | 2026-10-10T16:38:51+00:00 | Vulnerability · Source |
| CVE-2025-38147 | suse_vex | SUSE CVE CVE-2025-38147 | known affected: 746 known not affected: 36 recommended: 419 | 2026-10-10T16:38:50+00:00 | Vulnerability · Source |
| CVE-2025-38156 | suse_vex | SUSE CVE CVE-2025-38156 | known affected: 2 known not affected: 524 recommended: 154 | 2026-10-10T16:38:47+00:00 | Vulnerability · Source |
| CVE-2025-38187 | suse_vex | SUSE CVE CVE-2025-38187 | known affected: 437 known not affected: 399 recommended: 396 | 2026-10-10T16:38:43+00:00 | Vulnerability · Source |
| CVE-2025-38194 | suse_vex | SUSE CVE CVE-2025-38194 | known affected: 394 known not affected: 497 recommended: 318 | 2026-10-10T16:38:40+00:00 | Vulnerability · Source |
| CVE-2025-38197 | suse_vex | SUSE CVE CVE-2025-38197 | known affected: 539 known not affected: 299 recommended: 472 | 2026-10-10T16:38:39+00:00 | Vulnerability · Source |
| CVE-2025-38199 | suse_vex | SUSE CVE CVE-2025-38199 | known not affected: 451 recommended: 27 | 2026-10-10T16:38:37+00:00 | Vulnerability · Source |
| CVE-2025-38201 | suse_vex | SUSE CVE CVE-2025-38201 | known affected: 636 known not affected: 217 recommended: 472 | 2026-10-10T16:38:35+00:00 | Vulnerability · Source |
| CVE-2025-38227 | suse_vex | SUSE CVE CVE-2025-38227 | known affected: 396 known not affected: 442 recommended: 472 | 2026-10-10T16:38:31+00:00 | Vulnerability · Source |