VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286924 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-38206 | suse_vex | SUSE CVE CVE-2025-38206 | known affected: 441 known not affected: 99 recommended: 855 | 2026-07-31T01:12:10+00:00 | Vulnerability · Source |
| CVE-2025-38218 | suse_vex | SUSE CVE CVE-2025-38218 | known not affected: 470 | 2026-07-31T01:12:05+00:00 | Vulnerability · Source |
| CVE-2025-38219 | suse_vex | SUSE CVE CVE-2025-38219 | known not affected: 470 | 2026-07-31T01:12:02+00:00 | Vulnerability · Source |
| CVE-2025-38230 | suse_vex | SUSE CVE CVE-2025-38230 | known affected: 231 known not affected: 167 | 2026-07-31T01:11:57+00:00 | Vulnerability · Source |
| CVE-2025-38234 | suse_vex | SUSE CVE CVE-2025-38234 | first fixed: 2 known affected: 481 known not affected: 2 recommended: 862 | 2026-07-31T01:11:53+00:00 | Vulnerability · Source |
| CVE-2025-38237 | suse_vex | SUSE CVE CVE-2025-38237 | known not affected: 470 | 2026-07-31T01:11:50+00:00 | Vulnerability · Source |
| CVE-2025-38238 | suse_vex | SUSE CVE CVE-2025-38238 | known affected: 424 known not affected: 359 recommended: 111 | 2026-07-31T01:11:48+00:00 | Vulnerability · Source |
| CVE-2025-38242 | suse_vex | SUSE CVE CVE-2025-38242 | first fixed: 2 known affected: 5 known not affected: 450 recommended: 154 | 2026-07-31T01:11:45+00:00 | Vulnerability · Source |
| CVE-2025-38253 | suse_vex | SUSE CVE CVE-2025-38253 | first fixed: 2 known not affected: 416 recommended: 154 | 2026-07-31T01:11:40+00:00 | Vulnerability · Source |
| CVE-2025-38260 | suse_vex | SUSE CVE CVE-2025-38260 | known not affected: 341 | 2026-07-31T01:11:36+00:00 | Vulnerability · Source |
| CVE-2025-38261 | suse_vex | SUSE CVE CVE-2025-38261 | known not affected: 470 | 2026-07-31T01:11:34+00:00 | Vulnerability · Source |
| CVE-2025-38262 | suse_vex | SUSE CVE CVE-2025-38262 | first fixed: 2 known not affected: 416 recommended: 172 | 2026-07-31T01:11:32+00:00 | Vulnerability · Source |
| CVE-2025-38269 | suse_vex | SUSE CVE CVE-2025-38269 | known not affected: 470 | 2026-07-31T01:11:28+00:00 | Vulnerability · Source |
| CVE-2025-38270 | suse_vex | SUSE CVE CVE-2025-38270 | first fixed: 2 known affected: 5 known not affected: 450 recommended: 154 | 2026-07-31T01:11:25+00:00 | Vulnerability · Source |
| CVE-2025-38278 | suse_vex | SUSE CVE CVE-2025-38278 | first fixed: 2 known not affected: 277 recommended: 154 | 2026-07-31T01:11:21+00:00 | Vulnerability · Source |
| CVE-2025-38280 | suse_vex | SUSE CVE CVE-2025-38280 | known affected: 195 known not affected: 275 | 2026-07-31T01:11:19+00:00 | Vulnerability · Source |
| CVE-2025-38282 | suse_vex | SUSE CVE CVE-2025-38282 | known not affected: 341 | 2026-07-31T01:11:16+00:00 | Vulnerability · Source |
| CVE-2025-38284 | suse_vex | SUSE CVE CVE-2025-38284 | known not affected: 458 recommended: 27 | 2026-07-31T01:11:14+00:00 | Vulnerability · Source |
| CVE-2025-38285 | suse_vex | SUSE CVE CVE-2025-38285 | known affected: 195 known not affected: 116 | 2026-07-31T01:11:11+00:00 | Vulnerability · Source |
| CVE-2025-38287 | suse_vex | SUSE CVE CVE-2025-38287 | first fixed: 2 known affected: 394 known not affected: 389 recommended: 265 | 2026-07-31T01:11:08+00:00 | Vulnerability · Source |
| CVE-2025-38291 | suse_vex | SUSE CVE CVE-2025-38291 | first fixed: 2 known affected: 394 known not affected: 389 recommended: 265 | 2026-07-31T01:11:05+00:00 | Vulnerability · Source |
| CVE-2025-38295 | suse_vex | SUSE CVE CVE-2025-38295 | known not affected: 64 | 2026-07-31T01:11:01+00:00 | Vulnerability · Source |
| CVE-2025-38306 | suse_vex | SUSE CVE CVE-2025-38306 | first fixed: 2 known not affected: 448 recommended: 154 | 2026-07-31T01:10:58+00:00 | Vulnerability · Source |
| CVE-2025-38320 | suse_vex | SUSE CVE CVE-2025-38320 | known not affected: 470 | 2026-07-31T01:10:54+00:00 | Vulnerability · Source |
| CVE-2025-38324 | suse_vex | SUSE CVE CVE-2025-38324 | known affected: 269 known not affected: 70 | 2026-07-31T01:10:51+00:00 | Vulnerability · Source |
| CVE-2025-38325 | suse_vex | SUSE CVE CVE-2025-38325 | known not affected: 416 | 2026-07-31T01:10:48+00:00 | Vulnerability · Source |
| CVE-2025-38328 | suse_vex | SUSE CVE CVE-2025-38328 | known affected: 394 known not affected: 208 recommended: 354 | 2026-07-31T01:10:45+00:00 | Vulnerability · Source |
| CVE-2025-38331 | suse_vex | SUSE CVE CVE-2025-38331 | known not affected: 470 | 2026-07-31T01:10:42+00:00 | Vulnerability · Source |
| CVE-2025-38333 | suse_vex | SUSE CVE CVE-2025-38333 | known not affected: 470 | 2026-07-31T01:10:40+00:00 | Vulnerability · Source |
| CVE-2025-38346 | suse_vex | SUSE CVE CVE-2025-38346 | known affected: 178 known not affected: 163 | 2026-07-31T01:10:34+00:00 | Vulnerability · Source |
| CVE-2025-38347 | suse_vex | SUSE CVE CVE-2025-38347 | known not affected: 470 | 2026-07-31T01:10:31+00:00 | Vulnerability · Source |
| CVE-2025-38366 | suse_vex | SUSE CVE CVE-2025-38366 | known not affected: 416 | 2026-07-31T01:10:24+00:00 | Vulnerability · Source |
| CVE-2025-38388 | suse_vex | SUSE CVE CVE-2025-38388 | known not affected: 470 | 2026-07-31T01:10:18+00:00 | Vulnerability · Source |
| CVE-2025-38398 | suse_vex | SUSE CVE CVE-2025-38398 | known not affected: 416 | 2026-07-31T01:10:13+00:00 | Vulnerability · Source |
| CVE-2025-38405 | suse_vex | SUSE CVE CVE-2025-38405 | first fixed: 2 known not affected: 416 recommended: 154 | 2026-07-31T01:10:09+00:00 | Vulnerability · Source |
| CVE-2025-38407 | suse_vex | SUSE CVE CVE-2025-38407 | known not affected: 470 | 2026-07-31T01:10:06+00:00 | Vulnerability · Source |
| CVE-2025-38412 | suse_vex | SUSE CVE CVE-2025-38412 | first fixed: 2 known affected: 521 known not affected: 196 recommended: 550 | 2026-07-31T01:10:02+00:00 | Vulnerability · Source |
| CVE-2025-38413 | suse_vex | SUSE CVE CVE-2025-38413 | first fixed: 2 known not affected: 416 recommended: 154 | 2026-07-31T01:09:59+00:00 | Vulnerability · Source |
| CVE-2025-38422 | suse_vex | SUSE CVE CVE-2025-38422 | known affected: 178 known not affected: 163 | 2026-07-31T01:09:54+00:00 | Vulnerability · Source |
| CVE-2025-38434 | suse_vex | SUSE CVE CVE-2025-38434 | known not affected: 470 | 2026-07-31T01:09:49+00:00 | Vulnerability · Source |
| CVE-2025-38437 | suse_vex | SUSE CVE CVE-2025-38437 | known not affected: 470 | 2026-07-31T01:09:46+00:00 | Vulnerability · Source |
| CVE-2025-38446 | suse_vex | SUSE CVE CVE-2025-38446 | first fixed: 2 known not affected: 416 recommended: 154 | 2026-07-31T01:09:40+00:00 | Vulnerability · Source |
| CVE-2025-38452 | suse_vex | SUSE CVE CVE-2025-38452 | known not affected: 470 | 2026-07-31T01:09:36+00:00 | Vulnerability · Source |
| CVE-2025-38453 | suse_vex | SUSE CVE CVE-2025-38453 | first fixed: 2 known affected: 429 known not affected: 391 recommended: 313 | 2026-07-31T01:09:34+00:00 | Vulnerability · Source |
| CVE-2025-38475 | suse_vex | SUSE CVE CVE-2025-38475 | first fixed: 2 known affected: 424 known not affected: 391 recommended: 265 | 2026-07-31T01:09:21+00:00 | Vulnerability · Source |
| CVE-2025-38484 | suse_vex | SUSE CVE CVE-2025-38484 | first fixed: 2 known not affected: 416 recommended: 154 | 2026-07-31T01:09:16+00:00 | Vulnerability · Source |
| CVE-2025-38501 | suse_vex | SUSE CVE CVE-2025-38501 | known not affected: 431 | 2026-07-31T01:09:05+00:00 | Vulnerability · Source |
| CVE-2025-38511 | suse_vex | SUSE CVE CVE-2025-38511 | first fixed: 2 known affected: 394 known not affected: 393 recommended: 289 | 2026-07-31T01:09:01+00:00 | Vulnerability · Source |
| CVE-2025-38517 | suse_vex | SUSE CVE CVE-2025-38517 | known not affected: 470 | 2026-07-31T01:08:57+00:00 | Vulnerability · Source |
| CVE-2025-38536 | suse_vex | SUSE CVE CVE-2025-38536 | known not affected: 416 | 2026-07-31T01:08:50+00:00 | Vulnerability · Source |