VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
285031 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2015-5157 | suse_vex | SUSE CVE CVE-2015-5157 | known not affected: 45 recommended: 298 | 2026-07-26T01:13:57+00:00 | Vulnerability · Source |
| CVE-2015-5165 | suse_vex | SUSE CVE CVE-2015-5165 | known not affected: 123 recommended: 131 | 2026-07-26T01:13:55+00:00 | Vulnerability · Source |
| CVE-2015-5166 | suse_vex | SUSE CVE CVE-2015-5166 | known not affected: 8 recommended: 96 | 2026-07-26T01:13:52+00:00 | Vulnerability · Source |
| CVE-2015-5177 | suse_vex | SUSE CVE CVE-2015-5177 | known not affected: 47 | 2026-07-26T01:13:50+00:00 | Vulnerability · Source |
| CVE-2015-5185 | suse_vex | SUSE CVE CVE-2015-5185 | known affected: 1 known not affected: 45 recommended: 29 | 2026-07-26T01:13:48+00:00 | Vulnerability · Source |
| CVE-2015-5195 | suse_vex | SUSE CVE CVE-2015-5195 | known affected: 30 known not affected: 6 recommended: 5 | 2026-07-26T01:13:45+00:00 | Vulnerability · Source |
| CVE-2015-5199 | suse_vex | SUSE CVE CVE-2015-5199 | known not affected: 46 recommended: 201 | 2026-07-26T01:13:42+00:00 | Vulnerability · Source |
| CVE-2015-5200 | suse_vex | SUSE CVE CVE-2015-5200 | known not affected: 46 recommended: 201 | 2026-07-26T01:13:40+00:00 | Vulnerability · Source |
| CVE-2015-5218 | suse_vex | SUSE CVE CVE-2015-5218 | known affected: 321 known not affected: 349 recommended: 1671 | 2026-07-26T01:13:37+00:00 | Vulnerability · Source |
| CVE-2015-5239 | suse_vex | SUSE CVE CVE-2015-5239 | known affected: 320 known not affected: 587 recommended: 622 | 2026-07-26T01:13:34+00:00 | Vulnerability · Source |
| CVE-2015-5245 | suse_vex | SUSE CVE CVE-2015-5245 | known not affected: 583 recommended: 10 | 2026-07-26T01:13:31+00:00 | Vulnerability · Source |
| CVE-2015-5247 | suse_vex | SUSE CVE CVE-2015-5247 | known affected: 394 known not affected: 109 recommended: 2006 | 2026-07-26T01:13:28+00:00 | Vulnerability · Source |
| CVE-2015-5278 | suse_vex | SUSE CVE CVE-2015-5278 | known affected: 321 known not affected: 169 recommended: 2327 | 2026-07-26T01:13:25+00:00 | Vulnerability · Source |
| CVE-2015-5279 | suse_vex | SUSE CVE CVE-2015-5279 | known not affected: 136 recommended: 1783 | 2026-07-26T01:13:23+00:00 | Vulnerability · Source |
| CVE-2015-5288 | suse_vex | SUSE CVE CVE-2015-5288 | known affected: 2 recommended: 307 | 2026-07-26T01:13:20+00:00 | Vulnerability · Source |
| CVE-2015-5296 | suse_vex | SUSE CVE CVE-2015-5296 | known affected: 321 recommended: 4555 | 2026-07-26T01:13:17+00:00 | Vulnerability · Source |
| CVE-2015-5310 | suse_vex | SUSE CVE CVE-2015-5310 | known affected: 13 known not affected: 8 recommended: 88 | 2026-07-26T01:13:15+00:00 | Vulnerability · Source |
| CVE-2015-5345 | suse_vex | SUSE CVE CVE-2015-5345 | known affected: 394 recommended: 252 | 2026-07-26T01:13:11+00:00 | Vulnerability · Source |
| CVE-2015-5351 | suse_vex | SUSE CVE CVE-2015-5351 | known affected: 394 known not affected: 41 recommended: 220 | 2026-07-26T01:13:09+00:00 | Vulnerability · Source |
| CVE-2015-5400 | suse_vex | SUSE CVE CVE-2015-5400 | known affected: 394 known not affected: 60 recommended: 59 | 2026-07-26T01:13:06+00:00 | Vulnerability · Source |
| CVE-2015-5477 | suse_vex | SUSE CVE CVE-2015-5477 | known affected: 346 recommended: 1002 | 2026-07-26T01:13:04+00:00 | Vulnerability · Source |
| CVE-2015-5522 | suse_vex | SUSE CVE CVE-2015-5522 | recommended: 270 | 2026-07-26T01:13:01+00:00 | Vulnerability · Source |
| CVE-2015-5523 | suse_vex | SUSE CVE CVE-2015-5523 | recommended: 270 | 2026-07-26T01:12:59+00:00 | Vulnerability · Source |
| CVE-2015-5602 | suse_vex | SUSE CVE CVE-2015-5602 | known not affected: 85 | 2026-07-26T01:12:56+00:00 | Vulnerability · Source |
| CVE-2015-5722 | suse_vex | SUSE CVE CVE-2015-5722 | known affected: 347 recommended: 1002 | 2026-07-26T01:12:54+00:00 | Vulnerability · Source |
| CVE-2015-6243 | suse_vex | SUSE CVE CVE-2015-6243 | known affected: 1 recommended: 474 | 2026-07-26T01:12:51+00:00 | Vulnerability · Source |
| CVE-2015-6244 | suse_vex | SUSE CVE CVE-2015-6244 | known affected: 1 recommended: 474 | 2026-07-26T01:12:49+00:00 | Vulnerability · Source |
| CVE-2015-6246 | suse_vex | SUSE CVE CVE-2015-6246 | known affected: 1 recommended: 474 | 2026-07-26T01:12:46+00:00 | Vulnerability · Source |
| CVE-2015-6248 | suse_vex | SUSE CVE CVE-2015-6248 | known affected: 1 recommended: 474 | 2026-07-26T01:12:44+00:00 | Vulnerability · Source |
| CVE-2015-6252 | suse_vex | SUSE CVE CVE-2015-6252 | known not affected: 185 recommended: 301 | 2026-07-26T01:12:42+00:00 | Vulnerability · Source |
| CVE-2015-6526 | suse_vex | SUSE CVE CVE-2015-6526 | known not affected: 30 recommended: 12 | 2026-07-26T01:12:40+00:00 | Vulnerability · Source |
| CVE-2015-6564 | suse_vex | SUSE CVE CVE-2015-6564 | known affected: 2 known not affected: 5 recommended: 92 | 2026-07-26T01:12:37+00:00 | Vulnerability · Source |
| CVE-2015-6815 | suse_vex | SUSE CVE CVE-2015-6815 | known affected: 320 known not affected: 169 recommended: 2324 | 2026-07-26T01:12:34+00:00 | Vulnerability · Source |
| CVE-2015-7175 | suse_vex | SUSE CVE CVE-2015-7175 | known affected: 1 recommended: 468 | 2026-07-26T01:12:31+00:00 | Vulnerability · Source |
| CVE-2015-7177 | suse_vex | SUSE CVE CVE-2015-7177 | known affected: 1 recommended: 468 | 2026-07-26T01:12:28+00:00 | Vulnerability · Source |
| CVE-2015-7180 | suse_vex | SUSE CVE CVE-2015-7180 | known affected: 1 recommended: 472 | 2026-07-26T01:12:26+00:00 | Vulnerability · Source |
| CVE-2015-7182 | suse_vex | SUSE CVE CVE-2015-7182 | known affected: 5 known not affected: 183 recommended: 1657 | 2026-07-26T01:12:23+00:00 | Vulnerability · Source |
| CVE-2015-7183 | suse_vex | SUSE CVE CVE-2015-7183 | known affected: 399 known not affected: 183 recommended: 855 | 2026-07-26T01:12:20+00:00 | Vulnerability · Source |
| CVE-2015-7185 | suse_vex | SUSE CVE CVE-2015-7185 | known affected: 21 known not affected: 117 recommended: 255 | 2026-07-26T01:12:17+00:00 | Vulnerability · Source |
| CVE-2015-7187 | suse_vex | SUSE CVE CVE-2015-7187 | known affected: 5 known not affected: 183 recommended: 255 | 2026-07-26T01:12:15+00:00 | Vulnerability · Source |
| CVE-2015-7189 | suse_vex | SUSE CVE CVE-2015-7189 | known affected: 5 known not affected: 183 recommended: 621 | 2026-07-26T01:12:12+00:00 | Vulnerability · Source |
| CVE-2015-7192 | suse_vex | SUSE CVE CVE-2015-7192 | known affected: 5 known not affected: 183 recommended: 255 | 2026-07-26T01:12:10+00:00 | Vulnerability · Source |
| CVE-2015-7193 | suse_vex | SUSE CVE CVE-2015-7193 | known affected: 5 known not affected: 183 recommended: 621 | 2026-07-26T01:12:07+00:00 | Vulnerability · Source |
| CVE-2015-7197 | suse_vex | SUSE CVE CVE-2015-7197 | known affected: 5 known not affected: 183 recommended: 621 | 2026-07-26T01:12:05+00:00 | Vulnerability · Source |
| CVE-2015-7198 | suse_vex | SUSE CVE CVE-2015-7198 | known affected: 5 known not affected: 183 recommended: 621 | 2026-07-26T01:12:02+00:00 | Vulnerability · Source |
| CVE-2015-7212 | suse_vex | SUSE CVE CVE-2015-7212 | known affected: 2 recommended: 429 | 2026-07-26T01:11:59+00:00 | Vulnerability · Source |
| CVE-2015-7213 | suse_vex | SUSE CVE CVE-2015-7213 | known affected: 2 recommended: 429 | 2026-07-26T01:11:57+00:00 | Vulnerability · Source |
| CVE-2015-7214 | suse_vex | SUSE CVE CVE-2015-7214 | known affected: 2 recommended: 429 | 2026-07-26T01:11:54+00:00 | Vulnerability · Source |
| CVE-2015-7236 | suse_vex | SUSE CVE CVE-2015-7236 | known affected: 320 known not affected: 22 recommended: 172 | 2026-07-26T01:11:50+00:00 | Vulnerability · Source |
| CVE-2015-7295 | suse_vex | SUSE CVE CVE-2015-7295 | known not affected: 192 recommended: 1783 | 2026-07-26T01:11:47+00:00 | Vulnerability · Source |