VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292108 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-38228 | suse_vex | SUSE CVE CVE-2025-38228 | first fixed: 2 known not affected: 416 recommended: 154 | 2026-07-25T00:49:16+00:00 | Vulnerability · Source |
| CVE-2025-38235 | suse_vex | SUSE CVE CVE-2025-38235 | known not affected: 416 | 2026-07-25T00:49:10+00:00 | Vulnerability · Source |
| CVE-2025-38236 | suse_vex | SUSE CVE CVE-2025-38236 | known affected: 440 known not affected: 277 recommended: 407 | 2026-07-25T00:49:08+00:00 | Vulnerability · Source |
| CVE-2025-38243 | suse_vex | SUSE CVE CVE-2025-38243 | first fixed: 2 known affected: 394 known not affected: 326 recommended: 402 | 2026-07-25T00:49:06+00:00 | Vulnerability · Source |
| CVE-2025-38248 | suse_vex | SUSE CVE CVE-2025-38248 | known affected: 440 known not affected: 277 recommended: 427 | 2026-07-25T00:49:03+00:00 | Vulnerability · Source |
| CVE-2025-38249 | suse_vex | SUSE CVE CVE-2025-38249 | first fixed: 2 known affected: 593 known not affected: 98 recommended: 531 | 2026-07-25T00:49:02+00:00 | Vulnerability · Source |
| CVE-2025-38257 | suse_vex | SUSE CVE CVE-2025-38257 | first fixed: 2 known affected: 393 known not affected: 145 recommended: 801 | 2026-07-25T00:48:58+00:00 | Vulnerability · Source |
| CVE-2025-38258 | suse_vex | SUSE CVE CVE-2025-38258 | first fixed: 2 known not affected: 453 recommended: 154 | 2026-07-25T00:48:56+00:00 | Vulnerability · Source |
| CVE-2025-38259 | suse_vex | SUSE CVE CVE-2025-38259 | first fixed: 2 known affected: 572 known not affected: 145 recommended: 508 | 2026-07-25T00:48:55+00:00 | Vulnerability · Source |
| CVE-2025-38267 | suse_vex | SUSE CVE CVE-2025-38267 | first fixed: 2 known affected: 5 known not affected: 450 recommended: 154 | 2026-07-25T00:48:53+00:00 | Vulnerability · Source |
| CVE-2025-38271 | suse_vex | SUSE CVE CVE-2025-38271 | known not affected: 416 | 2026-07-25T00:48:51+00:00 | Vulnerability · Source |
| CVE-2025-38272 | suse_vex | SUSE CVE CVE-2025-38272 | first fixed: 2 known affected: 629 known not affected: 99 recommended: 508 | 2026-07-25T00:48:50+00:00 | Vulnerability · Source |
| CVE-2025-38277 | suse_vex | SUSE CVE CVE-2025-38277 | first fixed: 2 known affected: 394 known not affected: 323 recommended: 508 | 2026-07-25T00:48:47+00:00 | Vulnerability · Source |
| CVE-2025-38286 | suse_vex | SUSE CVE CVE-2025-38286 | first fixed: 2 known affected: 394 known not affected: 323 recommended: 508 | 2026-07-25T00:48:42+00:00 | Vulnerability · Source |
| CVE-2025-38289 | suse_vex | SUSE CVE CVE-2025-38289 | first fixed: 2 known affected: 372 known not affected: 266 recommended: 600 | 2026-07-25T00:48:39+00:00 | Vulnerability · Source |
| CVE-2025-38290 | suse_vex | SUSE CVE CVE-2025-38290 | first fixed: 2 known affected: 394 known not affected: 323 recommended: 508 | 2026-07-25T00:48:37+00:00 | Vulnerability · Source |
| CVE-2025-38292 | suse_vex | SUSE CVE CVE-2025-38292 | first fixed: 2 known affected: 394 known not affected: 323 recommended: 551 | 2026-07-25T00:48:35+00:00 | Vulnerability · Source |
| CVE-2025-38293 | suse_vex | SUSE CVE CVE-2025-38293 | first fixed: 2 known affected: 521 known not affected: 196 recommended: 508 | 2026-07-25T00:48:33+00:00 | Vulnerability · Source |
| CVE-2025-38297 | suse_vex | SUSE CVE CVE-2025-38297 | first fixed: 2 recommended: 172 | 2026-07-25T00:48:32+00:00 | Vulnerability · Source |
| CVE-2025-38301 | suse_vex | SUSE CVE CVE-2025-38301 | first fixed: 2 known affected: 3 known not affected: 422 recommended: 154 | 2026-07-25T00:48:30+00:00 | Vulnerability · Source |
| CVE-2025-38304 | suse_vex | SUSE CVE CVE-2025-38304 | first fixed: 2 known affected: 451 known not affected: 266 recommended: 508 | 2026-07-25T00:48:27+00:00 | Vulnerability · Source |
| CVE-2025-38307 | suse_vex | SUSE CVE CVE-2025-38307 | first fixed: 2 known affected: 394 known not affected: 323 recommended: 508 | 2026-07-25T00:48:24+00:00 | Vulnerability · Source |
| CVE-2025-38313 | suse_vex | SUSE CVE CVE-2025-38313 | first fixed: 2 known affected: 593 known not affected: 101 recommended: 531 | 2026-07-25T00:48:20+00:00 | Vulnerability · Source |
| 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 |