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-93564 | redhat_vex | io.netty/netty-codec-haproxy: Netty: HAProxy PROXY-v2 nested-TLV grandchild ByteBuf reference-count leak (incomplete fix of PR #16881) | fixed: 4 known affected: 8 known not affected: 1643 | 2026-10-15T16:42:33+00:00 | Vulnerability · Source |
| CVE-2025-38294 | suse_vex | SUSE CVE CVE-2025-38294 | known affected: 0 known not affected: 521 recommended: 58 | 2026-10-15T16:42:32+00:00 | Vulnerability · Source |
| CVE-2026-93558 | redhat_vex | io.netty/netty-codec-http: Netty: Unbounded Per-Connection Queue Growth in WebSocketServerExtensionHandler Leads to Denial of Service | fixed: 4 known affected: 11 known not affected: 1643 | 2026-10-15T16:42:31+00:00 | Vulnerability · Source |
| CVE-2025-38296 | suse_vex | SUSE CVE CVE-2025-38296 | recommended: 58 | 2026-10-15T16:42:29+00:00 | Vulnerability · Source |
| CVE-2025-38304 | suse_vex | SUSE CVE CVE-2025-38304 | known affected: 463 known not affected: 375 recommended: 503 | 2026-10-15T16:42:26+00:00 | Vulnerability · Source |
| CVE-2026-93491 | redhat_vex | io.netty/netty-codec-http: Netty: Denial of Service via unbounded HttpServerCodec HTTP/1.1 pipeline queue | fixed: 4 known affected: 11 known not affected: 1643 | 2026-10-15T16:42:25+00:00 | Vulnerability · Source |
| CVE-2025-38307 | suse_vex | SUSE CVE CVE-2025-38307 | known affected: 396 known not affected: 442 recommended: 503 | 2026-10-15T16:42:24+00:00 | Vulnerability · Source |
| CVE-2026-93488 | redhat_vex | io.netty/netty-codec-http: Netty: Denial of Service via unbounded concurrent SPDY streams | fixed: 4 known affected: 11 known not affected: 1643 | 2026-10-15T16:42:22+00:00 | Vulnerability · Source |
| CVE-2025-38309 | suse_vex | SUSE CVE CVE-2025-38309 | known affected: 0 known not affected: 521 recommended: 58 | 2026-10-15T16:42:22+00:00 | Vulnerability · Source |
| CVE-2025-38312 | suse_vex | SUSE CVE CVE-2025-38312 | known affected: 735 known not affected: 59 recommended: 540 | 2026-10-15T16:42:19+00:00 | Vulnerability · Source |
| CVE-2025-38313 | suse_vex | SUSE CVE CVE-2025-38313 | known affected: 645 known not affected: 142 recommended: 526 | 2026-10-15T16:42:16+00:00 | Vulnerability · Source |
| CVE-2025-38314 | suse_vex | SUSE CVE CVE-2025-38314 | known affected: 0 known not affected: 521 | 2026-10-15T16:42:14+00:00 | Vulnerability · Source |
| CVE-2025-38315 | suse_vex | SUSE CVE CVE-2025-38315 | known affected: 396 known not affected: 478 recommended: 278 | 2026-10-15T16:42:11+00:00 | Vulnerability · Source |
| CVE-2025-38317 | suse_vex | SUSE CVE CVE-2025-38317 | known affected: 396 known not affected: 494 recommended: 278 | 2026-10-15T16:42:10+00:00 | Vulnerability · Source |
| CVE-2025-38318 | suse_vex | SUSE CVE CVE-2025-38318 | known affected: 7 known not affected: 554 recommended: 185 | 2026-10-15T16:42:08+00:00 | Vulnerability · Source |
| CVE-2025-38319 | suse_vex | SUSE CVE CVE-2025-38319 | known affected: 645 known not affected: 139 recommended: 526 | 2026-10-15T16:42:06+00:00 | Vulnerability · Source |
| CVE-2025-38320 | suse_vex | SUSE CVE CVE-2025-38320 | known affected: 0 known not affected: 575 | 2026-10-15T16:42:04+00:00 | Vulnerability · Source |
| CVE-2025-38322 | suse_vex | SUSE CVE CVE-2025-38322 | known affected: 401 known not affected: 449 recommended: 480 | 2026-10-15T16:42:01+00:00 | Vulnerability · Source |
| CVE-2025-38323 | suse_vex | SUSE CVE CVE-2025-38323 | known affected: 467 known not affected: 362 recommended: 811 | 2026-10-15T16:41:59+00:00 | Vulnerability · Source |
| CVE-2025-38329 | suse_vex | SUSE CVE CVE-2025-38329 | known affected: 0 known not affected: 521 recommended: 100 | 2026-10-15T16:41:56+00:00 | Vulnerability · Source |
| CVE-2025-38330 | suse_vex | SUSE CVE CVE-2025-38330 | known affected: 0 known not affected: 521 recommended: 100 | 2026-10-15T16:41:54+00:00 | Vulnerability · Source |
| CVE-2025-38333 | suse_vex | SUSE CVE CVE-2025-38333 | known affected: 0 known not affected: 575 | 2026-10-15T16:41:52+00:00 | Vulnerability · Source |
| CVE-2025-38334 | suse_vex | SUSE CVE CVE-2025-38334 | known affected: 580 known not affected: 256 recommended: 427 | 2026-10-15T16:41:50+00:00 | Vulnerability · Source |
| CVE-2025-38336 | suse_vex | SUSE CVE CVE-2025-38336 | known affected: 741 known not affected: 75 recommended: 540 | 2026-10-15T16:41:47+00:00 | Vulnerability · Source |
| CVE-2026-55223 | redhat_vex | c3p0: c3p0: Remote code execution via deserialization vulnerability | fixed: 2 known affected: 3 known not affected: 7 | 2026-10-15T16:41:45+00:00 | Vulnerability · Source |
| CVE-2025-38340 | suse_vex | SUSE CVE CVE-2025-38340 | known affected: 0 known not affected: 521 recommended: 58 | 2026-10-15T16:41:45+00:00 | Vulnerability · Source |
| CVE-2025-38342 | suse_vex | SUSE CVE CVE-2025-38342 | known affected: 608 known not affected: 242 recommended: 503 | 2026-10-15T16:41:43+00:00 | Vulnerability · Source |
| CVE-2025-38343 | suse_vex | SUSE CVE CVE-2025-38343 | known affected: 396 known not affected: 454 recommended: 503 | 2026-10-15T16:41:41+00:00 | Vulnerability · Source |
| CVE-2025-38344 | suse_vex | SUSE CVE CVE-2025-38344 | known affected: 729 known not affected: 49 recommended: 472 | 2026-10-15T16:41:39+00:00 | Vulnerability · Source |
| CVE-2025-38350 | suse_vex | SUSE CVE CVE-2025-38350 | known affected: 459 known not affected: 129 recommended: 930 | 2026-10-15T16:41:37+00:00 | Vulnerability · Source |
| CVE-2025-38351 | suse_vex | SUSE CVE CVE-2025-38351 | known affected: 401 known not affected: 405 recommended: 581 | 2026-10-15T16:41:35+00:00 | Vulnerability · Source |
| CVE-2025-38353 | suse_vex | SUSE CVE CVE-2025-38353 | known affected: 396 known not affected: 489 recommended: 278 | 2026-10-15T16:41:33+00:00 | Vulnerability · Source |
| CVE-2025-38354 | suse_vex | SUSE CVE CVE-2025-38354 | known affected: 463 known not affected: 387 recommended: 503 | 2026-10-15T16:41:31+00:00 | Vulnerability · Source |
| CVE-2025-38355 | suse_vex | SUSE CVE CVE-2025-38355 | known affected: 396 known not affected: 478 recommended: 278 | 2026-10-15T16:41:29+00:00 | Vulnerability · Source |
| CVE-2025-38356 | suse_vex | SUSE CVE CVE-2025-38356 | known affected: 396 known not affected: 492 recommended: 278 | 2026-10-15T16:41:27+00:00 | Vulnerability · Source |
| CVE-2025-38357 | suse_vex | SUSE CVE CVE-2025-38357 | known affected: 0 known not affected: 521 | 2026-10-15T16:41:25+00:00 | Vulnerability · Source |
| CVE-2025-38360 | suse_vex | SUSE CVE CVE-2025-38360 | known affected: 417 known not affected: 434 recommended: 503 | 2026-10-15T16:41:22+00:00 | Vulnerability · Source |
| CVE-2025-38361 | suse_vex | SUSE CVE CVE-2025-38361 | known affected: 454 known not affected: 379 recommended: 495 | 2026-10-15T16:41:20+00:00 | Vulnerability · Source |
| CVE-2025-38364 | suse_vex | SUSE CVE CVE-2025-38364 | known affected: 439 known not affected: 399 recommended: 503 | 2026-10-15T16:41:18+00:00 | Vulnerability · Source |
| CVE-2025-38365 | suse_vex | SUSE CVE CVE-2025-38365 | known affected: 539 known not affected: 299 recommended: 503 | 2026-10-15T16:41:16+00:00 | Vulnerability · Source |
| CVE-2025-38366 | suse_vex | SUSE CVE CVE-2025-38366 | known affected: 0 known not affected: 521 | 2026-10-15T16:41:15+00:00 | Vulnerability · Source |
| CVE-2025-38368 | suse_vex | SUSE CVE CVE-2025-38368 | known affected: 2 known not affected: 521 recommended: 185 | 2026-10-15T16:41:13+00:00 | Vulnerability · Source |
| CVE-2025-38369 | suse_vex | SUSE CVE CVE-2025-38369 | known affected: 582 known not affected: 256 recommended: 545 | 2026-10-15T16:41:11+00:00 | Vulnerability · Source |
| CVE-2025-38371 | suse_vex | SUSE CVE CVE-2025-38371 | known affected: 657 known not affected: 181 recommended: 503 | 2026-10-15T16:41:09+00:00 | Vulnerability · Source |
| CVE-2025-38372 | suse_vex | SUSE CVE CVE-2025-38372 | known affected: 78 known not affected: 445 recommended: 185 | 2026-10-15T16:41:07+00:00 | Vulnerability · Source |
| CVE-2025-38374 | suse_vex | SUSE CVE CVE-2025-38374 | known affected: 7 known not affected: 552 recommended: 185 | 2026-10-15T16:41:04+00:00 | Vulnerability · Source |
| CVE-2025-38375 | suse_vex | SUSE CVE CVE-2025-38375 | known affected: 545 known not affected: 64 recommended: 777 | 2026-10-15T16:41:02+00:00 | Vulnerability · Source |
| CVE-2025-38377 | suse_vex | SUSE CVE CVE-2025-38377 | known affected: 517 known not affected: 201 recommended: 503 | 2026-10-15T16:40:59+00:00 | Vulnerability · Source |
| CVE-2025-38380 | suse_vex | SUSE CVE CVE-2025-38380 | known affected: 346 known not affected: 143 recommended: 815 | 2026-10-15T16:40:57+00:00 | Vulnerability · Source |
| CVE-2025-38383 | suse_vex | SUSE CVE CVE-2025-38383 | known affected: 561 recommended: 227 | 2026-10-15T16:40:55+00:00 | Vulnerability · Source |