VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292117 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2025-38275 | suse_vex | SUSE CVE CVE-2025-38275 | first fixed: 2 known affected: 394 known not affected: 321 recommended: 508 | 2026-07-23T01:41:05+00:00 | Vulnerability · Source |
| CVE-2025-38276 | suse_vex | SUSE CVE CVE-2025-38276 | known not affected: 345 | 2026-07-23T01:41:04+00:00 | Vulnerability · Source |
| CVE-2025-38296 | suse_vex | SUSE CVE CVE-2025-38296 | No product status | 2026-07-23T01:41:00+00:00 | Vulnerability · Source |
| CVE-2025-38298 | suse_vex | SUSE CVE CVE-2025-38298 | first fixed: 2 recommended: 145 | 2026-07-23T01:40:58+00:00 | Vulnerability · Source |
| CVE-2025-38300 | suse_vex | SUSE CVE CVE-2025-38300 | first fixed: 2 known affected: 521 known not affected: 194 recommended: 508 | 2026-07-23T01:40:56+00:00 | Vulnerability · Source |
| CVE-2025-38303 | suse_vex | SUSE CVE CVE-2025-38303 | first fixed: 2 known affected: 467 known not affected: 248 recommended: 481 | 2026-07-23T01:40:54+00:00 | Vulnerability · Source |
| CVE-2025-38305 | suse_vex | SUSE CVE CVE-2025-38305 | first fixed: 2 known affected: 521 known not affected: 194 recommended: 508 | 2026-07-23T01:40:53+00:00 | Vulnerability · Source |
| CVE-2025-38310 | suse_vex | SUSE CVE CVE-2025-38310 | known affected: 618 known not affected: 97 recommended: 380 | 2026-07-23T01:40:51+00:00 | Vulnerability · Source |
| CVE-2025-38314 | suse_vex | SUSE CVE CVE-2025-38314 | known not affected: 345 | 2026-07-23T01:40:50+00:00 | Vulnerability · Source |
| CVE-2025-38321 | suse_vex | SUSE CVE CVE-2025-38321 | first fixed: 2 known affected: 495 known not affected: 228 recommended: 357 | 2026-07-23T01:40:47+00:00 | Vulnerability · Source |
| CVE-2025-38338 | suse_vex | SUSE CVE CVE-2025-38338 | first fixed: 2 known affected: 394 known not affected: 321 recommended: 481 | 2026-07-23T01:40:39+00:00 | Vulnerability · Source |
| CVE-2025-38339 | suse_vex | SUSE CVE CVE-2025-38339 | first fixed: 2 known not affected: 414 recommended: 127 | 2026-07-23T01:40:38+00:00 | Vulnerability · Source |
| CVE-2025-38343 | suse_vex | SUSE CVE CVE-2025-38343 | first fixed: 2 known affected: 394 known not affected: 333 recommended: 508 | 2026-07-23T01:40:36+00:00 | Vulnerability · Source |