VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294149 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-53784 | suse_vex | SUSE CVE CVE-2023-53784 | known affected: 394 known not affected: 318 recommended: 259 | 2026-07-25T02:12:14+00:00 | Vulnerability · Source |
| CVE-2023-53792 | suse_vex | SUSE CVE CVE-2023-53792 | known affected: 354 known not affected: 206 recommended: 455 | 2026-07-25T02:12:06+00:00 | Vulnerability · Source |
| CVE-2023-53794 | suse_vex | SUSE CVE CVE-2023-53794 | known affected: 463 known not affected: 78 recommended: 479 | 2026-07-25T02:12:01+00:00 | Vulnerability · Source |
| CVE-2023-53840 | suse_vex | SUSE CVE CVE-2023-53840 | known affected: 450 known not affected: 170 recommended: 219 | 2026-07-25T02:11:16+00:00 | Vulnerability · Source |
| CVE-2023-53865 | suse_vex | SUSE CVE CVE-2023-53865 | known affected: 506 known not affected: 206 recommended: 230 | 2026-07-25T02:10:31+00:00 | Vulnerability · Source |
| CVE-2023-54026 | suse_vex | SUSE CVE CVE-2023-54026 | known affected: 354 known not affected: 231 recommended: 455 | 2026-07-25T02:09:29+00:00 | Vulnerability · Source |
| CVE-2023-54059 | suse_vex | SUSE CVE CVE-2023-54059 | known not affected: 453 | 2026-07-25T02:08:43+00:00 | Vulnerability · Source |
| CVE-2023-54066 | suse_vex | SUSE CVE CVE-2023-54066 | known affected: 506 known not affected: 231 recommended: 230 | 2026-07-25T02:08:34+00:00 | Vulnerability · Source |
| CVE-2023-54087 | suse_vex | SUSE CVE CVE-2023-54087 | known affected: 234 known not affected: 187 | 2026-07-25T02:07:59+00:00 | Vulnerability · Source |
| CVE-2023-54112 | suse_vex | SUSE CVE CVE-2023-54112 | known affected: 608 known not affected: 99 recommended: 253 | 2026-07-25T02:07:28+00:00 | Vulnerability · Source |
| CVE-2023-54121 | suse_vex | SUSE CVE CVE-2023-54121 | known affected: 628 known not affected: 77 recommended: 267 | 2026-07-25T02:07:11+00:00 | Vulnerability · Source |
| CVE-2023-54128 | suse_vex | SUSE CVE CVE-2023-54128 | known affected: 429 known not affected: 341 recommended: 87 | 2026-07-25T02:07:01+00:00 | Vulnerability · Source |
| CVE-2023-54130 | suse_vex | SUSE CVE CVE-2023-54130 | known affected: 354 known not affected: 311 recommended: 219 | 2026-07-25T02:06:56+00:00 | Vulnerability · Source |
| CVE-2023-54145 | suse_vex | SUSE CVE CVE-2023-54145 | known affected: 638 known not affected: 99 recommended: 259 | 2026-07-25T02:06:30+00:00 | Vulnerability · Source |
| CVE-2023-54167 | suse_vex | SUSE CVE CVE-2023-54167 | known not affected: 453 | 2026-07-25T02:06:08+00:00 | Vulnerability · Source |
| CVE-2023-54177 | suse_vex | SUSE CVE CVE-2023-54177 | known affected: 470 known not affected: 83 recommended: 463 | 2026-07-25T02:05:52+00:00 | Vulnerability · Source |
| CVE-2023-54181 | suse_vex | SUSE CVE CVE-2023-54181 | known affected: 547 known not affected: 170 recommended: 230 | 2026-07-25T02:05:45+00:00 | Vulnerability · Source |
| CVE-2023-54183 | suse_vex | SUSE CVE CVE-2023-54183 | known affected: 409 known not affected: 176 recommended: 426 | 2026-07-25T02:05:42+00:00 | Vulnerability · Source |
| CVE-2023-54186 | suse_vex | SUSE CVE CVE-2023-54186 | known affected: 426 known not affected: 239 recommended: 248 | 2026-07-25T02:05:37+00:00 | Vulnerability · Source |
| CVE-2023-54202 | suse_vex | SUSE CVE CVE-2023-54202 | known affected: 440 known not affected: 188 recommended: 268 | 2026-07-25T02:05:16+00:00 | Vulnerability · Source |
| CVE-2023-54205 | suse_vex | SUSE CVE CVE-2023-54205 | known affected: 409 known not affected: 286 recommended: 196 | 2026-07-25T02:05:13+00:00 | Vulnerability · Source |
| CVE-2023-54209 | suse_vex | SUSE CVE CVE-2023-54209 | known affected: 451 known not affected: 266 recommended: 230 | 2026-07-25T02:05:05+00:00 | Vulnerability · Source |
| CVE-2023-54220 | suse_vex | SUSE CVE CVE-2023-54220 | known affected: 506 known not affected: 185 recommended: 267 | 2026-07-25T02:04:52+00:00 | Vulnerability · Source |
| CVE-2023-54239 | suse_vex | SUSE CVE CVE-2023-54239 | known not affected: 453 recommended: 29 | 2026-07-25T02:04:28+00:00 | Vulnerability · Source |
| CVE-2023-54258 | suse_vex | SUSE CVE CVE-2023-54258 | known affected: 506 known not affected: 211 recommended: 230 | 2026-07-25T02:04:05+00:00 | Vulnerability · Source |
| CVE-2023-54276 | suse_vex | SUSE CVE CVE-2023-54276 | known affected: 394 known not affected: 343 recommended: 259 | 2026-07-25T02:03:41+00:00 | Vulnerability · Source |
| CVE-2024-0853 | suse_vex | SUSE CVE CVE-2024-0853 | known not affected: 200 recommended: 62 | 2026-07-25T02:02:28+00:00 | Vulnerability · Source |
| CVE-2024-7589 | suse_vex | SUSE CVE CVE-2024-7589 | known not affected: 224 | 2026-07-25T02:00:25+00:00 | Vulnerability · Source |
| CVE-2024-26588 | suse_vex | SUSE CVE CVE-2024-26588 | known not affected: 312 | 2026-07-25T01:57:58+00:00 | Vulnerability · Source |
| CVE-2024-26639 | suse_vex | SUSE CVE CVE-2024-26639 | known not affected: 292 | 2026-07-25T01:57:22+00:00 | Vulnerability · Source |
| CVE-2024-26660 | suse_vex | SUSE CVE CVE-2024-26660 | known affected: 441 known not affected: 237 recommended: 460 | 2026-07-25T01:57:11+00:00 | Vulnerability · Source |
| CVE-2024-26690 | suse_vex | SUSE CVE CVE-2024-26690 | known not affected: 272 | 2026-07-25T01:56:58+00:00 | Vulnerability · Source |
| CVE-2024-26705 | suse_vex | SUSE CVE CVE-2024-26705 | known not affected: 272 | 2026-07-25T01:56:53+00:00 | Vulnerability · Source |
| CVE-2024-27071 | suse_vex | SUSE CVE CVE-2024-27071 | known affected: 394 known not affected: 330 recommended: 213 | 2026-07-25T01:53:30+00:00 | Vulnerability · Source |
| CVE-2024-27281 | suse_vex | SUSE CVE CVE-2024-27281 | known not affected: 313 recommended: 68 | 2026-07-25T01:53:23+00:00 | Vulnerability · Source |
| CVE-2024-35793 | suse_vex | SUSE CVE CVE-2024-35793 | known not affected: 330 | 2026-07-25T01:51:28+00:00 | Vulnerability · Source |
| CVE-2024-36460 | suse_vex | SUSE CVE CVE-2024-36460 | known not affected: 11 | 2026-07-25T01:48:42+00:00 | Vulnerability · Source |
| CVE-2024-41817 | suse_vex | SUSE CVE CVE-2024-41817 | known not affected: 393 | 2026-07-25T01:43:38+00:00 | Vulnerability · Source |
| CVE-2024-42231 | suse_vex | SUSE CVE CVE-2024-42231 | known not affected: 324 | 2026-07-25T01:42:36+00:00 | Vulnerability · Source |
| CVE-2024-42234 | suse_vex | SUSE CVE CVE-2024-42234 | known not affected: 311 | 2026-07-25T01:42:34+00:00 | Vulnerability · Source |
| CVE-2024-42326 | suse_vex | SUSE CVE CVE-2024-42326 | known not affected: 12 | 2026-07-25T01:42:01+00:00 | Vulnerability · Source |
| CVE-2024-42331 | suse_vex | SUSE CVE CVE-2024-42331 | known not affected: 12 | 2026-07-25T01:41:59+00:00 | Vulnerability · Source |
| CVE-2024-43826 | suse_vex | SUSE CVE CVE-2024-43826 | known affected: 394 known not affected: 280 recommended: 360 | 2026-07-25T01:41:47+00:00 | Vulnerability · Source |
| CVE-2024-43849 | suse_vex | SUSE CVE CVE-2024-43849 | known affected: 340 known not affected: 139 recommended: 648 | 2026-07-25T01:41:32+00:00 | Vulnerability · Source |
| CVE-2024-43868 | suse_vex | SUSE CVE CVE-2024-43868 | known not affected: 403 | 2026-07-25T01:41:23+00:00 | Vulnerability · Source |
| CVE-2024-44934 | suse_vex | SUSE CVE CVE-2024-44934 | known affected: 492 known not affected: 199 recommended: 463 | 2026-07-25T01:40:54+00:00 | Vulnerability · Source |
| CVE-2024-45027 | suse_vex | SUSE CVE CVE-2024-45027 | known not affected: 324 recommended: 59 | 2026-07-25T01:39:51+00:00 | Vulnerability · Source |
| CVE-2024-45700 | suse_vex | SUSE CVE CVE-2024-45700 | known not affected: 11 | 2026-07-25T01:39:39+00:00 | Vulnerability · Source |
| CVE-2024-46742 | suse_vex | SUSE CVE CVE-2024-46742 | known not affected: 324 | 2026-07-25T01:38:51+00:00 | Vulnerability · Source |
| CVE-2024-50244 | suse_vex | SUSE CVE CVE-2024-50244 | known not affected: 379 recommended: 6 | 2026-07-25T01:25:51+00:00 | Vulnerability · Source |