VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
306217 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-40318 | suse_vex | SUSE CVE CVE-2025-40318 | known affected: 396 known not affected: 429 recommended: 467 | 2026-10-10T01:50:49+00:00 | Vulnerability · Source |
| CVE-2025-40322 | suse_vex | SUSE CVE CVE-2025-40322 | known affected: 724 known not affected: 47 recommended: 553 | 2026-10-10T01:50:46+00:00 | Vulnerability · Source |
| CVE-2025-40323 | suse_vex | SUSE CVE CVE-2025-40323 | known affected: 597 known not affected: 174 recommended: 520 | 2026-10-10T01:50:44+00:00 | Vulnerability · Source |
| CVE-2025-40324 | suse_vex | SUSE CVE CVE-2025-40324 | known affected: 524 known not affected: 301 recommended: 384 | 2026-10-10T01:50:40+00:00 | Vulnerability · Source |
| CVE-2025-40325 | suse_vex | SUSE CVE CVE-2025-40325 | known affected: 538 known not affected: 256 recommended: 400 | 2026-10-10T01:50:37+00:00 | Vulnerability · Source |
| CVE-2025-40328 | suse_vex | SUSE CVE CVE-2025-40328 | known affected: 571 known not affected: 260 recommended: 384 | 2026-10-10T01:50:34+00:00 | Vulnerability · Source |
| CVE-2025-40337 | suse_vex | SUSE CVE CVE-2025-40337 | known affected: 812 recommended: 326 | 2026-10-10T01:50:31+00:00 | Vulnerability · Source |
| CVE-2025-40338 | suse_vex | SUSE CVE CVE-2025-40338 | known affected: 484 known not affected: 388 recommended: 289 | 2026-10-10T01:50:27+00:00 | Vulnerability · Source |
| CVE-2025-40342 | suse_vex | SUSE CVE CVE-2025-40342 | known affected: 737 known not affected: 34 recommended: 421 | 2026-10-10T01:50:24+00:00 | Vulnerability · Source |
| CVE-2025-40346 | suse_vex | SUSE CVE CVE-2025-40346 | known affected: 612 known not affected: 260 recommended: 289 | 2026-10-10T01:50:21+00:00 | Vulnerability · Source |
| CVE-2025-40347 | suse_vex | SUSE CVE CVE-2025-40347 | known affected: 685 known not affected: 187 recommended: 289 | 2026-10-10T01:50:19+00:00 | Vulnerability · Source |
| CVE-2025-40353 | suse_vex | SUSE CVE CVE-2025-40353 | known affected: 396 known not affected: 543 recommended: 172 | 2026-10-10T01:50:16+00:00 | Vulnerability · Source |
| CVE-2025-40359 | suse_vex | SUSE CVE CVE-2025-40359 | known affected: 396 known not affected: 488 recommended: 265 | 2026-10-10T01:50:13+00:00 | Vulnerability · Source |
| CVE-2025-40360 | suse_vex | SUSE CVE CVE-2025-40360 | known affected: 551 known not affected: 321 recommended: 289 | 2026-10-10T01:50:10+00:00 | Vulnerability · Source |
| CVE-2025-40362 | suse_vex | SUSE CVE CVE-2025-40362 | known affected: 405 known not affected: 540 recommended: 172 | 2026-10-10T01:50:08+00:00 | Vulnerability · Source |
| CVE-2025-40363 | suse_vex | SUSE CVE CVE-2025-40363 | known affected: 812 recommended: 326 | 2026-10-10T01:50:06+00:00 | Vulnerability · Source |
| CVE-2025-40364 | suse_vex | SUSE CVE CVE-2025-40364 | known affected: 396 known not affected: 451 recommended: 241 | 2026-10-10T01:50:04+00:00 | Vulnerability · Source |
| CVE-2025-40778 | suse_vex | SUSE CVE CVE-2025-40778 | known affected: 603 recommended: 413 | 2026-10-10T01:50:02+00:00 | Vulnerability · Source |
| CVE-2025-40907 | suse_vex | SUSE CVE CVE-2025-40907 | recommended: 4 | 2026-10-10T01:50:00+00:00 | Vulnerability · Source |
| CVE-2025-40908 | suse_vex | SUSE CVE CVE-2025-40908 | known affected: 37 recommended: 18 | 2026-10-10T01:49:59+00:00 | Vulnerability · Source |
| CVE-2025-40909 | suse_vex | SUSE CVE CVE-2025-40909 | known affected: 528 known not affected: 1 recommended: 672 | 2026-10-10T01:49:57+00:00 | Vulnerability · Source |
| CVE-2025-41244 | suse_vex | SUSE CVE CVE-2025-41244 | known affected: 52 known not affected: 30 recommended: 247 | 2026-10-10T01:49:54+00:00 | Vulnerability · Source |
| CVE-2025-41423 | suse_vex | SUSE CVE CVE-2025-41423 | recommended: 4 | 2026-10-10T01:49:52+00:00 | Vulnerability · Source |
| CVE-2025-41443 | suse_vex | SUSE CVE CVE-2025-41443 | recommended: 1 | 2026-10-10T01:49:50+00:00 | Vulnerability · Source |
| CVE-2025-43213 | suse_vex | SUSE CVE CVE-2025-43213 | known affected: 176 recommended: 508 | 2026-10-10T01:49:48+00:00 | Vulnerability · Source |
| CVE-2025-43227 | suse_vex | SUSE CVE CVE-2025-43227 | known affected: 195 known not affected: 105 recommended: 566 | 2026-10-10T01:49:46+00:00 | Vulnerability · Source |
| CVE-2025-43240 | suse_vex | SUSE CVE CVE-2025-43240 | known affected: 195 known not affected: 105 recommended: 566 | 2026-10-10T01:49:44+00:00 | Vulnerability · Source |
| CVE-2025-43265 | suse_vex | SUSE CVE CVE-2025-43265 | known affected: 195 known not affected: 105 recommended: 566 | 2026-10-10T01:49:42+00:00 | Vulnerability · Source |
| CVE-2025-43272 | suse_vex | SUSE CVE CVE-2025-43272 | known affected: 237 recommended: 564 | 2026-10-10T01:49:39+00:00 | Vulnerability · Source |
| CVE-2025-43343 | suse_vex | SUSE CVE CVE-2025-43343 | known affected: 237 recommended: 564 | 2026-10-10T01:49:37+00:00 | Vulnerability · Source |
| CVE-2025-43356 | suse_vex | SUSE CVE CVE-2025-43356 | known affected: 237 recommended: 564 | 2026-10-10T01:49:34+00:00 | Vulnerability · Source |
| CVE-2025-43431 | suse_vex | SUSE CVE CVE-2025-43431 | known affected: 237 recommended: 588 | 2026-10-10T01:49:31+00:00 | Vulnerability · Source |
| CVE-2025-43434 | suse_vex | SUSE CVE CVE-2025-43434 | known affected: 221 known not affected: 16 recommended: 588 | 2026-10-10T01:49:28+00:00 | Vulnerability · Source |
| CVE-2025-43441 | suse_vex | SUSE CVE CVE-2025-43441 | known affected: 176 recommended: 508 | 2026-10-10T01:49:26+00:00 | Vulnerability · Source |
| CVE-2025-43443 | suse_vex | SUSE CVE CVE-2025-43443 | known affected: 221 known not affected: 16 recommended: 588 | 2026-10-10T01:49:23+00:00 | Vulnerability · Source |
| CVE-2025-43511 | suse_vex | SUSE CVE CVE-2025-43511 | known affected: 176 recommended: 508 | 2026-10-10T01:49:21+00:00 | Vulnerability · Source |
| CVE-2025-43535 | suse_vex | SUSE CVE CVE-2025-43535 | known affected: 238 recommended: 580 | 2026-10-10T01:49:19+00:00 | Vulnerability · Source |
| CVE-2025-43903 | suse_vex | SUSE CVE CVE-2025-43903 | known not affected: 340 recommended: 79 | 2026-10-10T01:49:16+00:00 | Vulnerability · Source |
| CVE-2025-43961 | suse_vex | SUSE CVE CVE-2025-43961 | known affected: 22 known not affected: 15 recommended: 47 | 2026-10-10T01:49:13+00:00 | Vulnerability · Source |
| CVE-2025-43962 | suse_vex | SUSE CVE CVE-2025-43962 | known affected: 34 recommended: 49 | 2026-10-10T01:49:11+00:00 | Vulnerability · Source |
| CVE-2025-43963 | suse_vex | SUSE CVE CVE-2025-43963 | known affected: 22 known not affected: 15 recommended: 47 | 2026-10-10T01:49:10+00:00 | Vulnerability · Source |
| CVE-2025-43971 | suse_vex | SUSE CVE CVE-2025-43971 | recommended: 4 | 2026-10-10T01:49:07+00:00 | Vulnerability · Source |
| CVE-2025-43972 | suse_vex | SUSE CVE CVE-2025-43972 | recommended: 4 | 2026-10-10T01:49:05+00:00 | Vulnerability · Source |
| CVE-2025-45582 | suse_vex | SUSE CVE CVE-2025-45582 | known affected: 429 recommended: 141 | 2026-10-10T01:49:03+00:00 | Vulnerability · Source |
| CVE-2025-46421 | suse_vex | SUSE CVE CVE-2025-46421 | known affected: 109 recommended: 242 | 2026-10-10T01:49:00+00:00 | Vulnerability · Source |
| CVE-2025-46701 | suse_vex | SUSE CVE CVE-2025-46701 | known affected: 521 known not affected: 38 recommended: 405 | 2026-10-10T01:48:58+00:00 | Vulnerability · Source |
| CVE-2025-46721 | suse_vex | SUSE CVE CVE-2025-46721 | recommended: 4 | 2026-10-10T01:48:55+00:00 | Vulnerability · Source |
| CVE-2025-46727 | suse_vex | SUSE CVE CVE-2025-46727 | known affected: 428 known not affected: 8 recommended: 93 | 2026-10-10T01:48:53+00:00 | Vulnerability · Source |
| CVE-2025-46819 | suse_vex | SUSE CVE CVE-2025-46819 | known affected: 4 known not affected: 7 recommended: 80 | 2026-10-10T01:48:50+00:00 | Vulnerability · Source |
| CVE-2025-46835 | suse_vex | SUSE CVE CVE-2025-46835 | known affected: 214 recommended: 444 | 2026-10-10T01:48:48+00:00 | Vulnerability · Source |