VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292442 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2025-40239 | suse_vex | SUSE CVE CVE-2025-40239 | first fixed: 2 known affected: 394 known not affected: 429 recommended: 172 | 2026-07-23T01:34:19+00:00 | Vulnerability · Source |
| CVE-2025-40244 | suse_vex | SUSE CVE CVE-2025-40244 | known affected: 394 known not affected: 306 recommended: 260 | 2026-07-23T01:34:18+00:00 | Vulnerability · Source |
| CVE-2025-40245 | suse_vex | SUSE CVE CVE-2025-40245 | known not affected: 378 | 2026-07-23T01:34:16+00:00 | Vulnerability · Source |
| CVE-2025-40250 | suse_vex | SUSE CVE CVE-2025-40250 | first fixed: 2 known affected: 490 known not affected: 264 recommended: 307 | 2026-07-23T01:34:13+00:00 | Vulnerability · Source |
| CVE-2025-40288 | suse_vex | SUSE CVE CVE-2025-40288 | first fixed: 2 known affected: 608 known not affected: 105 recommended: 402 | 2026-07-23T01:34:08+00:00 | Vulnerability · Source |
| CVE-2025-40292 | suse_vex | SUSE CVE CVE-2025-40292 | first fixed: 2 known affected: 490 known not affected: 264 recommended: 280 | 2026-07-23T01:34:07+00:00 | Vulnerability · Source |
| CVE-2025-40293 | suse_vex | SUSE CVE CVE-2025-40293 | first fixed: 2 known affected: 490 known not affected: 264 recommended: 307 | 2026-07-23T01:34:05+00:00 | Vulnerability · Source |
| CVE-2025-40296 | suse_vex | SUSE CVE CVE-2025-40296 | known not affected: 343 | 2026-07-23T01:34:04+00:00 | Vulnerability · Source |
| CVE-2025-40305 | suse_vex | SUSE CVE CVE-2025-40305 | known not affected: 378 | 2026-07-23T01:33:59+00:00 | Vulnerability · Source |
| CVE-2025-40310 | suse_vex | SUSE CVE CVE-2025-40310 | first fixed: 2 known affected: 451 known not affected: 262 recommended: 375 | 2026-07-23T01:33:57+00:00 | Vulnerability · Source |
| CVE-2025-40313 | suse_vex | SUSE CVE CVE-2025-40313 | known not affected: 347 | 2026-07-23T01:33:56+00:00 | Vulnerability · Source |
| CVE-2025-40319 | suse_vex | SUSE CVE CVE-2025-40319 | first fixed: 2 known affected: 643 known not affected: 111 recommended: 307 | 2026-07-23T01:33:54+00:00 | Vulnerability · Source |
| CVE-2025-40320 | suse_vex | SUSE CVE CVE-2025-40320 | first fixed: 2 known affected: 394 known not affected: 313 recommended: 402 | 2026-07-23T01:33:53+00:00 | Vulnerability · Source |
| CVE-2025-40321 | suse_vex | SUSE CVE CVE-2025-40321 | first fixed: 2 known affected: 622 known not affected: 61 recommended: 432 | 2026-07-23T01:33:51+00:00 | Vulnerability · Source |
| CVE-2025-40323 | suse_vex | SUSE CVE CVE-2025-40323 | first fixed: 2 known affected: 561 known not affected: 122 recommended: 432 | 2026-07-23T01:33:50+00:00 | Vulnerability · Source |
| CVE-2025-40324 | suse_vex | SUSE CVE CVE-2025-40324 | first fixed: 2 known affected: 506 known not affected: 201 recommended: 402 | 2026-07-23T01:33:49+00:00 | Vulnerability · Source |
| CVE-2025-40326 | suse_vex | SUSE CVE CVE-2025-40326 | known not affected: 337 | 2026-07-23T01:33:47+00:00 | Vulnerability · Source |
| CVE-2025-40328 | suse_vex | SUSE CVE CVE-2025-40328 | first fixed: 2 known affected: 561 known not affected: 152 recommended: 402 | 2026-07-23T01:33:46+00:00 | Vulnerability · Source |
| CVE-2025-40331 | suse_vex | SUSE CVE CVE-2025-40331 | first fixed: 2 known affected: 504 known not affected: 22 recommended: 625 | 2026-07-23T01:33:44+00:00 | Vulnerability · Source |
| CVE-2025-40333 | suse_vex | SUSE CVE CVE-2025-40333 | known not affected: 378 | 2026-07-23T01:33:43+00:00 | Vulnerability · Source |
| CVE-2025-40350 | suse_vex | SUSE CVE CVE-2025-40350 | first fixed: 2 known affected: 490 known not affected: 264 recommended: 307 | 2026-07-23T01:33:38+00:00 | Vulnerability · Source |
| CVE-2025-40351 | suse_vex | SUSE CVE CVE-2025-40351 | known affected: 394 known not affected: 323 recommended: 260 | 2026-07-23T01:33:37+00:00 | Vulnerability · Source |
| CVE-2025-40352 | suse_vex | SUSE CVE CVE-2025-40352 | known not affected: 347 | 2026-07-23T01:33:35+00:00 | Vulnerability · Source |
| CVE-2025-40355 | suse_vex | SUSE CVE CVE-2025-40355 | first fixed: 2 known affected: 602 known not affected: 152 recommended: 280 | 2026-07-23T01:33:34+00:00 | Vulnerability · Source |
| CVE-2025-40357 | suse_vex | SUSE CVE CVE-2025-40357 | first fixed: 2 known affected: 394 known not affected: 372 recommended: 283 | 2026-07-23T01:33:32+00:00 | Vulnerability · Source |
| CVE-2025-40358 | suse_vex | SUSE CVE CVE-2025-40358 | known not affected: 378 | 2026-07-23T01:33:31+00:00 | Vulnerability · Source |
| CVE-2025-40362 | suse_vex | SUSE CVE CVE-2025-40362 | first fixed: 2 known affected: 406 known not affected: 431 recommended: 172 | 2026-07-23T01:33:30+00:00 | Vulnerability · Source |
| CVE-2025-40918 | suse_vex | SUSE CVE CVE-2025-40918 | known affected: 9 recommended: 64 | 2026-07-23T01:33:28+00:00 | Vulnerability · Source |
| CVE-2025-43213 | suse_vex | SUSE CVE CVE-2025-43213 | known affected: 88 recommended: 521 | 2026-07-23T01:33:25+00:00 | Vulnerability · Source |
| CVE-2025-43434 | suse_vex | SUSE CVE CVE-2025-43434 | known affected: 124 known not affected: 8 recommended: 607 | 2026-07-23T01:33:21+00:00 | Vulnerability · Source |
| CVE-2025-43903 | suse_vex | SUSE CVE CVE-2025-43903 | known not affected: 160 recommended: 93 | 2026-07-23T01:33:19+00:00 | Vulnerability · Source |
| CVE-2025-46398 | suse_vex | SUSE CVE CVE-2025-46398 | known affected: 7 recommended: 14 | 2026-07-23T01:33:17+00:00 | Vulnerability · Source |
| CVE-2025-46421 | suse_vex | SUSE CVE CVE-2025-46421 | known affected: 55 recommended: 239 | 2026-07-23T01:33:16+00:00 | Vulnerability · Source |
| CVE-2025-46803 | suse_vex | SUSE CVE CVE-2025-46803 | known not affected: 38 | 2026-07-23T01:33:15+00:00 | Vulnerability · Source |
| CVE-2025-46804 | suse_vex | SUSE CVE CVE-2025-46804 | known not affected: 47 | 2026-07-23T01:33:13+00:00 | Vulnerability · Source |