VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286675 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2018-5358 | suse_vex | SUSE CVE CVE-2018-5358 | known affected: 10 known not affected: 144 | 2026-07-29T00:01:42+00:00 | Vulnerability · Source |
| CVE-2018-6061 | suse_vex | SUSE CVE CVE-2018-6061 | recommended: 10 | 2026-07-29T00:01:40+00:00 | Vulnerability · Source |
| CVE-2018-6064 | suse_vex | SUSE CVE CVE-2018-6064 | recommended: 10 | 2026-07-29T00:01:39+00:00 | Vulnerability · Source |
| CVE-2018-6914 | suse_vex | SUSE CVE CVE-2018-6914 | known affected: 320 known not affected: 22 recommended: 491 | 2026-07-29T00:01:37+00:00 | Vulnerability · Source |
| CVE-2018-7169 | suse_vex | SUSE CVE CVE-2018-7169 | known affected: 333 known not affected: 24 recommended: 212 | 2026-07-29T00:01:35+00:00 | Vulnerability · Source |
| CVE-2018-7173 | suse_vex | SUSE CVE CVE-2018-7173 | known not affected: 381 | 2026-07-29T00:01:34+00:00 | Vulnerability · Source |
| CVE-2018-7185 | suse_vex | SUSE CVE CVE-2018-7185 | known affected: 27 known not affected: 20 recommended: 100 | 2026-07-29T00:01:32+00:00 | Vulnerability · Source |
| CVE-2018-7191 | suse_vex | SUSE CVE CVE-2018-7191 | known not affected: 56 recommended: 792 | 2026-07-29T00:01:31+00:00 | Vulnerability · Source |
| CVE-2018-7454 | suse_vex | SUSE CVE CVE-2018-7454 | known not affected: 381 | 2026-07-29T00:01:29+00:00 | Vulnerability · Source |
| CVE-2018-8100 | suse_vex | SUSE CVE CVE-2018-8100 | known not affected: 381 | 2026-07-29T00:01:27+00:00 | Vulnerability · Source |
| CVE-2018-9055 | suse_vex | SUSE CVE CVE-2018-9055 | known affected: 47 known not affected: 61 recommended: 167 | 2026-07-29T00:01:26+00:00 | Vulnerability · Source |
| CVE-2018-9251 | suse_vex | SUSE CVE CVE-2018-9251 | known affected: 417 known not affected: 45 recommended: 521 | 2026-07-29T00:01:24+00:00 | Vulnerability · Source |
| CVE-2018-10360 | suse_vex | SUSE CVE CVE-2018-10360 | known affected: 1457 known not affected: 1379 recommended: 1284 | 2026-07-29T00:01:22+00:00 | Vulnerability · Source |
| CVE-2018-10373 | suse_vex | SUSE CVE CVE-2018-10373 | known affected: 457 known not affected: 264 recommended: 345 | 2026-07-29T00:01:21+00:00 | Vulnerability · Source |
| CVE-2018-11439 | suse_vex | SUSE CVE CVE-2018-11439 | known affected: 42 known not affected: 28 recommended: 237 | 2026-07-29T00:01:17+00:00 | Vulnerability · Source |
| CVE-2018-11713 | suse_vex | SUSE CVE CVE-2018-11713 | known not affected: 349 recommended: 1338 | 2026-07-29T00:01:15+00:00 | Vulnerability · Source |
| CVE-2018-11784 | suse_vex | SUSE CVE CVE-2018-11784 | known affected: 394 known not affected: 122 recommended: 331 | 2026-07-29T00:01:14+00:00 | Vulnerability · Source |
| CVE-2018-12180 | suse_vex | SUSE CVE CVE-2018-12180 | known affected: 50 recommended: 241 | 2026-07-29T00:01:12+00:00 | Vulnerability · Source |
| CVE-2018-12359 | suse_vex | SUSE CVE CVE-2018-12359 | known affected: 21 recommended: 451 | 2026-07-29T00:01:11+00:00 | Vulnerability · Source |
| CVE-2018-12377 | suse_vex | SUSE CVE CVE-2018-12377 | known not affected: 200 recommended: 819 | 2026-07-29T00:01:09+00:00 | Vulnerability · Source |
| CVE-2018-12395 | suse_vex | SUSE CVE CVE-2018-12395 | known affected: 1 recommended: 325 | 2026-07-29T00:01:08+00:00 | Vulnerability · Source |
| CVE-2018-12405 | suse_vex | SUSE CVE CVE-2018-12405 | known affected: 20 known not affected: 168 recommended: 1231 | 2026-07-29T00:01:06+00:00 | Vulnerability · Source |
| CVE-2018-12547 | suse_vex | SUSE CVE CVE-2018-12547 | known affected: 409 recommended: 183 | 2026-07-29T00:01:04+00:00 | Vulnerability · Source |
| CVE-2018-12904 | suse_vex | SUSE CVE CVE-2018-12904 | known affected: 28 known not affected: 404 recommended: 8 | 2026-07-29T00:01:03+00:00 | Vulnerability · Source |
| CVE-2018-12934 | suse_vex | SUSE CVE CVE-2018-12934 | known affected: 14 known not affected: 213 | 2026-07-29T00:01:01+00:00 | Vulnerability · Source |
| CVE-2018-13139 | suse_vex | SUSE CVE CVE-2018-13139 | known affected: 403 known not affected: 17 recommended: 243 | 2026-07-29T00:00:59+00:00 | Vulnerability · Source |
| CVE-2018-13988 | suse_vex | SUSE CVE CVE-2018-13988 | known affected: 8 known not affected: 386 recommended: 998 | 2026-07-29T00:00:57+00:00 | Vulnerability · Source |
| CVE-2018-14343 | suse_vex | SUSE CVE CVE-2018-14343 | known affected: 118 recommended: 1022 | 2026-07-29T00:00:56+00:00 | Vulnerability · Source |
| CVE-2018-14466 | suse_vex | SUSE CVE CVE-2018-14466 | known affected: 333 recommended: 145 | 2026-07-29T00:00:54+00:00 | Vulnerability · Source |
| CVE-2018-14468 | suse_vex | SUSE CVE CVE-2018-14468 | known affected: 333 recommended: 145 | 2026-07-29T00:00:52+00:00 | Vulnerability · Source |
| CVE-2018-14624 | suse_vex | SUSE CVE CVE-2018-14624 | recommended: 154 | 2026-07-29T00:00:50+00:00 | Vulnerability · Source |
| CVE-2018-14633 | suse_vex | SUSE CVE CVE-2018-14633 | known affected: 133 known not affected: 198 recommended: 910 | 2026-07-29T00:00:49+00:00 | Vulnerability · Source |
| CVE-2018-15127 | suse_vex | SUSE CVE CVE-2018-15127 | known affected: 41 recommended: 131 | 2026-07-29T00:00:47+00:00 | Vulnerability · Source |
| CVE-2018-15173 | suse_vex | SUSE CVE CVE-2018-15173 | known affected: 16 known not affected: 8 recommended: 105 | 2026-07-29T00:00:46+00:00 | Vulnerability · Source |
| CVE-2018-16151 | suse_vex | SUSE CVE CVE-2018-16151 | known affected: 26 known not affected: 135 recommended: 440 | 2026-07-29T00:00:44+00:00 | Vulnerability · Source |
| CVE-2018-16276 | suse_vex | SUSE CVE CVE-2018-16276 | known affected: 46 known not affected: 265 recommended: 357 | 2026-07-29T00:00:43+00:00 | Vulnerability · Source |
| CVE-2018-16368 | suse_vex | SUSE CVE CVE-2018-16368 | known not affected: 381 | 2026-07-29T00:00:41+00:00 | Vulnerability · Source |
| CVE-2018-16395 | suse_vex | SUSE CVE CVE-2018-16395 | known affected: 321 known not affected: 125 recommended: 495 | 2026-07-29T00:00:40+00:00 | Vulnerability · Source |
| CVE-2018-16396 | suse_vex | SUSE CVE CVE-2018-16396 | known affected: 323 known not affected: 45 recommended: 491 | 2026-07-29T00:00:38+00:00 | Vulnerability · Source |
| CVE-2018-16452 | suse_vex | SUSE CVE CVE-2018-16452 | known affected: 333 recommended: 145 | 2026-07-29T00:00:37+00:00 | Vulnerability · Source |
| CVE-2018-16541 | suse_vex | SUSE CVE CVE-2018-16541 | known affected: 16 recommended: 432 | 2026-07-29T00:00:35+00:00 | Vulnerability · Source |
| CVE-2018-16741 | suse_vex | SUSE CVE CVE-2018-16741 | known affected: 12 known not affected: 9 recommended: 153 | 2026-07-29T00:00:34+00:00 | Vulnerability · Source |
| CVE-2018-16853 | suse_vex | SUSE CVE CVE-2018-16853 | known affected: 320 known not affected: 1217 recommended: 2983 | 2026-07-29T00:00:32+00:00 | Vulnerability · Source |
| CVE-2018-16867 | suse_vex | SUSE CVE CVE-2018-16867 | known not affected: 275 | 2026-07-29T00:00:31+00:00 | Vulnerability · Source |
| CVE-2018-17204 | suse_vex | SUSE CVE CVE-2018-17204 | known not affected: 16 recommended: 4 | 2026-07-29T00:00:29+00:00 | Vulnerability · Source |
| CVE-2018-17206 | suse_vex | SUSE CVE CVE-2018-17206 | known not affected: 16 recommended: 4 | 2026-07-29T00:00:28+00:00 | Vulnerability · Source |
| CVE-2018-17466 | suse_vex | SUSE CVE CVE-2018-17466 | known affected: 20 known not affected: 168 recommended: 1244 | 2026-07-29T00:00:26+00:00 | Vulnerability · Source |
| CVE-2018-18064 | suse_vex | SUSE CVE CVE-2018-18064 | known not affected: 205 | 2026-07-29T00:00:24+00:00 | Vulnerability · Source |
| CVE-2018-18088 | suse_vex | SUSE CVE CVE-2018-18088 | known affected: 203 known not affected: 6 recommended: 57 | 2026-07-29T00:00:23+00:00 | Vulnerability · Source |
| CVE-2018-18309 | suse_vex | SUSE CVE CVE-2018-18309 | known affected: 448 recommended: 485 | 2026-07-29T00:00:22+00:00 | Vulnerability · Source |