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-46803 | suse_vex | SUSE CVE CVE-2025-46803 | known not affected: 60 | 2026-07-23T01:33:15+00:00 | Vulnerability · Source |
| CVE-2025-46804 | suse_vex | SUSE CVE CVE-2025-46804 | known not affected: 60 | 2026-07-23T01:33:13+00:00 | Vulnerability · Source |
| CVE-2025-46805 | suse_vex | SUSE CVE CVE-2025-46805 | known not affected: 60 | 2026-07-23T01:33:12+00:00 | Vulnerability · Source |
| CVE-2025-47151 | suse_vex | SUSE CVE CVE-2025-47151 | known affected: 12 recommended: 60 | 2026-07-23T01:33:11+00:00 | Vulnerability · Source |
| CVE-2025-47268 | suse_vex | SUSE CVE CVE-2025-47268 | known affected: 382 recommended: 100 | 2026-07-23T01:33:09+00:00 | Vulnerability · Source |
| CVE-2025-47947 | suse_vex | SUSE CVE CVE-2025-47947 | known affected: 21 recommended: 36 | 2026-07-23T01:33:07+00:00 | Vulnerability · Source |
| CVE-2025-48074 | suse_vex | SUSE CVE CVE-2025-48074 | known not affected: 186 recommended: 30 | 2026-07-23T01:33:06+00:00 | Vulnerability · Source |
| CVE-2025-48796 | suse_vex | SUSE CVE CVE-2025-48796 | known not affected: 63 | 2026-07-23T01:33:04+00:00 | Vulnerability · Source |
| CVE-2025-49641 | suse_vex | SUSE CVE CVE-2025-49641 | known not affected: 11 | 2026-07-23T01:33:02+00:00 | Vulnerability · Source |
| CVE-2025-49643 | suse_vex | SUSE CVE CVE-2025-49643 | known not affected: 19 | 2026-07-23T01:33:01+00:00 | Vulnerability · Source |
| CVE-2025-50817 | suse_vex | SUSE CVE CVE-2025-50817 | known affected: 46 recommended: 65 | 2026-07-23T01:32:57+00:00 | Vulnerability · Source |
| CVE-2025-50952 | suse_vex | SUSE CVE CVE-2025-50952 | known affected: 659 known not affected: 127 recommended: 1 | 2026-07-23T01:32:55+00:00 | Vulnerability · Source |
| CVE-2025-52099 | suse_vex | SUSE CVE CVE-2025-52099 | known not affected: 290 | 2026-07-23T01:32:54+00:00 | Vulnerability · Source |
| CVE-2025-52885 | suse_vex | SUSE CVE CVE-2025-52885 | known affected: 32 known not affected: 132 recommended: 213 | 2026-07-23T01:32:52+00:00 | Vulnerability · Source |
| CVE-2025-54080 | suse_vex | SUSE CVE CVE-2025-54080 | known affected: 180 known not affected: 1 recommended: 21 | 2026-07-23T01:32:45+00:00 | Vulnerability · Source |
| CVE-2025-54090 | suse_vex | SUSE CVE CVE-2025-54090 | known not affected: 307 recommended: 1 | 2026-07-23T01:32:44+00:00 | Vulnerability · Source |
| CVE-2025-54567 | suse_vex | SUSE CVE CVE-2025-54567 | known not affected: 1832 recommended: 120 | 2026-07-23T01:32:41+00:00 | Vulnerability · Source |
| CVE-2025-54874 | suse_vex | SUSE CVE CVE-2025-54874 | known affected: 394 known not affected: 659 recommended: 23 | 2026-07-23T01:32:39+00:00 | Vulnerability · Source |
| CVE-2025-55154 | suse_vex | SUSE CVE CVE-2025-55154 | known affected: 75 known not affected: 11 recommended: 316 | 2026-07-23T01:32:35+00:00 | Vulnerability · Source |
| CVE-2025-55157 | suse_vex | SUSE CVE CVE-2025-55157 | known affected: 344 known not affected: 222 recommended: 126 | 2026-07-23T01:32:34+00:00 | Vulnerability · Source |
| CVE-2025-55212 | suse_vex | SUSE CVE CVE-2025-55212 | known affected: 75 known not affected: 24 recommended: 362 | 2026-07-23T01:32:32+00:00 | Vulnerability · Source |
| CVE-2025-55304 | suse_vex | SUSE CVE CVE-2025-55304 | known affected: 139 known not affected: 33 recommended: 23 | 2026-07-23T01:32:30+00:00 | Vulnerability · Source |
| CVE-2025-55668 | suse_vex | SUSE CVE CVE-2025-55668 | known affected: 31 known not affected: 415 | 2026-07-23T01:32:28+00:00 | Vulnerability · Source |
| CVE-2025-58050 | suse_vex | SUSE CVE CVE-2025-58050 | known not affected: 7058 recommended: 45 | 2026-07-23T01:32:26+00:00 | Vulnerability · Source |
| CVE-2025-58149 | suse_vex | SUSE CVE CVE-2025-58149 | known affected: 616 recommended: 126 | 2026-07-23T01:32:24+00:00 | Vulnerability · Source |
| CVE-2025-58151 | suse_vex | SUSE CVE CVE-2025-58151 | known not affected: 261 | 2026-07-23T01:32:22+00:00 | Vulnerability · Source |
| CVE-2025-59464 | suse_vex | SUSE CVE CVE-2025-59464 | known not affected: 322 recommended: 41 | 2026-07-23T01:32:19+00:00 | Vulnerability · Source |
| CVE-2025-59777 | suse_vex | SUSE CVE CVE-2025-59777 | known not affected: 132 recommended: 29 | 2026-07-23T01:32:16+00:00 | Vulnerability · Source |
| CVE-2025-61100 | suse_vex | SUSE CVE CVE-2025-61100 | known affected: 267 known not affected: 335 recommended: 111 | 2026-07-23T01:32:14+00:00 | Vulnerability · Source |
| CVE-2025-61101 | suse_vex | SUSE CVE CVE-2025-61101 | known affected: 267 known not affected: 335 recommended: 101 | 2026-07-23T01:32:13+00:00 | Vulnerability · Source |
| CVE-2025-61144 | suse_vex | SUSE CVE CVE-2025-61144 | known affected: 540 known not affected: 43 recommended: 25 | 2026-07-23T01:32:10+00:00 | Vulnerability · Source |
| CVE-2025-61962 | suse_vex | SUSE CVE CVE-2025-61962 | known affected: 55 recommended: 34 | 2026-07-23T01:32:05+00:00 | Vulnerability · Source |
| CVE-2025-61971 | suse_vex | SUSE CVE CVE-2025-61971 | known affected: 411 | 2026-07-23T01:32:03+00:00 | Vulnerability · Source |
| CVE-2025-62171 | suse_vex | SUSE CVE CVE-2025-62171 | known affected: 322 known not affected: 24 recommended: 217 | 2026-07-23T01:32:01+00:00 | Vulnerability · Source |
| CVE-2025-62291 | suse_vex | SUSE CVE CVE-2025-62291 | known not affected: 106 recommended: 198 | 2026-07-23T01:31:57+00:00 | Vulnerability · Source |
| CVE-2025-64118 | suse_vex | SUSE CVE CVE-2025-64118 | known not affected: 293 | 2026-07-23T01:31:55+00:00 | Vulnerability · Source |
| CVE-2025-64524 | suse_vex | SUSE CVE CVE-2025-64524 | known affected: 111 recommended: 32 | 2026-07-23T01:31:52+00:00 | Vulnerability · Source |
| CVE-2025-64718 | suse_vex | SUSE CVE CVE-2025-64718 | known affected: 530 known not affected: 483 recommended: 11 | 2026-07-23T01:31:50+00:00 | Vulnerability · Source |
| CVE-2025-65955 | suse_vex | SUSE CVE CVE-2025-65955 | known affected: 161 known not affected: 101 recommended: 294 | 2026-07-23T01:31:48+00:00 | Vulnerability · Source |
| CVE-2025-66037 | suse_vex | SUSE CVE CVE-2025-66037 | known affected: 406 known not affected: 14 recommended: 33 | 2026-07-23T01:31:46+00:00 | Vulnerability · Source |
| CVE-2025-66038 | suse_vex | SUSE CVE CVE-2025-66038 | known affected: 406 known not affected: 14 recommended: 33 | 2026-07-23T01:31:45+00:00 | Vulnerability · Source |
| CVE-2025-66200 | suse_vex | SUSE CVE CVE-2025-66200 | known affected: 554 known not affected: 1 recommended: 214 | 2026-07-23T01:31:43+00:00 | Vulnerability · Source |
| CVE-2025-66382 | suse_vex | SUSE CVE CVE-2025-66382 | known affected: 258 known not affected: 433 recommended: 2 | 2026-07-23T01:31:41+00:00 | Vulnerability · Source |
| CVE-2025-66861 | suse_vex | SUSE CVE CVE-2025-66861 | known affected: 1 known not affected: 270 | 2026-07-23T01:31:40+00:00 | Vulnerability · Source |
| CVE-2025-66862 | suse_vex | SUSE CVE CVE-2025-66862 | known affected: 1 known not affected: 270 | 2026-07-23T01:31:38+00:00 | Vulnerability · Source |
| CVE-2025-66865 | suse_vex | SUSE CVE CVE-2025-66865 | known affected: 21 known not affected: 250 | 2026-07-23T01:31:36+00:00 | Vulnerability · Source |
| CVE-2025-67499 | suse_vex | SUSE CVE CVE-2025-67499 | known not affected: 155 recommended: 12 | 2026-07-23T01:31:35+00:00 | Vulnerability · Source |
| CVE-2025-68161 | suse_vex | SUSE CVE CVE-2025-68161 | known affected: 490 known not affected: 31 recommended: 35 | 2026-07-23T01:31:33+00:00 | Vulnerability · Source |
| CVE-2025-68171 | suse_vex | SUSE CVE CVE-2025-68171 | first fixed: 2 known affected: 610 known not affected: 260 recommended: 289 | 2026-07-23T01:31:31+00:00 | Vulnerability · Source |
| CVE-2025-68175 | suse_vex | SUSE CVE CVE-2025-68175 | known affected: 169 known not affected: 388 | 2026-07-23T01:31:29+00:00 | Vulnerability · Source |