VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283120 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-4511 | suse_vex | SUSE CVE CVE-2023-4511 | known affected: 109 recommended: 186 | 2026-07-19T18:08:31+00:00 | Vulnerability · Source |
| CVE-2023-4535 | suse_vex | SUSE CVE CVE-2023-4535 | known not affected: 53 recommended: 7 | 2026-07-19T18:08:30+00:00 | Vulnerability · Source |
| CVE-2023-4578 | suse_vex | SUSE CVE CVE-2023-4578 | known affected: 43 recommended: 283 | 2026-07-19T18:08:29+00:00 | Vulnerability · Source |
| CVE-2023-4583 | suse_vex | SUSE CVE CVE-2023-4583 | known affected: 43 recommended: 283 | 2026-07-19T18:08:27+00:00 | Vulnerability · Source |
| CVE-2023-4622 | suse_vex | SUSE CVE CVE-2023-4622 | known affected: 215 known not affected: 6 recommended: 1542 | 2026-07-19T18:08:26+00:00 | Vulnerability · Source |
| CVE-2023-4641 | suse_vex | SUSE CVE CVE-2023-4641 | known affected: 212 recommended: 321 | 2026-07-19T18:08:25+00:00 | Vulnerability · Source |
| CVE-2023-4693 | suse_vex | SUSE CVE CVE-2023-4693 | known affected: 260 recommended: 663 | 2026-07-19T18:08:23+00:00 | Vulnerability · Source |
| CVE-2023-4921 | suse_vex | SUSE CVE CVE-2023-4921 | known affected: 199 known not affected: 6 recommended: 1519 | 2026-07-19T18:08:22+00:00 | Vulnerability · Source |
| CVE-2023-5168 | suse_vex | SUSE CVE CVE-2023-5168 | known affected: 37 recommended: 272 | 2026-07-19T18:08:20+00:00 | Vulnerability · Source |
| CVE-2023-5178 | suse_vex | SUSE CVE CVE-2023-5178 | known affected: 215 known not affected: 287 recommended: 1036 | 2026-07-19T18:08:19+00:00 | Vulnerability · Source |
| CVE-2023-5215 | suse_vex | SUSE CVE CVE-2023-5215 | recommended: 46 | 2026-07-19T18:08:18+00:00 | Vulnerability · Source |
| CVE-2023-5678 | suse_vex | SUSE CVE CVE-2023-5678 | known affected: 322 known not affected: 120 recommended: 875 | 2026-07-19T18:08:16+00:00 | Vulnerability · Source |
| CVE-2023-5679 | suse_vex | SUSE CVE CVE-2023-5679 | known affected: 249 known not affected: 348 recommended: 268 | 2026-07-19T18:08:15+00:00 | Vulnerability · Source |
| CVE-2023-5730 | suse_vex | SUSE CVE CVE-2023-5730 | known affected: 38 recommended: 278 | 2026-07-19T18:08:14+00:00 | Vulnerability · Source |
| CVE-2023-5871 | suse_vex | SUSE CVE CVE-2023-5871 | recommended: 46 | 2026-07-19T18:08:13+00:00 | Vulnerability · Source |
| CVE-2023-6004 | suse_vex | SUSE CVE CVE-2023-6004 | known affected: 234 known not affected: 155 recommended: 334 | 2026-07-19T18:08:11+00:00 | Vulnerability · Source |
| CVE-2023-6121 | suse_vex | SUSE CVE CVE-2023-6121 | known affected: 254 known not affected: 62 recommended: 1042 | 2026-07-19T18:08:10+00:00 | Vulnerability · Source |
| CVE-2023-6129 | suse_vex | SUSE CVE CVE-2023-6129 | known not affected: 656 recommended: 147 | 2026-07-19T18:08:09+00:00 | Vulnerability · Source |
| CVE-2023-6175 | suse_vex | SUSE CVE CVE-2023-6175 | known affected: 120 known not affected: 63 recommended: 195 | 2026-07-19T18:08:07+00:00 | Vulnerability · Source |
| CVE-2023-6237 | suse_vex | SUSE CVE CVE-2023-6237 | known affected: 27 known not affected: 656 recommended: 147 | 2026-07-19T18:08:06+00:00 | Vulnerability · Source |
| CVE-2023-6246 | suse_vex | SUSE CVE CVE-2023-6246 | known not affected: 599 recommended: 217 | 2026-07-19T18:08:05+00:00 | Vulnerability · Source |
| CVE-2023-6351 | suse_vex | SUSE CVE CVE-2023-6351 | known not affected: 26 recommended: 47 | 2026-07-19T18:08:04+00:00 | Vulnerability · Source |
| CVE-2023-6356 | suse_vex | SUSE CVE CVE-2023-6356 | known affected: 239 known not affected: 221 recommended: 964 | 2026-07-19T18:08:02+00:00 | Vulnerability · Source |
| CVE-2023-6478 | suse_vex | SUSE CVE CVE-2023-6478 | known affected: 408 recommended: 218 | 2026-07-19T18:08:01+00:00 | Vulnerability · Source |
| CVE-2023-6679 | suse_vex | SUSE CVE CVE-2023-6679 | known not affected: 346 recommended: 235 | 2026-07-19T18:08:00+00:00 | Vulnerability · Source |
| CVE-2023-6693 | suse_vex | SUSE CVE CVE-2023-6693 | known affected: 697 known not affected: 223 recommended: 883 | 2026-07-19T18:07:58+00:00 | Vulnerability · Source |
| CVE-2023-6779 | suse_vex | SUSE CVE CVE-2023-6779 | known not affected: 599 recommended: 204 | 2026-07-19T18:07:57+00:00 | Vulnerability · Source |
| CVE-2023-6817 | suse_vex | SUSE CVE CVE-2023-6817 | known affected: 300 known not affected: 261 recommended: 838 | 2026-07-19T18:07:55+00:00 | Vulnerability · Source |
| CVE-2023-6860 | suse_vex | SUSE CVE CVE-2023-6860 | known affected: 28 recommended: 254 | 2026-07-19T18:07:54+00:00 | Vulnerability · Source |
| CVE-2023-6861 | suse_vex | SUSE CVE CVE-2023-6861 | known affected: 28 recommended: 254 | 2026-07-19T18:07:53+00:00 | Vulnerability · Source |
| CVE-2023-6864 | suse_vex | SUSE CVE CVE-2023-6864 | known affected: 28 recommended: 254 | 2026-07-19T18:07:52+00:00 | Vulnerability · Source |
| CVE-2023-6867 | suse_vex | SUSE CVE CVE-2023-6867 | known affected: 28 recommended: 196 | 2026-07-19T18:07:50+00:00 | Vulnerability · Source |
| CVE-2023-6917 | suse_vex | SUSE CVE CVE-2023-6917 | known affected: 556 recommended: 1203 | 2026-07-19T18:07:49+00:00 | Vulnerability · Source |
| CVE-2023-6918 | suse_vex | SUSE CVE CVE-2023-6918 | known affected: 234 known not affected: 155 recommended: 334 | 2026-07-19T18:07:48+00:00 | Vulnerability · Source |
| CVE-2023-7207 | suse_vex | SUSE CVE CVE-2023-7207 | known affected: 279 recommended: 280 | 2026-07-19T18:07:46+00:00 | Vulnerability · Source |
| CVE-2023-20032 | suse_vex | SUSE CVE CVE-2023-20032 | known affected: 1 recommended: 215 | 2026-07-19T18:07:45+00:00 | Vulnerability · Source |
| CVE-2023-20521 | suse_vex | SUSE CVE CVE-2023-20521 | known affected: 22 recommended: 1342 | 2026-07-19T18:07:44+00:00 | Vulnerability · Source |
| CVE-2023-21930 | suse_vex | SUSE CVE CVE-2023-21930 | known affected: 438 known not affected: 1 recommended: 932 | 2026-07-19T18:07:40+00:00 | Vulnerability · Source |
| CVE-2023-21939 | suse_vex | SUSE CVE CVE-2023-21939 | known affected: 439 recommended: 911 | 2026-07-19T18:07:39+00:00 | Vulnerability · Source |
| CVE-2023-21968 | suse_vex | SUSE CVE CVE-2023-21968 | known affected: 439 recommended: 932 | 2026-07-19T18:07:37+00:00 | Vulnerability · Source |
| CVE-2023-23598 | suse_vex | SUSE CVE CVE-2023-23598 | known affected: 36 recommended: 308 | 2026-07-19T18:07:35+00:00 | Vulnerability · Source |
| CVE-2023-23915 | suse_vex | SUSE CVE CVE-2023-23915 | known affected: 289 known not affected: 106 recommended: 237 | 2026-07-19T18:07:34+00:00 | Vulnerability · Source |
| CVE-2023-23916 | suse_vex | SUSE CVE CVE-2023-23916 | known affected: 326 known not affected: 6 recommended: 318 | 2026-07-19T18:07:32+00:00 | Vulnerability · Source |
| CVE-2023-24021 | suse_vex | SUSE CVE CVE-2023-24021 | known affected: 1 known not affected: 13 recommended: 40 | 2026-07-19T18:07:31+00:00 | Vulnerability · Source |
| CVE-2023-25732 | suse_vex | SUSE CVE CVE-2023-25732 | known affected: 1 recommended: 305 | 2026-07-19T18:07:29+00:00 | Vulnerability · Source |
| CVE-2023-25742 | suse_vex | SUSE CVE CVE-2023-25742 | known affected: 1 recommended: 305 | 2026-07-19T18:07:28+00:00 | Vulnerability · Source |
| CVE-2023-25744 | suse_vex | SUSE CVE CVE-2023-25744 | known affected: 1 recommended: 233 | 2026-07-19T18:07:27+00:00 | Vulnerability · Source |
| CVE-2023-25752 | suse_vex | SUSE CVE CVE-2023-25752 | known affected: 1 recommended: 292 | 2026-07-19T18:07:25+00:00 | Vulnerability · Source |
| CVE-2023-26484 | suse_vex | SUSE CVE CVE-2023-26484 | known affected: 5 known not affected: 24 recommended: 108 | 2026-07-19T18:07:24+00:00 | Vulnerability · Source |
| CVE-2023-26964 | suse_vex | SUSE CVE CVE-2023-26964 | known affected: 127 known not affected: 64 recommended: 73 | 2026-07-19T18:07:23+00:00 | Vulnerability · Source |