VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
282938 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-53379 | suse_vex | SUSE CVE CVE-2026-53379 | known affected: 144 known not affected: 140 | 2026-07-21T13:07:06+00:00 | Vulnerability · Source |
| CVE-2026-53380 | suse_vex | SUSE CVE CVE-2026-53380 | known not affected: 284 | 2026-07-21T13:07:05+00:00 | Vulnerability · Source |
| CVE-2026-53381 | suse_vex | SUSE CVE CVE-2026-53381 | No product status | 2026-07-21T13:07:04+00:00 | Vulnerability · Source |
| CVE-2026-53382 | suse_vex | SUSE CVE CVE-2026-53382 | No product status | 2026-07-21T13:07:03+00:00 | Vulnerability · Source |
| CVE-2026-53383 | suse_vex | SUSE CVE CVE-2026-53383 | No product status | 2026-07-21T13:07:02+00:00 | Vulnerability · Source |
| CVE-2026-53384 | suse_vex | SUSE CVE CVE-2026-53384 | No product status | 2026-07-21T13:07:01+00:00 | Vulnerability · Source |
| CVE-2026-41602 | redhat_vex | github.com/apache/thrift: Apache Thrift: Integer Overflow in TFramedTransport Go implementation | fixed: 48 known affected: 12 known not affected: 646 | 2026-07-21T13:06:59+00:00 | Vulnerability · Source |
| CVE-2026-53385 | suse_vex | SUSE CVE CVE-2026-53385 | No product status | 2026-07-21T13:06:59+00:00 | Vulnerability · Source |
| CVE-2026-53386 | suse_vex | SUSE CVE CVE-2026-53386 | No product status | 2026-07-21T13:06:58+00:00 | Vulnerability · Source |
| CVE-2026-53387 | suse_vex | SUSE CVE CVE-2026-53387 | No product status | 2026-07-21T13:06:57+00:00 | Vulnerability · Source |
| CVE-2026-53388 | suse_vex | SUSE CVE CVE-2026-53388 | No product status | 2026-07-21T13:06:55+00:00 | Vulnerability · Source |
| CVE-2026-53389 | suse_vex | SUSE CVE CVE-2026-53389 | No product status | 2026-07-21T13:06:54+00:00 | Vulnerability · Source |
| CVE-2026-53390 | suse_vex | SUSE CVE CVE-2026-53390 | No product status | 2026-07-21T13:06:53+00:00 | Vulnerability · Source |
| CVE-2026-53391 | suse_vex | SUSE CVE CVE-2026-53391 | No product status | 2026-07-21T13:06:51+00:00 | Vulnerability · Source |
| CVE-2026-53392 | suse_vex | SUSE CVE CVE-2026-53392 | No product status | 2026-07-21T13:06:50+00:00 | Vulnerability · Source |
| CVE-2026-53394 | suse_vex | SUSE CVE CVE-2026-53394 | No product status | 2026-07-21T13:06:48+00:00 | Vulnerability · Source |
| CVE-2026-53395 | suse_vex | SUSE CVE CVE-2026-53395 | No product status | 2026-07-21T13:06:46+00:00 | Vulnerability · Source |
| CVE-2026-53396 | suse_vex | SUSE CVE CVE-2026-53396 | No product status | 2026-07-21T13:06:45+00:00 | Vulnerability · Source |
| CVE-2026-53397 | suse_vex | SUSE CVE CVE-2026-53397 | No product status | 2026-07-21T13:06:43+00:00 | Vulnerability · Source |
| CVE-2026-53398 | suse_vex | SUSE CVE CVE-2026-53398 | No product status | 2026-07-21T13:06:42+00:00 | Vulnerability · Source |
| CVE-2026-53399 | suse_vex | SUSE CVE CVE-2026-53399 | No product status | 2026-07-21T13:06:40+00:00 | Vulnerability · Source |
| CVE-2026-53400 | suse_vex | SUSE CVE CVE-2026-53400 | No product status | 2026-07-21T13:06:39+00:00 | Vulnerability · Source |
| CVE-2026-53401 | suse_vex | SUSE CVE CVE-2026-53401 | No product status | 2026-07-21T13:06:37+00:00 | Vulnerability · Source |
| CVE-2026-53402 | suse_vex | SUSE CVE CVE-2026-53402 | No product status | 2026-07-21T13:06:36+00:00 | Vulnerability · Source |
| CVE-2026-53403 | suse_vex | SUSE CVE CVE-2026-53403 | No product status | 2026-07-21T13:06:35+00:00 | Vulnerability · Source |
| CVE-2026-53994 | suse_vex | SUSE CVE CVE-2026-53994 | known affected: 63 | 2026-07-21T13:06:32+00:00 | Vulnerability · Source |
| CVE-2026-54369 | suse_vex | SUSE CVE CVE-2026-54369 | known affected: 192 recommended: 5 | 2026-07-21T13:06:30+00:00 | Vulnerability · Source |
| CVE-2026-54538 | suse_vex | SUSE CVE CVE-2026-54538 | known affected: 93 | 2026-07-21T13:06:27+00:00 | Vulnerability · Source |
| CVE-2026-55200 | suse_vex | SUSE CVE CVE-2026-55200 | known affected: 9 known not affected: 114 recommended: 10 | 2026-07-21T13:06:26+00:00 | Vulnerability · Source |
| CVE-2026-55203 | suse_vex | SUSE CVE CVE-2026-55203 | known affected: 4 known not affected: 2 recommended: 13 | 2026-07-21T13:06:24+00:00 | Vulnerability · Source |
| CVE-2026-55204 | suse_vex | SUSE CVE CVE-2026-55204 | known affected: 4 known not affected: 2 recommended: 13 | 2026-07-21T13:06:23+00:00 | Vulnerability · Source |
| CVE-2026-55238 | suse_vex | SUSE CVE CVE-2026-55238 | known affected: 93 | 2026-07-21T13:06:21+00:00 | Vulnerability · Source |
| CVE-2026-55626 | suse_vex | SUSE CVE CVE-2026-55626 | known not affected: 93 | 2026-07-21T13:06:20+00:00 | Vulnerability · Source |
| CVE-2026-55639 | suse_vex | SUSE CVE CVE-2026-55639 | known affected: 93 | 2026-07-21T13:06:19+00:00 | Vulnerability · Source |
| CVE-2026-55645 | suse_vex | SUSE CVE CVE-2026-55645 | known affected: 93 | 2026-07-21T13:06:17+00:00 | Vulnerability · Source |
| CVE-2026-55831 | suse_vex | SUSE CVE CVE-2026-55831 | known affected: 3 known not affected: 42 | 2026-07-21T13:06:16+00:00 | Vulnerability · Source |
| CVE-2026-55833 | suse_vex | SUSE CVE CVE-2026-55833 | known affected: 3 known not affected: 42 | 2026-07-21T13:06:15+00:00 | Vulnerability · Source |
| CVE-2026-56109 | suse_vex | SUSE CVE CVE-2026-56109 | first fixed: 26 known affected: 539 recommended: 26 | 2026-07-21T13:06:13+00:00 | Vulnerability · Source |
| CVE-2026-56375 | suse_vex | SUSE CVE CVE-2026-56375 | No product status | 2026-07-21T13:06:12+00:00 | Vulnerability · Source |
| CVE-2026-56741 | suse_vex | SUSE CVE CVE-2026-56741 | known not affected: 35 | 2026-07-21T13:06:09+00:00 | Vulnerability · Source |
| CVE-2026-58469 | suse_vex | SUSE CVE CVE-2026-58469 | known affected: 32 known not affected: 4 recommended: 2 | 2026-07-21T13:06:02+00:00 | Vulnerability · Source |
| CVE-2026-58470 | suse_vex | SUSE CVE CVE-2026-58470 | known affected: 36 recommended: 2 | 2026-07-21T13:06:01+00:00 | Vulnerability · Source |
| CVE-2026-58471 | suse_vex | SUSE CVE CVE-2026-58471 | known affected: 32 known not affected: 4 recommended: 2 | 2026-07-21T13:06:00+00:00 | Vulnerability · Source |
| CVE-2026-58472 | suse_vex | SUSE CVE CVE-2026-58472 | known affected: 36 recommended: 2 | 2026-07-21T13:05:58+00:00 | Vulnerability · Source |
| CVE-2026-59884 | suse_vex | SUSE CVE CVE-2026-59884 | known affected: 99 | 2026-07-21T13:05:51+00:00 | Vulnerability · Source |
| CVE-2026-59885 | suse_vex | SUSE CVE CVE-2026-59885 | known affected: 99 | 2026-07-21T13:05:50+00:00 | Vulnerability · Source |
| CVE-2026-59886 | suse_vex | SUSE CVE CVE-2026-59886 | first fixed: 22 known affected: 100 | 2026-07-21T13:05:48+00:00 | Vulnerability · Source |
| CVE-2026-59888 | suse_vex | SUSE CVE CVE-2026-59888 | known affected: 27 | 2026-07-21T13:05:47+00:00 | Vulnerability · Source |
| CVE-2026-59889 | suse_vex | SUSE CVE CVE-2026-59889 | first fixed: 24 known affected: 27 recommended: 2 | 2026-07-21T13:05:46+00:00 | Vulnerability · Source |
| CVE-2026-60081 | suse_vex | SUSE CVE CVE-2026-60081 | first fixed: 7 known affected: 31 | 2026-07-21T13:05:44+00:00 | Vulnerability · Source |