VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291911 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-5588 | suse_vex | SUSE CVE CVE-2026-5588 | known affected: 24 recommended: 104 | 2026-08-07T17:10:49+00:00 | Vulnerability · Source |
| CVE-2026-5598 | suse_vex | SUSE CVE CVE-2026-5598 | known affected: 24 recommended: 104 | 2026-08-07T17:10:48+00:00 | Vulnerability · Source |
| CVE-2026-5674 | suse_vex | SUSE CVE CVE-2026-5674 | known affected: 193 recommended: 23 | 2026-08-07T17:10:47+00:00 | Vulnerability · Source |
| CVE-2026-7837 | suse_vex | SUSE CVE CVE-2026-7837 | known affected: 4 | 2026-08-07T17:10:35+00:00 | Vulnerability · Source |
| CVE-2026-7896 | suse_vex | SUSE CVE CVE-2026-7896 | recommended: 6 | 2026-08-07T17:10:32+00:00 | Vulnerability · Source |
| CVE-2026-9537 | suse_vex | SUSE CVE CVE-2026-9537 | recommended: 2 | 2026-08-07T17:10:19+00:00 | Vulnerability · Source |
| CVE-2026-11793 | suse_vex | SUSE CVE CVE-2026-11793 | known affected: 54 recommended: 40 | 2026-08-07T17:10:10+00:00 | Vulnerability · Source |
| CVE-2026-18103 | suse_vex | SUSE CVE CVE-2026-18103 | known affected: 141 | 2026-08-07T17:09:03+00:00 | Vulnerability · Source |
| CVE-2026-18487 | suse_vex | SUSE CVE CVE-2026-18487 | No product status | 2026-08-07T17:09:01+00:00 | Vulnerability · Source |
| CVE-2026-31448 | suse_vex | SUSE CVE CVE-2026-31448 | first fixed: 2 known affected: 394 known not affected: 233 recommended: 294 | 2026-08-07T17:07:58+00:00 | Vulnerability · Source |
| CVE-2026-31786 | suse_vex | SUSE CVE CVE-2026-31786 | known affected: 24 known not affected: 79 recommended: 107 | 2026-08-07T17:07:30+00:00 | Vulnerability · Source |
| CVE-2026-31787 | suse_vex | SUSE CVE CVE-2026-31787 | first fixed: 2 known affected: 463 known not affected: 4 recommended: 617 | 2026-08-07T17:07:29+00:00 | Vulnerability · Source |
| CVE-2026-32327 | suse_vex | SUSE CVE CVE-2026-32327 | known affected: 158 | 2026-08-07T17:07:25+00:00 | Vulnerability · Source |
| CVE-2026-32766 | suse_vex | SUSE CVE CVE-2026-32766 | known not affected: 5 recommended: 7 | 2026-08-07T17:07:23+00:00 | Vulnerability · Source |
| CVE-2026-34966 | suse_vex | SUSE CVE CVE-2026-34966 | No product status | 2026-08-07T17:07:16+00:00 | Vulnerability · Source |
| CVE-2026-39882 | suse_vex | SUSE CVE CVE-2026-39882 | first fixed: 13 known affected: 318 | 2026-08-07T17:07:00+00:00 | Vulnerability · Source |
| CVE-2026-43260 | suse_vex | SUSE CVE CVE-2026-43260 | first fixed: 2 known affected: 394 known not affected: 223 recommended: 326 | 2026-08-07T17:06:02+00:00 | Vulnerability · Source |
| CVE-2026-43492 | suse_vex | SUSE CVE CVE-2026-43492 | first fixed: 2 known affected: 569 known not affected: 4 recommended: 306 | 2026-08-07T17:05:45+00:00 | Vulnerability · Source |
| CVE-2026-43622 | suse_vex | SUSE CVE CVE-2026-43622 | No product status | 2026-08-07T17:05:43+00:00 | Vulnerability · Source |
| CVE-2026-43627 | suse_vex | SUSE CVE CVE-2026-43627 | No product status | 2026-08-07T17:05:42+00:00 | Vulnerability · Source |
| CVE-2026-43628 | suse_vex | SUSE CVE CVE-2026-43628 | No product status | 2026-08-07T17:05:41+00:00 | Vulnerability · Source |
| CVE-2026-43629 | suse_vex | SUSE CVE CVE-2026-43629 | No product status | 2026-08-07T17:05:39+00:00 | Vulnerability · Source |
| CVE-2026-43630 | suse_vex | SUSE CVE CVE-2026-43630 | No product status | 2026-08-07T17:05:38+00:00 | Vulnerability · Source |
| CVE-2026-43631 | suse_vex | SUSE CVE CVE-2026-43631 | No product status | 2026-08-07T17:05:36+00:00 | Vulnerability · Source |
| CVE-2026-43632 | suse_vex | SUSE CVE CVE-2026-43632 | No product status | 2026-08-07T17:05:35+00:00 | Vulnerability · Source |
| CVE-2026-45850 | suse_vex | SUSE CVE CVE-2026-45850 | known affected: 295 | 2026-08-07T17:04:51+00:00 | Vulnerability · Source |
| CVE-2026-62992 | redhat_vex | php-smarty: symlink path traversal out of trusted directories | known not affected: 1 | 2026-08-07T17:04:19+00:00 | Vulnerability · Source |
| CVE-2026-46330 | suse_vex | SUSE CVE CVE-2026-46330 | known affected: 394 known not affected: 133 recommended: 132 | 2026-08-07T17:04:09+00:00 | Vulnerability · Source |
| CVE-2026-46917 | suse_vex | SUSE CVE CVE-2026-46917 | known affected: 261 recommended: 466 | 2026-08-07T17:04:01+00:00 | Vulnerability · Source |
| CVE-2026-48145 | suse_vex | SUSE CVE CVE-2026-48145 | recommended: 17 | 2026-08-07T17:03:38+00:00 | Vulnerability · Source |
| CVE-2026-49980 | suse_vex | SUSE CVE CVE-2026-49980 | recommended: 9 | 2026-08-07T17:03:30+00:00 | Vulnerability · Source |
| CVE-2026-50159 | suse_vex | SUSE CVE CVE-2026-50159 | No product status | 2026-08-07T17:03:27+00:00 | Vulnerability · Source |
| CVE-2026-52987 | suse_vex | SUSE CVE CVE-2026-52987 | known not affected: 293 | 2026-08-07T17:03:12+00:00 | Vulnerability · Source |
| CVE-2026-54619 | suse_vex | SUSE CVE CVE-2026-54619 | known affected: 4 | 2026-08-07T17:02:41+00:00 | Vulnerability · Source |
| CVE-2026-59084 | suse_vex | SUSE CVE CVE-2026-59084 | known affected: 43 recommended: 374 | 2026-08-07T17:01:50+00:00 | Vulnerability · Source |
| CVE-2026-61632 | suse_vex | SUSE CVE CVE-2026-61632 | No product status | 2026-08-07T17:01:05+00:00 | Vulnerability · Source |
| CVE-2026-64039 | suse_vex | SUSE CVE CVE-2026-64039 | known not affected: 298 | 2026-08-07T17:00:56+00:00 | Vulnerability · Source |
| CVE-2026-64051 | suse_vex | SUSE CVE CVE-2026-64051 | known not affected: 296 | 2026-08-07T17:00:55+00:00 | Vulnerability · Source |
| CVE-2026-64083 | suse_vex | SUSE CVE CVE-2026-64083 | known not affected: 298 | 2026-08-07T17:00:53+00:00 | Vulnerability · Source |
| CVE-2026-64084 | suse_vex | SUSE CVE CVE-2026-64084 | known not affected: 298 | 2026-08-07T17:00:52+00:00 | Vulnerability · Source |
| CVE-2026-64086 | suse_vex | SUSE CVE CVE-2026-64086 | known not affected: 298 | 2026-08-07T17:00:51+00:00 | Vulnerability · Source |
| CVE-2026-64096 | suse_vex | SUSE CVE CVE-2026-64096 | known affected: 292 known not affected: 4 | 2026-08-07T17:00:50+00:00 | Vulnerability · Source |
| CVE-2026-64123 | suse_vex | SUSE CVE CVE-2026-64123 | known affected: 243 known not affected: 53 | 2026-08-07T17:00:48+00:00 | Vulnerability · Source |
| CVE-2026-64135 | suse_vex | SUSE CVE CVE-2026-64135 | known not affected: 298 | 2026-08-07T17:00:47+00:00 | Vulnerability · Source |
| CVE-2026-64163 | suse_vex | SUSE CVE CVE-2026-64163 | known affected: 9 known not affected: 289 | 2026-08-07T17:00:45+00:00 | Vulnerability · Source |
| CVE-2026-64516 | suse_vex | SUSE CVE CVE-2026-64516 | known not affected: 298 | 2026-08-07T16:59:55+00:00 | Vulnerability · Source |
| CVE-2026-64517 | suse_vex | SUSE CVE CVE-2026-64517 | known not affected: 298 | 2026-08-07T16:59:54+00:00 | Vulnerability · Source |
| CVE-2026-64519 | suse_vex | SUSE CVE CVE-2026-64519 | known affected: 29 known not affected: 269 | 2026-08-07T16:59:53+00:00 | Vulnerability · Source |
| CVE-2026-64520 | suse_vex | SUSE CVE CVE-2026-64520 | known affected: 17 known not affected: 281 | 2026-08-07T16:59:51+00:00 | Vulnerability · Source |
| CVE-2026-64521 | suse_vex | SUSE CVE CVE-2026-64521 | known not affected: 298 | 2026-08-07T16:59:50+00:00 | Vulnerability · Source |