VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
303795 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-68788 | suse_vex | SUSE CVE CVE-2025-68788 | known affected: 710 recommended: 326 | 2026-10-01T01:37:17+00:00 | Vulnerability · Source |
| CVE-2025-68797 | suse_vex | SUSE CVE CVE-2025-68797 | known affected: 710 recommended: 326 | 2026-10-01T01:37:14+00:00 | Vulnerability · Source |
| CVE-2025-68816 | suse_vex | SUSE CVE CVE-2025-68816 | known affected: 633 known not affected: 62 recommended: 312 | 2026-10-01T01:37:11+00:00 | Vulnerability · Source |
| CVE-2025-69647 | suse_vex | SUSE CVE CVE-2025-69647 | known affected: 170 recommended: 7 | 2026-10-01T01:37:08+00:00 | Vulnerability · Source |
| CVE-2025-69648 | suse_vex | SUSE CVE CVE-2025-69648 | known affected: 170 recommended: 7 | 2026-10-01T01:37:06+00:00 | Vulnerability · Source |
| CVE-2025-69649 | suse_vex | SUSE CVE CVE-2025-69649 | known affected: 170 recommended: 7 | 2026-10-01T01:37:05+00:00 | Vulnerability · Source |
| CVE-2025-71085 | suse_vex | SUSE CVE CVE-2025-71085 | known affected: 490 known not affected: 34 recommended: 835 | 2026-10-01T01:37:02+00:00 | Vulnerability · Source |
| CVE-2025-71108 | suse_vex | SUSE CVE CVE-2025-71108 | known affected: 668 known not affected: 34 recommended: 312 | 2026-10-01T01:37:00+00:00 | Vulnerability · Source |
| CVE-2025-71120 | suse_vex | SUSE CVE CVE-2025-71120 | known affected: 442 known not affected: 62 recommended: 731 | 2026-10-01T01:36:58+00:00 | Vulnerability · Source |
| CVE-2025-71183 | suse_vex | SUSE CVE CVE-2025-71183 | known affected: 614 known not affected: 108 recommended: 317 | 2026-10-01T01:36:54+00:00 | Vulnerability · Source |
| CVE-2025-71186 | suse_vex | SUSE CVE CVE-2025-71186 | known affected: 169 known not affected: 231 recommended: 172 | 2026-10-01T01:36:52+00:00 | Vulnerability · Source |
| CVE-2025-71233 | suse_vex | SUSE CVE CVE-2025-71233 | known affected: 217 known not affected: 213 recommended: 176 | 2026-10-01T01:36:50+00:00 | Vulnerability · Source |
| CVE-2025-71269 | suse_vex | SUSE CVE CVE-2025-71269 | known affected: 694 known not affected: 24 recommended: 317 | 2026-10-01T01:36:47+00:00 | Vulnerability · Source |
| CVE-2025-71273 | suse_vex | SUSE CVE CVE-2025-71273 | known affected: 247 known not affected: 142 recommended: 145 | 2026-10-01T01:36:45+00:00 | Vulnerability · Source |
| CVE-2025-71274 | suse_vex | SUSE CVE CVE-2025-71274 | known affected: 580 known not affected: 140 recommended: 250 | 2026-10-01T01:36:43+00:00 | Vulnerability · Source |
| CVE-2025-71286 | suse_vex | SUSE CVE CVE-2025-71286 | known affected: 426 known not affected: 294 recommended: 250 | 2026-10-01T01:36:40+00:00 | Vulnerability · Source |
| CVE-2025-71287 | suse_vex | SUSE CVE CVE-2025-71287 | known affected: 366 known not affected: 23 recommended: 145 | 2026-10-01T01:36:37+00:00 | Vulnerability · Source |
| CVE-2025-71288 | suse_vex | SUSE CVE CVE-2025-71288 | known affected: 93 known not affected: 296 recommended: 145 | 2026-10-01T01:36:35+00:00 | Vulnerability · Source |
| CVE-2025-71291 | suse_vex | SUSE CVE CVE-2025-71291 | known affected: 426 known not affected: 294 recommended: 250 | 2026-10-01T01:36:33+00:00 | Vulnerability · Source |
| CVE-2025-71294 | suse_vex | SUSE CVE CVE-2025-71294 | known affected: 426 known not affected: 294 recommended: 250 | 2026-10-01T01:36:30+00:00 | Vulnerability · Source |
| CVE-2025-71297 | suse_vex | SUSE CVE CVE-2025-71297 | known affected: 550 known not affected: 170 recommended: 250 | 2026-10-01T01:36:26+00:00 | Vulnerability · Source |
| CVE-2025-71302 | suse_vex | SUSE CVE CVE-2025-71302 | known affected: 396 known not affected: 321 recommended: 255 | 2026-10-01T01:36:23+00:00 | Vulnerability · Source |
| 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 |