VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292444 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-71143 | suse_vex | SUSE CVE CVE-2025-71143 | first fixed: 2 known affected: 394 known not affected: 376 recommended: 265 | 2026-07-23T01:28:13+00:00 | Vulnerability · Source |
| CVE-2025-71146 | suse_vex | SUSE CVE CVE-2025-71146 | known not affected: 437 | 2026-07-23T01:28:11+00:00 | Vulnerability · Source |
| CVE-2025-71148 | suse_vex | SUSE CVE CVE-2025-71148 | first fixed: 2 known affected: 449 known not affected: 312 recommended: 280 | 2026-07-23T01:28:09+00:00 | Vulnerability · Source |
| CVE-2025-71150 | suse_vex | SUSE CVE CVE-2025-71150 | known not affected: 437 | 2026-07-23T01:28:08+00:00 | Vulnerability · Source |
| CVE-2025-71154 | suse_vex | SUSE CVE CVE-2025-71154 | first fixed: 2 known affected: 689 known not affected: 9 recommended: 289 | 2026-07-23T01:28:06+00:00 | Vulnerability · Source |
| CVE-2025-71155 | suse_vex | SUSE CVE CVE-2025-71155 | known not affected: 259 | 2026-07-23T01:28:04+00:00 | Vulnerability · Source |
| CVE-2025-71158 | suse_vex | SUSE CVE CVE-2025-71158 | known not affected: 441 | 2026-07-23T01:28:02+00:00 | Vulnerability · Source |
| CVE-2025-71180 | suse_vex | SUSE CVE CVE-2025-71180 | known affected: 237 known not affected: 208 | 2026-07-23T01:28:01+00:00 | Vulnerability · Source |
| CVE-2025-71183 | suse_vex | SUSE CVE CVE-2025-71183 | first fixed: 2 known affected: 612 known not affected: 108 recommended: 317 | 2026-07-23T01:27:59+00:00 | Vulnerability · Source |
| CVE-2025-71184 | suse_vex | SUSE CVE CVE-2025-71184 | first fixed: 2 known affected: 622 recommended: 325 | 2026-07-23T01:27:57+00:00 | Vulnerability · Source |
| CVE-2025-71189 | suse_vex | SUSE CVE CVE-2025-71189 | first fixed: 2 known affected: 394 known not affected: 367 recommended: 280 | 2026-07-23T01:27:56+00:00 | Vulnerability · Source |
| CVE-2025-71194 | suse_vex | SUSE CVE CVE-2025-71194 | first fixed: 2 known affected: 691 known not affected: 4 recommended: 317 | 2026-07-23T01:27:54+00:00 | Vulnerability · Source |
| CVE-2025-71198 | suse_vex | SUSE CVE CVE-2025-71198 | first fixed: 2 known affected: 394 known not affected: 367 recommended: 280 | 2026-07-23T01:27:53+00:00 | Vulnerability · Source |
| CVE-2025-71202 | suse_vex | SUSE CVE CVE-2025-71202 | known affected: 275 known not affected: 153 | 2026-07-23T01:27:51+00:00 | Vulnerability · Source |
| CVE-2025-71220 | suse_vex | SUSE CVE CVE-2025-71220 | known not affected: 437 | 2026-07-23T01:27:49+00:00 | Vulnerability · Source |
| CVE-2025-71221 | suse_vex | SUSE CVE CVE-2025-71221 | known affected: 4 known not affected: 437 | 2026-07-23T01:27:48+00:00 | Vulnerability · Source |
| CVE-2025-71222 | suse_vex | SUSE CVE CVE-2025-71222 | first fixed: 2 known affected: 451 known not affected: 9 recommended: 295 | 2026-07-23T01:27:46+00:00 | Vulnerability · Source |
| CVE-2025-71225 | suse_vex | SUSE CVE CVE-2025-71225 | first fixed: 2 known affected: 614 known not affected: 4 recommended: 295 | 2026-07-23T01:27:44+00:00 | Vulnerability · Source |
| CVE-2025-71267 | suse_vex | SUSE CVE CVE-2025-71267 | known not affected: 437 | 2026-07-23T01:27:40+00:00 | Vulnerability · Source |
| CVE-2025-71269 | suse_vex | SUSE CVE CVE-2025-71269 | first fixed: 2 known affected: 692 known not affected: 24 recommended: 317 | 2026-07-23T01:27:39+00:00 | Vulnerability · Source |
| CVE-2025-71270 | suse_vex | SUSE CVE CVE-2025-71270 | known not affected: 441 | 2026-07-23T01:27:37+00:00 | Vulnerability · Source |
| CVE-2025-71272 | suse_vex | SUSE CVE CVE-2025-71272 | known not affected: 385 | 2026-07-23T01:27:35+00:00 | Vulnerability · Source |
| CVE-2025-71285 | suse_vex | SUSE CVE CVE-2025-71285 | known affected: 162 known not affected: 131 | 2026-07-23T01:27:34+00:00 | Vulnerability · Source |
| CVE-2025-71295 | suse_vex | SUSE CVE CVE-2025-71295 | known affected: 17 known not affected: 370 | 2026-07-23T01:27:30+00:00 | Vulnerability · Source |
| CVE-2025-71308 | suse_vex | SUSE CVE CVE-2025-71308 | known not affected: 385 recommended: 27 | 2026-07-23T01:27:27+00:00 | Vulnerability · Source |
| CVE-2025-71313 | suse_vex | SUSE CVE CVE-2025-71313 | known affected: 212 known not affected: 175 | 2026-07-23T01:27:25+00:00 | Vulnerability · Source |
| CVE-2026-0988 | suse_vex | SUSE CVE CVE-2026-0988 | known affected: 553 recommended: 407 | 2026-07-23T01:27:14+00:00 | Vulnerability · Source |
| CVE-2026-1484 | suse_vex | SUSE CVE CVE-2026-1484 | known affected: 484 recommended: 286 | 2026-07-23T01:27:11+00:00 | Vulnerability · Source |
| CVE-2026-1485 | suse_vex | SUSE CVE CVE-2026-1485 | known affected: 484 recommended: 286 | 2026-07-23T01:27:09+00:00 | Vulnerability · Source |
| CVE-2026-1489 | suse_vex | SUSE CVE CVE-2026-1489 | known affected: 484 recommended: 286 | 2026-07-23T01:27:08+00:00 | Vulnerability · Source |
| CVE-2026-3441 | suse_vex | SUSE CVE CVE-2026-3441 | known affected: 169 | 2026-07-23T01:27:01+00:00 | Vulnerability · Source |
| CVE-2026-3442 | suse_vex | SUSE CVE CVE-2026-3442 | known affected: 169 | 2026-07-23T01:26:59+00:00 | Vulnerability · Source |
| CVE-2026-3805 | suse_vex | SUSE CVE CVE-2026-3805 | first fixed: 13 known affected: 382 known not affected: 31 recommended: 173 | 2026-07-23T01:26:50+00:00 | Vulnerability · Source |
| CVE-2026-3904 | suse_vex | SUSE CVE CVE-2026-3904 | known not affected: 423 | 2026-07-23T01:26:47+00:00 | Vulnerability · Source |
| CVE-2026-4647 | suse_vex | SUSE CVE CVE-2026-4647 | known affected: 169 | 2026-07-23T01:26:37+00:00 | Vulnerability · Source |
| CVE-2026-5222 | suse_vex | SUSE CVE CVE-2026-5222 | known affected: 80 | 2026-07-23T01:26:29+00:00 | Vulnerability · Source |
| CVE-2026-5223 | suse_vex | SUSE CVE CVE-2026-5223 | known affected: 80 | 2026-07-23T01:26:28+00:00 | Vulnerability · Source |
| CVE-2026-6722 | suse_vex | SUSE CVE CVE-2026-6722 | known affected: 706 recommended: 1630 | 2026-07-23T01:26:13+00:00 | Vulnerability · Source |
| CVE-2026-6846 | suse_vex | SUSE CVE CVE-2026-6846 | known affected: 206 | 2026-07-23T01:26:11+00:00 | Vulnerability · Source |
| CVE-2026-8091 | suse_vex | SUSE CVE CVE-2026-8091 | known affected: 39 recommended: 90 | 2026-07-23T01:26:08+00:00 | Vulnerability · Source |
| CVE-2026-8368 | suse_vex | SUSE CVE CVE-2026-8368 | known affected: 427 recommended: 13 | 2026-07-23T01:26:04+00:00 | Vulnerability · Source |
| CVE-2026-8829 | suse_vex | SUSE CVE CVE-2026-8829 | known affected: 430 recommended: 13 | 2026-07-23T01:25:59+00:00 | Vulnerability · Source |
| CVE-2026-9277 | suse_vex | SUSE CVE CVE-2026-9277 | known affected: 356 known not affected: 147 recommended: 6 | 2026-07-23T01:25:49+00:00 | Vulnerability · Source |
| CVE-2026-11850 | suse_vex | SUSE CVE CVE-2026-11850 | known affected: 526 recommended: 220 | 2026-07-23T01:25:38+00:00 | Vulnerability · Source |
| CVE-2026-15899 | suse_vex | SUSE CVE CVE-2026-15899 | recommended: 6 | 2026-07-23T01:25:11+00:00 | Vulnerability · Source |
| CVE-2026-15900 | suse_vex | SUSE CVE CVE-2026-15900 | recommended: 6 | 2026-07-23T01:25:08+00:00 | Vulnerability · Source |
| CVE-2026-15901 | suse_vex | SUSE CVE CVE-2026-15901 | recommended: 6 | 2026-07-23T01:25:06+00:00 | Vulnerability · Source |
| CVE-2026-15902 | suse_vex | SUSE CVE CVE-2026-15902 | recommended: 6 | 2026-07-23T01:25:04+00:00 | Vulnerability · Source |
| CVE-2026-15903 | suse_vex | SUSE CVE CVE-2026-15903 | recommended: 6 | 2026-07-23T01:25:01+00:00 | Vulnerability · Source |
| CVE-2026-15904 | suse_vex | SUSE CVE CVE-2026-15904 | recommended: 6 | 2026-07-23T01:24:59+00:00 | Vulnerability · Source |