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-89509 | redhat_vex | kernel: RDMA/ionic: Embed counter driver data in rdma_counter allocation | known not affected: 277 | 2026-10-15T18:33:38+00:00 | Vulnerability · Source |
| CVE-2026-89508 | redhat_vex | kernel: RDMA/ucma: Lock the handler in ucma_set_ib_path() | known not affected: 277 | 2026-10-15T18:33:34+00:00 | Vulnerability · Source |
| CVE-2026-89507 | redhat_vex | kernel: RDMA/ucma: Lock the handler in ucma_write_cm_event() | known not affected: 277 | 2026-10-15T18:33:32+00:00 | Vulnerability · Source |
| CVE-2026-89505 | redhat_vex | kernel: RDMA/uverbs: Guard legacy bundles without method_elm | known not affected: 277 | 2026-10-15T18:33:22+00:00 | Vulnerability · Source |
| CVE-2026-89495 | redhat_vex | kernel: ocfs2: bound namelen in dlm_migrate_request_handler | known not affected: 277 | 2026-10-15T18:33:22+00:00 | Vulnerability · Source |
| CVE-2026-89465 | redhat_vex | kernel: power: supply: rt9455: quiesce delayed work before teardown | known not affected: 277 | 2026-10-15T18:33:22+00:00 | Vulnerability · Source |
| CVE-2026-55858 | redhat_vex | org.mariadb.jdbc/mariadb-java-client: MariaDB Connector/J: Silent data corruption due to character set mismatch | fixed: 1 known affected: 43 known not affected: 1112 | 2026-10-15T18:18:39+00:00 | Vulnerability · Source |
| CVE-2026-55857 | redhat_vex | org.mariadb.jdbc/mariadb-java-client: MariaDB Connector/J: Information Disclosure via Insecure PAM Dialog Authentication | fixed: 1 known affected: 43 known not affected: 1112 | 2026-10-15T18:18:03+00:00 | Vulnerability · Source |
| CVE-2026-66422 | redhat_vex | tomcat: Apache Tomcat: Improper Authorization allows bypass of declarative role constraints | fixed: 110 known affected: 43 known not affected: 22 | 2026-10-15T17:08:07+00:00 | Vulnerability · Source |
| CVE-2026-65183 | redhat_vex | tomcat: Apache Tomcat: Local information disclosure via Unix domain socket TOCTOU race condition | fixed: 110 known affected: 62 known not affected: 3 | 2026-10-15T17:08:03+00:00 | Vulnerability · Source |
| CVE-2026-55276 | redhat_vex | tomcat: Apache Tomcat: Misleading security logs due to incorrect control flow | fixed: 191 known affected: 51 | 2026-10-15T17:08:01+00:00 | Vulnerability · Source |
| CVE-2026-53434 | redhat_vex | tomcat: Apache Tomcat: Error condition not handled when configuring CRLs | fixed: 191 known affected: 51 | 2026-10-15T17:07:57+00:00 | Vulnerability · Source |
| CVE-2026-93574 | redhat_vex | io.netty/netty-codec-http: Netty: HTTP request smuggling via post-digit whitespace in chunk-size parsing | fixed: 3 known affected: 11 | 2026-10-15T17:01:21+00:00 | Vulnerability · Source |
| CVE-2026-93573 | redhat_vex | io.netty/netty-codec-http: Netty split Transfer-Encoding fields bypass final-chunked validation and enable request smuggling | fixed: 3 known affected: 11 | 2026-10-15T17:01:19+00:00 | Vulnerability · Source |
| CVE-2026-93566 | redhat_vex | io.netty/netty-codec-http: Netty: HTTP Request Smuggling due to control characters in the chunk-size line | fixed: 3 known affected: 11 | 2026-10-15T17:01:16+00:00 | Vulnerability · Source |
| CVE-2026-93562 | redhat_vex | io.netty/netty-codec-http: Netty: Incomplete validation of malformed Transfer-Encoding allows HTTP request smuggling | fixed: 3 known affected: 11 | 2026-10-15T17:01:14+00:00 | Vulnerability · Source |
| CVE-2025-21852 | suse_vex | SUSE CVE CVE-2025-21852 | known affected: 67 known not affected: 364 recommended: 438 | 2026-10-15T17:00:18+00:00 | Vulnerability · Source |
| CVE-2025-21853 | suse_vex | SUSE CVE CVE-2025-21853 | known affected: 634 known not affected: 191 recommended: 521 | 2026-10-15T17:00:16+00:00 | Vulnerability · Source |
| CVE-2025-21856 | suse_vex | SUSE CVE CVE-2025-21856 | known affected: 477 known not affected: 321 recommended: 415 | 2026-10-15T17:00:14+00:00 | Vulnerability · Source |
| CVE-2025-21857 | suse_vex | SUSE CVE CVE-2025-21857 | known affected: 477 known not affected: 321 recommended: 457 | 2026-10-15T17:00:12+00:00 | Vulnerability · Source |
| CVE-2025-21858 | suse_vex | SUSE CVE CVE-2025-21858 | known affected: 736 known not affected: 6 recommended: 475 | 2026-10-15T17:00:10+00:00 | Vulnerability · Source |
| CVE-2025-21859 | suse_vex | SUSE CVE CVE-2025-21859 | known affected: 712 known not affected: 98 recommended: 415 | 2026-10-15T17:00:09+00:00 | Vulnerability · Source |
| CVE-2025-21861 | suse_vex | SUSE CVE CVE-2025-21861 | known affected: 607 known not affected: 191 recommended: 498 | 2026-10-15T17:00:07+00:00 | Vulnerability · Source |
| CVE-2025-21862 | suse_vex | SUSE CVE CVE-2025-21862 | known affected: 742 recommended: 455 | 2026-10-15T17:00:05+00:00 | Vulnerability · Source |
| CVE-2025-21863 | suse_vex | SUSE CVE CVE-2025-21863 | known affected: 565 known not affected: 260 recommended: 527 | 2026-10-15T17:00:04+00:00 | Vulnerability · Source |
| CVE-2025-21864 | suse_vex | SUSE CVE CVE-2025-21864 | known affected: 477 known not affected: 321 recommended: 498 | 2026-10-15T17:00:02+00:00 | Vulnerability · Source |
| CVE-2025-21865 | suse_vex | SUSE CVE CVE-2025-21865 | known affected: 485 known not affected: 259 recommended: 441 | 2026-10-15T17:00:00+00:00 | Vulnerability · Source |
| CVE-2025-21866 | suse_vex | SUSE CVE CVE-2025-21866 | known affected: 591 known not affected: 207 recommended: 415 | 2026-10-15T16:59:58+00:00 | Vulnerability · Source |
| CVE-2025-21867 | suse_vex | SUSE CVE CVE-2025-21867 | known affected: 504 known not affected: 317 recommended: 503 | 2026-10-15T16:59:56+00:00 | Vulnerability · Source |
| CVE-2025-21873 | suse_vex | SUSE CVE CVE-2025-21873 | known affected: 504 known not affected: 317 recommended: 415 | 2026-10-15T16:59:54+00:00 | Vulnerability · Source |
| CVE-2025-21875 | suse_vex | SUSE CVE CVE-2025-21875 | known affected: 565 known not affected: 256 recommended: 415 | 2026-10-15T16:59:52+00:00 | Vulnerability · Source |
| CVE-2025-21881 | suse_vex | SUSE CVE CVE-2025-21881 | known affected: 696 known not affected: 6 recommended: 569 | 2026-10-15T16:59:50+00:00 | Vulnerability · Source |
| CVE-2025-21883 | suse_vex | SUSE CVE CVE-2025-21883 | known affected: 477 known not affected: 317 recommended: 501 | 2026-10-15T16:59:49+00:00 | Vulnerability · Source |
| CVE-2025-21887 | suse_vex | SUSE CVE CVE-2025-21887 | known affected: 504 known not affected: 317 recommended: 501 | 2026-10-15T16:59:47+00:00 | Vulnerability · Source |
| CVE-2025-21890 | suse_vex | SUSE CVE CVE-2025-21890 | known affected: 538 known not affected: 256 recommended: 415 | 2026-10-15T16:59:45+00:00 | Vulnerability · Source |
| CVE-2025-21891 | suse_vex | SUSE CVE CVE-2025-21891 | known affected: 732 known not affected: 6 recommended: 455 | 2026-10-15T16:59:44+00:00 | Vulnerability · Source |
| CVE-2025-21892 | suse_vex | SUSE CVE CVE-2025-21892 | known affected: 461 known not affected: 333 recommended: 415 | 2026-10-15T16:59:42+00:00 | Vulnerability · Source |
| CVE-2025-21894 | suse_vex | SUSE CVE CVE-2025-21894 | known affected: 634 known not affected: 187 recommended: 415 | 2026-10-15T16:59:40+00:00 | Vulnerability · Source |
| CVE-2025-21896 | suse_vex | SUSE CVE CVE-2025-21896 | known affected: 0 known not affected: 821 | 2026-10-15T16:59:39+00:00 | Vulnerability · Source |
| CVE-2025-21898 | suse_vex | SUSE CVE CVE-2025-21898 | known affected: 750 known not affected: 36 recommended: 450 | 2026-10-15T16:59:37+00:00 | Vulnerability · Source |
| CVE-2025-21899 | suse_vex | SUSE CVE CVE-2025-21899 | known affected: 649 known not affected: 187 recommended: 427 | 2026-10-15T16:59:35+00:00 | Vulnerability · Source |
| CVE-2025-21903 | suse_vex | SUSE CVE CVE-2025-21903 | known affected: 0 known not affected: 488 recommended: 109 | 2026-10-15T16:59:34+00:00 | Vulnerability · Source |
| CVE-2025-21905 | suse_vex | SUSE CVE CVE-2025-21905 | known affected: 591 known not affected: 203 recommended: 521 | 2026-10-15T16:59:32+00:00 | Vulnerability · Source |
| CVE-2025-21908 | suse_vex | SUSE CVE CVE-2025-21908 | known affected: 437 known not affected: 384 recommended: 415 | 2026-10-15T16:59:30+00:00 | Vulnerability · Source |
| CVE-2025-21909 | suse_vex | SUSE CVE CVE-2025-21909 | known affected: 722 known not affected: 43 recommended: 455 | 2026-10-15T16:59:28+00:00 | Vulnerability · Source |
| CVE-2025-21910 | suse_vex | SUSE CVE CVE-2025-21910 | known affected: 722 known not affected: 43 recommended: 424 | 2026-10-15T16:59:27+00:00 | Vulnerability · Source |
| CVE-2025-21911 | suse_vex | SUSE CVE CVE-2025-21911 | known affected: 394 known not affected: 456 recommended: 202 | 2026-10-15T16:59:25+00:00 | Vulnerability · Source |
| CVE-2025-21913 | suse_vex | SUSE CVE CVE-2025-21913 | known affected: 437 known not affected: 384 recommended: 415 | 2026-10-15T16:59:23+00:00 | Vulnerability · Source |
| CVE-2025-21919 | suse_vex | SUSE CVE CVE-2025-21919 | known affected: 565 known not affected: 256 recommended: 537 | 2026-10-15T16:59:22+00:00 | Vulnerability · Source |
| CVE-2025-21920 | suse_vex | SUSE CVE CVE-2025-21920 | known affected: 784 recommended: 550 | 2026-10-15T16:59:20+00:00 | Vulnerability · Source |