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-2025-37942 | suse_vex | SUSE CVE CVE-2025-37942 | known affected: 550 known not affected: 17 recommended: 109 | 2026-10-15T16:48:34+00:00 | Vulnerability · Source |
| CVE-2025-37945 | suse_vex | SUSE CVE CVE-2025-37945 | known affected: 580 known not affected: 256 recommended: 427 | 2026-10-15T16:48:32+00:00 | Vulnerability · Source |
| CVE-2025-37946 | suse_vex | SUSE CVE CVE-2025-37946 | known affected: 461 known not affected: 360 recommended: 427 | 2026-10-15T16:48:30+00:00 | Vulnerability · Source |
| CVE-2025-37948 | suse_vex | SUSE CVE CVE-2025-37948 | known affected: 540 known not affected: 51 recommended: 664 | 2026-10-15T16:48:28+00:00 | Vulnerability · Source |
| CVE-2025-37949 | suse_vex | SUSE CVE CVE-2025-37949 | known affected: 746 known not affected: 36 recommended: 454 | 2026-10-15T16:48:26+00:00 | Vulnerability · Source |
| CVE-2025-37950 | suse_vex | SUSE CVE CVE-2025-37950 | known affected: 0 known not affected: 502 | 2026-10-15T16:48:25+00:00 | Vulnerability · Source |
| CVE-2025-37953 | suse_vex | SUSE CVE CVE-2025-37953 | known affected: 0 known not affected: 244 recommended: 699 | 2026-10-15T16:48:22+00:00 | Vulnerability · Source |
| CVE-2025-37954 | suse_vex | SUSE CVE CVE-2025-37954 | known affected: 580 known not affected: 256 recommended: 427 | 2026-10-15T16:48:20+00:00 | Vulnerability · Source |
| CVE-2025-37955 | suse_vex | SUSE CVE CVE-2025-37955 | known affected: 69 known not affected: 435 recommended: 207 | 2026-10-15T16:48:19+00:00 | Vulnerability · Source |
| CVE-2025-37957 | suse_vex | SUSE CVE CVE-2025-37957 | known affected: 580 known not affected: 256 recommended: 431 | 2026-10-15T16:48:17+00:00 | Vulnerability · Source |
| CVE-2025-37958 | suse_vex | SUSE CVE CVE-2025-37958 | known affected: 471 known not affected: 187 recommended: 723 | 2026-10-15T16:48:15+00:00 | Vulnerability · Source |
| CVE-2025-37959 | suse_vex | SUSE CVE CVE-2025-37959 | known affected: 522 known not affected: 299 recommended: 427 | 2026-10-15T16:48:13+00:00 | Vulnerability · Source |
| CVE-2025-37961 | suse_vex | SUSE CVE CVE-2025-37961 | known affected: 774 known not affected: 6 recommended: 464 | 2026-10-15T16:48:11+00:00 | Vulnerability · Source |
| CVE-2025-37962 | suse_vex | SUSE CVE CVE-2025-37962 | known affected: 0 known not affected: 502 | 2026-10-15T16:48:10+00:00 | Vulnerability · Source |
| CVE-2025-37963 | suse_vex | SUSE CVE CVE-2025-37963 | known affected: 339 known not affected: 252 recommended: 664 | 2026-10-15T16:48:07+00:00 | Vulnerability · Source |
| CVE-2025-37964 | suse_vex | SUSE CVE CVE-2025-37964 | known affected: 0 known not affected: 502 | 2026-10-15T16:48:05+00:00 | Vulnerability · Source |
| CVE-2025-37969 | suse_vex | SUSE CVE CVE-2025-37969 | known affected: 591 known not affected: 230 recommended: 427 | 2026-10-15T16:48:04+00:00 | Vulnerability · Source |
| CVE-2022-23806 | redhat_vex | golang: crypto/elliptic: IsOnCurve returns true for invalid field elements | fixed: 908 known affected: 97 known not affected: 1002 under investigation: 2 | 2026-10-15T16:48:03+00:00 | Vulnerability · Source |
| CVE-2025-37971 | suse_vex | SUSE CVE CVE-2025-37971 | known affected: 67 known not affected: 435 recommended: 109 | 2026-10-15T16:48:02+00:00 | Vulnerability · Source |
| CVE-2025-37972 | suse_vex | SUSE CVE CVE-2025-37972 | known affected: 461 known not affected: 360 recommended: 427 | 2026-10-15T16:48:00+00:00 | Vulnerability · Source |
| CVE-2025-37974 | suse_vex | SUSE CVE CVE-2025-37974 | known affected: 504 known not affected: 332 recommended: 431 | 2026-10-15T16:47:59+00:00 | Vulnerability · Source |
| CVE-2025-37976 | suse_vex | SUSE CVE CVE-2025-37976 | known affected: 67 known not affected: 435 | 2026-10-15T16:47:57+00:00 | Vulnerability · Source |
| CVE-2025-37977 | suse_vex | SUSE CVE CVE-2025-37977 | known affected: 67 known not affected: 338 | 2026-10-15T16:47:55+00:00 | Vulnerability · Source |
| CVE-2025-37980 | suse_vex | SUSE CVE CVE-2025-37980 | known affected: 731 known not affected: 49 recommended: 464 | 2026-10-15T16:47:54+00:00 | Vulnerability · Source |
| CVE-2025-37981 | suse_vex | SUSE CVE CVE-2025-37981 | known affected: 461 known not affected: 411 recommended: 202 | 2026-10-15T16:47:52+00:00 | Vulnerability · Source |
| CVE-2025-37983 | suse_vex | SUSE CVE CVE-2025-37983 | known affected: 716 known not affected: 43 recommended: 427 | 2026-10-15T16:47:51+00:00 | Vulnerability · Source |
| CVE-2025-37985 | suse_vex | SUSE CVE CVE-2025-37985 | known affected: 522 known not affected: 299 recommended: 427 | 2026-10-15T16:47:49+00:00 | Vulnerability · Source |
| CVE-2025-37988 | suse_vex | SUSE CVE CVE-2025-37988 | known affected: 67 known not affected: 435 recommended: 109 | 2026-10-15T16:47:47+00:00 | Vulnerability · Source |
| CVE-2025-37990 | suse_vex | SUSE CVE CVE-2025-37990 | known affected: 733 known not affected: 107 recommended: 441 | 2026-10-15T16:47:45+00:00 | Vulnerability · Source |
| CVE-2025-37991 | suse_vex | SUSE CVE CVE-2025-37991 | known affected: 0 known not affected: 560 | 2026-10-15T16:47:44+00:00 | Vulnerability · Source |
| CVE-2025-37993 | suse_vex | SUSE CVE CVE-2025-37993 | known affected: 0 known not affected: 502 recommended: 109 | 2026-10-15T16:47:42+00:00 | Vulnerability · Source |
| CVE-2025-37994 | suse_vex | SUSE CVE CVE-2025-37994 | known affected: 591 known not affected: 230 recommended: 510 | 2026-10-15T16:47:40+00:00 | Vulnerability · Source |
| CVE-2025-37997 | suse_vex | SUSE CVE CVE-2025-37997 | known affected: 387 known not affected: 276 recommended: 700 | 2026-10-15T16:47:39+00:00 | Vulnerability · Source |
| CVE-2025-37998 | suse_vex | SUSE CVE CVE-2025-37998 | known affected: 774 known not affected: 6 recommended: 449 | 2026-10-15T16:47:37+00:00 | Vulnerability · Source |
| CVE-2025-38002 | suse_vex | SUSE CVE CVE-2025-38002 | known affected: 0 known not affected: 502 recommended: 58 | 2026-10-15T16:47:35+00:00 | Vulnerability · Source |
| CVE-2025-38005 | suse_vex | SUSE CVE CVE-2025-38005 | known affected: 522 known not affected: 299 recommended: 427 | 2026-10-15T16:47:33+00:00 | Vulnerability · Source |
| CVE-2025-38006 | suse_vex | SUSE CVE CVE-2025-38006 | known affected: 444 known not affected: 405 recommended: 503 | 2026-10-15T16:47:32+00:00 | Vulnerability · Source |
| CVE-2025-38007 | suse_vex | SUSE CVE CVE-2025-38007 | known affected: 394 known not affected: 367 recommended: 464 | 2026-10-15T16:47:30+00:00 | Vulnerability · Source |
| CVE-2025-38010 | suse_vex | SUSE CVE CVE-2025-38010 | known affected: 394 known not affected: 427 recommended: 427 | 2026-10-15T16:47:28+00:00 | Vulnerability · Source |
| CVE-2025-38014 | suse_vex | SUSE CVE CVE-2025-38014 | known affected: 387 known not affected: 256 recommended: 653 | 2026-10-15T16:47:26+00:00 | Vulnerability · Source |
| CVE-2025-38018 | suse_vex | SUSE CVE CVE-2025-38018 | known affected: 437 known not affected: 399 recommended: 427 | 2026-10-15T16:47:24+00:00 | Vulnerability · Source |
| CVE-2025-38019 | suse_vex | SUSE CVE CVE-2025-38019 | known affected: 7 known not affected: 552 recommended: 185 | 2026-10-15T16:47:22+00:00 | Vulnerability · Source |
| CVE-2026-66299 | redhat_vex | tomcat: Apache Tomcat: Denial of Service via WebSocket chat example | fixed: 56 known affected: 36 known not affected: 44 | 2026-10-15T16:47:19+00:00 | Vulnerability · Source |
| CVE-2025-38020 | suse_vex | SUSE CVE CVE-2025-38020 | known affected: 461 known not affected: 360 recommended: 427 | 2026-10-15T16:47:19+00:00 | Vulnerability · Source |
| CVE-2025-38021 | suse_vex | SUSE CVE CVE-2025-38021 | known affected: 0 known not affected: 506 recommended: 58 | 2026-10-15T16:47:18+00:00 | Vulnerability · Source |
| CVE-2026-73180 | redhat_vex | tomcat: Apache Tomcat: Authenticated WebSocket session persists after HTTP session termination | fixed: 110 known affected: 65 | 2026-10-15T16:47:16+00:00 | Vulnerability · Source |
| CVE-2025-38022 | suse_vex | SUSE CVE CVE-2025-38022 | known affected: 565 known not affected: 256 recommended: 559 | 2026-10-15T16:47:15+00:00 | Vulnerability · Source |
| CVE-2025-38023 | suse_vex | SUSE CVE CVE-2025-38023 | known affected: 703 known not affected: 79 recommended: 450 | 2026-10-15T16:47:13+00:00 | Vulnerability · Source |
| CVE-2025-38024 | suse_vex | SUSE CVE CVE-2025-38024 | known affected: 703 known not affected: 77 recommended: 581 | 2026-10-15T16:47:11+00:00 | Vulnerability · Source |
| CVE-2025-38029 | suse_vex | SUSE CVE CVE-2025-38029 | known affected: 6 known not affected: 554 | 2026-10-15T16:47:09+00:00 | Vulnerability · Source |