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-9943 | suse_vex | SUSE CVE CVE-2025-9943 | known affected: 128 recommended: 102 | 2026-10-16T01:05:57+00:00 | Vulnerability · Source |
| CVE-2025-10148 | suse_vex | SUSE CVE CVE-2025-10148 | known affected: 366 known not affected: 75 recommended: 231 | 2026-10-16T01:05:55+00:00 | Vulnerability · Source |
| CVE-2025-10158 | suse_vex | SUSE CVE CVE-2025-10158 | known affected: 425 recommended: 44 | 2026-10-16T01:05:54+00:00 | Vulnerability · Source |
| CVE-2025-10527 | suse_vex | SUSE CVE CVE-2025-10527 | known affected: 73 recommended: 186 | 2026-10-16T01:05:49+00:00 | Vulnerability · Source |
| CVE-2025-10528 | suse_vex | SUSE CVE CVE-2025-10528 | known affected: 73 recommended: 186 | 2026-10-16T01:05:47+00:00 | Vulnerability · Source |
| CVE-2025-10532 | suse_vex | SUSE CVE CVE-2025-10532 | known affected: 73 recommended: 186 | 2026-10-16T01:05:46+00:00 | Vulnerability · Source |
| CVE-2025-10533 | suse_vex | SUSE CVE CVE-2025-10533 | known affected: 73 recommended: 186 | 2026-10-16T01:05:44+00:00 | Vulnerability · Source |
| CVE-2025-10536 | suse_vex | SUSE CVE CVE-2025-10536 | known affected: 73 recommended: 186 | 2026-10-16T01:05:42+00:00 | Vulnerability · Source |
| CVE-2025-10630 | suse_vex | SUSE CVE CVE-2025-10630 | recommended: 3 | 2026-10-16T01:05:40+00:00 | Vulnerability · Source |
| CVE-2025-10911 | suse_vex | SUSE CVE CVE-2025-10911 | known affected: 423 recommended: 258 | 2026-10-16T01:05:38+00:00 | Vulnerability · Source |
| CVE-2025-10966 | suse_vex | SUSE CVE CVE-2025-10966 | known affected: 0 known not affected: 236 recommended: 23 | 2026-10-16T01:05:36+00:00 | Vulnerability · Source |
| CVE-2025-11021 | suse_vex | SUSE CVE CVE-2025-11021 | known affected: 0 known not affected: 326 recommended: 121 | 2026-10-16T01:05:34+00:00 | Vulnerability · Source |
| CVE-2025-11065 | suse_vex | SUSE CVE CVE-2025-11065 | known affected: 676 known not affected: 479 recommended: 98 | 2026-10-16T01:05:32+00:00 | Vulnerability · Source |
| CVE-2025-11082 | suse_vex | SUSE CVE CVE-2025-11082 | known affected: 0 known not affected: 259 recommended: 10 | 2026-10-16T01:05:30+00:00 | Vulnerability · Source |
| CVE-2025-11083 | suse_vex | SUSE CVE CVE-2025-11083 | known affected: 470 known not affected: 46 recommended: 532 | 2026-10-16T01:05:28+00:00 | Vulnerability · Source |
| CVE-2025-11187 | suse_vex | SUSE CVE CVE-2025-11187 | known affected: 402 known not affected: 688 recommended: 69 | 2026-10-16T01:05:26+00:00 | Vulnerability · Source |
| CVE-2025-11234 | suse_vex | SUSE CVE CVE-2025-11234 | known affected: 1132 known not affected: 109 recommended: 1240 | 2026-10-16T01:05:24+00:00 | Vulnerability · Source |
| CVE-2025-11277 | suse_vex | SUSE CVE CVE-2025-11277 | known affected: 3 recommended: 17 | 2026-10-16T01:05:22+00:00 | Vulnerability · Source |
| CVE-2025-11375 | suse_vex | SUSE CVE CVE-2025-11375 | recommended: 3 | 2026-10-16T01:05:20+00:00 | Vulnerability · Source |
| CVE-2025-11393 | suse_vex | SUSE CVE CVE-2025-11393 | recommended: 2 | 2026-10-16T01:05:19+00:00 | Vulnerability · Source |
| CVE-2025-11395 | suse_vex | SUSE CVE CVE-2025-11395 | known affected: 168 recommended: 8 | 2026-10-16T01:05:17+00:00 | Vulnerability · Source |
| CVE-2025-11412 | suse_vex | SUSE CVE CVE-2025-11412 | known affected: 471 known not affected: 45 recommended: 495 | 2026-10-16T01:05:15+00:00 | Vulnerability · Source |
| CVE-2025-11413 | suse_vex | SUSE CVE CVE-2025-11413 | known affected: 471 known not affected: 45 recommended: 495 | 2026-10-16T01:05:13+00:00 | Vulnerability · Source |
| CVE-2025-11414 | suse_vex | SUSE CVE CVE-2025-11414 | known affected: 471 known not affected: 45 recommended: 495 | 2026-10-16T01:05:11+00:00 | Vulnerability · Source |
| CVE-2025-11494 | suse_vex | SUSE CVE CVE-2025-11494 | known affected: 470 known not affected: 1 recommended: 495 | 2026-10-16T01:05:09+00:00 | Vulnerability · Source |
| CVE-2025-11495 | suse_vex | SUSE CVE CVE-2025-11495 | known affected: 470 known not affected: 1 recommended: 495 | 2026-10-16T01:05:07+00:00 | Vulnerability · Source |
| CVE-2025-11561 | suse_vex | SUSE CVE CVE-2025-11561 | known affected: 412 recommended: 1050 | 2026-10-16T01:05:05+00:00 | Vulnerability · Source |
| CVE-2025-11563 | suse_vex | SUSE CVE CVE-2025-11563 | known affected: 459 known not affected: 79 recommended: 136 | 2026-10-16T01:05:03+00:00 | Vulnerability · Source |
| CVE-2025-11579 | suse_vex | SUSE CVE CVE-2025-11579 | known affected: 2 recommended: 9 | 2026-10-16T01:05:01+00:00 | Vulnerability · Source |
| CVE-2025-11621 | suse_vex | SUSE CVE CVE-2025-11621 | recommended: 3 | 2026-10-16T01:04:58+00:00 | Vulnerability · Source |
| CVE-2025-11687 | suse_vex | SUSE CVE CVE-2025-11687 | known affected: 3 recommended: 7 | 2026-10-16T01:04:56+00:00 | Vulnerability · Source |
| CVE-2025-11708 | suse_vex | SUSE CVE CVE-2025-11708 | known affected: 73 recommended: 184 | 2026-10-16T01:04:54+00:00 | Vulnerability · Source |
| CVE-2025-11710 | suse_vex | SUSE CVE CVE-2025-11710 | known affected: 73 recommended: 184 | 2026-10-16T01:04:52+00:00 | Vulnerability · Source |
| CVE-2025-11711 | suse_vex | SUSE CVE CVE-2025-11711 | known affected: 73 recommended: 184 | 2026-10-16T01:04:51+00:00 | Vulnerability · Source |
| CVE-2025-11712 | suse_vex | SUSE CVE CVE-2025-11712 | known affected: 73 recommended: 184 | 2026-10-16T01:04:48+00:00 | Vulnerability · Source |
| CVE-2025-11714 | suse_vex | SUSE CVE CVE-2025-11714 | known affected: 73 recommended: 184 | 2026-10-16T01:04:46+00:00 | Vulnerability · Source |
| CVE-2025-11731 | suse_vex | SUSE CVE CVE-2025-11731 | known affected: 475 recommended: 141 | 2026-10-16T01:04:43+00:00 | Vulnerability · Source |
| CVE-2025-11776 | suse_vex | SUSE CVE CVE-2025-11776 | recommended: 2 | 2026-10-16T01:04:42+00:00 | Vulnerability · Source |
| CVE-2025-11777 | suse_vex | SUSE CVE CVE-2025-11777 | recommended: 2 | 2026-10-16T01:04:40+00:00 | Vulnerability · Source |
| CVE-2025-11839 | suse_vex | SUSE CVE CVE-2025-11839 | known affected: 0 known not affected: 290 recommended: 7 | 2026-10-16T01:04:38+00:00 | Vulnerability · Source |
| CVE-2025-11840 | suse_vex | SUSE CVE CVE-2025-11840 | known affected: 0 known not affected: 290 recommended: 7 | 2026-10-16T01:04:36+00:00 | Vulnerability · Source |
| CVE-2025-11896 | suse_vex | SUSE CVE CVE-2025-11896 | known affected: 324 recommended: 163 | 2026-10-16T01:04:34+00:00 | Vulnerability · Source |
| CVE-2025-11961 | suse_vex | SUSE CVE CVE-2025-11961 | known affected: 494 recommended: 83 | 2026-10-16T01:04:31+00:00 | Vulnerability · Source |
| CVE-2025-12044 | suse_vex | SUSE CVE CVE-2025-12044 | recommended: 3 | 2026-10-16T01:04:29+00:00 | Vulnerability · Source |
| CVE-2025-12084 | suse_vex | SUSE CVE CVE-2025-12084 | known affected: 793 recommended: 794 | 2026-10-16T01:04:27+00:00 | Vulnerability · Source |
| CVE-2025-12419 | suse_vex | SUSE CVE CVE-2025-12419 | recommended: 2 | 2026-10-16T01:04:25+00:00 | Vulnerability · Source |
| CVE-2025-12464 | suse_vex | SUSE CVE CVE-2025-12464 | known affected: 569 known not affected: 688 recommended: 1139 | 2026-10-16T01:04:23+00:00 | Vulnerability · Source |
| CVE-2025-12756 | suse_vex | SUSE CVE CVE-2025-12756 | recommended: 2 | 2026-10-16T01:04:21+00:00 | Vulnerability · Source |
| CVE-2025-12816 | suse_vex | SUSE CVE CVE-2025-12816 | known affected: 176 known not affected: 424 recommended: 114 | 2026-10-16T01:04:19+00:00 | Vulnerability · Source |
| CVE-2025-12817 | suse_vex | SUSE CVE CVE-2025-12817 | known affected: 553 known not affected: 684 recommended: 1917 | 2026-10-16T01:04:17+00:00 | Vulnerability · Source |