VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
303432 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-93355 | suse_vex | SUSE CVE CVE-2026-93355 | recommended: 1 | 2026-09-29T23:52:48+00:00 | Vulnerability · Source |
| CVE-2026-93488 | suse_vex | SUSE CVE CVE-2026-93488 | recommended: 21 | 2026-09-29T23:52:46+00:00 | Vulnerability · Source |
| CVE-2026-93491 | suse_vex | SUSE CVE CVE-2026-93491 | recommended: 21 | 2026-09-29T23:52:45+00:00 | Vulnerability · Source |
| CVE-2026-93492 | suse_vex | SUSE CVE CVE-2026-93492 | recommended: 21 | 2026-09-29T23:52:43+00:00 | Vulnerability · Source |
| CVE-2026-93494 | suse_vex | SUSE CVE CVE-2026-93494 | known not affected: 52 recommended: 21 | 2026-09-29T23:52:41+00:00 | Vulnerability · Source |
| CVE-2026-93558 | suse_vex | SUSE CVE CVE-2026-93558 | recommended: 21 | 2026-09-29T23:52:39+00:00 | Vulnerability · Source |
| CVE-2026-93560 | suse_vex | SUSE CVE CVE-2026-93560 | recommended: 21 | 2026-09-29T23:52:38+00:00 | Vulnerability · Source |
| CVE-2026-93562 | suse_vex | SUSE CVE CVE-2026-93562 | recommended: 21 | 2026-09-29T23:52:36+00:00 | Vulnerability · Source |
| CVE-2026-93564 | suse_vex | SUSE CVE CVE-2026-93564 | recommended: 21 | 2026-09-29T23:52:34+00:00 | Vulnerability · Source |
| CVE-2026-93565 | suse_vex | SUSE CVE CVE-2026-93565 | recommended: 21 | 2026-09-29T23:52:33+00:00 | Vulnerability · Source |
| CVE-2026-93566 | suse_vex | SUSE CVE CVE-2026-93566 | recommended: 21 | 2026-09-29T23:52:31+00:00 | Vulnerability · Source |
| CVE-2026-93567 | suse_vex | SUSE CVE CVE-2026-93567 | recommended: 21 | 2026-09-29T23:52:29+00:00 | Vulnerability · Source |
| CVE-2026-93568 | suse_vex | SUSE CVE CVE-2026-93568 | recommended: 21 | 2026-09-29T23:52:27+00:00 | Vulnerability · Source |
| CVE-2026-93569 | suse_vex | SUSE CVE CVE-2026-93569 | recommended: 21 | 2026-09-29T23:52:25+00:00 | Vulnerability · Source |
| CVE-2026-93573 | suse_vex | SUSE CVE CVE-2026-93573 | recommended: 21 | 2026-09-29T23:52:23+00:00 | Vulnerability · Source |
| CVE-2026-93574 | suse_vex | SUSE CVE CVE-2026-93574 | recommended: 21 | 2026-09-29T23:52:21+00:00 | Vulnerability · Source |
| CVE-2026-93576 | suse_vex | SUSE CVE CVE-2026-93576 | known not affected: 52 recommended: 21 | 2026-09-29T23:52:19+00:00 | Vulnerability · Source |
| CVE-2026-93579 | suse_vex | SUSE CVE CVE-2026-93579 | recommended: 21 | 2026-09-29T23:52:17+00:00 | Vulnerability · Source |
| CVE-2026-93586 | suse_vex | SUSE CVE CVE-2026-93586 | known affected: 361 known not affected: 20 recommended: 39 | 2026-09-29T23:52:15+00:00 | Vulnerability · Source |
| CVE-2026-93587 | suse_vex | SUSE CVE CVE-2026-93587 | known affected: 353 known not affected: 20 recommended: 39 | 2026-09-29T23:52:13+00:00 | Vulnerability · Source |
| CVE-2026-93588 | suse_vex | SUSE CVE CVE-2026-93588 | known affected: 353 known not affected: 20 recommended: 39 | 2026-09-29T23:52:11+00:00 | Vulnerability · Source |
| CVE-2026-93589 | suse_vex | SUSE CVE CVE-2026-93589 | known affected: 309 known not affected: 64 recommended: 39 | 2026-09-29T23:52:10+00:00 | Vulnerability · Source |
| CVE-2026-93590 | suse_vex | SUSE CVE CVE-2026-93590 | known affected: 81 known not affected: 302 recommended: 15 | 2026-09-29T23:52:08+00:00 | Vulnerability · Source |
| CVE-2026-93599 | suse_vex | SUSE CVE CVE-2026-93599 | known affected: 148 known not affected: 959 recommended: 1 | 2026-09-29T23:52:07+00:00 | Vulnerability · Source |
| CVE-2026-93600 | suse_vex | SUSE CVE CVE-2026-93600 | known affected: 148 known not affected: 959 | 2026-09-29T23:52:05+00:00 | Vulnerability · Source |
| CVE-2026-93601 | suse_vex | SUSE CVE CVE-2026-93601 | known affected: 148 known not affected: 959 | 2026-09-29T23:52:03+00:00 | Vulnerability · Source |
| CVE-2026-93602 | suse_vex | SUSE CVE CVE-2026-93602 | known affected: 148 known not affected: 959 | 2026-09-29T23:52:00+00:00 | Vulnerability · Source |
| CVE-2026-93781 | suse_vex | SUSE CVE CVE-2026-93781 | known affected: 162 known not affected: 185 | 2026-09-29T23:51:58+00:00 | Vulnerability · Source |
| CVE-2026-93788 | suse_vex | SUSE CVE CVE-2026-93788 | known affected: 62 known not affected: 285 | 2026-09-29T23:51:56+00:00 | Vulnerability · Source |
| CVE-2026-93794 | suse_vex | SUSE CVE CVE-2026-93794 | known affected: 343 known not affected: 4 | 2026-09-29T23:51:54+00:00 | Vulnerability · Source |
| CVE-2026-93795 | suse_vex | SUSE CVE CVE-2026-93795 | known affected: 254 known not affected: 93 | 2026-09-29T23:51:52+00:00 | Vulnerability · Source |
| CVE-2026-93796 | suse_vex | SUSE CVE CVE-2026-93796 | known affected: 230 known not affected: 117 | 2026-09-29T23:51:50+00:00 | Vulnerability · Source |
| CVE-2026-93797 | suse_vex | SUSE CVE CVE-2026-93797 | known affected: 198 known not affected: 149 | 2026-09-29T23:51:48+00:00 | Vulnerability · Source |
| CVE-2026-93802 | suse_vex | SUSE CVE CVE-2026-93802 | known affected: 254 known not affected: 93 | 2026-09-29T23:51:46+00:00 | Vulnerability · Source |
| CVE-2026-93807 | suse_vex | SUSE CVE CVE-2026-93807 | known affected: 343 known not affected: 4 | 2026-09-29T23:51:44+00:00 | Vulnerability · Source |
| CVE-2026-93810 | suse_vex | SUSE CVE CVE-2026-93810 | known affected: 108 known not affected: 239 | 2026-09-29T23:51:41+00:00 | Vulnerability · Source |
| CVE-2026-93811 | suse_vex | SUSE CVE CVE-2026-93811 | known affected: 108 known not affected: 239 | 2026-09-29T23:51:39+00:00 | Vulnerability · Source |
| CVE-2026-93813 | suse_vex | SUSE CVE CVE-2026-93813 | known affected: 240 known not affected: 107 | 2026-09-29T23:51:36+00:00 | Vulnerability · Source |
| CVE-2026-93989 | suse_vex | SUSE CVE CVE-2026-93989 | recommended: 1 | 2026-09-29T23:51:33+00:00 | Vulnerability · Source |
| CVE-2026-94640 | suse_vex | SUSE CVE CVE-2026-94640 | known affected: 49 recommended: 1 | 2026-09-29T23:51:31+00:00 | Vulnerability · Source |
| CVE-2026-95274 | suse_vex | SUSE CVE CVE-2026-95274 | recommended: 2 | 2026-09-29T23:51:29+00:00 | Vulnerability · Source |
| CVE-2026-95275 | suse_vex | SUSE CVE CVE-2026-95275 | recommended: 2 | 2026-09-29T23:51:27+00:00 | Vulnerability · Source |
| CVE-2026-95276 | suse_vex | SUSE CVE CVE-2026-95276 | recommended: 2 | 2026-09-29T23:51:25+00:00 | Vulnerability · Source |
| CVE-2026-95277 | suse_vex | SUSE CVE CVE-2026-95277 | recommended: 2 | 2026-09-29T23:51:22+00:00 | Vulnerability · Source |
| CVE-2026-95278 | suse_vex | SUSE CVE CVE-2026-95278 | recommended: 2 | 2026-09-29T23:51:20+00:00 | Vulnerability · Source |
| CVE-2026-95279 | suse_vex | SUSE CVE CVE-2026-95279 | recommended: 2 | 2026-09-29T23:51:18+00:00 | Vulnerability · Source |
| CVE-2026-95280 | suse_vex | SUSE CVE CVE-2026-95280 | recommended: 2 | 2026-09-29T23:51:16+00:00 | Vulnerability · Source |
| CVE-2026-95281 | suse_vex | SUSE CVE CVE-2026-95281 | recommended: 2 | 2026-09-29T23:51:14+00:00 | Vulnerability · Source |
| CVE-2026-95282 | suse_vex | SUSE CVE CVE-2026-95282 | recommended: 2 | 2026-09-29T23:51:12+00:00 | Vulnerability · Source |
| CVE-2026-95283 | suse_vex | SUSE CVE CVE-2026-95283 | recommended: 2 | 2026-09-29T23:51:10+00:00 | Vulnerability · Source |