VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
288586 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-33748 | suse_vex | SUSE CVE CVE-2026-33748 | known affected: 321 known not affected: 34 recommended: 73 | 2026-07-31T16:43:39+00:00 | Vulnerability · Source |
| CVE-2026-33809 | suse_vex | SUSE CVE CVE-2026-33809 | recommended: 20 | 2026-07-31T16:43:38+00:00 | Vulnerability · Source |
| CVE-2026-34001 | suse_vex | SUSE CVE CVE-2026-34001 | known affected: 424 recommended: 148 | 2026-07-31T16:43:30+00:00 | Vulnerability · Source |
| CVE-2026-35386 | suse_vex | SUSE CVE CVE-2026-35386 | known affected: 212 known not affected: 11 recommended: 20 | 2026-07-31T16:43:20+00:00 | Vulnerability · Source |
| CVE-2026-35387 | suse_vex | SUSE CVE CVE-2026-35387 | known affected: 223 recommended: 20 | 2026-07-31T16:43:19+00:00 | Vulnerability · Source |
| CVE-2026-39395 | suse_vex | SUSE CVE CVE-2026-39395 | known affected: 13 recommended: 30 | 2026-07-31T16:43:12+00:00 | Vulnerability · Source |
| CVE-2026-39817 | suse_vex | SUSE CVE CVE-2026-39817 | known affected: 67 known not affected: 51 recommended: 271 | 2026-07-31T16:43:10+00:00 | Vulnerability · Source |
| CVE-2026-39819 | suse_vex | SUSE CVE CVE-2026-39819 | known affected: 67 known not affected: 51 recommended: 271 | 2026-07-31T16:43:08+00:00 | Vulnerability · Source |
| CVE-2026-39822 | suse_vex | SUSE CVE CVE-2026-39822 | known affected: 67 known not affected: 51 recommended: 275 | 2026-07-31T16:43:05+00:00 | Vulnerability · Source |
| CVE-2026-39823 | suse_vex | SUSE CVE CVE-2026-39823 | known affected: 67 known not affected: 51 recommended: 271 | 2026-07-31T16:43:03+00:00 | Vulnerability · Source |
| CVE-2026-39825 | suse_vex | SUSE CVE CVE-2026-39825 | known affected: 67 known not affected: 51 recommended: 271 | 2026-07-31T16:43:02+00:00 | Vulnerability · Source |
| CVE-2026-39826 | suse_vex | SUSE CVE CVE-2026-39826 | known affected: 67 known not affected: 51 recommended: 271 | 2026-07-31T16:43:00+00:00 | Vulnerability · Source |
| CVE-2026-39836 | suse_vex | SUSE CVE CVE-2026-39836 | known affected: 67 known not affected: 51 recommended: 271 | 2026-07-31T16:42:56+00:00 | Vulnerability · Source |
| CVE-2026-40197 | suse_vex | SUSE CVE CVE-2026-40197 | No product status | 2026-07-31T16:42:50+00:00 | Vulnerability · Source |
| CVE-2026-40460 | suse_vex | SUSE CVE CVE-2026-40460 | known not affected: 43 recommended: 8 | 2026-07-31T16:42:45+00:00 | Vulnerability · Source |
| CVE-2026-41082 | suse_vex | SUSE CVE CVE-2026-41082 | recommended: 11 | 2026-07-31T16:42:36+00:00 | Vulnerability · Source |
| CVE-2026-41176 | suse_vex | SUSE CVE CVE-2026-41176 | recommended: 15 | 2026-07-31T16:42:34+00:00 | Vulnerability · Source |
| CVE-2026-41874 | suse_vex | SUSE CVE CVE-2026-41874 | No product status | 2026-07-31T16:42:22+00:00 | Vulnerability · Source |
| CVE-2026-42055 | suse_vex | SUSE CVE CVE-2026-42055 | first fixed: 24 known affected: 34 recommended: 49 | 2026-07-31T16:42:15+00:00 | Vulnerability · Source |
| CVE-2026-42448 | suse_vex | SUSE CVE CVE-2026-42448 | recommended: 6 | 2026-07-31T16:42:12+00:00 | Vulnerability · Source |
| CVE-2026-42501 | suse_vex | SUSE CVE CVE-2026-42501 | known affected: 67 known not affected: 51 recommended: 275 | 2026-07-31T16:42:10+00:00 | Vulnerability · Source |
| CVE-2026-42507 | suse_vex | SUSE CVE CVE-2026-42507 | known affected: 67 known not affected: 51 recommended: 263 | 2026-07-31T16:42:05+00:00 | Vulnerability · Source |
| CVE-2026-43503 | suse_vex | SUSE CVE CVE-2026-43503 | first fixed: 2 known affected: 431 known not affected: 4 recommended: 848 | 2026-07-31T16:41:06+00:00 | Vulnerability · Source |
| CVE-2026-44518 | suse_vex | SUSE CVE CVE-2026-44518 | known affected: 7 recommended: 21 | 2026-07-31T16:40:50+00:00 | Vulnerability · Source |
| CVE-2026-44660 | suse_vex | SUSE CVE CVE-2026-44660 | known affected: 52 | 2026-07-31T16:40:46+00:00 | Vulnerability · Source |
| CVE-2026-42586 | redhat_vex | netty-codec-redis: Netty: Command injection via CRLF characters in Redis codec encoder | fixed: 2 known affected: 3 known not affected: 2 | 2026-07-31T16:40:25+00:00 | Vulnerability · Source |
| CVE-2026-45974 | suse_vex | SUSE CVE CVE-2026-45974 | first fixed: 2 known affected: 512 known not affected: 93 recommended: 294 | 2026-07-31T16:40:17+00:00 | Vulnerability · Source |
| CVE-2026-46327 | suse_vex | SUSE CVE CVE-2026-46327 | known affected: 202 known not affected: 93 | 2026-07-31T16:39:43+00:00 | Vulnerability · Source |
| CVE-2026-46344 | suse_vex | SUSE CVE CVE-2026-46344 | known affected: 7 recommended: 25 | 2026-07-31T16:39:40+00:00 | Vulnerability · Source |
| CVE-2026-46680 | suse_vex | SUSE CVE CVE-2026-46680 | known affected: 190 recommended: 16 | 2026-07-31T16:39:27+00:00 | Vulnerability · Source |
| CVE-2026-47030 | suse_vex | SUSE CVE CVE-2026-47030 | known not affected: 510 recommended: 2 | 2026-07-31T16:39:16+00:00 | Vulnerability · Source |
| CVE-2026-47089 | suse_vex | SUSE CVE CVE-2026-47089 | recommended: 10 | 2026-07-31T16:39:09+00:00 | Vulnerability · Source |
| CVE-2026-47262 | suse_vex | SUSE CVE CVE-2026-47262 | known affected: 271 recommended: 16 | 2026-07-31T16:39:07+00:00 | Vulnerability · Source |
| CVE-2026-48142 | suse_vex | SUSE CVE CVE-2026-48142 | first fixed: 24 known affected: 34 recommended: 20 | 2026-07-31T16:39:00+00:00 | Vulnerability · Source |
| CVE-2026-48588 | suse_vex | SUSE CVE CVE-2026-48588 | recommended: 10 | 2026-07-31T16:38:58+00:00 | Vulnerability · Source |
| CVE-2026-49835 | suse_vex | SUSE CVE CVE-2026-49835 | known affected: 38 known not affected: 348 recommended: 4 | 2026-07-31T16:38:48+00:00 | Vulnerability · Source |
| CVE-2026-50195 | suse_vex | SUSE CVE CVE-2026-50195 | known not affected: 81 recommended: 3 | 2026-07-31T16:38:37+00:00 | Vulnerability · Source |
| CVE-2026-50642 | suse_vex | SUSE CVE CVE-2026-50642 | No product status | 2026-07-31T16:38:27+00:00 | Vulnerability · Source |
| CVE-2026-50811 | suse_vex | SUSE CVE CVE-2026-50811 | known not affected: 131 recommended: 32 | 2026-07-31T16:38:24+00:00 | Vulnerability · Source |
| CVE-2026-52791 | suse_vex | SUSE CVE CVE-2026-52791 | known affected: 33 | 2026-07-31T16:38:20+00:00 | Vulnerability · Source |
| CVE-2026-52863 | suse_vex | SUSE CVE CVE-2026-52863 | known not affected: 130 recommended: 6 | 2026-07-31T16:38:17+00:00 | Vulnerability · Source |
| CVE-2026-52949 | suse_vex | SUSE CVE CVE-2026-52949 | known not affected: 295 | 2026-07-31T16:38:13+00:00 | Vulnerability · Source |
| CVE-2026-53488 | suse_vex | SUSE CVE CVE-2026-53488 | known affected: 201 recommended: 16 | 2026-07-31T16:37:52+00:00 | Vulnerability · Source |
| CVE-2026-53489 | suse_vex | SUSE CVE CVE-2026-53489 | known affected: 80 recommended: 3 | 2026-07-31T16:37:50+00:00 | Vulnerability · Source |
| CVE-2026-53492 | suse_vex | SUSE CVE CVE-2026-53492 | known affected: 80 recommended: 3 | 2026-07-31T16:37:49+00:00 | Vulnerability · Source |
| CVE-2026-54761 | suse_vex | SUSE CVE CVE-2026-54761 | No product status | 2026-07-31T16:37:43+00:00 | Vulnerability · Source |
| CVE-2026-54762 | suse_vex | SUSE CVE CVE-2026-54762 | No product status | 2026-07-31T16:37:42+00:00 | Vulnerability · Source |
| CVE-2026-59849 | suse_vex | SUSE CVE CVE-2026-59849 | known affected: 20 known not affected: 136 recommended: 15 | 2026-07-31T16:36:40+00:00 | Vulnerability · Source |
| CVE-2026-59995 | suse_vex | SUSE CVE CVE-2026-59995 | known affected: 202 | 2026-07-31T16:36:34+00:00 | Vulnerability · Source |
| CVE-2026-59996 | suse_vex | SUSE CVE CVE-2026-59996 | known affected: 172 known not affected: 30 | 2026-07-31T16:36:33+00:00 | Vulnerability · Source |