VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
99398 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-45337 | redhat_vex | golang.org/x/crypto/ssh: Misuse of ServerConfig.PublicKeyCallback may cause authorization bypass in golang.org/x/crypto | fixed: 1801 known affected: 72 known not affected: 8478 | 2026-10-16T16:52:48+00:00 | Vulnerability · Source |
| CVE-2023-25151 | redhat_vex | opentelemetry-go: DoS vulnerability for high cardinality metrics in otelhttp and otelbeego | known not affected: 287 | 2026-10-16T16:41:19+00:00 | Vulnerability · Source |
| CVE-2023-5332 | redhat_vex | consul: Command injection through script checks option | known affected: 20 known not affected: 55 | 2026-10-16T16:41:02+00:00 | Vulnerability · Source |
| CVE-2022-3064 | redhat_vex | go-yaml: Improve heuristics preventing CPU/memory abuse by parsing malicious or large YAML documents | fixed: 658 known affected: 77 known not affected: 3384 under investigation: 2 | 2026-10-16T16:40:41+00:00 | Vulnerability · Source |
| CVE-2026-93541 | suse_vex | SUSE CVE CVE-2026-93541 | known affected: 560 recommended: 4 | 2026-10-16T16:30:36+00:00 | Vulnerability · Source |
| CVE-2026-93542 | suse_vex | SUSE CVE CVE-2026-93542 | known affected: 560 recommended: 4 | 2026-10-16T16:30:34+00:00 | Vulnerability · Source |
| CVE-2026-93543 | suse_vex | SUSE CVE CVE-2026-93543 | known affected: 560 recommended: 4 | 2026-10-16T16:30:33+00:00 | Vulnerability · Source |
| CVE-2026-93544 | suse_vex | SUSE CVE CVE-2026-93544 | known affected: 560 recommended: 4 | 2026-10-16T16:30:31+00:00 | Vulnerability · Source |
| CVE-2026-93545 | suse_vex | SUSE CVE CVE-2026-93545 | known affected: 560 recommended: 4 | 2026-10-16T16:30:29+00:00 | Vulnerability · Source |
| CVE-2026-94114 | suse_vex | SUSE CVE CVE-2026-94114 | known affected: 45 recommended: 2 | 2026-10-16T16:30:07+00:00 | Vulnerability · Source |
| CVE-2026-94281 | suse_vex | SUSE CVE CVE-2026-94281 | known affected: 560 recommended: 4 | 2026-10-16T16:30:05+00:00 | Vulnerability · Source |
| CVE-2026-94282 | suse_vex | SUSE CVE CVE-2026-94282 | known affected: 560 recommended: 4 | 2026-10-16T16:30:03+00:00 | Vulnerability · Source |
| CVE-2026-97222 | suse_vex | SUSE CVE CVE-2026-97222 | No product status | 2026-10-16T16:29:59+00:00 | Vulnerability · Source |
| CVE-2026-97617 | suse_vex | SUSE CVE CVE-2026-97617 | known affected: 29 known not affected: 318 recommended: 4 | 2026-10-16T16:29:45+00:00 | Vulnerability · Source |
| CVE-2026-97687 | suse_vex | SUSE CVE CVE-2026-97687 | known affected: 99 known not affected: 80 recommended: 2 | 2026-10-16T16:29:43+00:00 | Vulnerability · Source |
| CVE-2026-98014 | suse_vex | SUSE CVE CVE-2026-98014 | known affected: 232 known not affected: 115 recommended: 4 | 2026-10-16T16:29:26+00:00 | Vulnerability · Source |
| CVE-2026-98076 | suse_vex | SUSE CVE CVE-2026-98076 | known affected: 204 known not affected: 143 recommended: 4 | 2026-10-16T16:29:21+00:00 | Vulnerability · Source |
| CVE-2026-98314 | suse_vex | SUSE CVE CVE-2026-98314 | known affected: 269 known not affected: 78 | 2026-10-16T16:29:12+00:00 | Vulnerability · Source |
| CVE-2026-98335 | suse_vex | SUSE CVE CVE-2026-98335 | known affected: 282 known not affected: 65 | 2026-10-16T16:29:10+00:00 | Vulnerability · Source |
| CVE-2026-101258 | suse_vex | SUSE CVE CVE-2026-101258 | known affected: 131 recommended: 26 | 2026-10-16T16:28:47+00:00 | Vulnerability · Source |
| CVE-2026-102555 | suse_vex | SUSE CVE CVE-2026-102555 | known affected: 26 known not affected: 183 recommended: 63 | 2026-10-16T16:28:41+00:00 | Vulnerability · Source |
| CVE-2026-102556 | suse_vex | SUSE CVE CVE-2026-102556 | known affected: 221 recommended: 116 | 2026-10-16T16:28:39+00:00 | Vulnerability · Source |
| CVE-2026-102557 | suse_vex | SUSE CVE CVE-2026-102557 | known affected: 221 recommended: 116 | 2026-10-16T16:28:36+00:00 | Vulnerability · Source |
| CVE-2026-102558 | suse_vex | SUSE CVE CVE-2026-102558 | known affected: 221 recommended: 116 | 2026-10-16T16:28:34+00:00 | Vulnerability · Source |
| CVE-2026-102559 | suse_vex | SUSE CVE CVE-2026-102559 | known affected: 221 recommended: 116 | 2026-10-16T16:28:31+00:00 | Vulnerability · Source |
| CVE-2026-102560 | suse_vex | SUSE CVE CVE-2026-102560 | known affected: 65 known not affected: 156 recommended: 96 | 2026-10-16T16:28:29+00:00 | Vulnerability · Source |
| CVE-2026-103111 | suse_vex | SUSE CVE CVE-2026-103111 | known affected: 595 recommended: 24 | 2026-10-16T16:28:23+00:00 | Vulnerability · Source |
| CVE-2026-103226 | suse_vex | SUSE CVE CVE-2026-103226 | known affected: 131 recommended: 26 | 2026-10-16T16:28:21+00:00 | Vulnerability · Source |
| CVE-2026-103261 | suse_vex | SUSE CVE CVE-2026-103261 | known affected: 60 known not affected: 83 | 2026-10-16T16:28:18+00:00 | Vulnerability · Source |
| CVE-2026-103262 | suse_vex | SUSE CVE CVE-2026-103262 | known affected: 52 known not affected: 91 recommended: 2 | 2026-10-16T16:28:16+00:00 | Vulnerability · Source |
| CVE-2026-103263 | suse_vex | SUSE CVE CVE-2026-103263 | known affected: 52 known not affected: 91 | 2026-10-16T16:28:14+00:00 | Vulnerability · Source |
| CVE-2026-103399 | suse_vex | SUSE CVE CVE-2026-103399 | known affected: 319 recommended: 51 | 2026-10-16T16:28:12+00:00 | Vulnerability · Source |
| CVE-2026-104031 | suse_vex | SUSE CVE CVE-2026-104031 | known affected: 939 | 2026-10-16T16:28:09+00:00 | Vulnerability · Source |
| CVE-2026-104032 | suse_vex | SUSE CVE CVE-2026-104032 | known affected: 939 | 2026-10-16T16:28:07+00:00 | Vulnerability · Source |
| CVE-2026-104033 | suse_vex | SUSE CVE CVE-2026-104033 | known affected: 939 | 2026-10-16T16:28:05+00:00 | Vulnerability · Source |
| CVE-2026-104034 | suse_vex | SUSE CVE CVE-2026-104034 | known affected: 558 known not affected: 381 | 2026-10-16T16:28:02+00:00 | Vulnerability · Source |
| CVE-2026-104035 | suse_vex | SUSE CVE CVE-2026-104035 | known affected: 558 known not affected: 381 | 2026-10-16T16:27:59+00:00 | Vulnerability · Source |
| CVE-2026-104036 | suse_vex | SUSE CVE CVE-2026-104036 | known affected: 939 | 2026-10-16T16:27:57+00:00 | Vulnerability · Source |
| CVE-2026-104037 | suse_vex | SUSE CVE CVE-2026-104037 | known affected: 939 | 2026-10-16T16:27:54+00:00 | Vulnerability · Source |
| CVE-2026-104038 | suse_vex | SUSE CVE CVE-2026-104038 | known affected: 291 known not affected: 648 | 2026-10-16T16:27:52+00:00 | Vulnerability · Source |
| CVE-2026-104039 | suse_vex | SUSE CVE CVE-2026-104039 | known affected: 558 known not affected: 381 | 2026-10-16T16:27:50+00:00 | Vulnerability · Source |
| CVE-2026-104041 | suse_vex | SUSE CVE CVE-2026-104041 | known affected: 939 | 2026-10-16T16:27:47+00:00 | Vulnerability · Source |
| CVE-2026-104045 | suse_vex | SUSE CVE CVE-2026-104045 | known affected: 939 | 2026-10-16T16:27:45+00:00 | Vulnerability · Source |
| CVE-2026-105111 | suse_vex | SUSE CVE CVE-2026-105111 | known affected: 47 recommended: 2 | 2026-10-16T16:27:40+00:00 | Vulnerability · Source |
| CVE-2026-105922 | suse_vex | SUSE CVE CVE-2026-105922 | recommended: 1 | 2026-10-16T16:27:38+00:00 | Vulnerability · Source |
| CVE-2026-106564 | suse_vex | SUSE CVE CVE-2026-106564 | known affected: 369 known not affected: 8 recommended: 63 | 2026-10-16T16:27:31+00:00 | Vulnerability · Source |
| CVE-2026-106565 | suse_vex | SUSE CVE CVE-2026-106565 | known affected: 404 known not affected: 8 recommended: 63 | 2026-10-16T16:27:28+00:00 | Vulnerability · Source |
| CVE-2026-106566 | suse_vex | SUSE CVE CVE-2026-106566 | known affected: 396 known not affected: 8 recommended: 63 | 2026-10-16T16:27:25+00:00 | Vulnerability · Source |
| CVE-2026-106567 | suse_vex | SUSE CVE CVE-2026-106567 | known affected: 404 known not affected: 8 recommended: 63 | 2026-10-16T16:27:23+00:00 | Vulnerability · Source |
| CVE-2026-106568 | suse_vex | SUSE CVE CVE-2026-106568 | known affected: 404 known not affected: 8 recommended: 63 | 2026-10-16T16:27:20+00:00 | Vulnerability · Source |