VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
306035 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-98346 | suse_vex | SUSE CVE CVE-2026-98346 | known not affected: 347 | 2026-10-08T16:47:02+00:00 | Vulnerability · Source |
| CVE-2026-98348 | suse_vex | SUSE CVE CVE-2026-98348 | known affected: 301 known not affected: 46 | 2026-10-08T16:47:00+00:00 | Vulnerability · Source |
| CVE-2026-98349 | suse_vex | SUSE CVE CVE-2026-98349 | known affected: 301 known not affected: 46 | 2026-10-08T16:46:58+00:00 | Vulnerability · Source |
| CVE-2026-98350 | suse_vex | SUSE CVE CVE-2026-98350 | known not affected: 347 | 2026-10-08T16:46:55+00:00 | Vulnerability · Source |
| CVE-2026-98352 | suse_vex | SUSE CVE CVE-2026-98352 | known affected: 158 known not affected: 184 | 2026-10-08T16:46:53+00:00 | Vulnerability · Source |
| CVE-2026-98356 | suse_vex | SUSE CVE CVE-2026-98356 | known not affected: 347 | 2026-10-08T16:46:50+00:00 | Vulnerability · Source |
| CVE-2026-98360 | suse_vex | SUSE CVE CVE-2026-98360 | known affected: 62 known not affected: 285 | 2026-10-08T16:46:48+00:00 | Vulnerability · Source |
| CVE-2026-98362 | suse_vex | SUSE CVE CVE-2026-98362 | known affected: 297 known not affected: 50 | 2026-10-08T16:46:46+00:00 | Vulnerability · Source |
| CVE-2026-98363 | suse_vex | SUSE CVE CVE-2026-98363 | known affected: 297 known not affected: 50 | 2026-10-08T16:46:44+00:00 | Vulnerability · Source |
| CVE-2026-98364 | suse_vex | SUSE CVE CVE-2026-98364 | known affected: 347 | 2026-10-08T16:46:42+00:00 | Vulnerability · Source |
| CVE-2026-98366 | suse_vex | SUSE CVE CVE-2026-98366 | known not affected: 347 | 2026-10-08T16:46:39+00:00 | Vulnerability · Source |
| CVE-2026-98369 | suse_vex | SUSE CVE CVE-2026-98369 | known affected: 62 known not affected: 285 | 2026-10-08T16:46:38+00:00 | Vulnerability · Source |
| CVE-2026-100075 | suse_vex | SUSE CVE CVE-2026-100075 | known affected: 374 known not affected: 16 recommended: 4 | 2026-10-08T16:46:36+00:00 | Vulnerability · Source |
| CVE-2026-102555 | suse_vex | SUSE CVE CVE-2026-102555 | known affected: 123 known not affected: 183 | 2026-10-08T16:46:33+00:00 | Vulnerability · Source |
| CVE-2026-102556 | suse_vex | SUSE CVE CVE-2026-102556 | known affected: 306 | 2026-10-08T16:46:31+00:00 | Vulnerability · Source |
| CVE-2026-102557 | suse_vex | SUSE CVE CVE-2026-102557 | known affected: 306 | 2026-10-08T16:46:29+00:00 | Vulnerability · Source |
| CVE-2026-102558 | suse_vex | SUSE CVE CVE-2026-102558 | known affected: 306 | 2026-10-08T16:46:28+00:00 | Vulnerability · Source |
| CVE-2026-102559 | suse_vex | SUSE CVE CVE-2026-102559 | known affected: 306 | 2026-10-08T16:46:26+00:00 | Vulnerability · Source |
| CVE-2026-102560 | suse_vex | SUSE CVE CVE-2026-102560 | known affected: 123 known not affected: 183 | 2026-10-08T16:46:24+00:00 | Vulnerability · Source |
| CVE-2026-103118 | suse_vex | SUSE CVE CVE-2026-103118 | known affected: 8 known not affected: 368 recommended: 8 | 2026-10-08T16:46:22+00:00 | Vulnerability · Source |
| CVE-2026-103623 | suse_vex | SUSE CVE CVE-2026-103623 | recommended: 6 | 2026-10-08T16:46:19+00:00 | Vulnerability · Source |
| CVE-2026-103625 | suse_vex | SUSE CVE CVE-2026-103625 | recommended: 6 | 2026-10-08T16:46:17+00:00 | Vulnerability · Source |
| CVE-2026-103630 | suse_vex | SUSE CVE CVE-2026-103630 | recommended: 6 | 2026-10-08T16:46:14+00:00 | Vulnerability · Source |
| CVE-2026-106016 | suse_vex | SUSE CVE CVE-2026-106016 | known affected: 149 | 2026-10-08T16:46:04+00:00 | Vulnerability · Source |
| CVE-2026-106061 | suse_vex | SUSE CVE CVE-2026-106061 | known affected: 26 | 2026-10-08T16:46:01+00:00 | Vulnerability · Source |
| CVE-2026-106062 | suse_vex | SUSE CVE CVE-2026-106062 | known affected: 26 | 2026-10-08T16:45:58+00:00 | Vulnerability · Source |
| CVE-2026-106063 | suse_vex | SUSE CVE CVE-2026-106063 | known affected: 26 | 2026-10-08T16:45:56+00:00 | Vulnerability · Source |
| CVE-2026-106064 | suse_vex | SUSE CVE CVE-2026-106064 | known affected: 26 | 2026-10-08T16:45:53+00:00 | Vulnerability · Source |
| CVE-2026-106065 | suse_vex | SUSE CVE CVE-2026-106065 | known affected: 26 | 2026-10-08T16:45:51+00:00 | Vulnerability · Source |
| CVE-2026-106066 | suse_vex | SUSE CVE CVE-2026-106066 | known affected: 26 | 2026-10-08T16:45:49+00:00 | Vulnerability · Source |
| CVE-2026-106067 | suse_vex | SUSE CVE CVE-2026-106067 | known affected: 26 | 2026-10-08T16:45:47+00:00 | Vulnerability · Source |
| CVE-2026-106443 | suse_vex | SUSE CVE CVE-2026-106443 | No product status | 2026-10-08T16:44:01+00:00 | Vulnerability · Source |
| CVE-2026-106547 | suse_vex | SUSE CVE CVE-2026-106547 | known affected: 708 | 2026-10-08T16:43:58+00:00 | Vulnerability · Source |
| CVE-2026-106552 | suse_vex | SUSE CVE CVE-2026-106552 | known affected: 269 | 2026-10-08T16:43:55+00:00 | Vulnerability · Source |
| CVE-2026-106553 | suse_vex | SUSE CVE CVE-2026-106553 | known affected: 269 | 2026-10-08T16:43:53+00:00 | Vulnerability · Source |
| CVE-2026-106555 | suse_vex | SUSE CVE CVE-2026-106555 | No product status | 2026-10-08T16:43:51+00:00 | Vulnerability · Source |
| CVE-2026-106564 | suse_vex | SUSE CVE CVE-2026-106564 | known affected: 368 known not affected: 8 | 2026-10-08T16:43:50+00:00 | Vulnerability · Source |
| CVE-2026-106565 | suse_vex | SUSE CVE CVE-2026-106565 | known affected: 368 known not affected: 8 | 2026-10-08T16:43:48+00:00 | Vulnerability · Source |
| CVE-2026-106566 | suse_vex | SUSE CVE CVE-2026-106566 | known affected: 368 known not affected: 8 | 2026-10-08T16:43:46+00:00 | Vulnerability · Source |
| CVE-2026-106567 | suse_vex | SUSE CVE CVE-2026-106567 | known affected: 368 known not affected: 8 | 2026-10-08T16:43:44+00:00 | Vulnerability · Source |
| CVE-2026-106568 | suse_vex | SUSE CVE CVE-2026-106568 | known affected: 368 known not affected: 8 | 2026-10-08T16:43:42+00:00 | Vulnerability · Source |
| CVE-2026-106569 | suse_vex | SUSE CVE CVE-2026-106569 | known affected: 368 known not affected: 8 | 2026-10-08T16:43:41+00:00 | Vulnerability · Source |
| CVE-2026-106570 | suse_vex | SUSE CVE CVE-2026-106570 | known affected: 368 known not affected: 8 | 2026-10-08T16:43:39+00:00 | Vulnerability · Source |
| CVE-2026-106571 | suse_vex | SUSE CVE CVE-2026-106571 | known affected: 368 known not affected: 8 | 2026-10-08T16:43:36+00:00 | Vulnerability · Source |
| CVE-2026-106572 | suse_vex | SUSE CVE CVE-2026-106572 | known affected: 368 known not affected: 8 | 2026-10-08T16:43:34+00:00 | Vulnerability · Source |
| CVE-2026-106573 | suse_vex | SUSE CVE CVE-2026-106573 | known affected: 368 known not affected: 8 | 2026-10-08T16:43:31+00:00 | Vulnerability · Source |
| CVE-2026-106574 | suse_vex | SUSE CVE CVE-2026-106574 | known affected: 368 known not affected: 8 | 2026-10-08T16:43:28+00:00 | Vulnerability · Source |
| CVE-2026-106575 | suse_vex | SUSE CVE CVE-2026-106575 | known affected: 368 known not affected: 8 | 2026-10-08T16:43:26+00:00 | Vulnerability · Source |
| CVE-2026-106576 | suse_vex | SUSE CVE CVE-2026-106576 | known affected: 368 known not affected: 8 | 2026-10-08T16:43:24+00:00 | Vulnerability · Source |
| CVE-2026-106577 | suse_vex | SUSE CVE CVE-2026-106577 | known affected: 368 known not affected: 8 | 2026-10-08T16:43:21+00:00 | Vulnerability · Source |