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-46316 | suse_vex | SUSE CVE CVE-2026-46316 | known affected: 396 known not affected: 370 recommended: 302 | 2026-10-08T17:16:06+00:00 | Vulnerability · Source |
| CVE-2026-46323 | suse_vex | SUSE CVE CVE-2026-46323 | known affected: 396 known not affected: 239 recommended: 766 | 2026-10-08T17:16:03+00:00 | Vulnerability · Source |
| CVE-2026-46331 | suse_vex | SUSE CVE CVE-2026-46331 | known affected: 396 known not affected: 111 recommended: 679 | 2026-10-08T17:16:01+00:00 | Vulnerability · Source |
| CVE-2026-46333 | suse_vex | SUSE CVE CVE-2026-46333 | known affected: 507 known not affected: 4 recommended: 836 | 2026-10-08T17:15:58+00:00 | Vulnerability · Source |
| CVE-2026-46529 | suse_vex | SUSE CVE CVE-2026-46529 | known affected: 216 recommended: 352 | 2026-10-08T17:15:54+00:00 | Vulnerability · Source |
| CVE-2026-46597 | suse_vex | SUSE CVE CVE-2026-46597 | known affected: 327 known not affected: 355 recommended: 419 | 2026-10-08T17:15:52+00:00 | Vulnerability · Source |
| CVE-2026-46917 | suse_vex | SUSE CVE CVE-2026-46917 | known affected: 314 recommended: 578 | 2026-10-08T17:15:49+00:00 | Vulnerability · Source |
| CVE-2026-46968 | suse_vex | SUSE CVE CVE-2026-46968 | known affected: 538 recommended: 822 | 2026-10-08T17:15:46+00:00 | Vulnerability · Source |
| CVE-2026-47010 | suse_vex | SUSE CVE CVE-2026-47010 | known affected: 538 recommended: 815 | 2026-10-08T17:15:43+00:00 | Vulnerability · Source |
| CVE-2026-47021 | suse_vex | SUSE CVE CVE-2026-47021 | known affected: 538 recommended: 794 | 2026-10-08T17:15:40+00:00 | Vulnerability · Source |
| CVE-2026-47027 | suse_vex | SUSE CVE CVE-2026-47027 | known affected: 538 recommended: 815 | 2026-10-08T17:15:37+00:00 | Vulnerability · Source |
| CVE-2026-47057 | suse_vex | SUSE CVE CVE-2026-47057 | known affected: 734 recommended: 382 | 2026-10-08T17:15:34+00:00 | Vulnerability · Source |
| CVE-2026-47058 | suse_vex | SUSE CVE CVE-2026-47058 | known affected: 734 recommended: 382 | 2026-10-08T17:15:32+00:00 | Vulnerability · Source |
| CVE-2026-47059 | suse_vex | SUSE CVE CVE-2026-47059 | known affected: 538 recommended: 815 | 2026-10-08T17:15:30+00:00 | Vulnerability · Source |
| CVE-2026-47063 | suse_vex | SUSE CVE CVE-2026-47063 | known affected: 538 recommended: 794 | 2026-10-08T17:15:28+00:00 | Vulnerability · Source |
| CVE-2026-47242 | suse_vex | SUSE CVE CVE-2026-47242 | known affected: 16 known not affected: 176 recommended: 152 | 2026-10-08T17:15:26+00:00 | Vulnerability · Source |
| CVE-2026-47300 | suse_vex | SUSE CVE CVE-2026-47300 | recommended: 148 | 2026-10-08T17:15:24+00:00 | Vulnerability · Source |
| CVE-2026-47302 | suse_vex | SUSE CVE CVE-2026-47302 | recommended: 148 | 2026-10-08T17:15:22+00:00 | Vulnerability · Source |
| CVE-2026-47303 | suse_vex | SUSE CVE CVE-2026-47303 | recommended: 148 | 2026-10-08T17:15:20+00:00 | Vulnerability · Source |
| CVE-2026-47304 | suse_vex | SUSE CVE CVE-2026-47304 | recommended: 148 | 2026-10-08T17:15:18+00:00 | Vulnerability · Source |
| CVE-2026-48526 | suse_vex | SUSE CVE CVE-2026-48526 | known affected: 415 recommended: 216 | 2026-10-08T17:15:15+00:00 | Vulnerability · Source |
| CVE-2026-48615 | suse_vex | SUSE CVE CVE-2026-48615 | known affected: 226 recommended: 139 | 2026-10-08T17:15:13+00:00 | Vulnerability · Source |
| CVE-2026-48618 | suse_vex | SUSE CVE CVE-2026-48618 | known affected: 144 recommended: 203 | 2026-10-08T17:15:12+00:00 | Vulnerability · Source |
| CVE-2026-48864 | suse_vex | SUSE CVE CVE-2026-48864 | recommended: 13 | 2026-10-08T17:15:10+00:00 | Vulnerability · Source |
| CVE-2026-48913 | suse_vex | SUSE CVE CVE-2026-48913 | known affected: 490 recommended: 169 | 2026-10-08T17:15:08+00:00 | Vulnerability · Source |
| CVE-2026-48933 | suse_vex | SUSE CVE CVE-2026-48933 | known affected: 32 known not affected: 112 recommended: 203 | 2026-10-08T17:15:06+00:00 | Vulnerability · Source |
| CVE-2026-48962 | suse_vex | SUSE CVE CVE-2026-48962 | recommended: 227 | 2026-10-08T17:15:04+00:00 | Vulnerability · Source |
| CVE-2026-49261 | suse_vex | SUSE CVE CVE-2026-49261 | known affected: 592 known not affected: 47 recommended: 222 | 2026-10-08T17:15:02+00:00 | Vulnerability · Source |
| CVE-2026-49975 | suse_vex | SUSE CVE CVE-2026-49975 | known affected: 490 recommended: 180 | 2026-10-08T17:14:51+00:00 | Vulnerability · Source |
| CVE-2026-50031 | suse_vex | SUSE CVE CVE-2026-50031 | known affected: 498 recommended: 187 | 2026-10-08T17:14:49+00:00 | Vulnerability · Source |
| CVE-2026-50229 | suse_vex | SUSE CVE CVE-2026-50229 | known affected: 324 known not affected: 69 recommended: 243 | 2026-10-08T17:14:47+00:00 | Vulnerability · Source |
| CVE-2026-50256 | suse_vex | SUSE CVE CVE-2026-50256 | known affected: 44 recommended: 59 | 2026-10-08T17:14:45+00:00 | Vulnerability · Source |
| CVE-2026-50257 | suse_vex | SUSE CVE CVE-2026-50257 | known not affected: 44 recommended: 59 | 2026-10-08T17:14:43+00:00 | Vulnerability · Source |
| CVE-2026-50258 | suse_vex | SUSE CVE CVE-2026-50258 | known affected: 44 recommended: 59 | 2026-10-08T17:14:41+00:00 | Vulnerability · Source |
| CVE-2026-50259 | suse_vex | SUSE CVE CVE-2026-50259 | known affected: 44 recommended: 59 | 2026-10-08T17:14:39+00:00 | Vulnerability · Source |
| CVE-2026-50260 | suse_vex | SUSE CVE CVE-2026-50260 | known affected: 44 recommended: 59 | 2026-10-08T17:14:37+00:00 | Vulnerability · Source |
| CVE-2026-50261 | suse_vex | SUSE CVE CVE-2026-50261 | known affected: 44 recommended: 59 | 2026-10-08T17:14:35+00:00 | Vulnerability · Source |
| CVE-2026-50262 | suse_vex | SUSE CVE CVE-2026-50262 | known affected: 44 recommended: 59 | 2026-10-08T17:14:33+00:00 | Vulnerability · Source |
| CVE-2026-50263 | suse_vex | SUSE CVE CVE-2026-50263 | known affected: 44 recommended: 59 | 2026-10-08T17:14:30+00:00 | Vulnerability · Source |
| CVE-2026-50264 | suse_vex | SUSE CVE CVE-2026-50264 | known affected: 44 known not affected: 9 recommended: 59 | 2026-10-08T17:14:28+00:00 | Vulnerability · Source |
| CVE-2026-50524 | suse_vex | SUSE CVE CVE-2026-50524 | recommended: 148 | 2026-10-08T17:14:26+00:00 | Vulnerability · Source |
| CVE-2026-50525 | suse_vex | SUSE CVE CVE-2026-50525 | recommended: 148 | 2026-10-08T17:14:24+00:00 | Vulnerability · Source |
| CVE-2026-50526 | suse_vex | SUSE CVE CVE-2026-50526 | recommended: 148 | 2026-10-08T17:14:21+00:00 | Vulnerability · Source |
| CVE-2026-50527 | suse_vex | SUSE CVE CVE-2026-50527 | recommended: 148 | 2026-10-08T17:14:19+00:00 | Vulnerability · Source |
| CVE-2026-50528 | suse_vex | SUSE CVE CVE-2026-50528 | recommended: 148 | 2026-10-08T17:14:17+00:00 | Vulnerability · Source |
| CVE-2026-50646 | suse_vex | SUSE CVE CVE-2026-50646 | recommended: 148 | 2026-10-08T17:14:15+00:00 | Vulnerability · Source |
| CVE-2026-50648 | suse_vex | SUSE CVE CVE-2026-50648 | recommended: 148 | 2026-10-08T17:14:13+00:00 | Vulnerability · Source |
| CVE-2026-50649 | suse_vex | SUSE CVE CVE-2026-50649 | recommended: 148 | 2026-10-08T17:14:11+00:00 | Vulnerability · Source |
| CVE-2026-50650 | suse_vex | SUSE CVE CVE-2026-50650 | recommended: 148 | 2026-10-08T17:14:08+00:00 | Vulnerability · Source |
| CVE-2026-50651 | suse_vex | SUSE CVE CVE-2026-50651 | recommended: 148 | 2026-10-08T17:14:06+00:00 | Vulnerability · Source |