VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
303777 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-71305 | suse_vex | SUSE CVE CVE-2025-71305 | known affected: 484 known not affected: 236 recommended: 250 | 2026-10-01T01:36:21+00:00 | Vulnerability · Source |
| CVE-2025-71314 | suse_vex | SUSE CVE CVE-2025-71314 | known affected: 396 known not affected: 336 recommended: 228 | 2026-10-01T01:36:18+00:00 | Vulnerability · Source |
| CVE-2026-1703 | suse_vex | SUSE CVE CVE-2026-1703 | known affected: 777 known not affected: 217 recommended: 172 | 2026-10-01T01:36:12+00:00 | Vulnerability · Source |
| CVE-2026-2303 | suse_vex | SUSE CVE CVE-2026-2303 | known affected: 79 known not affected: 598 recommended: 19 | 2026-10-01T01:36:10+00:00 | Vulnerability · Source |
| CVE-2026-3219 | suse_vex | SUSE CVE CVE-2026-3219 | known affected: 922 known not affected: 40 recommended: 218 | 2026-10-01T01:36:07+00:00 | Vulnerability · Source |
| CVE-2026-6383 | suse_vex | SUSE CVE CVE-2026-6383 | known affected: 45 | 2026-10-01T01:36:03+00:00 | Vulnerability · Source |
| CVE-2026-6879 | suse_vex | SUSE CVE CVE-2026-6879 | known affected: 419 recommended: 49 | 2026-10-01T01:35:59+00:00 | Vulnerability · Source |
| CVE-2026-7374 | suse_vex | SUSE CVE CVE-2026-7374 | known affected: 22 recommended: 12 | 2026-10-01T01:35:56+00:00 | Vulnerability · Source |
| CVE-2026-8643 | suse_vex | SUSE CVE CVE-2026-8643 | known affected: 902 recommended: 160 | 2026-10-01T01:35:51+00:00 | Vulnerability · Source |
| CVE-2026-9669 | suse_vex | SUSE CVE CVE-2026-9669 | known affected: 476 known not affected: 330 recommended: 209 | 2026-10-01T01:35:48+00:00 | Vulnerability · Source |
| CVE-2026-9804 | suse_vex | SUSE CVE CVE-2026-9804 | known affected: 22 recommended: 57 | 2026-10-01T01:35:46+00:00 | Vulnerability · Source |
| CVE-2026-10722 | suse_vex | SUSE CVE CVE-2026-10722 | known affected: 195 known not affected: 902 recommended: 17 | 2026-10-01T01:35:44+00:00 | Vulnerability · Source |
| CVE-2026-12912 | suse_vex | SUSE CVE CVE-2026-12912 | known affected: 454 recommended: 113 | 2026-10-01T01:35:40+00:00 | Vulnerability · Source |
| CVE-2026-13087 | suse_vex | SUSE CVE CVE-2026-13087 | known affected: 347 | 2026-10-01T01:35:38+00:00 | Vulnerability · Source |
| CVE-2026-13346 | suse_vex | SUSE CVE CVE-2026-13346 | known affected: 951 known not affected: 38 recommended: 132 | 2026-10-01T01:35:36+00:00 | Vulnerability · Source |
| CVE-2026-13719 | suse_vex | SUSE CVE CVE-2026-13719 | known affected: 2 | 2026-10-01T01:35:34+00:00 | Vulnerability · Source |
| CVE-2026-13720 | suse_vex | SUSE CVE CVE-2026-13720 | known affected: 2 | 2026-10-01T01:35:33+00:00 | Vulnerability · Source |
| CVE-2026-15310 | suse_vex | SUSE CVE CVE-2026-15310 | known affected: 739 known not affected: 79 recommended: 146 | 2026-10-01T01:35:28+00:00 | Vulnerability · Source |
| CVE-2026-15544 | suse_vex | SUSE CVE CVE-2026-15544 | No product status | 2026-10-01T01:35:24+00:00 | Vulnerability · Source |
| CVE-2026-15806 | suse_vex | SUSE CVE CVE-2026-15806 | known affected: 814 recommended: 147 | 2026-10-01T01:35:20+00:00 | Vulnerability · Source |
| CVE-2026-17084 | suse_vex | SUSE CVE CVE-2026-17084 | known affected: 794 recommended: 197 | 2026-10-01T01:35:16+00:00 | Vulnerability · Source |
| CVE-2026-17106 | suse_vex | SUSE CVE CVE-2026-17106 | known affected: 254 known not affected: 161 recommended: 21 | 2026-10-01T01:35:14+00:00 | Vulnerability · Source |
| CVE-2026-18503 | suse_vex | SUSE CVE CVE-2026-18503 | known affected: 419 recommended: 49 | 2026-10-01T01:35:12+00:00 | Vulnerability · Source |
| CVE-2026-23008 | suse_vex | SUSE CVE CVE-2026-23008 | known not affected: 441 | 2026-10-01T01:35:07+00:00 | Vulnerability · Source |
| CVE-2026-23036 | suse_vex | SUSE CVE CVE-2026-23036 | known affected: 2 known not affected: 441 recommended: 145 | 2026-10-01T01:35:05+00:00 | Vulnerability · Source |
| CVE-2026-23040 | suse_vex | SUSE CVE CVE-2026-23040 | known not affected: 441 | 2026-10-01T01:35:03+00:00 | Vulnerability · Source |
| CVE-2026-23052 | suse_vex | SUSE CVE CVE-2026-23052 | known affected: 2 known not affected: 441 recommended: 145 | 2026-10-01T01:35:01+00:00 | Vulnerability · Source |
| CVE-2026-23130 | suse_vex | SUSE CVE CVE-2026-23130 | known not affected: 437 | 2026-10-01T01:34:58+00:00 | Vulnerability · Source |
| CVE-2026-23162 | suse_vex | SUSE CVE CVE-2026-23162 | known not affected: 441 | 2026-10-01T01:34:56+00:00 | Vulnerability · Source |
| CVE-2026-23183 | suse_vex | SUSE CVE CVE-2026-23183 | known not affected: 437 | 2026-10-01T01:34:54+00:00 | Vulnerability · Source |
| CVE-2026-23227 | suse_vex | SUSE CVE CVE-2026-23227 | known affected: 783 known not affected: 4 recommended: 232 | 2026-10-01T01:34:50+00:00 | Vulnerability · Source |
| CVE-2026-23248 | suse_vex | SUSE CVE CVE-2026-23248 | known affected: 7 known not affected: 423 recommended: 172 | 2026-10-01T01:34:48+00:00 | Vulnerability · Source |
| CVE-2026-23308 | suse_vex | SUSE CVE CVE-2026-23308 | known affected: 10 known not affected: 374 recommended: 253 | 2026-10-01T01:34:45+00:00 | Vulnerability · Source |
| CVE-2026-23332 | suse_vex | SUSE CVE CVE-2026-23332 | known not affected: 437 | 2026-10-01T01:34:42+00:00 | Vulnerability · Source |
| CVE-2026-23338 | suse_vex | SUSE CVE CVE-2026-23338 | known not affected: 445 | 2026-10-01T01:34:40+00:00 | Vulnerability · Source |
| CVE-2026-23341 | suse_vex | SUSE CVE CVE-2026-23341 | known not affected: 437 | 2026-10-01T01:34:37+00:00 | Vulnerability · Source |
| CVE-2026-23348 | suse_vex | SUSE CVE CVE-2026-23348 | known affected: 239 known not affected: 208 recommended: 145 | 2026-10-01T01:34:35+00:00 | Vulnerability · Source |
| CVE-2026-23366 | suse_vex | SUSE CVE CVE-2026-23366 | known not affected: 445 | 2026-10-01T01:34:32+00:00 | Vulnerability · Source |
| CVE-2026-23451 | suse_vex | SUSE CVE CVE-2026-23451 | known affected: 461 known not affected: 188 recommended: 421 | 2026-10-01T01:34:29+00:00 | Vulnerability · Source |
| CVE-2026-25541 | suse_vex | SUSE CVE CVE-2026-25541 | known affected: 920 known not affected: 1999 recommended: 142 | 2026-10-01T01:34:26+00:00 | Vulnerability · Source |
| CVE-2026-25680 | suse_vex | SUSE CVE CVE-2026-25680 | known affected: 191 known not affected: 610 recommended: 315 | 2026-10-01T01:34:24+00:00 | Vulnerability · Source |
| CVE-2026-25681 | suse_vex | SUSE CVE CVE-2026-25681 | known affected: 191 known not affected: 610 recommended: 322 | 2026-10-01T01:34:22+00:00 | Vulnerability · Source |
| CVE-2026-26961 | suse_vex | SUSE CVE CVE-2026-26961 | known affected: 14 known not affected: 40 recommended: 63 | 2026-10-01T01:34:20+00:00 | Vulnerability · Source |
| CVE-2026-26962 | suse_vex | SUSE CVE CVE-2026-26962 | known affected: 14 known not affected: 37 recommended: 62 | 2026-10-01T01:34:19+00:00 | Vulnerability · Source |
| CVE-2026-27136 | suse_vex | SUSE CVE CVE-2026-27136 | known affected: 191 known not affected: 610 recommended: 367 | 2026-10-01T01:34:17+00:00 | Vulnerability · Source |
| CVE-2026-31414 | suse_vex | SUSE CVE CVE-2026-31414 | known affected: 731 recommended: 279 | 2026-10-01T01:34:13+00:00 | Vulnerability · Source |
| CVE-2026-31429 | suse_vex | SUSE CVE CVE-2026-31429 | known affected: 444 known not affected: 284 recommended: 279 | 2026-10-01T01:34:11+00:00 | Vulnerability · Source |
| CVE-2026-31430 | suse_vex | SUSE CVE CVE-2026-31430 | known affected: 443 known not affected: 304 recommended: 250 | 2026-10-01T01:34:10+00:00 | Vulnerability · Source |
| CVE-2026-31436 | suse_vex | SUSE CVE CVE-2026-31436 | known affected: 398 known not affected: 212 recommended: 445 | 2026-10-01T01:34:07+00:00 | Vulnerability · Source |
| CVE-2026-31438 | suse_vex | SUSE CVE CVE-2026-31438 | known affected: 2 known not affected: 375 recommended: 172 | 2026-10-01T01:34:06+00:00 | Vulnerability · Source |