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-40008 | suse_vex | SUSE CVE CVE-2025-40008 | known not affected: 345 | 2026-07-23T01:35:51+00:00 | Vulnerability · Source |
| CVE-2025-40009 | suse_vex | SUSE CVE CVE-2025-40009 | first fixed: 2 known affected: 397 known not affected: 405 recommended: 127 | 2026-07-23T01:35:50+00:00 | Vulnerability · Source |
| CVE-2025-40011 | suse_vex | SUSE CVE CVE-2025-40011 | first fixed: 2 known affected: 567 known not affected: 87 recommended: 473 | 2026-07-23T01:35:48+00:00 | Vulnerability · Source |
| CVE-2025-40012 | suse_vex | SUSE CVE CVE-2025-40012 | first fixed: 2 known affected: 394 known not affected: 374 recommended: 265 | 2026-07-23T01:35:47+00:00 | Vulnerability · Source |
| CVE-2025-40025 | suse_vex | SUSE CVE CVE-2025-40025 | known not affected: 336 recommended: 6 | 2026-07-23T01:35:43+00:00 | Vulnerability · Source |
| CVE-2025-40031 | suse_vex | SUSE CVE CVE-2025-40031 | first fixed: 2 known not affected: 431 recommended: 160 | 2026-07-23T01:35:41+00:00 | Vulnerability · Source |
| CVE-2025-40037 | suse_vex | SUSE CVE CVE-2025-40037 | first fixed: 2 known affected: 394 known not affected: 348 recommended: 271 | 2026-07-23T01:35:39+00:00 | Vulnerability · Source |
| CVE-2025-40038 | suse_vex | SUSE CVE CVE-2025-40038 | first fixed: 2 known affected: 394 known not affected: 266 recommended: 479 | 2026-07-23T01:35:37+00:00 | Vulnerability · Source |
| CVE-2025-40041 | suse_vex | SUSE CVE CVE-2025-40041 | known not affected: 336 recommended: 6 | 2026-07-23T01:35:35+00:00 | Vulnerability · Source |
| CVE-2025-40042 | suse_vex | SUSE CVE CVE-2025-40042 | first fixed: 2 known affected: 685 recommended: 408 | 2026-07-23T01:35:34+00:00 | Vulnerability · Source |
| CVE-2025-40049 | suse_vex | SUSE CVE CVE-2025-40049 | first fixed: 2 known affected: 630 recommended: 536 | 2026-07-23T01:35:32+00:00 | Vulnerability · Source |
| CVE-2025-40054 | suse_vex | SUSE CVE CVE-2025-40054 | known not affected: 339 recommended: 6 | 2026-07-23T01:35:30+00:00 | Vulnerability · Source |
| CVE-2025-40059 | suse_vex | SUSE CVE CVE-2025-40059 | first fixed: 2 known affected: 394 known not affected: 266 recommended: 506 | 2026-07-23T01:35:28+00:00 | Vulnerability · Source |
| CVE-2025-40072 | suse_vex | SUSE CVE CVE-2025-40072 | known not affected: 336 recommended: 6 | 2026-07-23T01:35:25+00:00 | Vulnerability · Source |
| CVE-2025-40076 | suse_vex | SUSE CVE CVE-2025-40076 | known not affected: 336 recommended: 6 | 2026-07-23T01:35:24+00:00 | Vulnerability · Source |
| CVE-2025-40086 | suse_vex | SUSE CVE CVE-2025-40086 | first fixed: 2 known affected: 394 known not affected: 374 recommended: 271 | 2026-07-23T01:35:21+00:00 | Vulnerability · Source |
| CVE-2025-40087 | suse_vex | SUSE CVE CVE-2025-40087 | first fixed: 2 known affected: 610 known not affected: 22 recommended: 529 | 2026-07-23T01:35:19+00:00 | Vulnerability · Source |
| CVE-2025-40091 | suse_vex | SUSE CVE CVE-2025-40091 | first fixed: 2 known affected: 394 known not affected: 348 recommended: 244 | 2026-07-23T01:35:18+00:00 | Vulnerability · Source |
| CVE-2025-40095 | suse_vex | SUSE CVE CVE-2025-40095 | known not affected: 336 recommended: 6 | 2026-07-23T01:35:16+00:00 | Vulnerability · Source |
| CVE-2025-40097 | suse_vex | SUSE CVE CVE-2025-40097 | first fixed: 2 known affected: 561 known not affected: 158 recommended: 381 | 2026-07-23T01:35:15+00:00 | Vulnerability · Source |
| CVE-2025-40109 | suse_vex | SUSE CVE CVE-2025-40109 | first fixed: 2 known affected: 506 known not affected: 146 recommended: 473 | 2026-07-23T01:35:11+00:00 | Vulnerability · Source |
| CVE-2025-40111 | suse_vex | SUSE CVE CVE-2025-40111 | first fixed: 2 known affected: 561 known not affected: 126 recommended: 500 | 2026-07-23T01:35:10+00:00 | Vulnerability · Source |
| CVE-2025-40112 | suse_vex | SUSE CVE CVE-2025-40112 | known not affected: 337 | 2026-07-23T01:35:09+00:00 | Vulnerability · Source |
| CVE-2025-40115 | suse_vex | SUSE CVE CVE-2025-40115 | first fixed: 2 known affected: 622 known not affected: 6 recommended: 503 | 2026-07-23T01:35:07+00:00 | Vulnerability · Source |
| CVE-2025-40116 | suse_vex | SUSE CVE CVE-2025-40116 | first fixed: 2 known affected: 616 known not affected: 36 recommended: 473 | 2026-07-23T01:35:06+00:00 | Vulnerability · Source |
| CVE-2025-40118 | suse_vex | SUSE CVE CVE-2025-40118 | first fixed: 2 known affected: 394 known not affected: 264 recommended: 500 | 2026-07-23T01:35:05+00:00 | Vulnerability · Source |
| CVE-2025-40119 | suse_vex | SUSE CVE CVE-2025-40119 | known not affected: 337 | 2026-07-23T01:35:03+00:00 | Vulnerability · Source |
| CVE-2025-40125 | suse_vex | SUSE CVE CVE-2025-40125 | known affected: 163 known not affected: 15 | 2026-07-23T01:35:02+00:00 | Vulnerability · Source |
| CVE-2025-40128 | suse_vex | SUSE CVE CVE-2025-40128 | known not affected: 337 | 2026-07-23T01:35:01+00:00 | Vulnerability · Source |
| CVE-2025-40142 | suse_vex | SUSE CVE CVE-2025-40142 | first fixed: 2 known affected: 394 known not affected: 346 recommended: 238 | 2026-07-23T01:34:56+00:00 | Vulnerability · Source |
| CVE-2025-40148 | suse_vex | SUSE CVE CVE-2025-40148 | known not affected: 337 | 2026-07-23T01:34:54+00:00 | Vulnerability · Source |
| CVE-2025-40167 | suse_vex | SUSE CVE CVE-2025-40167 | first fixed: 2 known affected: 677 known not affected: 6 recommended: 405 | 2026-07-23T01:34:50+00:00 | Vulnerability · Source |
| CVE-2025-40172 | suse_vex | SUSE CVE CVE-2025-40172 | first fixed: 2 known affected: 394 known not affected: 258 recommended: 473 | 2026-07-23T01:34:48+00:00 | Vulnerability · Source |
| CVE-2025-40177 | suse_vex | SUSE CVE CVE-2025-40177 | first fixed: 2 known affected: 394 known not affected: 346 recommended: 265 | 2026-07-23T01:34:46+00:00 | Vulnerability · Source |
| CVE-2025-40181 | suse_vex | SUSE CVE CVE-2025-40181 | first fixed: 2 known affected: 411 known not affected: 372 recommended: 283 | 2026-07-23T01:34:44+00:00 | Vulnerability · Source |
| CVE-2025-40183 | suse_vex | SUSE CVE CVE-2025-40183 | first fixed: 2 known affected: 506 known not affected: 152 recommended: 500 | 2026-07-23T01:34:42+00:00 | Vulnerability · Source |
| CVE-2025-40184 | suse_vex | SUSE CVE CVE-2025-40184 | known not affected: 337 | 2026-07-23T01:34:41+00:00 | Vulnerability · Source |
| CVE-2025-40187 | suse_vex | SUSE CVE CVE-2025-40187 | first fixed: 2 known affected: 616 known not affected: 114 recommended: 384 | 2026-07-23T01:34:39+00:00 | Vulnerability · Source |
| CVE-2025-40189 | suse_vex | SUSE CVE CVE-2025-40189 | known not affected: 337 | 2026-07-23T01:34:38+00:00 | Vulnerability · Source |
| CVE-2025-40195 | suse_vex | SUSE CVE CVE-2025-40195 | first fixed: 2 known not affected: 403 recommended: 145 | 2026-07-23T01:34:36+00:00 | Vulnerability · Source |
| CVE-2025-40205 | suse_vex | SUSE CVE CVE-2025-40205 | first fixed: 2 known affected: 628 recommended: 503 | 2026-07-23T01:34:34+00:00 | Vulnerability · Source |
| CVE-2025-40206 | suse_vex | SUSE CVE CVE-2025-40206 | first fixed: 2 known affected: 429 known not affected: 223 recommended: 500 | 2026-07-23T01:34:32+00:00 | Vulnerability · Source |
| CVE-2025-40207 | suse_vex | SUSE CVE CVE-2025-40207 | first fixed: 2 known affected: 394 known not affected: 258 recommended: 500 | 2026-07-23T01:34:31+00:00 | Vulnerability · Source |
| CVE-2025-40210 | suse_vex | SUSE CVE CVE-2025-40210 | known not affected: 337 | 2026-07-23T01:34:29+00:00 | Vulnerability · Source |
| CVE-2025-40211 | suse_vex | SUSE CVE CVE-2025-40211 | first fixed: 2 known affected: 622 known not affected: 61 recommended: 402 | 2026-07-23T01:34:28+00:00 | Vulnerability · Source |
| CVE-2025-40212 | suse_vex | SUSE CVE CVE-2025-40212 | first fixed: 2 known affected: 394 known not affected: 403 recommended: 184 | 2026-07-23T01:34:26+00:00 | Vulnerability · Source |
| CVE-2025-40217 | suse_vex | SUSE CVE CVE-2025-40217 | known affected: 17 known not affected: 356 | 2026-07-23T01:34:25+00:00 | Vulnerability · Source |
| CVE-2025-40221 | suse_vex | SUSE CVE CVE-2025-40221 | first fixed: 2 known affected: 394 known not affected: 403 recommended: 172 | 2026-07-23T01:34:23+00:00 | Vulnerability · Source |
| CVE-2025-40231 | suse_vex | SUSE CVE CVE-2025-40231 | first fixed: 2 known affected: 394 known not affected: 334 recommended: 280 | 2026-07-23T01:34:22+00:00 | Vulnerability · Source |
| CVE-2025-40235 | suse_vex | SUSE CVE CVE-2025-40235 | first fixed: 2 known affected: 394 known not affected: 403 recommended: 172 | 2026-07-23T01:34:20+00:00 | Vulnerability · Source |