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-40252 | suse_vex | SUSE CVE CVE-2025-40252 | first fixed: 2 known affected: 718 known not affected: 6 recommended: 364 | 2026-07-25T00:33:01+00:00 | Vulnerability · Source |
| CVE-2025-40254 | suse_vex | SUSE CVE CVE-2025-40254 | first fixed: 2 known affected: 657 known not affected: 99 recommended: 307 | 2026-07-25T00:32:58+00:00 | Vulnerability · Source |
| CVE-2025-40255 | suse_vex | SUSE CVE CVE-2025-40255 | first fixed: 2 known affected: 561 known not affected: 266 recommended: 172 | 2026-07-25T00:32:56+00:00 | Vulnerability · Source |
| CVE-2025-40256 | suse_vex | SUSE CVE CVE-2025-40256 | first fixed: 2 known not affected: 164 recommended: 599 | 2026-07-25T00:32:53+00:00 | Vulnerability · Source |
| CVE-2025-40257 | suse_vex | SUSE CVE CVE-2025-40257 | first fixed: 2 known affected: 407 known not affected: 154 recommended: 598 | 2026-07-25T00:32:50+00:00 | Vulnerability · Source |
| CVE-2025-40259 | suse_vex | SUSE CVE CVE-2025-40259 | first fixed: 2 known affected: 677 known not affected: 6 recommended: 439 | 2026-07-25T00:32:47+00:00 | Vulnerability · Source |
| CVE-2025-40262 | suse_vex | SUSE CVE CVE-2025-40262 | first fixed: 2 known affected: 394 known not affected: 207 recommended: 402 | 2026-07-25T00:32:44+00:00 | Vulnerability · Source |
| CVE-2025-40263 | suse_vex | SUSE CVE CVE-2025-40263 | first fixed: 2 known affected: 561 known not affected: 154 recommended: 402 | 2026-07-25T00:32:41+00:00 | Vulnerability · Source |
| CVE-2025-40264 | suse_vex | SUSE CVE CVE-2025-40264 | first fixed: 2 known affected: 718 known not affected: 6 recommended: 344 | 2026-07-25T00:32:39+00:00 | Vulnerability · Source |
| CVE-2025-40268 | suse_vex | SUSE CVE CVE-2025-40268 | first fixed: 2 known affected: 602 known not affected: 154 recommended: 307 | 2026-07-25T00:32:36+00:00 | Vulnerability · Source |
| CVE-2025-40270 | suse_vex | SUSE CVE CVE-2025-40270 | known not affected: 408 | 2026-07-25T00:32:31+00:00 | Vulnerability · Source |
| CVE-2025-40272 | suse_vex | SUSE CVE CVE-2025-40272 | first fixed: 2 known affected: 506 known not affected: 203 recommended: 402 | 2026-07-25T00:32:28+00:00 | Vulnerability · Source |
| CVE-2025-40273 | suse_vex | SUSE CVE CVE-2025-40273 | first fixed: 2 known affected: 506 known not affected: 203 recommended: 402 | 2026-07-25T00:32:26+00:00 | Vulnerability · Source |
| CVE-2025-40274 | suse_vex | SUSE CVE CVE-2025-40274 | first fixed: 2 known affected: 490 known not affected: 266 recommended: 307 | 2026-07-25T00:32:23+00:00 | Vulnerability · Source |
| CVE-2025-40275 | suse_vex | SUSE CVE CVE-2025-40275 | first fixed: 2 known affected: 578 known not affected: 107 recommended: 425 | 2026-07-25T00:32:21+00:00 | Vulnerability · Source |
| CVE-2025-40278 | suse_vex | SUSE CVE CVE-2025-40278 | first fixed: 2 known affected: 704 known not affected: 22 recommended: 330 | 2026-07-25T00:32:15+00:00 | Vulnerability · Source |
| CVE-2025-40279 | suse_vex | SUSE CVE CVE-2025-40279 | first fixed: 2 known affected: 718 known not affected: 6 recommended: 344 | 2026-07-25T00:32:13+00:00 | Vulnerability · Source |
| CVE-2025-40280 | suse_vex | SUSE CVE CVE-2025-40280 | first fixed: 2 known affected: 457 known not affected: 99 recommended: 602 | 2026-07-25T00:32:10+00:00 | Vulnerability · Source |
| CVE-2025-40282 | suse_vex | SUSE CVE CVE-2025-40282 | first fixed: 2 known affected: 394 known not affected: 321 recommended: 402 | 2026-07-25T00:32:07+00:00 | Vulnerability · Source |
| CVE-2025-40283 | suse_vex | SUSE CVE CVE-2025-40283 | first fixed: 2 known affected: 608 known not affected: 77 recommended: 425 | 2026-07-25T00:32:05+00:00 | Vulnerability · Source |
| CVE-2025-40284 | suse_vex | SUSE CVE CVE-2025-40284 | first fixed: 2 known affected: 394 known not affected: 315 recommended: 477 | 2026-07-25T00:32:02+00:00 | Vulnerability · Source |
| CVE-2025-40287 | suse_vex | SUSE CVE CVE-2025-40287 | first fixed: 2 known affected: 657 known not affected: 99 recommended: 307 | 2026-07-25T00:31:59+00:00 | Vulnerability · Source |
| CVE-2025-40289 | suse_vex | SUSE CVE CVE-2025-40289 | first fixed: 2 known affected: 490 known not affected: 266 recommended: 307 | 2026-07-25T00:31:56+00:00 | Vulnerability · Source |
| CVE-2025-40291 | suse_vex | SUSE CVE CVE-2025-40291 | known not affected: 408 | 2026-07-25T00:31:54+00:00 | Vulnerability · Source |
| CVE-2025-40297 | suse_vex | SUSE CVE CVE-2025-40297 | first fixed: 2 known affected: 449 known not affected: 266 recommended: 484 | 2026-07-25T00:31:50+00:00 | Vulnerability · Source |
| CVE-2025-40300 | suse_vex | SUSE CVE CVE-2025-40300 | first fixed: 2 known affected: 416 known not affected: 67 recommended: 789 | 2026-07-25T00:31:47+00:00 | Vulnerability · Source |
| CVE-2025-40302 | suse_vex | SUSE CVE CVE-2025-40302 | first fixed: 2 known affected: 394 known not affected: 354 recommended: 283 | 2026-07-25T00:31:44+00:00 | Vulnerability · Source |
| CVE-2025-40303 | suse_vex | SUSE CVE CVE-2025-40303 | first fixed: 2 known affected: 549 known not affected: 278 recommended: 172 | 2026-07-25T00:31:42+00:00 | Vulnerability · Source |
| CVE-2025-40306 | suse_vex | SUSE CVE CVE-2025-40306 | known affected: 394 known not affected: 338 recommended: 230 | 2026-07-25T00:31:39+00:00 | Vulnerability · Source |
| CVE-2025-40308 | suse_vex | SUSE CVE CVE-2025-40308 | first fixed: 2 known affected: 394 known not affected: 289 recommended: 439 | 2026-07-25T00:31:36+00:00 | Vulnerability · Source |
| CVE-2025-40311 | suse_vex | SUSE CVE CVE-2025-40311 | first fixed: 2 known affected: 394 known not affected: 301 recommended: 402 | 2026-07-25T00:31:33+00:00 | Vulnerability · Source |
| CVE-2025-40312 | suse_vex | SUSE CVE CVE-2025-40312 | known affected: 394 known not affected: 338 recommended: 230 | 2026-07-25T00:31:31+00:00 | Vulnerability · Source |
| CVE-2025-40314 | suse_vex | SUSE CVE CVE-2025-40314 | first fixed: 2 known affected: 506 known not affected: 189 recommended: 402 | 2026-07-25T00:31:29+00:00 | Vulnerability · Source |
| CVE-2025-40315 | suse_vex | SUSE CVE CVE-2025-40315 | first fixed: 2 known affected: 441 known not affected: 274 recommended: 402 | 2026-07-25T00:31:26+00:00 | Vulnerability · Source |
| CVE-2025-40316 | suse_vex | SUSE CVE CVE-2025-40316 | first fixed: 2 known affected: 394 known not affected: 315 recommended: 402 | 2026-07-25T00:31:24+00:00 | Vulnerability · Source |
| CVE-2025-40317 | suse_vex | SUSE CVE CVE-2025-40317 | first fixed: 2 known affected: 555 known not affected: 154 recommended: 402 | 2026-07-25T00:31:22+00:00 | Vulnerability · Source |
| CVE-2025-40329 | suse_vex | SUSE CVE CVE-2025-40329 | first fixed: 2 known affected: 394 known not affected: 315 recommended: 402 | 2026-07-25T00:31:09+00:00 | Vulnerability · Source |
| CVE-2025-40337 | suse_vex | SUSE CVE CVE-2025-40337 | first fixed: 2 known affected: 724 recommended: 344 | 2026-07-25T00:31:06+00:00 | Vulnerability · Source |
| CVE-2025-40338 | suse_vex | SUSE CVE CVE-2025-40338 | first fixed: 2 known affected: 490 known not affected: 266 recommended: 307 | 2026-07-25T00:31:03+00:00 | Vulnerability · Source |
| CVE-2025-40340 | suse_vex | SUSE CVE CVE-2025-40340 | first fixed: 2 known affected: 394 known not affected: 348 recommended: 283 | 2026-07-25T00:31:00+00:00 | Vulnerability · Source |
| CVE-2025-40343 | suse_vex | SUSE CVE CVE-2025-40343 | first fixed: 2 known affected: 451 known not affected: 264 recommended: 402 | 2026-07-25T00:30:53+00:00 | Vulnerability · Source |
| CVE-2025-40345 | suse_vex | SUSE CVE CVE-2025-40345 | first fixed: 2 known affected: 628 known not affected: 84 recommended: 439 | 2026-07-25T00:30:51+00:00 | Vulnerability · Source |
| CVE-2025-40346 | suse_vex | SUSE CVE CVE-2025-40346 | first fixed: 2 known affected: 602 known not affected: 154 recommended: 307 | 2026-07-25T00:30:49+00:00 | Vulnerability · Source |
| CVE-2025-40347 | suse_vex | SUSE CVE CVE-2025-40347 | first fixed: 2 known affected: 657 known not affected: 99 recommended: 307 | 2026-07-25T00:30:48+00:00 | Vulnerability · Source |
| CVE-2025-40349 | suse_vex | SUSE CVE CVE-2025-40349 | known affected: 394 known not affected: 306 recommended: 267 | 2026-07-25T00:30:45+00:00 | Vulnerability · Source |
| CVE-2025-40359 | suse_vex | SUSE CVE CVE-2025-40359 | first fixed: 2 known affected: 394 known not affected: 374 recommended: 283 | 2026-07-25T00:30:42+00:00 | Vulnerability · Source |
| CVE-2025-40360 | suse_vex | SUSE CVE CVE-2025-40360 | first fixed: 2 known affected: 547 known not affected: 209 recommended: 307 | 2026-07-25T00:30:40+00:00 | Vulnerability · Source |
| CVE-2025-40363 | suse_vex | SUSE CVE CVE-2025-40363 | first fixed: 2 known affected: 724 recommended: 344 | 2026-07-25T00:30:37+00:00 | Vulnerability · Source |
| CVE-2025-40908 | suse_vex | SUSE CVE CVE-2025-40908 | known affected: 24 recommended: 19 | 2026-07-25T00:30:31+00:00 | Vulnerability · Source |
| CVE-2025-43272 | suse_vex | SUSE CVE CVE-2025-43272 | known affected: 132 recommended: 608 | 2026-07-25T00:30:28+00:00 | Vulnerability · Source |