VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283120 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-52720 | suse_vex | SUSE CVE CVE-2026-52720 | first fixed: 136 known affected: 512 recommended: 361 | 2026-07-21T13:08:13+00:00 | Vulnerability · Source |
| CVE-2026-52721 | suse_vex | SUSE CVE CVE-2026-52721 | first fixed: 274 known affected: 691 known not affected: 136 | 2026-07-21T13:08:12+00:00 | Vulnerability · Source |
| CVE-2026-52722 | suse_vex | SUSE CVE CVE-2026-52722 | known affected: 512 recommended: 282 | 2026-07-21T13:08:10+00:00 | Vulnerability · Source |
| CVE-2026-52908 | suse_vex | SUSE CVE CVE-2026-52908 | known affected: 47 known not affected: 179 recommended: 108 | 2026-07-21T13:08:09+00:00 | Vulnerability · Source |
| CVE-2026-52954 | suse_vex | SUSE CVE CVE-2026-52954 | known affected: 192 known not affected: 4 recommended: 138 | 2026-07-21T13:08:01+00:00 | Vulnerability · Source |
| CVE-2026-52962 | suse_vex | SUSE CVE CVE-2026-52962 | known affected: 198 recommended: 131 | 2026-07-21T13:07:58+00:00 | Vulnerability · Source |
| CVE-2026-53040 | suse_vex | SUSE CVE CVE-2026-53040 | known affected: 192 known not affected: 4 recommended: 138 | 2026-07-21T13:07:54+00:00 | Vulnerability · Source |
| CVE-2026-53081 | suse_vex | SUSE CVE CVE-2026-53081 | known affected: 162 known not affected: 131 | 2026-07-21T13:07:47+00:00 | Vulnerability · Source |
| CVE-2026-53122 | suse_vex | SUSE CVE CVE-2026-53122 | known affected: 161 known not affected: 65 recommended: 108 | 2026-07-21T13:07:43+00:00 | Vulnerability · Source |
| CVE-2026-53138 | suse_vex | SUSE CVE CVE-2026-53138 | known affected: 189 known not affected: 37 recommended: 108 | 2026-07-21T13:07:41+00:00 | Vulnerability · Source |
| CVE-2026-53210 | suse_vex | SUSE CVE CVE-2026-53210 | known affected: 15 known not affected: 276 | 2026-07-21T13:07:33+00:00 | Vulnerability · Source |
| CVE-2026-53266 | suse_vex | SUSE CVE CVE-2026-53266 | known affected: 135 known not affected: 91 recommended: 169 | 2026-07-21T13:07:29+00:00 | Vulnerability · Source |
| CVE-2026-53273 | suse_vex | SUSE CVE CVE-2026-53273 | known affected: 140 known not affected: 151 | 2026-07-21T13:07:28+00:00 | Vulnerability · Source |
| CVE-2026-53281 | suse_vex | SUSE CVE CVE-2026-53281 | known affected: 47 known not affected: 179 recommended: 108 | 2026-07-21T13:07:27+00:00 | Vulnerability · Source |
| CVE-2026-53287 | suse_vex | SUSE CVE CVE-2026-53287 | known affected: 196 recommended: 138 | 2026-07-21T13:07:26+00:00 | Vulnerability · Source |
| CVE-2026-53367 | suse_vex | SUSE CVE CVE-2026-53367 | No product status | 2026-07-21T13:07:20+00:00 | Vulnerability · Source |
| CVE-2026-53368 | suse_vex | SUSE CVE CVE-2026-53368 | No product status | 2026-07-21T13:07:19+00:00 | Vulnerability · Source |
| CVE-2026-53369 | suse_vex | SUSE CVE CVE-2026-53369 | No product status | 2026-07-21T13:07:18+00:00 | Vulnerability · Source |
| CVE-2026-53370 | suse_vex | SUSE CVE CVE-2026-53370 | No product status | 2026-07-21T13:07:17+00:00 | Vulnerability · Source |
| CVE-2026-53371 | suse_vex | SUSE CVE CVE-2026-53371 | No product status | 2026-07-21T13:07:15+00:00 | Vulnerability · Source |
| CVE-2026-53372 | suse_vex | SUSE CVE CVE-2026-53372 | No product status | 2026-07-21T13:07:14+00:00 | Vulnerability · Source |
| CVE-2026-53373 | suse_vex | SUSE CVE CVE-2026-53373 | known not affected: 284 | 2026-07-21T13:07:13+00:00 | Vulnerability · Source |
| CVE-2026-53374 | suse_vex | SUSE CVE CVE-2026-53374 | known affected: 191 known not affected: 93 | 2026-07-21T13:07:12+00:00 | Vulnerability · Source |
| CVE-2026-53375 | suse_vex | SUSE CVE CVE-2026-53375 | known affected: 78 known not affected: 206 | 2026-07-21T13:07:11+00:00 | Vulnerability · Source |
| CVE-2026-53376 | suse_vex | SUSE CVE CVE-2026-53376 | known affected: 189 known not affected: 95 | 2026-07-21T13:07:10+00:00 | Vulnerability · Source |
| CVE-2026-53377 | suse_vex | SUSE CVE CVE-2026-53377 | known affected: 12 known not affected: 272 | 2026-07-21T13:07:09+00:00 | Vulnerability · Source |
| CVE-2026-53378 | suse_vex | SUSE CVE CVE-2026-53378 | known not affected: 284 | 2026-07-21T13:07:07+00:00 | Vulnerability · Source |
| 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-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 |