VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-71554 | redhat_vex | h2: h2: Request smuggling due to duplicate Host headers | known affected: 17 | 2026-10-15T16:09:55+00:00 | Vulnerability · Source |
| CVE-2026-59888 | redhat_vex | com.fasterxml.jackson.core/jackson-databind: tools.jackson.core/jackson-databind: jackson-databind: @JsonIgnore bypass in Java Records | fixed: 25 known affected: 190 known not affected: 55 | 2026-10-15T16:09:27+00:00 | Vulnerability · Source |
| CVE-2026-18040 | redhat_vex | bouncycastle: bcprov-jdk18on: bouncycastle: Information disclosure via cryptographic side channels in HQC | known affected: 34 | 2026-10-15T16:08:53+00:00 | Vulnerability · Source |
| CVE-2025-68476 | redhat_vex | github.com/kedacore/keda: KEDA: Arbitrary file read vulnerability in Vault authentication | fixed: 44 known affected: 3 known not affected: 513 | 2026-10-15T16:08:11+00:00 | Vulnerability · Source |
| CVE-2022-49940 | redhat_vex | kernel: tty: n_gsm: add sanity check for gsm->receive in gsm_receive_buf() | fixed: 519 known not affected: 157 | 2026-10-15T16:08:03+00:00 | Vulnerability · Source |
| CVE-2026-89700 | redhat_vex | kernel: nfsd: validate sockaddr length per family in listener_set | known affected: 185 known not affected: 90 | 2026-10-15T16:06:02+00:00 | Vulnerability · Source |
| CVE-2026-89610 | redhat_vex | kernel: ntfs: verify run length exceeding volume boundary | known not affected: 277 | 2026-10-15T16:05:58+00:00 | Vulnerability · Source |
| CVE-2026-98159 | redhat_vex | kernel: wifi: mt76: mt7921: validate CLC firmware records | known affected: 234 known not affected: 43 | 2026-10-15T16:05:56+00:00 | Vulnerability · Source |
| CVE-2026-98080 | redhat_vex | kernel: btrfs: do not force reloc root creation during qgroup_account_snapshot() | known affected: 77 known not affected: 200 | 2026-10-15T16:05:50+00:00 | Vulnerability · Source |
| CVE-2025-53367 | suse_vex | SUSE CVE CVE-2025-53367 | known affected: 114 recommended: 44 | 2026-10-15T16:04:16+00:00 | Vulnerability · Source |
| CVE-2025-53512 | suse_vex | SUSE CVE CVE-2025-53512 | recommended: 4 | 2026-10-15T16:04:15+00:00 | Vulnerability · Source |
| CVE-2025-53513 | suse_vex | SUSE CVE CVE-2025-53513 | recommended: 4 | 2026-10-15T16:04:13+00:00 | Vulnerability · Source |
| CVE-2025-53514 | suse_vex | SUSE CVE CVE-2025-53514 | recommended: 1 | 2026-10-15T16:04:12+00:00 | Vulnerability · Source |
| CVE-2025-53633 | suse_vex | SUSE CVE CVE-2025-53633 | recommended: 4 | 2026-10-15T16:04:11+00:00 | Vulnerability · Source |
| CVE-2025-53634 | suse_vex | SUSE CVE CVE-2025-53634 | recommended: 4 | 2026-10-15T16:04:10+00:00 | Vulnerability · Source |
| CVE-2025-53817 | suse_vex | SUSE CVE CVE-2025-53817 | known affected: 53 known not affected: 19 recommended: 27 | 2026-10-15T16:04:08+00:00 | Vulnerability · Source |
| CVE-2025-53826 | suse_vex | SUSE CVE CVE-2025-53826 | recommended: 4 | 2026-10-15T16:04:06+00:00 | Vulnerability · Source |
| CVE-2025-53857 | suse_vex | SUSE CVE CVE-2025-53857 | recommended: 1 | 2026-10-15T16:04:04+00:00 | Vulnerability · Source |
| CVE-2025-53884 | suse_vex | SUSE CVE CVE-2025-53884 | recommended: 1 | 2026-10-15T16:04:02+00:00 | Vulnerability · Source |
| CVE-2025-53893 | suse_vex | SUSE CVE CVE-2025-53893 | recommended: 4 | 2026-10-15T16:04:00+00:00 | Vulnerability · Source |
| CVE-2025-53905 | suse_vex | SUSE CVE CVE-2025-53905 | known affected: 582 recommended: 148 | 2026-10-15T16:03:59+00:00 | Vulnerability · Source |
| CVE-2025-53910 | suse_vex | SUSE CVE CVE-2025-53910 | recommended: 1 | 2026-10-15T16:03:57+00:00 | Vulnerability · Source |
| CVE-2025-54080 | suse_vex | SUSE CVE CVE-2025-54080 | known affected: 180 known not affected: 1 recommended: 21 | 2026-10-15T16:03:55+00:00 | Vulnerability · Source |
| CVE-2025-54121 | suse_vex | SUSE CVE CVE-2025-54121 | known affected: 3 recommended: 8 | 2026-10-15T16:03:54+00:00 | Vulnerability · Source |
| CVE-2025-54123 | suse_vex | SUSE CVE CVE-2025-54123 | recommended: 1 | 2026-10-15T16:03:52+00:00 | Vulnerability · Source |
| CVE-2025-54286 | suse_vex | SUSE CVE CVE-2025-54286 | recommended: 1 | 2026-10-15T16:03:50+00:00 | Vulnerability · Source |
| CVE-2025-54288 | suse_vex | SUSE CVE CVE-2025-54288 | recommended: 1 | 2026-10-15T16:03:49+00:00 | Vulnerability · Source |
| CVE-2025-54289 | suse_vex | SUSE CVE CVE-2025-54289 | recommended: 1 | 2026-10-15T16:03:47+00:00 | Vulnerability · Source |
| CVE-2025-54290 | suse_vex | SUSE CVE CVE-2025-54290 | recommended: 1 | 2026-10-15T16:03:45+00:00 | Vulnerability · Source |
| CVE-2025-54349 | suse_vex | SUSE CVE CVE-2025-54349 | recommended: 27 | 2026-10-15T16:03:43+00:00 | Vulnerability · Source |
| CVE-2025-54376 | suse_vex | SUSE CVE CVE-2025-54376 | recommended: 1 | 2026-10-15T16:03:41+00:00 | Vulnerability · Source |
| CVE-2025-54379 | suse_vex | SUSE CVE CVE-2025-54379 | recommended: 4 | 2026-10-15T16:03:39+00:00 | Vulnerability · Source |
| CVE-2025-54388 | suse_vex | SUSE CVE CVE-2025-54388 | known affected: 422 known not affected: 20 recommended: 120 | 2026-10-15T16:03:37+00:00 | Vulnerability · Source |
| CVE-2025-54409 | suse_vex | SUSE CVE CVE-2025-54409 | known affected: 71 recommended: 5 | 2026-10-15T16:03:36+00:00 | Vulnerability · Source |
| CVE-2025-54410 | suse_vex | SUSE CVE CVE-2025-54410 | known affected: 15 known not affected: 7 recommended: 4 | 2026-10-15T16:03:34+00:00 | Vulnerability · Source |
| CVE-2025-54424 | suse_vex | SUSE CVE CVE-2025-54424 | recommended: 4 | 2026-10-15T16:03:33+00:00 | Vulnerability · Source |
| CVE-2025-54458 | suse_vex | SUSE CVE CVE-2025-54458 | recommended: 1 | 2026-10-15T16:03:31+00:00 | Vulnerability · Source |
| CVE-2025-54468 | suse_vex | SUSE CVE CVE-2025-54468 | recommended: 1 | 2026-10-15T16:03:29+00:00 | Vulnerability · Source |
| CVE-2025-54470 | suse_vex | SUSE CVE CVE-2025-54470 | recommended: 1 | 2026-10-15T16:03:27+00:00 | Vulnerability · Source |
| CVE-2025-54471 | suse_vex | SUSE CVE CVE-2025-54471 | recommended: 1 | 2026-10-15T16:03:25+00:00 | Vulnerability · Source |
| CVE-2025-54499 | suse_vex | SUSE CVE CVE-2025-54499 | recommended: 1 | 2026-10-15T16:03:24+00:00 | Vulnerability · Source |
| CVE-2025-54518 | suse_vex | SUSE CVE CVE-2025-54518 | known affected: 603 recommended: 878 | 2026-10-15T16:03:21+00:00 | Vulnerability · Source |
| CVE-2025-54525 | suse_vex | SUSE CVE CVE-2025-54525 | recommended: 1 | 2026-10-15T16:03:19+00:00 | Vulnerability · Source |
| CVE-2025-54567 | suse_vex | SUSE CVE CVE-2025-54567 | known not affected: 1832 recommended: 120 | 2026-10-15T16:03:17+00:00 | Vulnerability · Source |
| CVE-2025-54771 | suse_vex | SUSE CVE CVE-2025-54771 | known affected: 734 recommended: 284 | 2026-10-15T16:03:16+00:00 | Vulnerability · Source |
| CVE-2025-54798 | suse_vex | SUSE CVE CVE-2025-54798 | known affected: 97 known not affected: 11 recommended: 14 | 2026-10-15T16:03:14+00:00 | Vulnerability · Source |
| CVE-2025-54799 | suse_vex | SUSE CVE CVE-2025-54799 | recommended: 4 | 2026-10-15T16:03:13+00:00 | Vulnerability · Source |
| CVE-2025-54801 | suse_vex | SUSE CVE CVE-2025-54801 | recommended: 4 | 2026-10-15T16:03:11+00:00 | Vulnerability · Source |
| CVE-2025-54874 | suse_vex | SUSE CVE CVE-2025-54874 | known affected: 394 known not affected: 793 recommended: 30 | 2026-10-15T16:03:09+00:00 | Vulnerability · Source |
| CVE-2025-54882 | suse_vex | SUSE CVE CVE-2025-54882 | known not affected: 46 recommended: 46 | 2026-10-15T16:03:08+00:00 | Vulnerability · Source |