VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286443 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-42499 | suse_vex | SUSE CVE CVE-2026-42499 | known affected: 67 known not affected: 51 recommended: 275 | 2026-07-27T17:06:16+00:00 | Vulnerability · Source |
| CVE-2026-42508 | suse_vex | SUSE CVE CVE-2026-42508 | known affected: 362 known not affected: 254 recommended: 503 | 2026-07-27T17:06:11+00:00 | Vulnerability · Source |
| CVE-2026-42766 | suse_vex | SUSE CVE CVE-2026-42766 | known affected: 503 known not affected: 84 recommended: 362 | 2026-07-27T17:06:09+00:00 | Vulnerability · Source |
| CVE-2026-42767 | suse_vex | SUSE CVE CVE-2026-42767 | known affected: 413 known not affected: 383 recommended: 138 | 2026-07-27T17:06:08+00:00 | Vulnerability · Source |
| CVE-2026-42770 | suse_vex | SUSE CVE CVE-2026-42770 | known affected: 413 known not affected: 383 recommended: 138 | 2026-07-27T17:06:06+00:00 | Vulnerability · Source |
| CVE-2026-43145 | suse_vex | SUSE CVE CVE-2026-43145 | known affected: 17 known not affected: 276 | 2026-07-27T17:05:59+00:00 | Vulnerability · Source |
| CVE-2026-43351 | suse_vex | SUSE CVE CVE-2026-43351 | known affected: 17 known not affected: 276 | 2026-07-27T17:05:57+00:00 | Vulnerability · Source |
| CVE-2026-43491 | suse_vex | SUSE CVE CVE-2026-43491 | first fixed: 55 known affected: 529 known not affected: 93 recommended: 242 | 2026-07-27T17:05:55+00:00 | Vulnerability · Source |
| CVE-2026-43502 | suse_vex | SUSE CVE CVE-2026-43502 | first fixed: 55 known affected: 555 known not affected: 67 recommended: 213 | 2026-07-27T17:05:53+00:00 | Vulnerability · Source |
| CVE-2026-43618 | suse_vex | SUSE CVE CVE-2026-43618 | known affected: 406 recommended: 42 | 2026-07-27T17:05:52+00:00 | Vulnerability · Source |
| CVE-2026-44420 | suse_vex | SUSE CVE CVE-2026-44420 | known affected: 117 recommended: 73 | 2026-07-27T17:05:41+00:00 | Vulnerability · Source |
| CVE-2026-44421 | suse_vex | SUSE CVE CVE-2026-44421 | known affected: 117 recommended: 73 | 2026-07-27T17:05:40+00:00 | Vulnerability · Source |
| CVE-2026-44422 | suse_vex | SUSE CVE CVE-2026-44422 | known affected: 117 recommended: 73 | 2026-07-27T17:05:39+00:00 | Vulnerability · Source |
| CVE-2026-54478 | redhat_vex | unbound: Unbound: DNS Cookie security bypass via incorrect server cookie calculation | fixed: 4 known affected: 15 known not affected: 15 | 2026-07-27T17:05:38+00:00 | Vulnerability · Source |
| CVE-2025-6170 | redhat_vex | libxml2: Stack Buffer Overflow in xmllint Interactive Shell Command Handling | fixed: 155 known affected: 12 | 2026-07-27T17:05:37+00:00 | Vulnerability · Source |
| CVE-2026-45445 | suse_vex | SUSE CVE CVE-2026-45445 | known affected: 413 known not affected: 388 recommended: 138 | 2026-07-27T17:05:32+00:00 | Vulnerability · Source |
| CVE-2026-45446 | suse_vex | SUSE CVE CVE-2026-45446 | known affected: 413 known not affected: 388 recommended: 138 | 2026-07-27T17:05:31+00:00 | Vulnerability · Source |
| CVE-2026-45447 | suse_vex | SUSE CVE CVE-2026-45447 | known affected: 507 known not affected: 75 recommended: 380 | 2026-07-27T17:05:29+00:00 | Vulnerability · Source |
| CVE-2026-47057 | suse_vex | SUSE CVE CVE-2026-47057 | first fixed: 81 known affected: 489 recommended: 7 | 2026-07-27T17:05:11+00:00 | Vulnerability · Source |
| CVE-2026-47058 | suse_vex | SUSE CVE CVE-2026-47058 | first fixed: 81 known affected: 489 recommended: 7 | 2026-07-27T17:05:10+00:00 | Vulnerability · Source |
| CVE-2026-47086 | suse_vex | SUSE CVE CVE-2026-47086 | No product status | 2026-07-27T17:05:06+00:00 | Vulnerability · Source |
| CVE-2026-48526 | suse_vex | SUSE CVE CVE-2026-48526 | known affected: 423 recommended: 163 | 2026-07-27T17:05:05+00:00 | Vulnerability · Source |
| CVE-2026-50031 | suse_vex | SUSE CVE CVE-2026-50031 | known affected: 186 recommended: 77 | 2026-07-27T17:04:57+00:00 | Vulnerability · Source |
| CVE-2026-50256 | suse_vex | SUSE CVE CVE-2026-50256 | known affected: 27 recommended: 35 | 2026-07-27T17:04:56+00:00 | Vulnerability · Source |
| CVE-2026-50257 | suse_vex | SUSE CVE CVE-2026-50257 | known affected: 5 known not affected: 22 recommended: 35 | 2026-07-27T17:04:54+00:00 | Vulnerability · Source |
| CVE-2026-50258 | suse_vex | SUSE CVE CVE-2026-50258 | known affected: 27 recommended: 35 | 2026-07-27T17:04:53+00:00 | Vulnerability · Source |
| CVE-2026-50259 | suse_vex | SUSE CVE CVE-2026-50259 | known affected: 27 recommended: 35 | 2026-07-27T17:04:52+00:00 | Vulnerability · Source |
| CVE-2026-50260 | suse_vex | SUSE CVE CVE-2026-50260 | known affected: 27 recommended: 35 | 2026-07-27T17:04:51+00:00 | Vulnerability · Source |
| CVE-2026-50261 | suse_vex | SUSE CVE CVE-2026-50261 | known affected: 27 recommended: 35 | 2026-07-27T17:04:50+00:00 | Vulnerability · Source |
| CVE-2026-50262 | suse_vex | SUSE CVE CVE-2026-50262 | known affected: 27 recommended: 35 | 2026-07-27T17:04:48+00:00 | Vulnerability · Source |
| CVE-2026-50263 | suse_vex | SUSE CVE CVE-2026-50263 | known affected: 27 recommended: 35 | 2026-07-27T17:04:47+00:00 | Vulnerability · Source |
| CVE-2026-50264 | suse_vex | SUSE CVE CVE-2026-50264 | known affected: 22 known not affected: 9 recommended: 35 | 2026-07-27T17:04:46+00:00 | Vulnerability · Source |
| CVE-2026-53217 | suse_vex | SUSE CVE CVE-2026-53217 | first fixed: 55 known affected: 555 known not affected: 67 recommended: 197 | 2026-07-27T17:04:33+00:00 | Vulnerability · Source |
| CVE-2026-53379 | suse_vex | SUSE CVE CVE-2026-53379 | known affected: 144 known not affected: 140 | 2026-07-27T17:04:26+00:00 | Vulnerability · Source |
| CVE-2026-53467 | suse_vex | SUSE CVE CVE-2026-53467 | first fixed: 28 known affected: 203 known not affected: 8 recommended: 217 | 2026-07-27T17:04:24+00:00 | Vulnerability · Source |
| CVE-2026-54058 | suse_vex | SUSE CVE CVE-2026-54058 | first fixed: 32 known affected: 49 recommended: 5 | 2026-07-27T17:04:21+00:00 | Vulnerability · Source |
| CVE-2026-55594 | suse_vex | SUSE CVE CVE-2026-55594 | first fixed: 28 known affected: 151 known not affected: 60 recommended: 201 | 2026-07-27T17:04:15+00:00 | Vulnerability · Source |
| CVE-2026-55595 | suse_vex | SUSE CVE CVE-2026-55595 | first fixed: 28 known affected: 91 known not affected: 8 recommended: 201 | 2026-07-27T17:04:13+00:00 | Vulnerability · Source |
| CVE-2026-55597 | suse_vex | SUSE CVE CVE-2026-55597 | known affected: 57 known not affected: 43 recommended: 229 | 2026-07-27T17:04:11+00:00 | Vulnerability · Source |
| CVE-2026-56361 | suse_vex | SUSE CVE CVE-2026-56361 | first fixed: 28 known affected: 75 known not affected: 8 recommended: 217 | 2026-07-27T17:04:03+00:00 | Vulnerability · Source |
| CVE-2026-56363 | suse_vex | SUSE CVE CVE-2026-56363 | first fixed: 28 known affected: 75 known not affected: 8 recommended: 217 | 2026-07-27T17:04:00+00:00 | Vulnerability · Source |
| CVE-2026-56364 | suse_vex | SUSE CVE CVE-2026-56364 | first fixed: 28 known affected: 75 known not affected: 24 recommended: 201 | 2026-07-27T17:03:58+00:00 | Vulnerability · Source |
| CVE-2026-56374 | suse_vex | SUSE CVE CVE-2026-56374 | first fixed: 28 known affected: 21 known not affected: 151 recommended: 113 | 2026-07-27T17:03:56+00:00 | Vulnerability · Source |
| CVE-2026-59197 | suse_vex | SUSE CVE CVE-2026-59197 | first fixed: 32 known affected: 49 recommended: 1 | 2026-07-27T17:03:43+00:00 | Vulnerability · Source |
| CVE-2026-59198 | suse_vex | SUSE CVE CVE-2026-59198 | first fixed: 32 known affected: 49 recommended: 5 | 2026-07-27T17:03:41+00:00 | Vulnerability · Source |
| CVE-2026-59199 | suse_vex | SUSE CVE CVE-2026-59199 | first fixed: 32 known affected: 49 recommended: 1 | 2026-07-27T17:03:39+00:00 | Vulnerability · Source |
| CVE-2026-59200 | suse_vex | SUSE CVE CVE-2026-59200 | first fixed: 32 known affected: 49 recommended: 5 | 2026-07-27T17:03:37+00:00 | Vulnerability · Source |
| CVE-2026-59204 | suse_vex | SUSE CVE CVE-2026-59204 | first fixed: 32 known affected: 49 recommended: 5 | 2026-07-27T17:03:36+00:00 | Vulnerability · Source |
| CVE-2026-59205 | suse_vex | SUSE CVE CVE-2026-59205 | first fixed: 32 known affected: 49 recommended: 1 | 2026-07-27T17:03:34+00:00 | Vulnerability · Source |
| CVE-2026-59888 | suse_vex | SUSE CVE CVE-2026-59888 | first fixed: 36 known affected: 23 recommended: 8 | 2026-07-27T17:03:22+00:00 | Vulnerability · Source |