VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-41117 | suse_vex | SUSE CVE CVE-2025-41117 | known not affected: 6 | 2026-10-15T16:24:45+00:00 | Vulnerability · Source |
| CVE-2025-41410 | suse_vex | SUSE CVE CVE-2025-41410 | recommended: 1 | 2026-10-15T16:24:43+00:00 | Vulnerability · Source |
| CVE-2025-41436 | suse_vex | SUSE CVE CVE-2025-41436 | No product status | 2026-10-15T16:24:41+00:00 | Vulnerability · Source |
| CVE-2025-43211 | suse_vex | SUSE CVE CVE-2025-43211 | known affected: 179 recommended: 566 | 2026-10-15T16:24:40+00:00 | Vulnerability · Source |
| CVE-2025-43212 | suse_vex | SUSE CVE CVE-2025-43212 | known affected: 179 known not affected: 105 recommended: 566 | 2026-10-15T16:24:38+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-15T16:24:37+00:00 | Vulnerability · Source |
| CVE-2025-43272 | suse_vex | SUSE CVE CVE-2025-43272 | known affected: 237 recommended: 564 | 2026-10-15T16:24:35+00:00 | Vulnerability · Source |
| CVE-2025-43342 | suse_vex | SUSE CVE CVE-2025-43342 | known affected: 237 recommended: 564 | 2026-10-15T16:24:33+00:00 | Vulnerability · Source |
| CVE-2025-43368 | suse_vex | SUSE CVE CVE-2025-43368 | known affected: 237 recommended: 564 | 2026-10-15T16:24:32+00:00 | Vulnerability · Source |
| CVE-2025-43392 | suse_vex | SUSE CVE CVE-2025-43392 | known affected: 221 recommended: 584 | 2026-10-15T16:24:30+00:00 | Vulnerability · Source |
| CVE-2025-43419 | suse_vex | SUSE CVE CVE-2025-43419 | known affected: 221 recommended: 584 | 2026-10-15T16:24:29+00:00 | Vulnerability · Source |
| CVE-2025-43425 | suse_vex | SUSE CVE CVE-2025-43425 | known affected: 221 recommended: 588 | 2026-10-15T16:24:27+00:00 | Vulnerability · Source |
| CVE-2025-43427 | suse_vex | SUSE CVE CVE-2025-43427 | known affected: 221 recommended: 588 | 2026-10-15T16:24:25+00:00 | Vulnerability · Source |
| CVE-2025-43431 | suse_vex | SUSE CVE CVE-2025-43431 | known affected: 237 recommended: 588 | 2026-10-15T16:24:23+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-15T16:24:21+00:00 | Vulnerability · Source |
| CVE-2025-43440 | suse_vex | SUSE CVE CVE-2025-43440 | known affected: 221 known not affected: 16 recommended: 588 | 2026-10-15T16:24:19+00:00 | Vulnerability · Source |
| CVE-2025-43480 | suse_vex | SUSE CVE CVE-2025-43480 | known affected: 72 known not affected: 165 recommended: 584 | 2026-10-15T16:24:16+00:00 | Vulnerability · Source |
| CVE-2025-43501 | suse_vex | SUSE CVE CVE-2025-43501 | known affected: 238 recommended: 580 | 2026-10-15T16:24:14+00:00 | Vulnerability · Source |
| CVE-2025-43535 | suse_vex | SUSE CVE CVE-2025-43535 | known affected: 238 recommended: 580 | 2026-10-15T16:24:11+00:00 | Vulnerability · Source |
| CVE-2025-43541 | suse_vex | SUSE CVE CVE-2025-43541 | known affected: 238 recommended: 580 | 2026-10-15T16:24:09+00:00 | Vulnerability · Source |
| CVE-2025-43964 | suse_vex | SUSE CVE CVE-2025-43964 | known affected: 34 recommended: 49 | 2026-10-15T16:24:06+00:00 | Vulnerability · Source |
| CVE-2025-43970 | suse_vex | SUSE CVE CVE-2025-43970 | recommended: 4 | 2026-10-15T16:24:04+00:00 | Vulnerability · Source |
| CVE-2025-43972 | suse_vex | SUSE CVE CVE-2025-43972 | recommended: 4 | 2026-10-15T16:24:03+00:00 | Vulnerability · Source |
| CVE-2025-43973 | suse_vex | SUSE CVE CVE-2025-43973 | recommended: 4 | 2026-10-15T16:24:01+00:00 | Vulnerability · Source |
| CVE-2025-44001 | suse_vex | SUSE CVE CVE-2025-44001 | recommended: 1 | 2026-10-15T16:24:00+00:00 | Vulnerability · Source |
| CVE-2025-44004 | suse_vex | SUSE CVE CVE-2025-44004 | recommended: 1 | 2026-10-15T16:23:58+00:00 | Vulnerability · Source |
| CVE-2025-44005 | suse_vex | SUSE CVE CVE-2025-44005 | No product status | 2026-10-15T16:23:57+00:00 | Vulnerability · Source |
| CVE-2025-45582 | suse_vex | SUSE CVE CVE-2025-45582 | known affected: 429 recommended: 141 | 2026-10-15T16:23:56+00:00 | Vulnerability · Source |
| CVE-2025-46327 | suse_vex | SUSE CVE CVE-2025-46327 | recommended: 8 | 2026-10-15T16:23:54+00:00 | Vulnerability · Source |
| CVE-2025-46334 | suse_vex | SUSE CVE CVE-2025-46334 | known not affected: 703 recommended: 53 | 2026-10-15T16:23:52+00:00 | Vulnerability · Source |
| CVE-2025-46342 | suse_vex | SUSE CVE CVE-2025-46342 | recommended: 4 | 2026-10-15T16:23:51+00:00 | Vulnerability · Source |
| CVE-2025-46394 | suse_vex | SUSE CVE CVE-2025-46394 | known affected: 41 recommended: 115 | 2026-10-15T16:23:49+00:00 | Vulnerability · Source |
| CVE-2025-46702 | suse_vex | SUSE CVE CVE-2025-46702 | recommended: 4 | 2026-10-15T16:23:47+00:00 | Vulnerability · Source |
| CVE-2025-46705 | suse_vex | SUSE CVE CVE-2025-46705 | known affected: 12 recommended: 54 | 2026-10-15T16:23:45+00:00 | Vulnerability · Source |
| CVE-2025-46728 | suse_vex | SUSE CVE CVE-2025-46728 | recommended: 11 | 2026-10-15T16:23:43+00:00 | Vulnerability · Source |
| CVE-2025-46735 | suse_vex | SUSE CVE CVE-2025-46735 | recommended: 4 | 2026-10-15T16:23:41+00:00 | Vulnerability · Source |
| CVE-2025-46802 | suse_vex | SUSE CVE CVE-2025-46802 | known affected: 439 recommended: 20 | 2026-10-15T16:23:39+00:00 | Vulnerability · Source |
| CVE-2025-46815 | suse_vex | SUSE CVE CVE-2025-46815 | recommended: 4 | 2026-10-15T16:23:37+00:00 | Vulnerability · Source |
| CVE-2025-46817 | suse_vex | SUSE CVE CVE-2025-46817 | known affected: 4 known not affected: 7 recommended: 80 | 2026-10-15T16:23:34+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-15T16:23:32+00:00 | Vulnerability · Source |
| CVE-2025-46835 | suse_vex | SUSE CVE CVE-2025-46835 | known affected: 214 recommended: 444 | 2026-10-15T16:23:30+00:00 | Vulnerability · Source |
| CVE-2025-46836 | suse_vex | SUSE CVE CVE-2025-46836 | known affected: 472 recommended: 83 | 2026-10-15T16:23:29+00:00 | Vulnerability · Source |
| CVE-2025-47151 | suse_vex | SUSE CVE CVE-2025-47151 | known affected: 12 recommended: 63 | 2026-10-15T16:23:27+00:00 | Vulnerability · Source |
| CVE-2025-47153 | suse_vex | SUSE CVE CVE-2025-47153 | known not affected: 484 | 2026-10-15T16:23:26+00:00 | Vulnerability · Source |
| CVE-2025-47282 | suse_vex | SUSE CVE CVE-2025-47282 | recommended: 4 | 2026-10-15T16:23:24+00:00 | Vulnerability · Source |
| CVE-2025-47287 | suse_vex | SUSE CVE CVE-2025-47287 | known affected: 430 known not affected: 22 recommended: 421 | 2026-10-15T16:23:22+00:00 | Vulnerability · Source |
| CVE-2025-47291 | suse_vex | SUSE CVE CVE-2025-47291 | known not affected: 387 recommended: 9 | 2026-10-15T16:23:20+00:00 | Vulnerability · Source |
| CVE-2025-47711 | suse_vex | SUSE CVE CVE-2025-47711 | known not affected: 3 recommended: 120 | 2026-10-15T16:23:19+00:00 | Vulnerability · Source |
| CVE-2025-47712 | suse_vex | SUSE CVE CVE-2025-47712 | known not affected: 3 recommended: 120 | 2026-10-15T16:23:17+00:00 | Vulnerability · Source |
| CVE-2025-47871 | suse_vex | SUSE CVE CVE-2025-47871 | recommended: 4 | 2026-10-15T16:23:15+00:00 | Vulnerability · Source |