VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283109 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-10649 | suse_vex | SUSE CVE CVE-2026-10649 | known affected: 419 recommended: 99 | 2026-07-21T13:17:36+00:00 | Vulnerability · Source |
| CVE-2026-11332 | suse_vex | SUSE CVE CVE-2026-11332 | known affected: 12 recommended: 16 | 2026-07-21T13:17:34+00:00 | Vulnerability · Source |
| CVE-2026-12080 | suse_vex | SUSE CVE CVE-2026-12080 | known affected: 867 known not affected: 212 | 2026-07-21T13:17:32+00:00 | Vulnerability · Source |
| CVE-2026-12478 | suse_vex | SUSE CVE CVE-2026-12478 | known affected: 227 | 2026-07-21T13:17:30+00:00 | Vulnerability · Source |
| CVE-2026-14474 | suse_vex | SUSE CVE CVE-2026-14474 | first fixed: 354 known affected: 481 recommended: 258 | 2026-07-21T13:17:27+00:00 | Vulnerability · Source |
| CVE-2026-14476 | suse_vex | SUSE CVE CVE-2026-14476 | first fixed: 354 known affected: 481 recommended: 258 | 2026-07-21T13:17:25+00:00 | Vulnerability · Source |
| CVE-2026-14741 | suse_vex | SUSE CVE CVE-2026-14741 | known affected: 29 | 2026-07-21T13:17:24+00:00 | Vulnerability · Source |
| CVE-2026-15043 | suse_vex | SUSE CVE CVE-2026-15043 | first fixed: 7 known affected: 31 | 2026-07-21T13:17:22+00:00 | Vulnerability · Source |
| CVE-2026-15146 | suse_vex | SUSE CVE CVE-2026-15146 | known affected: 36 | 2026-07-21T13:17:21+00:00 | Vulnerability · Source |
| CVE-2026-15392 | suse_vex | SUSE CVE CVE-2026-15392 | known affected: 31 | 2026-07-21T13:17:20+00:00 | Vulnerability · Source |
| CVE-2026-15809 | suse_vex | SUSE CVE CVE-2026-15809 | No product status | 2026-07-21T13:17:18+00:00 | Vulnerability · Source |
| CVE-2026-15811 | suse_vex | SUSE CVE CVE-2026-15811 | known affected: 49 | 2026-07-21T13:17:17+00:00 | Vulnerability · Source |
| CVE-2026-15812 | suse_vex | SUSE CVE CVE-2026-15812 | known affected: 49 | 2026-07-21T13:17:15+00:00 | Vulnerability · Source |
| CVE-2026-15813 | suse_vex | SUSE CVE CVE-2026-15813 | known affected: 49 | 2026-07-21T13:17:14+00:00 | Vulnerability · Source |
| CVE-2026-16207 | suse_vex | SUSE CVE CVE-2026-16207 | No product status | 2026-07-21T13:17:02+00:00 | Vulnerability · Source |
| CVE-2026-16208 | suse_vex | SUSE CVE CVE-2026-16208 | No product status | 2026-07-21T13:17:00+00:00 | Vulnerability · Source |
| CVE-2026-16221 | suse_vex | SUSE CVE CVE-2026-16221 | known affected: 75 known not affected: 41 | 2026-07-21T13:16:59+00:00 | Vulnerability · Source |
| CVE-2026-16277 | suse_vex | SUSE CVE CVE-2026-16277 | known affected: 36 | 2026-07-21T13:16:57+00:00 | Vulnerability · Source |
| CVE-2026-21441 | suse_vex | SUSE CVE CVE-2026-21441 | known affected: 449 recommended: 208 | 2026-07-21T13:16:55+00:00 | Vulnerability · Source |
| CVE-2026-21729 | suse_vex | SUSE CVE CVE-2026-21729 | No product status | 2026-07-21T13:16:53+00:00 | Vulnerability · Source |
| CVE-2025-61140 | redhat_vex | jsonpath: jsonpath: Prototype Pollution vulnerability in the value function | fixed: 12 known affected: 9 known not affected: 211 | 2026-07-21T13:16:47+00:00 | Vulnerability · Source |
| CVE-2026-23231 | suse_vex | SUSE CVE CVE-2026-23231 | first fixed: 2 known affected: 416 known not affected: 202 recommended: 448 | 2026-07-21T13:16:43+00:00 | Vulnerability · Source |
| CVE-2026-23393 | suse_vex | SUSE CVE CVE-2026-23393 | first fixed: 21 known affected: 420 known not affected: 110 recommended: 557 | 2026-07-21T13:16:29+00:00 | Vulnerability · Source |
| CVE-2026-23490 | suse_vex | SUSE CVE CVE-2026-23490 | known affected: 394 recommended: 253 | 2026-07-21T13:16:21+00:00 | Vulnerability · Source |
| CVE-2026-24049 | suse_vex | SUSE CVE CVE-2026-24049 | known affected: 394 known not affected: 283 recommended: 40 | 2026-07-21T13:16:19+00:00 | Vulnerability · Source |
| CVE-2026-25541 | suse_vex | SUSE CVE CVE-2026-25541 | known affected: 11 recommended: 11 | 2026-07-21T13:16:17+00:00 | Vulnerability · Source |
| CVE-2026-25680 | suse_vex | SUSE CVE CVE-2026-25680 | known affected: 372 known not affected: 351 recommended: 278 | 2026-07-21T13:16:15+00:00 | Vulnerability · Source |
| CVE-2026-25681 | suse_vex | SUSE CVE CVE-2026-25681 | known affected: 372 known not affected: 351 recommended: 271 | 2026-07-21T13:16:13+00:00 | Vulnerability · Source |
| CVE-2026-25990 | suse_vex | SUSE CVE CVE-2026-25990 | known not affected: 54 recommended: 12 | 2026-07-21T13:16:12+00:00 | Vulnerability · Source |
| CVE-2026-26032 | suse_vex | SUSE CVE CVE-2026-26032 | first fixed: 12 known affected: 25 | 2026-07-21T13:16:10+00:00 | Vulnerability · Source |
| CVE-2026-26080 | suse_vex | SUSE CVE CVE-2026-26080 | known not affected: 11 recommended: 4 | 2026-07-21T13:16:03+00:00 | Vulnerability · Source |
| CVE-2026-26081 | suse_vex | SUSE CVE CVE-2026-26081 | known not affected: 11 recommended: 5 | 2026-07-21T13:16:01+00:00 | Vulnerability · Source |
| CVE-2026-26197 | suse_vex | SUSE CVE CVE-2026-26197 | known not affected: 707 | 2026-07-21T13:15:59+00:00 | Vulnerability · Source |
| CVE-2026-26199 | suse_vex | SUSE CVE CVE-2026-26199 | known affected: 707 | 2026-07-21T13:15:58+00:00 | Vulnerability · Source |
| CVE-2026-26961 | suse_vex | SUSE CVE CVE-2026-26961 | known affected: 29 known not affected: 6 recommended: 57 | 2026-07-21T13:15:56+00:00 | Vulnerability · Source |
| CVE-2026-27136 | suse_vex | SUSE CVE CVE-2026-27136 | known affected: 372 known not affected: 351 recommended: 277 | 2026-07-21T13:15:53+00:00 | Vulnerability · Source |
| CVE-2026-27459 | suse_vex | SUSE CVE CVE-2026-27459 | known affected: 410 known not affected: 52 recommended: 42 | 2026-07-21T13:15:50+00:00 | Vulnerability · Source |
| CVE-2026-29146 | suse_vex | SUSE CVE CVE-2026-29146 | known affected: 82 known not affected: 1 recommended: 406 | 2026-07-21T13:15:46+00:00 | Vulnerability · Source |
| CVE-2026-31414 | suse_vex | SUSE CVE CVE-2026-31414 | known affected: 636 recommended: 149 | 2026-07-21T13:15:41+00:00 | Vulnerability · Source |
| CVE-2026-31429 | suse_vex | SUSE CVE CVE-2026-31429 | known affected: 459 known not affected: 184 recommended: 149 | 2026-07-21T13:15:36+00:00 | Vulnerability · Source |
| CVE-2026-31450 | suse_vex | SUSE CVE CVE-2026-31450 | known affected: 242 known not affected: 4 recommended: 142 | 2026-07-21T13:15:35+00:00 | Vulnerability · Source |
| CVE-2026-31452 | suse_vex | SUSE CVE CVE-2026-31452 | known affected: 458 known not affected: 154 recommended: 179 | 2026-07-21T13:15:33+00:00 | Vulnerability · Source |
| CVE-2026-31466 | suse_vex | SUSE CVE CVE-2026-31466 | known affected: 225 known not affected: 6 recommended: 108 | 2026-07-21T13:15:31+00:00 | Vulnerability · Source |
| CVE-2026-31469 | suse_vex | SUSE CVE CVE-2026-31469 | known affected: 595 recommended: 179 | 2026-07-21T13:15:30+00:00 | Vulnerability · Source |
| CVE-2026-31492 | suse_vex | SUSE CVE CVE-2026-31492 | known affected: 546 known not affected: 96 recommended: 149 | 2026-07-21T13:15:28+00:00 | Vulnerability · Source |
| CVE-2026-31495 | suse_vex | SUSE CVE CVE-2026-31495 | known affected: 647 recommended: 149 | 2026-07-21T13:15:26+00:00 | Vulnerability · Source |
| CVE-2026-31499 | suse_vex | SUSE CVE CVE-2026-31499 | known affected: 459 known not affected: 154 recommended: 179 | 2026-07-21T13:15:24+00:00 | Vulnerability · Source |
| CVE-2026-31502 | suse_vex | SUSE CVE CVE-2026-31502 | known affected: 219 known not affected: 4 recommended: 165 | 2026-07-21T13:15:22+00:00 | Vulnerability · Source |
| CVE-2026-31505 | suse_vex | SUSE CVE CVE-2026-31505 | first fixed: 34 known affected: 411 known not affected: 136 recommended: 452 | 2026-07-21T13:15:20+00:00 | Vulnerability · Source |
| CVE-2026-31533 | suse_vex | SUSE CVE CVE-2026-31533 | first fixed: 34 known affected: 442 known not affected: 65 recommended: 558 | 2026-07-21T13:15:16+00:00 | Vulnerability · Source |