VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294017 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2019-13272 | suse_vex | SUSE CVE CVE-2019-13272 | known affected: 84 known not affected: 418 recommended: 285 | 2026-07-25T18:01:53+00:00 | Vulnerability · Source |
| CVE-2019-13301 | suse_vex | SUSE CVE CVE-2019-13301 | known affected: 142 recommended: 728 | 2026-07-25T18:01:43+00:00 | Vulnerability · Source |
| CVE-2019-14192 | suse_vex | SUSE CVE CVE-2019-14192 | known affected: 19 recommended: 46 | 2026-07-25T18:01:29+00:00 | Vulnerability · Source |
| CVE-2019-14275 | suse_vex | SUSE CVE CVE-2019-14275 | known affected: 12 known not affected: 8 recommended: 40 | 2026-07-25T18:01:26+00:00 | Vulnerability · Source |
| CVE-2019-14289 | suse_vex | SUSE CVE CVE-2019-14289 | known not affected: 895 | 2026-07-25T18:01:24+00:00 | Vulnerability · Source |
| CVE-2019-14299 | suse_vex | SUSE CVE CVE-2019-14299 | recommended: 8 | 2026-07-25T18:01:21+00:00 | Vulnerability · Source |
| CVE-2019-14494 | suse_vex | SUSE CVE CVE-2019-14494 | known affected: 51 known not affected: 213 recommended: 191 | 2026-07-25T18:01:19+00:00 | Vulnerability · Source |
| CVE-2019-14513 | suse_vex | SUSE CVE CVE-2019-14513 | known not affected: 87 | 2026-07-25T18:01:17+00:00 | Vulnerability · Source |
| CVE-2019-14763 | suse_vex | SUSE CVE CVE-2019-14763 | known not affected: 433 | 2026-07-25T18:01:10+00:00 | Vulnerability · Source |
| CVE-2019-14844 | suse_vex | SUSE CVE CVE-2019-14844 | known affected: 16 known not affected: 231 | 2026-07-25T18:00:56+00:00 | Vulnerability · Source |
| CVE-2019-14869 | suse_vex | SUSE CVE CVE-2019-14869 | known affected: 20 known not affected: 24 recommended: 266 | 2026-07-25T18:00:50+00:00 | Vulnerability · Source |
| CVE-2019-15031 | suse_vex | SUSE CVE CVE-2019-15031 | known affected: 428 known not affected: 252 recommended: 1451 | 2026-07-25T18:00:33+00:00 | Vulnerability · Source |
| CVE-2019-15034 | suse_vex | SUSE CVE CVE-2019-15034 | known affected: 104 known not affected: 674 recommended: 289 | 2026-07-25T18:00:32+00:00 | Vulnerability · Source |
| CVE-2019-15043 | suse_vex | SUSE CVE CVE-2019-15043 | known affected: 3 known not affected: 6 recommended: 1009 | 2026-07-25T18:00:30+00:00 | Vulnerability · Source |
| CVE-2019-15117 | suse_vex | SUSE CVE CVE-2019-15117 | known not affected: 102 recommended: 804 | 2026-07-25T18:00:24+00:00 | Vulnerability · Source |
| CVE-2019-15718 | suse_vex | SUSE CVE CVE-2019-15718 | known affected: 22 known not affected: 340 recommended: 8 | 2026-07-25T18:00:06+00:00 | Vulnerability · Source |
| CVE-2019-15807 | suse_vex | SUSE CVE CVE-2019-15807 | known not affected: 313 recommended: 284 | 2026-07-25T18:00:05+00:00 | Vulnerability · Source |
| CVE-2019-15923 | suse_vex | SUSE CVE CVE-2019-15923 | known not affected: 372 | 2026-07-25T17:59:58+00:00 | Vulnerability · Source |
| CVE-2019-15925 | suse_vex | SUSE CVE CVE-2019-15925 | known not affected: 459 recommended: 20 | 2026-07-25T17:59:56+00:00 | Vulnerability · Source |
| CVE-2019-15926 | suse_vex | SUSE CVE CVE-2019-15926 | known not affected: 84 recommended: 859 | 2026-07-25T17:59:55+00:00 | Vulnerability · Source |
| CVE-2019-16163 | suse_vex | SUSE CVE CVE-2019-16163 | known affected: 284 known not affected: 11 recommended: 297 | 2026-07-25T17:59:52+00:00 | Vulnerability · Source |
| CVE-2019-16255 | suse_vex | SUSE CVE CVE-2019-16255 | known affected: 322 known not affected: 23 recommended: 489 | 2026-07-25T17:59:47+00:00 | Vulnerability · Source |
| CVE-2019-16935 | suse_vex | SUSE CVE CVE-2019-16935 | known affected: 353 recommended: 1548 | 2026-07-25T17:59:36+00:00 | Vulnerability · Source |
| CVE-2019-16995 | suse_vex | SUSE CVE CVE-2019-16995 | known not affected: 93 recommended: 718 | 2026-07-25T17:59:33+00:00 | Vulnerability · Source |
| CVE-2019-17012 | suse_vex | SUSE CVE CVE-2019-17012 | known affected: 20 known not affected: 176 recommended: 449 | 2026-07-25T17:59:30+00:00 | Vulnerability · Source |
| CVE-2019-17041 | suse_vex | SUSE CVE CVE-2019-17041 | known affected: 425 known not affected: 199 recommended: 367 | 2026-07-25T17:59:25+00:00 | Vulnerability · Source |
| CVE-2019-17341 | suse_vex | SUSE CVE CVE-2019-17341 | known affected: 18 known not affected: 13 recommended: 226 | 2026-07-25T17:59:21+00:00 | Vulnerability · Source |
| CVE-2019-17342 | suse_vex | SUSE CVE CVE-2019-17342 | known affected: 18 known not affected: 13 recommended: 226 | 2026-07-25T17:59:19+00:00 | Vulnerability · Source |
| CVE-2019-17343 | suse_vex | SUSE CVE CVE-2019-17343 | known affected: 18 known not affected: 13 recommended: 226 | 2026-07-25T17:59:18+00:00 | Vulnerability · Source |
| CVE-2019-17349 | suse_vex | SUSE CVE CVE-2019-17349 | known affected: 320 known not affected: 76 recommended: 380 | 2026-07-25T17:59:15+00:00 | Vulnerability · Source |
| CVE-2019-17541 | suse_vex | SUSE CVE CVE-2019-17541 | known not affected: 645 recommended: 34 | 2026-07-25T17:59:10+00:00 | Vulnerability · Source |
| CVE-2019-18276 | suse_vex | SUSE CVE CVE-2019-18276 | recommended: 2 | 2026-07-25T17:59:03+00:00 | Vulnerability · Source |
| CVE-2019-18281 | suse_vex | SUSE CVE CVE-2019-18281 | known not affected: 964 recommended: 81 | 2026-07-25T17:59:01+00:00 | Vulnerability · Source |
| CVE-2019-18423 | suse_vex | SUSE CVE CVE-2019-18423 | known not affected: 36 recommended: 179 | 2026-07-25T17:58:57+00:00 | Vulnerability · Source |
| CVE-2019-18425 | suse_vex | SUSE CVE CVE-2019-18425 | recommended: 269 | 2026-07-25T17:58:56+00:00 | Vulnerability · Source |
| CVE-2019-18810 | suse_vex | SUSE CVE CVE-2019-18810 | known not affected: 223 | 2026-07-25T17:58:45+00:00 | Vulnerability · Source |
| CVE-2019-18853 | suse_vex | SUSE CVE CVE-2019-18853 | known affected: 20 known not affected: 476 | 2026-07-25T17:58:40+00:00 | Vulnerability · Source |
| CVE-2019-18905 | suse_vex | SUSE CVE CVE-2019-18905 | known affected: 394 known not affected: 113 recommended: 110 | 2026-07-25T17:58:32+00:00 | Vulnerability · Source |
| CVE-2019-19036 | suse_vex | SUSE CVE CVE-2019-19036 | known affected: 72 known not affected: 101 recommended: 501 | 2026-07-25T17:58:31+00:00 | Vulnerability · Source |
| CVE-2019-19059 | suse_vex | SUSE CVE CVE-2019-19059 | known not affected: 458 recommended: 33 | 2026-07-25T17:58:19+00:00 | Vulnerability · Source |
| CVE-2019-19072 | suse_vex | SUSE CVE CVE-2019-19072 | known affected: 320 known not affected: 381 recommended: 801 | 2026-07-25T17:58:12+00:00 | Vulnerability · Source |
| CVE-2019-19317 | suse_vex | SUSE CVE CVE-2019-19317 | known affected: 314 known not affected: 76 recommended: 435 | 2026-07-25T17:57:58+00:00 | Vulnerability · Source |
| CVE-2019-19378 | suse_vex | SUSE CVE CVE-2019-19378 | known not affected: 459 | 2026-07-25T17:57:53+00:00 | Vulnerability · Source |
| CVE-2019-19448 | suse_vex | SUSE CVE CVE-2019-19448 | known not affected: 348 | 2026-07-25T17:57:51+00:00 | Vulnerability · Source |
| CVE-2019-19529 | suse_vex | SUSE CVE CVE-2019-19529 | known affected: 428 known not affected: 153 recommended: 1328 | 2026-07-25T17:57:43+00:00 | Vulnerability · Source |
| CVE-2019-19535 | suse_vex | SUSE CVE CVE-2019-19535 | known affected: 124 known not affected: 40 recommended: 676 | 2026-07-25T17:57:38+00:00 | Vulnerability · Source |
| CVE-2019-19646 | suse_vex | SUSE CVE CVE-2019-19646 | known affected: 299 known not affected: 29 recommended: 435 | 2026-07-25T17:57:31+00:00 | Vulnerability · Source |
| CVE-2019-19797 | suse_vex | SUSE CVE CVE-2019-19797 | known affected: 1 known not affected: 23 recommended: 47 | 2026-07-25T17:57:22+00:00 | Vulnerability · Source |
| CVE-2019-19813 | suse_vex | SUSE CVE CVE-2019-19813 | known affected: 14 known not affected: 251 | 2026-07-25T17:57:20+00:00 | Vulnerability · Source |
| CVE-2019-19816 | suse_vex | SUSE CVE CVE-2019-19816 | known not affected: 207 | 2026-07-25T17:57:19+00:00 | Vulnerability · Source |