VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292260 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-42217 | suse_vex | SUSE CVE CVE-2026-42217 | known not affected: 101 recommended: 55 | 2026-07-15T05:14:50+00:00 | Vulnerability · Source |
| CVE-2026-42308 | suse_vex | SUSE CVE CVE-2026-42308 | recommended: 39 | 2026-07-15T05:14:41+00:00 | Vulnerability · Source |
| CVE-2026-42309 | suse_vex | SUSE CVE CVE-2026-42309 | known not affected: 51 recommended: 6 | 2026-07-15T05:14:40+00:00 | Vulnerability · Source |
| CVE-2026-42310 | suse_vex | SUSE CVE CVE-2026-42310 | recommended: 39 | 2026-07-15T05:14:39+00:00 | Vulnerability · Source |
| CVE-2026-42311 | suse_vex | SUSE CVE CVE-2026-42311 | first fixed: 4 known affected: 7 known not affected: 51 recommended: 6 | 2026-07-15T05:14:38+00:00 | Vulnerability · Source |
| CVE-2026-42498 | suse_vex | SUSE CVE CVE-2026-42498 | known affected: 524 recommended: 374 | 2026-07-15T05:14:32+00:00 | Vulnerability · Source |
| CVE-2026-42798 | suse_vex | SUSE CVE CVE-2026-42798 | known affected: 11 known not affected: 101 recommended: 14 | 2026-07-15T05:14:15+00:00 | Vulnerability · Source |
| CVE-2026-42946 | suse_vex | SUSE CVE CVE-2026-42946 | known affected: 406 recommended: 44 | 2026-07-15T05:14:11+00:00 | Vulnerability · Source |
| CVE-2026-43012 | suse_vex | SUSE CVE CVE-2026-43012 | first fixed: 2 known affected: 411 known not affected: 274 recommended: 145 | 2026-07-15T05:14:06+00:00 | Vulnerability · Source |
| CVE-2026-43014 | suse_vex | SUSE CVE CVE-2026-43014 | known affected: 287 known not affected: 4 | 2026-07-15T05:14:04+00:00 | Vulnerability · Source |
| CVE-2026-43015 | suse_vex | SUSE CVE CVE-2026-43015 | known affected: 256 known not affected: 35 | 2026-07-15T05:14:02+00:00 | Vulnerability · Source |
| CVE-2026-43045 | suse_vex | SUSE CVE CVE-2026-43045 | first fixed: 2 known affected: 394 known not affected: 274 recommended: 145 | 2026-07-15T05:13:39+00:00 | Vulnerability · Source |
| CVE-2026-43082 | suse_vex | SUSE CVE CVE-2026-43082 | first fixed: 2 known affected: 411 known not affected: 276 recommended: 145 | 2026-07-15T05:13:17+00:00 | Vulnerability · Source |
| CVE-2026-43090 | suse_vex | SUSE CVE CVE-2026-43090 | known affected: 17 known not affected: 276 | 2026-07-15T05:13:10+00:00 | Vulnerability · Source |
| CVE-2026-43132 | suse_vex | SUSE CVE CVE-2026-43132 | known affected: 289 known not affected: 4 | 2026-07-15T05:12:52+00:00 | Vulnerability · Source |
| CVE-2026-43163 | suse_vex | SUSE CVE CVE-2026-43163 | known affected: 289 known not affected: 4 recommended: 116 | 2026-07-15T05:12:42+00:00 | Vulnerability · Source |
| CVE-2026-43175 | suse_vex | SUSE CVE CVE-2026-43175 | known affected: 17 known not affected: 276 | 2026-07-15T05:12:38+00:00 | Vulnerability · Source |
| CVE-2026-43298 | suse_vex | SUSE CVE CVE-2026-43298 | known affected: 114 known not affected: 179 | 2026-07-15T05:12:00+00:00 | Vulnerability · Source |
| CVE-2026-43386 | suse_vex | SUSE CVE CVE-2026-43386 | known affected: 287 known not affected: 6 | 2026-07-15T05:11:28+00:00 | Vulnerability · Source |
| CVE-2026-43393 | suse_vex | SUSE CVE CVE-2026-43393 | first fixed: 2 known affected: 411 known not affected: 276 recommended: 145 | 2026-07-15T05:11:26+00:00 | Vulnerability · Source |
| CVE-2026-43394 | suse_vex | SUSE CVE CVE-2026-43394 | first fixed: 2 known affected: 394 known not affected: 276 recommended: 145 | 2026-07-15T05:11:25+00:00 | Vulnerability · Source |
| CVE-2026-43413 | suse_vex | SUSE CVE CVE-2026-43413 | known affected: 569 known not affected: 21 recommended: 145 | 2026-07-15T05:11:17+00:00 | Vulnerability · Source |
| CVE-2026-43512 | suse_vex | SUSE CVE CVE-2026-43512 | known affected: 454 recommended: 383 | 2026-07-15T05:10:49+00:00 | Vulnerability · Source |
| CVE-2026-43513 | suse_vex | SUSE CVE CVE-2026-43513 | known affected: 524 recommended: 374 | 2026-07-15T05:10:48+00:00 | Vulnerability · Source |
| CVE-2026-43514 | suse_vex | SUSE CVE CVE-2026-43514 | known affected: 524 recommended: 374 | 2026-07-15T05:10:46+00:00 | Vulnerability · Source |
| CVE-2026-43515 | suse_vex | SUSE CVE CVE-2026-43515 | known affected: 523 recommended: 383 | 2026-07-15T05:10:45+00:00 | Vulnerability · Source |
| CVE-2026-43660 | suse_vex | SUSE CVE CVE-2026-43660 | known affected: 70 recommended: 469 | 2026-07-15T05:10:42+00:00 | Vulnerability · Source |
| CVE-2026-43859 | suse_vex | SUSE CVE CVE-2026-43859 | known affected: 449 recommended: 32 | 2026-07-15T05:10:40+00:00 | Vulnerability · Source |
| CVE-2026-43860 | suse_vex | SUSE CVE CVE-2026-43860 | known affected: 449 recommended: 29 | 2026-07-15T05:10:39+00:00 | Vulnerability · Source |
| CVE-2026-43861 | suse_vex | SUSE CVE CVE-2026-43861 | known affected: 449 recommended: 32 | 2026-07-15T05:10:38+00:00 | Vulnerability · Source |
| CVE-2026-43862 | suse_vex | SUSE CVE CVE-2026-43862 | known affected: 449 recommended: 32 | 2026-07-15T05:10:37+00:00 | Vulnerability · Source |
| CVE-2026-43863 | suse_vex | SUSE CVE CVE-2026-43863 | known affected: 449 recommended: 32 | 2026-07-15T05:10:35+00:00 | Vulnerability · Source |
| CVE-2026-43864 | suse_vex | SUSE CVE CVE-2026-43864 | known affected: 449 recommended: 29 | 2026-07-15T05:10:34+00:00 | Vulnerability · Source |
| CVE-2026-43894 | suse_vex | SUSE CVE CVE-2026-43894 | known affected: 394 known not affected: 76 recommended: 14 | 2026-07-15T05:10:33+00:00 | Vulnerability · Source |
| CVE-2026-43895 | suse_vex | SUSE CVE CVE-2026-43895 | known affected: 87 recommended: 3 | 2026-07-15T05:10:32+00:00 | Vulnerability · Source |
| CVE-2026-44024 | suse_vex | SUSE CVE CVE-2026-44024 | No product status | 2026-07-15T05:10:26+00:00 | Vulnerability · Source |
| CVE-2026-44171 | suse_vex | SUSE CVE CVE-2026-44171 | known affected: 503 known not affected: 22 recommended: 206 | 2026-07-15T05:10:21+00:00 | Vulnerability · Source |
| CVE-2026-44243 | suse_vex | SUSE CVE CVE-2026-44243 | known affected: 38 recommended: 6 | 2026-07-15T05:10:16+00:00 | Vulnerability · Source |
| CVE-2026-44244 | suse_vex | SUSE CVE CVE-2026-44244 | known affected: 38 recommended: 6 | 2026-07-15T05:10:15+00:00 | Vulnerability · Source |
| CVE-2026-44681 | suse_vex | SUSE CVE CVE-2026-44681 | known affected: 6 recommended: 8 | 2026-07-15T05:10:05+00:00 | Vulnerability · Source |
| CVE-2026-44708 | suse_vex | SUSE CVE CVE-2026-44708 | known not affected: 35 recommended: 3 | 2026-07-15T05:10:03+00:00 | Vulnerability · Source |
| CVE-2026-44889 | suse_vex | SUSE CVE CVE-2026-44889 | known affected: 41 known not affected: 10 recommended: 33 | 2026-07-15T05:10:00+00:00 | Vulnerability · Source |
| CVE-2026-44896 | suse_vex | SUSE CVE CVE-2026-44896 | first fixed: 2 known not affected: 35 recommended: 3 | 2026-07-15T05:09:59+00:00 | Vulnerability · Source |
| CVE-2026-44897 | suse_vex | SUSE CVE CVE-2026-44897 | known not affected: 35 recommended: 6 | 2026-07-15T05:09:58+00:00 | Vulnerability · Source |
| CVE-2026-44899 | suse_vex | SUSE CVE CVE-2026-44899 | known not affected: 35 recommended: 3 | 2026-07-15T05:09:56+00:00 | Vulnerability · Source |
| CVE-2026-44988 | suse_vex | SUSE CVE CVE-2026-44988 | known affected: 6 recommended: 30 | 2026-07-15T05:09:52+00:00 | Vulnerability · Source |
| CVE-2026-45108 | suse_vex | SUSE CVE CVE-2026-45108 | known affected: 68 recommended: 18 | 2026-07-15T05:09:50+00:00 | Vulnerability · Source |
| CVE-2026-45205 | suse_vex | SUSE CVE CVE-2026-45205 | known affected: 4 known not affected: 13 recommended: 69 | 2026-07-15T05:09:47+00:00 | Vulnerability · Source |
| CVE-2026-45678 | suse_vex | SUSE CVE CVE-2026-45678 | known affected: 3 recommended: 9 | 2026-07-15T05:09:39+00:00 | Vulnerability · Source |
| CVE-2026-45682 | suse_vex | SUSE CVE CVE-2026-45682 | known affected: 3 recommended: 9 | 2026-07-15T05:09:38+00:00 | Vulnerability · Source |