VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283449 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-39180 | suse_vex | SUSE CVE CVE-2023-39180 | known not affected: 506 | 2026-07-25T02:35:33+00:00 | Vulnerability · Source |
| CVE-2023-39190 | suse_vex | SUSE CVE CVE-2023-39190 | known not affected: 337 | 2026-07-25T02:35:31+00:00 | Vulnerability · Source |
| CVE-2023-39328 | suse_vex | SUSE CVE CVE-2023-39328 | known affected: 137 known not affected: 134 | 2026-07-25T02:35:29+00:00 | Vulnerability · Source |
| CVE-2023-39368 | suse_vex | SUSE CVE CVE-2023-39368 | known affected: 12 known not affected: 67 recommended: 52 | 2026-07-25T02:35:26+00:00 | Vulnerability · Source |
| CVE-2023-39434 | suse_vex | SUSE CVE CVE-2023-39434 | known affected: 95 known not affected: 85 recommended: 803 | 2026-07-25T02:35:24+00:00 | Vulnerability · Source |
| CVE-2023-39615 | suse_vex | SUSE CVE CVE-2023-39615 | known affected: 284 recommended: 536 | 2026-07-25T02:35:22+00:00 | Vulnerability · Source |
| CVE-2023-40217 | suse_vex | SUSE CVE CVE-2023-40217 | known affected: 327 recommended: 1823 | 2026-07-25T02:35:20+00:00 | Vulnerability · Source |
| CVE-2023-40360 | suse_vex | SUSE CVE CVE-2023-40360 | known not affected: 1299 | 2026-07-25T02:35:18+00:00 | Vulnerability · Source |
| CVE-2023-40397 | suse_vex | SUSE CVE CVE-2023-40397 | known affected: 35 known not affected: 96 recommended: 598 | 2026-07-25T02:35:16+00:00 | Vulnerability · Source |
| CVE-2023-40400 | suse_vex | SUSE CVE CVE-2023-40400 | known not affected: 143 | 2026-07-25T02:35:14+00:00 | Vulnerability · Source |
| CVE-2023-40414 | suse_vex | SUSE CVE CVE-2023-40414 | known affected: 69 known not affected: 56 recommended: 649 | 2026-07-25T02:35:12+00:00 | Vulnerability · Source |
| CVE-2023-40474 | suse_vex | SUSE CVE CVE-2023-40474 | known affected: 351 recommended: 1546 | 2026-07-25T02:35:09+00:00 | Vulnerability · Source |
| CVE-2023-40477 | suse_vex | SUSE CVE CVE-2023-40477 | known affected: 22 recommended: 205 | 2026-07-25T02:35:07+00:00 | Vulnerability · Source |
| CVE-2023-40546 | suse_vex | SUSE CVE CVE-2023-40546 | known affected: 433 recommended: 57 | 2026-07-25T02:35:05+00:00 | Vulnerability · Source |
| CVE-2023-40548 | suse_vex | SUSE CVE CVE-2023-40548 | known affected: 394 known not affected: 34 recommended: 57 | 2026-07-25T02:35:04+00:00 | Vulnerability · Source |
| CVE-2023-40550 | suse_vex | SUSE CVE CVE-2023-40550 | known affected: 433 recommended: 57 | 2026-07-25T02:35:02+00:00 | Vulnerability · Source |
| CVE-2023-40551 | suse_vex | SUSE CVE CVE-2023-40551 | known affected: 433 recommended: 57 | 2026-07-25T02:34:59+00:00 | Vulnerability · Source |
| CVE-2023-41080 | suse_vex | SUSE CVE CVE-2023-41080 | known affected: 521 recommended: 398 | 2026-07-25T02:34:57+00:00 | Vulnerability · Source |
| CVE-2023-41334 | suse_vex | SUSE CVE CVE-2023-41334 | recommended: 6 | 2026-07-25T02:34:55+00:00 | Vulnerability · Source |
| CVE-2023-41358 | suse_vex | SUSE CVE CVE-2023-41358 | known affected: 89 recommended: 635 | 2026-07-25T02:34:53+00:00 | Vulnerability · Source |
| CVE-2023-41913 | suse_vex | SUSE CVE CVE-2023-41913 | known affected: 31 known not affected: 53 recommended: 206 | 2026-07-25T02:34:51+00:00 | Vulnerability · Source |
| CVE-2023-41983 | suse_vex | SUSE CVE CVE-2023-41983 | known affected: 109 recommended: 787 | 2026-07-25T02:34:49+00:00 | Vulnerability · Source |
| CVE-2023-41993 | suse_vex | SUSE CVE CVE-2023-41993 | known affected: 95 known not affected: 115 recommended: 807 | 2026-07-25T02:34:46+00:00 | Vulnerability · Source |
| CVE-2023-42363 | suse_vex | SUSE CVE CVE-2023-42363 | known affected: 21 known not affected: 1 recommended: 122 | 2026-07-25T02:34:44+00:00 | Vulnerability · Source |
| CVE-2023-42753 | suse_vex | SUSE CVE CVE-2023-42753 | known affected: 215 known not affected: 142 recommended: 1665 | 2026-07-25T02:34:41+00:00 | Vulnerability · Source |
| CVE-2023-42755 | suse_vex | SUSE CVE CVE-2023-42755 | known affected: 424 known not affected: 45 recommended: 417 | 2026-07-25T02:34:38+00:00 | Vulnerability · Source |
| CVE-2023-42852 | suse_vex | SUSE CVE CVE-2023-42852 | known affected: 109 recommended: 787 | 2026-07-25T02:34:36+00:00 | Vulnerability · Source |
| CVE-2023-42916 | suse_vex | SUSE CVE CVE-2023-42916 | known affected: 110 recommended: 779 | 2026-07-25T02:34:34+00:00 | Vulnerability · Source |
| CVE-2023-42917 | suse_vex | SUSE CVE CVE-2023-42917 | known affected: 110 recommended: 779 | 2026-07-25T02:34:32+00:00 | Vulnerability · Source |
| CVE-2023-43090 | suse_vex | SUSE CVE CVE-2023-43090 | known not affected: 169 recommended: 61 | 2026-07-25T02:34:30+00:00 | Vulnerability · Source |
| CVE-2023-43114 | suse_vex | SUSE CVE CVE-2023-43114 | known not affected: 2120 recommended: 528 | 2026-07-25T02:34:28+00:00 | Vulnerability · Source |
| CVE-2023-43115 | suse_vex | SUSE CVE CVE-2023-43115 | known affected: 43 known not affected: 1 recommended: 165 | 2026-07-25T02:34:26+00:00 | Vulnerability · Source |
| CVE-2023-43490 | suse_vex | SUSE CVE CVE-2023-43490 | known affected: 12 known not affected: 67 recommended: 52 | 2026-07-25T02:34:24+00:00 | Vulnerability · Source |
| CVE-2023-43789 | suse_vex | SUSE CVE CVE-2023-43789 | known affected: 475 recommended: 124 | 2026-07-25T02:34:21+00:00 | Vulnerability · Source |
| CVE-2023-44398 | suse_vex | SUSE CVE CVE-2023-44398 | known not affected: 146 recommended: 9 | 2026-07-25T02:34:19+00:00 | Vulnerability · Source |
| CVE-2023-44429 | suse_vex | SUSE CVE CVE-2023-44429 | known affected: 180 known not affected: 526 recommended: 1052 | 2026-07-25T02:34:17+00:00 | Vulnerability · Source |
| CVE-2023-44446 | suse_vex | SUSE CVE CVE-2023-44446 | known affected: 175 recommended: 1406 | 2026-07-25T02:34:15+00:00 | Vulnerability · Source |
| CVE-2023-44487 | suse_vex | SUSE CVE CVE-2023-44487 | first fixed: 26 known affected: 317 known not affected: 296 recommended: 2727 | 2026-07-25T02:34:12+00:00 | Vulnerability · Source |
| CVE-2023-45221 | suse_vex | SUSE CVE CVE-2023-45221 | known not affected: 2 recommended: 173 | 2026-07-25T02:34:09+00:00 | Vulnerability · Source |
| CVE-2023-45230 | suse_vex | SUSE CVE CVE-2023-45230 | known affected: 150 known not affected: 21 recommended: 153 | 2026-07-25T02:34:06+00:00 | Vulnerability · Source |
| CVE-2023-45232 | suse_vex | SUSE CVE CVE-2023-45232 | known affected: 153 known not affected: 21 recommended: 142 | 2026-07-25T02:34:04+00:00 | Vulnerability · Source |
| CVE-2023-45236 | suse_vex | SUSE CVE CVE-2023-45236 | known affected: 249 recommended: 111 | 2026-07-25T02:34:02+00:00 | Vulnerability · Source |
| CVE-2023-45802 | suse_vex | SUSE CVE CVE-2023-45802 | known affected: 531 known not affected: 2 recommended: 272 | 2026-07-25T02:33:59+00:00 | Vulnerability · Source |
| CVE-2023-45863 | suse_vex | SUSE CVE CVE-2023-45863 | known affected: 264 recommended: 1084 | 2026-07-25T02:33:57+00:00 | Vulnerability · Source |
| CVE-2023-45866 | suse_vex | SUSE CVE CVE-2023-45866 | known affected: 100 known not affected: 35 recommended: 102 | 2026-07-25T02:33:55+00:00 | Vulnerability · Source |
| CVE-2023-45919 | suse_vex | SUSE CVE CVE-2023-45919 | known affected: 935 known not affected: 113 recommended: 1110 | 2026-07-25T02:33:52+00:00 | Vulnerability · Source |
| CVE-2023-45922 | suse_vex | SUSE CVE CVE-2023-45922 | known affected: 935 known not affected: 113 recommended: 1110 | 2026-07-25T02:33:49+00:00 | Vulnerability · Source |
| CVE-2023-45935 | suse_vex | SUSE CVE CVE-2023-45935 | known affected: 394 known not affected: 720 recommended: 1649 | 2026-07-25T02:33:47+00:00 | Vulnerability · Source |
| CVE-2023-46045 | suse_vex | SUSE CVE CVE-2023-46045 | known affected: 469 known not affected: 18 recommended: 185 | 2026-07-25T02:33:45+00:00 | Vulnerability · Source |
| CVE-2023-46048 | suse_vex | SUSE CVE CVE-2023-46048 | known not affected: 4905 recommended: 1448 | 2026-07-25T02:33:43+00:00 | Vulnerability · Source |