VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292440 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-37907 | suse_vex | SUSE CVE CVE-2025-37907 | known not affected: 281 recommended: 53 | 2026-07-23T01:43:27+00:00 | Vulnerability · Source |
| CVE-2025-37927 | suse_vex | SUSE CVE CVE-2025-37927 | known affected: 683 known not affected: 6 recommended: 437 | 2026-07-23T01:43:24+00:00 | Vulnerability · Source |
| CVE-2025-37933 | suse_vex | SUSE CVE CVE-2025-37933 | known affected: 440 known not affected: 275 recommended: 392 | 2026-07-23T01:43:21+00:00 | Vulnerability · Source |
| CVE-2025-37939 | suse_vex | SUSE CVE CVE-2025-37939 | known affected: 37 known not affected: 267 | 2026-07-23T01:43:20+00:00 | Vulnerability · Source |
| CVE-2025-37944 | suse_vex | SUSE CVE CVE-2025-37944 | known affected: 441 known not affected: 237 recommended: 380 | 2026-07-23T01:43:18+00:00 | Vulnerability · Source |
| CVE-2025-37960 | suse_vex | SUSE CVE CVE-2025-37960 | known affected: 497 known not affected: 218 recommended: 384 | 2026-07-23T01:43:08+00:00 | Vulnerability · Source |
| CVE-2025-37968 | suse_vex | SUSE CVE CVE-2025-37968 | known affected: 679 known not affected: 36 recommended: 392 | 2026-07-23T01:43:06+00:00 | Vulnerability · Source |
| CVE-2025-37996 | suse_vex | SUSE CVE CVE-2025-37996 | known not affected: 395 recommended: 53 | 2026-07-23T01:43:00+00:00 | Vulnerability · Source |
| CVE-2025-38002 | suse_vex | SUSE CVE CVE-2025-38002 | known not affected: 326 | 2026-07-23T01:42:59+00:00 | Vulnerability · Source |
| CVE-2025-38008 | suse_vex | SUSE CVE CVE-2025-38008 | first fixed: 2 known affected: 451 known not affected: 224 recommended: 500 | 2026-07-23T01:42:57+00:00 | Vulnerability · Source |
| CVE-2025-38017 | suse_vex | SUSE CVE CVE-2025-38017 | known not affected: 330 | 2026-07-23T01:42:50+00:00 | Vulnerability · Source |
| CVE-2025-38030 | suse_vex | SUSE CVE CVE-2025-38030 | known not affected: 330 | 2026-07-23T01:42:49+00:00 | Vulnerability · Source |
| CVE-2025-38045 | suse_vex | SUSE CVE CVE-2025-38045 | known affected: 500 known not affected: 212 recommended: 407 | 2026-07-23T01:42:47+00:00 | Vulnerability · Source |
| CVE-2025-38075 | suse_vex | SUSE CVE CVE-2025-38075 | first fixed: 2 known affected: 394 known not affected: 316 recommended: 579 | 2026-07-23T01:42:35+00:00 | Vulnerability · Source |
| CVE-2025-38078 | suse_vex | SUSE CVE CVE-2025-38078 | known affected: 643 known not affected: 46 recommended: 437 | 2026-07-23T01:42:34+00:00 | Vulnerability · Source |
| CVE-2025-38087 | suse_vex | SUSE CVE CVE-2025-38087 | first fixed: 2 known affected: 394 known not affected: 321 recommended: 578 | 2026-07-23T01:42:26+00:00 | Vulnerability · Source |
| CVE-2025-38098 | suse_vex | SUSE CVE CVE-2025-38098 | first fixed: 2 known affected: 410 known not affected: 305 recommended: 508 | 2026-07-23T01:42:23+00:00 | Vulnerability · Source |
| CVE-2025-38113 | suse_vex | SUSE CVE CVE-2025-38113 | first fixed: 2 known affected: 451 known not affected: 264 recommended: 481 | 2026-07-23T01:42:21+00:00 | Vulnerability · Source |
| CVE-2025-38118 | suse_vex | SUSE CVE CVE-2025-38118 | first fixed: 2 known affected: 394 known not affected: 321 recommended: 508 | 2026-07-23T01:42:18+00:00 | Vulnerability · Source |
| CVE-2025-38119 | suse_vex | SUSE CVE CVE-2025-38119 | first fixed: 2 known affected: 639 known not affected: 6 recommended: 500 | 2026-07-23T01:42:16+00:00 | Vulnerability · Source |
| CVE-2025-38124 | suse_vex | SUSE CVE CVE-2025-38124 | first fixed: 2 known affected: 394 known not affected: 321 recommended: 524 | 2026-07-23T01:42:13+00:00 | Vulnerability · Source |
| CVE-2025-38130 | suse_vex | SUSE CVE CVE-2025-38130 | known not affected: 414 | 2026-07-23T01:42:12+00:00 | Vulnerability · Source |
| CVE-2025-38134 | suse_vex | SUSE CVE CVE-2025-38134 | first fixed: 2 known not affected: 414 recommended: 154 | 2026-07-23T01:42:10+00:00 | Vulnerability · Source |
| CVE-2025-38136 | suse_vex | SUSE CVE CVE-2025-38136 | first fixed: 2 known affected: 394 known not affected: 321 recommended: 508 | 2026-07-23T01:42:09+00:00 | Vulnerability · Source |
| CVE-2025-38142 | suse_vex | SUSE CVE CVE-2025-38142 | first fixed: 2 known affected: 394 known not affected: 321 recommended: 508 | 2026-07-23T01:42:07+00:00 | Vulnerability · Source |
| CVE-2025-38145 | suse_vex | SUSE CVE CVE-2025-38145 | first fixed: 2 known affected: 521 known not affected: 194 recommended: 508 | 2026-07-23T01:42:06+00:00 | Vulnerability · Source |
| CVE-2025-38154 | suse_vex | SUSE CVE CVE-2025-38154 | first fixed: 2 known affected: 497 known not affected: 218 recommended: 530 | 2026-07-23T01:42:04+00:00 | Vulnerability · Source |
| CVE-2025-38169 | suse_vex | SUSE CVE CVE-2025-38169 | first fixed: 2 known not affected: 414 recommended: 154 | 2026-07-23T01:42:02+00:00 | Vulnerability · Source |
| CVE-2025-38170 | suse_vex | SUSE CVE CVE-2025-38170 | first fixed: 2 known affected: 6 known not affected: 445 recommended: 154 | 2026-07-23T01:42:01+00:00 | Vulnerability · Source |
| CVE-2025-38171 | suse_vex | SUSE CVE CVE-2025-38171 | known not affected: 345 | 2026-07-23T01:42:00+00:00 | Vulnerability · Source |
| CVE-2025-38173 | suse_vex | SUSE CVE CVE-2025-38173 | first fixed: 2 known affected: 623 known not affected: 69 recommended: 538 | 2026-07-23T01:41:58+00:00 | Vulnerability · Source |
| CVE-2025-38175 | suse_vex | SUSE CVE CVE-2025-38175 | known not affected: 345 | 2026-07-23T01:41:57+00:00 | Vulnerability · Source |
| CVE-2025-38176 | suse_vex | SUSE CVE CVE-2025-38176 | known not affected: 345 | 2026-07-23T01:41:55+00:00 | Vulnerability · Source |
| CVE-2025-38215 | suse_vex | SUSE CVE CVE-2025-38215 | first fixed: 2 known affected: 675 known not affected: 80 recommended: 508 | 2026-07-23T01:41:44+00:00 | Vulnerability · Source |
| CVE-2025-38216 | suse_vex | SUSE CVE CVE-2025-38216 | first fixed: 2 known affected: 399 known not affected: 350 recommended: 305 | 2026-07-23T01:41:43+00:00 | Vulnerability · Source |
| CVE-2025-38217 | suse_vex | SUSE CVE CVE-2025-38217 | first fixed: 2 known affected: 394 known not affected: 321 recommended: 508 | 2026-07-23T01:41:41+00:00 | Vulnerability · Source |
| CVE-2025-38221 | suse_vex | SUSE CVE CVE-2025-38221 | known not affected: 345 | 2026-07-23T01:41:38+00:00 | Vulnerability · Source |
| CVE-2025-38225 | suse_vex | SUSE CVE CVE-2025-38225 | first fixed: 2 known affected: 521 known not affected: 194 recommended: 508 | 2026-07-23T01:41:34+00:00 | Vulnerability · Source |
| CVE-2025-38227 | suse_vex | SUSE CVE CVE-2025-38227 | first fixed: 2 known affected: 394 known not affected: 321 recommended: 481 | 2026-07-23T01:41:33+00:00 | Vulnerability · Source |
| CVE-2025-38229 | suse_vex | SUSE CVE CVE-2025-38229 | first fixed: 2 known affected: 639 known not affected: 46 recommended: 508 | 2026-07-23T01:41:31+00:00 | Vulnerability · Source |
| CVE-2025-38231 | suse_vex | SUSE CVE CVE-2025-38231 | first fixed: 2 known affected: 521 known not affected: 194 recommended: 508 | 2026-07-23T01:41:29+00:00 | Vulnerability · Source |
| CVE-2025-38232 | suse_vex | SUSE CVE CVE-2025-38232 | first fixed: 2 known affected: 239 known not affected: 6 recommended: 154 | 2026-07-23T01:41:28+00:00 | Vulnerability · Source |
| CVE-2025-38245 | suse_vex | SUSE CVE CVE-2025-38245 | first fixed: 2 known affected: 713 recommended: 538 | 2026-07-23T01:41:20+00:00 | Vulnerability · Source |
| CVE-2025-38246 | suse_vex | SUSE CVE CVE-2025-38246 | first fixed: 2 known affected: 451 known not affected: 264 recommended: 481 | 2026-07-23T01:41:18+00:00 | Vulnerability · Source |
| CVE-2025-38251 | suse_vex | SUSE CVE CVE-2025-38251 | first fixed: 2 known affected: 590 known not affected: 158 recommended: 481 | 2026-07-23T01:41:17+00:00 | Vulnerability · Source |
| CVE-2025-38252 | suse_vex | SUSE CVE CVE-2025-38252 | known not affected: 345 | 2026-07-23T01:41:15+00:00 | Vulnerability · Source |
| CVE-2025-38254 | suse_vex | SUSE CVE CVE-2025-38254 | known not affected: 345 | 2026-07-23T01:41:14+00:00 | Vulnerability · Source |
| CVE-2025-38268 | suse_vex | SUSE CVE CVE-2025-38268 | first fixed: 2 known affected: 394 known not affected: 387 recommended: 265 | 2026-07-23T01:41:10+00:00 | Vulnerability · Source |
| CVE-2025-38273 | suse_vex | SUSE CVE CVE-2025-38273 | first fixed: 2 known not affected: 333 recommended: 481 | 2026-07-23T01:41:08+00:00 | Vulnerability · Source |
| CVE-2025-38274 | suse_vex | SUSE CVE CVE-2025-38274 | first fixed: 2 known not affected: 414 recommended: 154 | 2026-07-23T01:41:07+00:00 | Vulnerability · Source |