VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292268 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-38316 | suse_vex | SUSE CVE CVE-2025-38316 | known not affected: 416 | 2026-07-25T00:48:18+00:00 | Vulnerability · Source |
| CVE-2025-38318 | suse_vex | SUSE CVE CVE-2025-38318 | first fixed: 2 known affected: 5 known not affected: 450 recommended: 154 | 2026-07-25T00:48:16+00:00 | Vulnerability · Source |
| CVE-2025-38319 | suse_vex | SUSE CVE CVE-2025-38319 | first fixed: 2 known affected: 593 known not affected: 98 recommended: 531 | 2026-07-25T00:48:14+00:00 | Vulnerability · Source |
| CVE-2025-38326 | suse_vex | SUSE CVE CVE-2025-38326 | first fixed: 2 known affected: 572 known not affected: 145 recommended: 508 | 2026-07-25T00:48:07+00:00 | Vulnerability · Source |
| CVE-2025-38335 | suse_vex | SUSE CVE CVE-2025-38335 | first fixed: 2 known affected: 400 known not affected: 317 recommended: 508 | 2026-07-25T00:47:57+00:00 | Vulnerability · Source |
| CVE-2025-38340 | suse_vex | SUSE CVE CVE-2025-38340 | known not affected: 416 recommended: 27 | 2026-07-25T00:47:54+00:00 | Vulnerability · Source |
| CVE-2025-38341 | suse_vex | SUSE CVE CVE-2025-38341 | first fixed: 2 known affected: 5 known not affected: 448 recommended: 154 | 2026-07-25T00:47:52+00:00 | Vulnerability · Source |
| CVE-2025-38342 | suse_vex | SUSE CVE CVE-2025-38342 | first fixed: 2 known affected: 572 known not affected: 157 recommended: 508 | 2026-07-25T00:47:50+00:00 | Vulnerability · Source |
| CVE-2025-38344 | suse_vex | SUSE CVE CVE-2025-38344 | first fixed: 2 known affected: 633 known not affected: 52 recommended: 508 | 2026-07-25T00:47:48+00:00 | Vulnerability · Source |
| CVE-2025-38345 | suse_vex | SUSE CVE CVE-2025-38345 | first fixed: 2 known affected: 639 known not affected: 46 recommended: 508 | 2026-07-25T00:47:46+00:00 | Vulnerability · Source |
| CVE-2025-38354 | suse_vex | SUSE CVE CVE-2025-38354 | first fixed: 2 known affected: 451 known not affected: 278 recommended: 508 | 2026-07-25T00:47:39+00:00 | Vulnerability · Source |
| CVE-2025-38359 | suse_vex | SUSE CVE CVE-2025-38359 | first fixed: 2 known affected: 564 known not affected: 118 recommended: 500 | 2026-07-25T00:47:37+00:00 | Vulnerability · Source |
| CVE-2025-38361 | suse_vex | SUSE CVE CVE-2025-38361 | first fixed: 2 known affected: 424 known not affected: 288 recommended: 500 | 2026-07-25T00:47:34+00:00 | Vulnerability · Source |
| CVE-2025-38362 | suse_vex | SUSE CVE CVE-2025-38362 | first fixed: 2 known affected: 558 known not affected: 171 recommended: 508 | 2026-07-25T00:47:32+00:00 | Vulnerability · Source |
| CVE-2025-38364 | suse_vex | SUSE CVE CVE-2025-38364 | first fixed: 2 known affected: 440 known not affected: 277 recommended: 508 | 2026-07-25T00:47:29+00:00 | Vulnerability · Source |
| CVE-2025-38365 | suse_vex | SUSE CVE CVE-2025-38365 | first fixed: 2 known affected: 521 known not affected: 196 recommended: 508 | 2026-07-25T00:47:27+00:00 | Vulnerability · Source |
| CVE-2025-38367 | suse_vex | SUSE CVE CVE-2025-38367 | known not affected: 416 | 2026-07-25T00:47:25+00:00 | Vulnerability · Source |
| CVE-2025-38369 | suse_vex | SUSE CVE CVE-2025-38369 | first fixed: 2 known affected: 558 known not affected: 159 recommended: 550 | 2026-07-25T00:47:22+00:00 | Vulnerability · Source |
| CVE-2025-38370 | suse_vex | SUSE CVE CVE-2025-38370 | known not affected: 416 | 2026-07-25T00:47:20+00:00 | Vulnerability · Source |
| CVE-2025-38373 | suse_vex | SUSE CVE CVE-2025-38373 | first fixed: 2 known affected: 464 known not affected: 253 recommended: 508 | 2026-07-25T00:47:18+00:00 | Vulnerability · Source |
| CVE-2025-38376 | suse_vex | SUSE CVE CVE-2025-38376 | first fixed: 2 known affected: 394 known not affected: 323 recommended: 508 | 2026-07-25T00:47:16+00:00 | Vulnerability · Source |
| CVE-2025-38378 | suse_vex | SUSE CVE CVE-2025-38378 | known not affected: 416 | 2026-07-25T00:47:13+00:00 | Vulnerability · Source |
| CVE-2025-38379 | suse_vex | SUSE CVE CVE-2025-38379 | first fixed: 2 known affected: 394 known not affected: 326 recommended: 402 | 2026-07-25T00:47:11+00:00 | Vulnerability · Source |
| CVE-2025-38382 | suse_vex | SUSE CVE CVE-2025-38382 | first fixed: 2 known affected: 440 known not affected: 283 recommended: 508 | 2026-07-25T00:47:07+00:00 | Vulnerability · Source |
| CVE-2025-38386 | suse_vex | SUSE CVE CVE-2025-38386 | first fixed: 2 known affected: 643 known not affected: 49 recommended: 545 | 2026-07-25T00:47:05+00:00 | Vulnerability · Source |
| CVE-2025-38387 | suse_vex | SUSE CVE CVE-2025-38387 | first fixed: 2 known affected: 572 known not affected: 145 recommended: 508 | 2026-07-25T00:47:03+00:00 | Vulnerability · Source |
| CVE-2025-38389 | suse_vex | SUSE CVE CVE-2025-38389 | first fixed: 2 known affected: 572 known not affected: 145 recommended: 508 | 2026-07-25T00:47:00+00:00 | Vulnerability · Source |
| CVE-2025-38391 | suse_vex | SUSE CVE CVE-2025-38391 | first fixed: 2 known affected: 593 known not affected: 98 recommended: 531 | 2026-07-25T00:46:59+00:00 | Vulnerability · Source |
| CVE-2025-38392 | suse_vex | SUSE CVE CVE-2025-38392 | first fixed: 2 known affected: 567 known not affected: 156 recommended: 571 | 2026-07-25T00:46:57+00:00 | Vulnerability · Source |
| CVE-2025-38393 | suse_vex | SUSE CVE CVE-2025-38393 | first fixed: 2 known affected: 521 known not affected: 196 recommended: 555 | 2026-07-25T00:46:55+00:00 | Vulnerability · Source |
| CVE-2025-38395 | suse_vex | SUSE CVE CVE-2025-38395 | first fixed: 2 known affected: 572 known not affected: 145 recommended: 508 | 2026-07-25T00:46:54+00:00 | Vulnerability · Source |
| CVE-2025-38396 | suse_vex | SUSE CVE CVE-2025-38396 | first fixed: 2 known affected: 440 known not affected: 283 recommended: 607 | 2026-07-25T00:46:52+00:00 | Vulnerability · Source |
| CVE-2025-38400 | suse_vex | SUSE CVE CVE-2025-38400 | first fixed: 2 known affected: 451 known not affected: 266 recommended: 550 | 2026-07-25T00:46:50+00:00 | Vulnerability · Source |
| CVE-2025-38401 | suse_vex | SUSE CVE CVE-2025-38401 | first fixed: 2 known affected: 404 known not affected: 325 recommended: 508 | 2026-07-25T00:46:49+00:00 | Vulnerability · Source |
| CVE-2025-38404 | suse_vex | SUSE CVE CVE-2025-38404 | first fixed: 2 known affected: 394 known not affected: 323 recommended: 508 | 2026-07-25T00:46:44+00:00 | Vulnerability · Source |
| CVE-2025-38406 | suse_vex | SUSE CVE CVE-2025-38406 | first fixed: 2 known affected: 639 known not affected: 57 recommended: 508 | 2026-07-25T00:46:42+00:00 | Vulnerability · Source |
| CVE-2025-38408 | suse_vex | SUSE CVE CVE-2025-38408 | first fixed: 2 known affected: 521 known not affected: 156 recommended: 508 | 2026-07-25T00:46:41+00:00 | Vulnerability · Source |
| CVE-2025-38409 | suse_vex | SUSE CVE CVE-2025-38409 | first fixed: 2 known affected: 582 known not affected: 105 recommended: 508 | 2026-07-25T00:46:39+00:00 | Vulnerability · Source |
| CVE-2025-38410 | suse_vex | SUSE CVE CVE-2025-38410 | first fixed: 2 known affected: 633 known not affected: 84 recommended: 508 | 2026-07-25T00:46:37+00:00 | Vulnerability · Source |
| CVE-2025-38416 | suse_vex | SUSE CVE CVE-2025-38416 | first fixed: 2 known affected: 633 known not affected: 52 recommended: 508 | 2026-07-25T00:46:33+00:00 | Vulnerability · Source |
| CVE-2025-38420 | suse_vex | SUSE CVE CVE-2025-38420 | first fixed: 2 known affected: 643 known not affected: 46 recommended: 531 | 2026-07-25T00:46:29+00:00 | Vulnerability · Source |
| CVE-2025-38423 | suse_vex | SUSE CVE CVE-2025-38423 | first fixed: 2 known not affected: 416 recommended: 172 | 2026-07-25T00:46:27+00:00 | Vulnerability · Source |
| CVE-2025-38424 | suse_vex | SUSE CVE CVE-2025-38424 | first fixed: 2 known affected: 643 known not affected: 57 recommended: 545 | 2026-07-25T00:46:25+00:00 | Vulnerability · Source |
| CVE-2025-38425 | suse_vex | SUSE CVE CVE-2025-38425 | first fixed: 2 known affected: 521 known not affected: 196 recommended: 508 | 2026-07-25T00:46:24+00:00 | Vulnerability · Source |
| CVE-2025-38429 | suse_vex | SUSE CVE CVE-2025-38429 | first fixed: 2 known affected: 440 known not affected: 277 recommended: 508 | 2026-07-25T00:46:21+00:00 | Vulnerability · Source |
| CVE-2025-38430 | suse_vex | SUSE CVE CVE-2025-38430 | first fixed: 2 known affected: 623 known not affected: 71 recommended: 531 | 2026-07-25T00:46:20+00:00 | Vulnerability · Source |
| CVE-2025-38436 | suse_vex | SUSE CVE CVE-2025-38436 | first fixed: 2 known affected: 641 known not affected: 57 recommended: 531 | 2026-07-25T00:46:18+00:00 | Vulnerability · Source |
| CVE-2025-38442 | suse_vex | SUSE CVE CVE-2025-38442 | known not affected: 416 | 2026-07-25T00:46:16+00:00 | Vulnerability · Source |
| CVE-2025-38443 | suse_vex | SUSE CVE CVE-2025-38443 | first fixed: 2 known affected: 521 known not affected: 196 recommended: 508 | 2026-07-25T00:46:15+00:00 | Vulnerability · Source |
| CVE-2025-38447 | suse_vex | SUSE CVE CVE-2025-38447 | known not affected: 416 | 2026-07-25T00:46:12+00:00 | Vulnerability · Source |