VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286675 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-42876 | suse_vex | SUSE CVE CVE-2026-42876 | No product status | 2026-07-30T16:52:10+00:00 | Vulnerability · Source |
| CVE-2026-42880 | suse_vex | SUSE CVE CVE-2026-42880 | No product status | 2026-07-30T16:52:09+00:00 | Vulnerability · Source |
| CVE-2026-42882 | suse_vex | SUSE CVE CVE-2026-42882 | No product status | 2026-07-30T16:52:08+00:00 | Vulnerability · Source |
| CVE-2026-42923 | suse_vex | SUSE CVE CVE-2026-42923 | known affected: 28 recommended: 94 | 2026-07-30T16:52:06+00:00 | Vulnerability · Source |
| CVE-2026-42944 | suse_vex | SUSE CVE CVE-2026-42944 | known affected: 28 recommended: 110 | 2026-07-30T16:52:05+00:00 | Vulnerability · Source |
| CVE-2026-42959 | suse_vex | SUSE CVE CVE-2026-42959 | known affected: 28 recommended: 110 | 2026-07-30T16:52:03+00:00 | Vulnerability · Source |
| CVE-2026-42960 | suse_vex | SUSE CVE CVE-2026-42960 | known affected: 28 recommended: 94 | 2026-07-30T16:52:02+00:00 | Vulnerability · Source |
| CVE-2026-43294 | suse_vex | SUSE CVE CVE-2026-43294 | known affected: 424 known not affected: 181 recommended: 120 | 2026-07-30T16:51:36+00:00 | Vulnerability · Source |
| CVE-2026-43414 | suse_vex | SUSE CVE CVE-2026-43414 | first fixed: 2 known affected: 512 known not affected: 63 recommended: 400 | 2026-07-30T16:51:26+00:00 | Vulnerability · Source |
| CVE-2026-43451 | suse_vex | SUSE CVE CVE-2026-43451 | known affected: 289 known not affected: 6 | 2026-07-30T16:51:23+00:00 | Vulnerability · Source |
| CVE-2026-43484 | suse_vex | SUSE CVE CVE-2026-43484 | known affected: 252 known not affected: 60 | 2026-07-30T16:51:16+00:00 | Vulnerability · Source |
| CVE-2026-43485 | suse_vex | SUSE CVE CVE-2026-43485 | known affected: 91 known not affected: 221 | 2026-07-30T16:51:15+00:00 | Vulnerability · Source |
| CVE-2026-43644 | suse_vex | SUSE CVE CVE-2026-43644 | No product status | 2026-07-30T16:51:04+00:00 | Vulnerability · Source |
| CVE-2026-44015 | suse_vex | SUSE CVE CVE-2026-44015 | No product status | 2026-07-30T16:50:16+00:00 | Vulnerability · Source |
| CVE-2026-44245 | suse_vex | SUSE CVE CVE-2026-44245 | No product status | 2026-07-30T16:50:11+00:00 | Vulnerability · Source |
| CVE-2026-44247 | suse_vex | SUSE CVE CVE-2026-44247 | No product status | 2026-07-30T16:50:09+00:00 | Vulnerability · Source |
| CVE-2026-44315 | suse_vex | SUSE CVE CVE-2026-44315 | No product status | 2026-07-30T16:50:04+00:00 | Vulnerability · Source |
| CVE-2026-44316 | suse_vex | SUSE CVE CVE-2026-44316 | No product status | 2026-07-30T16:50:03+00:00 | Vulnerability · Source |
| CVE-2026-44317 | suse_vex | SUSE CVE CVE-2026-44317 | No product status | 2026-07-30T16:50:01+00:00 | Vulnerability · Source |
| CVE-2026-44318 | suse_vex | SUSE CVE CVE-2026-44318 | No product status | 2026-07-30T16:49:59+00:00 | Vulnerability · Source |
| CVE-2026-44319 | suse_vex | SUSE CVE CVE-2026-44319 | No product status | 2026-07-30T16:49:57+00:00 | Vulnerability · Source |
| CVE-2026-44320 | suse_vex | SUSE CVE CVE-2026-44320 | No product status | 2026-07-30T16:49:54+00:00 | Vulnerability · Source |
| CVE-2026-44321 | suse_vex | SUSE CVE CVE-2026-44321 | No product status | 2026-07-30T16:49:52+00:00 | Vulnerability · Source |
| CVE-2026-44322 | suse_vex | SUSE CVE CVE-2026-44322 | No product status | 2026-07-30T16:49:51+00:00 | Vulnerability · Source |
| CVE-2026-44323 | suse_vex | SUSE CVE CVE-2026-44323 | No product status | 2026-07-30T16:49:49+00:00 | Vulnerability · Source |
| CVE-2026-44324 | suse_vex | SUSE CVE CVE-2026-44324 | No product status | 2026-07-30T16:49:46+00:00 | Vulnerability · Source |
| CVE-2026-44325 | suse_vex | SUSE CVE CVE-2026-44325 | No product status | 2026-07-30T16:49:44+00:00 | Vulnerability · Source |
| CVE-2026-44326 | suse_vex | SUSE CVE CVE-2026-44326 | No product status | 2026-07-30T16:49:42+00:00 | Vulnerability · Source |
| CVE-2026-44327 | suse_vex | SUSE CVE CVE-2026-44327 | No product status | 2026-07-30T16:49:40+00:00 | Vulnerability · Source |
| CVE-2026-44328 | suse_vex | SUSE CVE CVE-2026-44328 | No product status | 2026-07-30T16:49:38+00:00 | Vulnerability · Source |
| CVE-2026-44329 | suse_vex | SUSE CVE CVE-2026-44329 | No product status | 2026-07-30T16:49:35+00:00 | Vulnerability · Source |
| CVE-2026-44330 | suse_vex | SUSE CVE CVE-2026-44330 | No product status | 2026-07-30T16:49:33+00:00 | Vulnerability · Source |
| CVE-2026-44342 | suse_vex | SUSE CVE CVE-2026-44342 | No product status | 2026-07-30T16:49:31+00:00 | Vulnerability · Source |
| CVE-2026-44349 | suse_vex | SUSE CVE CVE-2026-44349 | No product status | 2026-07-30T16:49:29+00:00 | Vulnerability · Source |
| CVE-2026-44390 | suse_vex | SUSE CVE CVE-2026-44390 | known affected: 28 recommended: 110 | 2026-07-30T16:49:27+00:00 | Vulnerability · Source |
| CVE-2026-44423 | suse_vex | SUSE CVE CVE-2026-44423 | No product status | 2026-07-30T16:49:25+00:00 | Vulnerability · Source |
| CVE-2026-44424 | suse_vex | SUSE CVE CVE-2026-44424 | No product status | 2026-07-30T16:49:23+00:00 | Vulnerability · Source |
| CVE-2026-44425 | suse_vex | SUSE CVE CVE-2026-44425 | No product status | 2026-07-30T16:49:21+00:00 | Vulnerability · Source |
| CVE-2026-44426 | suse_vex | SUSE CVE CVE-2026-44426 | No product status | 2026-07-30T16:49:19+00:00 | Vulnerability · Source |
| CVE-2026-44427 | suse_vex | SUSE CVE CVE-2026-44427 | No product status | 2026-07-30T16:49:18+00:00 | Vulnerability · Source |
| CVE-2026-44428 | suse_vex | SUSE CVE CVE-2026-44428 | No product status | 2026-07-30T16:49:16+00:00 | Vulnerability · Source |
| CVE-2026-44429 | suse_vex | SUSE CVE CVE-2026-44429 | No product status | 2026-07-30T16:49:15+00:00 | Vulnerability · Source |
| CVE-2026-44430 | suse_vex | SUSE CVE CVE-2026-44430 | No product status | 2026-07-30T16:49:13+00:00 | Vulnerability · Source |
| CVE-2026-44454 | suse_vex | SUSE CVE CVE-2026-44454 | No product status | 2026-07-30T16:49:11+00:00 | Vulnerability · Source |
| CVE-2026-44473 | suse_vex | SUSE CVE CVE-2026-44473 | No product status | 2026-07-30T16:49:08+00:00 | Vulnerability · Source |
| CVE-2026-44475 | suse_vex | SUSE CVE CVE-2026-44475 | No product status | 2026-07-30T16:49:06+00:00 | Vulnerability · Source |
| CVE-2026-44477 | suse_vex | SUSE CVE CVE-2026-44477 | No product status | 2026-07-30T16:49:04+00:00 | Vulnerability · Source |
| CVE-2026-44503 | suse_vex | SUSE CVE CVE-2026-44503 | No product status | 2026-07-30T16:48:59+00:00 | Vulnerability · Source |
| CVE-2026-44514 | suse_vex | SUSE CVE CVE-2026-44514 | No product status | 2026-07-30T16:48:56+00:00 | Vulnerability · Source |
| CVE-2026-44522 | suse_vex | SUSE CVE CVE-2026-44522 | No product status | 2026-07-30T16:48:54+00:00 | Vulnerability · Source |