VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283120 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-43128 | suse_vex | SUSE CVE CVE-2026-43128 | known affected: 135 known not affected: 91 recommended: 191 | 2026-07-21T13:12:01+00:00 | Vulnerability · Source |
| CVE-2026-43139 | suse_vex | SUSE CVE CVE-2026-43139 | known affected: 196 recommended: 138 | 2026-07-21T13:11:59+00:00 | Vulnerability · Source |
| CVE-2026-43158 | suse_vex | SUSE CVE CVE-2026-43158 | known affected: 586 known not affected: 4 recommended: 295 | 2026-07-21T13:11:57+00:00 | Vulnerability · Source |
| CVE-2026-43168 | suse_vex | SUSE CVE CVE-2026-43168 | known affected: 226 | 2026-07-21T13:11:55+00:00 | Vulnerability · Source |
| CVE-2026-43171 | suse_vex | SUSE CVE CVE-2026-43171 | known affected: 543 known not affected: 77 recommended: 149 | 2026-07-21T13:11:53+00:00 | Vulnerability · Source |
| CVE-2026-43187 | suse_vex | SUSE CVE CVE-2026-43187 | known affected: 586 known not affected: 4 recommended: 179 | 2026-07-21T13:11:51+00:00 | Vulnerability · Source |
| CVE-2026-43190 | suse_vex | SUSE CVE CVE-2026-43190 | first fixed: 34 known affected: 468 recommended: 732 | 2026-07-21T13:11:49+00:00 | Vulnerability · Source |
| CVE-2026-43198 | suse_vex | SUSE CVE CVE-2026-43198 | known affected: 463 recommended: 487 | 2026-07-21T13:11:47+00:00 | Vulnerability · Source |
| CVE-2026-43238 | suse_vex | SUSE CVE CVE-2026-43238 | known affected: 47 known not affected: 179 recommended: 108 | 2026-07-21T13:11:41+00:00 | Vulnerability · Source |
| CVE-2026-43303 | suse_vex | SUSE CVE CVE-2026-43303 | known affected: 95 known not affected: 131 recommended: 191 | 2026-07-21T13:11:33+00:00 | Vulnerability · Source |
| CVE-2026-43336 | suse_vex | SUSE CVE CVE-2026-43336 | known affected: 192 known not affected: 4 recommended: 138 | 2026-07-21T13:11:28+00:00 | Vulnerability · Source |
| CVE-2026-43339 | suse_vex | SUSE CVE CVE-2026-43339 | known affected: 586 known not affected: 6 recommended: 172 | 2026-07-21T13:11:26+00:00 | Vulnerability · Source |
| CVE-2026-43345 | suse_vex | SUSE CVE CVE-2026-43345 | known affected: 441 known not affected: 179 recommended: 149 | 2026-07-21T13:11:23+00:00 | Vulnerability · Source |
| CVE-2026-43366 | suse_vex | SUSE CVE CVE-2026-43366 | first fixed: 34 known affected: 411 known not affected: 131 recommended: 454 | 2026-07-21T13:11:18+00:00 | Vulnerability · Source |
| CVE-2026-43374 | suse_vex | SUSE CVE CVE-2026-43374 | known affected: 14 known not affected: 212 | 2026-07-21T13:11:15+00:00 | Vulnerability · Source |
| CVE-2026-43398 | suse_vex | SUSE CVE CVE-2026-43398 | known not affected: 226 | 2026-07-21T13:11:11+00:00 | Vulnerability · Source |
| CVE-2026-43399 | suse_vex | SUSE CVE CVE-2026-43399 | known not affected: 226 | 2026-07-21T13:11:09+00:00 | Vulnerability · Source |
| CVE-2026-43405 | suse_vex | SUSE CVE CVE-2026-43405 | known affected: 529 known not affected: 91 recommended: 149 | 2026-07-21T13:11:07+00:00 | Vulnerability · Source |
| CVE-2026-43406 | suse_vex | SUSE CVE CVE-2026-43406 | known affected: 529 known not affected: 91 recommended: 149 | 2026-07-21T13:11:05+00:00 | Vulnerability · Source |
| CVE-2026-43407 | suse_vex | SUSE CVE CVE-2026-43407 | known affected: 590 recommended: 179 | 2026-07-21T13:11:03+00:00 | Vulnerability · Source |
| CVE-2026-43415 | suse_vex | SUSE CVE CVE-2026-43415 | known affected: 15 known not affected: 212 | 2026-07-21T13:11:01+00:00 | Vulnerability · Source |
| CVE-2026-43420 | suse_vex | SUSE CVE CVE-2026-43420 | known affected: 161 known not affected: 65 recommended: 108 | 2026-07-21T13:10:59+00:00 | Vulnerability · Source |
| CVE-2026-1784 | redhat_vex | ose-cluster-ingress-operator: Remote Code Execution Through HAProxy Configuration Injection | fixed: 29 known not affected: 4787 | 2026-07-21T13:10:57+00:00 | Vulnerability · Source |
| CVE-2026-43456 | suse_vex | SUSE CVE CVE-2026-43456 | known affected: 196 recommended: 165 | 2026-07-21T13:10:51+00:00 | Vulnerability · Source |
| CVE-2026-43457 | suse_vex | SUSE CVE CVE-2026-43457 | known affected: 102 known not affected: 125 | 2026-07-21T13:10:50+00:00 | Vulnerability · Source |
| CVE-2026-43458 | suse_vex | SUSE CVE CVE-2026-43458 | known affected: 227 | 2026-07-21T13:10:48+00:00 | Vulnerability · Source |
| CVE-2026-43469 | suse_vex | SUSE CVE CVE-2026-43469 | known affected: 529 known not affected: 91 recommended: 149 | 2026-07-21T13:10:41+00:00 | Vulnerability · Source |
| CVE-2026-43470 | suse_vex | SUSE CVE CVE-2026-43470 | known affected: 517 known not affected: 103 recommended: 149 | 2026-07-21T13:10:39+00:00 | Vulnerability · Source |
| CVE-2026-43471 | suse_vex | SUSE CVE CVE-2026-43471 | known affected: 15 known not affected: 212 | 2026-07-21T13:10:37+00:00 | Vulnerability · Source |
| CVE-2026-43477 | suse_vex | SUSE CVE CVE-2026-43477 | known not affected: 206 | 2026-07-21T13:10:36+00:00 | Vulnerability · Source |
| CVE-2026-43491 | suse_vex | SUSE CVE CVE-2026-43491 | known affected: 529 known not affected: 91 recommended: 153 | 2026-07-21T13:10:34+00:00 | Vulnerability · Source |
| CVE-2026-43492 | suse_vex | SUSE CVE CVE-2026-43492 | known affected: 192 known not affected: 4 recommended: 142 | 2026-07-21T13:10:32+00:00 | Vulnerability · Source |
| CVE-2026-43501 | suse_vex | SUSE CVE CVE-2026-43501 | first fixed: 32 known affected: 415 known not affected: 77 recommended: 487 | 2026-07-21T13:10:30+00:00 | Vulnerability · Source |
| CVE-2026-43502 | suse_vex | SUSE CVE CVE-2026-43502 | known affected: 161 known not affected: 65 recommended: 112 | 2026-07-21T13:10:28+00:00 | Vulnerability · Source |
| CVE-2026-44172 | suse_vex | SUSE CVE CVE-2026-44172 | first fixed: 80 known affected: 639 known not affected: 22 recommended: 150 | 2026-07-21T13:10:24+00:00 | Vulnerability · Source |
| CVE-2026-44178 | suse_vex | SUSE CVE CVE-2026-44178 | known affected: 92 known not affected: 1 | 2026-07-21T13:10:23+00:00 | Vulnerability · Source |
| CVE-2026-44978 | suse_vex | SUSE CVE CVE-2026-44978 | known affected: 93 | 2026-07-21T13:10:07+00:00 | Vulnerability · Source |
| CVE-2026-45793 | suse_vex | SUSE CVE CVE-2026-45793 | first fixed: 6 known affected: 18 | 2026-07-21T13:10:02+00:00 | Vulnerability · Source |
| CVE-2026-45837 | suse_vex | SUSE CVE CVE-2026-45837 | known affected: 15 known not affected: 276 recommended: 4 | 2026-07-21T13:10:01+00:00 | Vulnerability · Source |
| CVE-2026-45838 | suse_vex | SUSE CVE CVE-2026-45838 | known affected: 206 known not affected: 20 recommended: 112 | 2026-07-21T13:09:59+00:00 | Vulnerability · Source |
| CVE-2026-45840 | suse_vex | SUSE CVE CVE-2026-45840 | known affected: 586 known not affected: 4 recommended: 183 | 2026-07-21T13:09:58+00:00 | Vulnerability · Source |
| CVE-2026-45841 | suse_vex | SUSE CVE CVE-2026-45841 | known affected: 590 recommended: 183 | 2026-07-21T13:09:57+00:00 | Vulnerability · Source |
| CVE-2026-45848 | suse_vex | SUSE CVE CVE-2026-45848 | known affected: 161 known not affected: 65 recommended: 135 | 2026-07-21T13:09:55+00:00 | Vulnerability · Source |
| CVE-2026-45852 | suse_vex | SUSE CVE CVE-2026-45852 | first fixed: 2 known affected: 427 known not affected: 20 recommended: 566 | 2026-07-21T13:09:54+00:00 | Vulnerability · Source |
| CVE-2026-45862 | suse_vex | SUSE CVE CVE-2026-45862 | known affected: 489 known not affected: 131 recommended: 149 | 2026-07-21T13:09:50+00:00 | Vulnerability · Source |
| CVE-2026-45870 | suse_vex | SUSE CVE CVE-2026-45870 | known affected: 586 known not affected: 4 recommended: 179 | 2026-07-21T13:09:49+00:00 | Vulnerability · Source |
| CVE-2026-45884 | suse_vex | SUSE CVE CVE-2026-45884 | known affected: 15 known not affected: 212 | 2026-07-21T13:09:48+00:00 | Vulnerability · Source |
| CVE-2026-45888 | suse_vex | SUSE CVE CVE-2026-45888 | known not affected: 227 | 2026-07-21T13:09:46+00:00 | Vulnerability · Source |
| CVE-2026-45891 | suse_vex | SUSE CVE CVE-2026-45891 | known affected: 135 known not affected: 91 recommended: 108 | 2026-07-21T13:09:45+00:00 | Vulnerability · Source |
| CVE-2026-45912 | suse_vex | SUSE CVE CVE-2026-45912 | known affected: 166 known not affected: 30 recommended: 165 | 2026-07-21T13:09:44+00:00 | Vulnerability · Source |