VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
304351 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-64444 | suse_vex | SUSE CVE CVE-2026-64444 | known affected: 673 known not affected: 79 recommended: 256 | 2026-10-03T00:44:13+00:00 | Vulnerability · Source |
| CVE-2026-64445 | suse_vex | SUSE CVE CVE-2026-64445 | known affected: 671 known not affected: 64 recommended: 256 | 2026-10-03T00:44:10+00:00 | Vulnerability · Source |
| CVE-2026-64446 | suse_vex | SUSE CVE CVE-2026-64446 | known affected: 343 known not affected: 35 recommended: 149 | 2026-10-03T00:44:08+00:00 | Vulnerability · Source |
| CVE-2026-32280 | redhat_vex | crypto/x509: crypto/tls: golang: Go: Denial of Service vulnerability in certificate chain building | fixed: 4577 known affected: 130 known not affected: 7228 | 2026-10-03T00:44:06+00:00 | Vulnerability · Source |
| CVE-2026-64448 | suse_vex | SUSE CVE CVE-2026-64448 | known affected: 729 known not affected: 4 recommended: 111 | 2026-10-03T00:44:05+00:00 | Vulnerability · Source |
| CVE-2026-64450 | suse_vex | SUSE CVE CVE-2026-64450 | known affected: 688 known not affected: 6 recommended: 363 | 2026-10-03T00:44:02+00:00 | Vulnerability · Source |
| CVE-2026-64452 | suse_vex | SUSE CVE CVE-2026-64452 | known affected: 748 known not affected: 4 recommended: 232 | 2026-10-03T00:43:59+00:00 | Vulnerability · Source |
| CVE-2026-64454 | suse_vex | SUSE CVE CVE-2026-64454 | known affected: 530 known not affected: 205 recommended: 256 | 2026-10-03T00:43:56+00:00 | Vulnerability · Source |
| CVE-2026-64455 | suse_vex | SUSE CVE CVE-2026-64455 | known affected: 673 known not affected: 62 recommended: 256 | 2026-10-03T00:43:54+00:00 | Vulnerability · Source |
| CVE-2026-64456 | suse_vex | SUSE CVE CVE-2026-64456 | known affected: 283 known not affected: 95 recommended: 191 | 2026-10-03T00:43:52+00:00 | Vulnerability · Source |
| CVE-2026-64458 | suse_vex | SUSE CVE CVE-2026-64458 | known affected: 127 known not affected: 251 recommended: 149 | 2026-10-03T00:43:50+00:00 | Vulnerability · Source |
| CVE-2026-64460 | suse_vex | SUSE CVE CVE-2026-64460 | known affected: 12 known not affected: 364 recommended: 4 | 2026-10-03T00:43:48+00:00 | Vulnerability · Source |
| CVE-2026-64463 | suse_vex | SUSE CVE CVE-2026-64463 | known affected: 638 known not affected: 97 recommended: 256 | 2026-10-03T00:43:45+00:00 | Vulnerability · Source |
| CVE-2026-64470 | suse_vex | SUSE CVE CVE-2026-64470 | known affected: 617 known not affected: 64 recommended: 279 | 2026-10-03T00:43:42+00:00 | Vulnerability · Source |
| CVE-2026-64471 | suse_vex | SUSE CVE CVE-2026-64471 | known affected: 623 known not affected: 58 recommended: 279 | 2026-10-03T00:43:40+00:00 | Vulnerability · Source |
| CVE-2026-64472 | suse_vex | SUSE CVE CVE-2026-64472 | known affected: 542 known not affected: 193 recommended: 256 | 2026-10-03T00:43:37+00:00 | Vulnerability · Source |
| CVE-2026-64473 | suse_vex | SUSE CVE CVE-2026-64473 | known affected: 78 known not affected: 298 recommended: 4 | 2026-10-03T00:43:35+00:00 | Vulnerability · Source |
| CVE-2026-64474 | suse_vex | SUSE CVE CVE-2026-64474 | known affected: 183 known not affected: 193 recommended: 4 | 2026-10-03T00:43:32+00:00 | Vulnerability · Source |
| CVE-2026-64477 | suse_vex | SUSE CVE CVE-2026-64477 | known affected: 454 known not affected: 298 recommended: 232 | 2026-10-03T00:43:31+00:00 | Vulnerability · Source |
| CVE-2026-64478 | suse_vex | SUSE CVE CVE-2026-64478 | known affected: 426 known not affected: 326 recommended: 256 | 2026-10-03T00:43:28+00:00 | Vulnerability · Source |
| CVE-2026-64479 | suse_vex | SUSE CVE CVE-2026-64479 | known affected: 426 known not affected: 309 recommended: 256 | 2026-10-03T00:43:26+00:00 | Vulnerability · Source |
| CVE-2026-64480 | suse_vex | SUSE CVE CVE-2026-64480 | known affected: 426 known not affected: 309 recommended: 256 | 2026-10-03T00:43:24+00:00 | Vulnerability · Source |
| CVE-2026-64481 | suse_vex | SUSE CVE CVE-2026-64481 | known affected: 489 known not affected: 205 recommended: 363 | 2026-10-03T00:43:21+00:00 | Vulnerability · Source |
| CVE-2026-64482 | suse_vex | SUSE CVE CVE-2026-64482 | known affected: 426 known not affected: 309 recommended: 256 | 2026-10-03T00:43:18+00:00 | Vulnerability · Source |
| CVE-2026-64483 | suse_vex | SUSE CVE CVE-2026-64483 | known affected: 677 known not affected: 58 recommended: 256 | 2026-10-03T00:43:16+00:00 | Vulnerability · Source |
| CVE-2026-64484 | suse_vex | SUSE CVE CVE-2026-64484 | known affected: 673 known not affected: 79 recommended: 256 | 2026-10-03T00:43:14+00:00 | Vulnerability · Source |
| CVE-2026-64486 | suse_vex | SUSE CVE CVE-2026-64486 | known affected: 426 known not affected: 309 recommended: 256 | 2026-10-03T00:43:12+00:00 | Vulnerability · Source |
| CVE-2026-64487 | suse_vex | SUSE CVE CVE-2026-64487 | known affected: 677 known not affected: 58 recommended: 256 | 2026-10-03T00:43:10+00:00 | Vulnerability · Source |
| CVE-2026-64489 | suse_vex | SUSE CVE CVE-2026-64489 | known affected: 426 known not affected: 309 recommended: 256 | 2026-10-03T00:43:08+00:00 | Vulnerability · Source |
| CVE-2026-64490 | suse_vex | SUSE CVE CVE-2026-64490 | known affected: 2 known not affected: 376 recommended: 232 | 2026-10-03T00:43:06+00:00 | Vulnerability · Source |
| CVE-2026-64494 | suse_vex | SUSE CVE CVE-2026-64494 | known affected: 530 known not affected: 205 recommended: 256 | 2026-10-03T00:43:04+00:00 | Vulnerability · Source |
| CVE-2026-64495 | suse_vex | SUSE CVE CVE-2026-64495 | known affected: 673 known not affected: 62 recommended: 256 | 2026-10-03T00:43:02+00:00 | Vulnerability · Source |
| CVE-2026-64496 | suse_vex | SUSE CVE CVE-2026-64496 | known affected: 673 known not affected: 62 recommended: 275 | 2026-10-03T00:43:01+00:00 | Vulnerability · Source |
| CVE-2026-64497 | suse_vex | SUSE CVE CVE-2026-64497 | known affected: 530 known not affected: 205 recommended: 256 | 2026-10-03T00:42:59+00:00 | Vulnerability · Source |
| CVE-2026-64499 | suse_vex | SUSE CVE CVE-2026-64499 | known affected: 2 known not affected: 376 recommended: 149 | 2026-10-03T00:42:56+00:00 | Vulnerability · Source |
| CVE-2026-64500 | suse_vex | SUSE CVE CVE-2026-64500 | known affected: 671 known not affected: 64 recommended: 256 | 2026-10-03T00:42:54+00:00 | Vulnerability · Source |
| CVE-2026-64503 | suse_vex | SUSE CVE CVE-2026-64503 | known affected: 671 known not affected: 64 recommended: 256 | 2026-10-03T00:42:51+00:00 | Vulnerability · Source |
| CVE-2026-64504 | suse_vex | SUSE CVE CVE-2026-64504 | known affected: 673 known not affected: 62 recommended: 256 | 2026-10-03T00:42:48+00:00 | Vulnerability · Source |
| CVE-2026-64505 | suse_vex | SUSE CVE CVE-2026-64505 | known affected: 677 known not affected: 58 recommended: 256 | 2026-10-03T00:42:46+00:00 | Vulnerability · Source |
| CVE-2026-64507 | suse_vex | SUSE CVE CVE-2026-64507 | known affected: 185 known not affected: 193 recommended: 149 | 2026-10-03T00:42:43+00:00 | Vulnerability · Source |
| CVE-2026-64511 | suse_vex | SUSE CVE CVE-2026-64511 | known affected: 426 known not affected: 309 recommended: 256 | 2026-10-03T00:42:41+00:00 | Vulnerability · Source |
| CVE-2026-64512 | suse_vex | SUSE CVE CVE-2026-64512 | known affected: 488 known not affected: 193 recommended: 279 | 2026-10-03T00:42:39+00:00 | Vulnerability · Source |
| CVE-2026-64513 | suse_vex | SUSE CVE CVE-2026-64513 | known affected: 617 known not affected: 64 recommended: 279 | 2026-10-03T00:42:36+00:00 | Vulnerability · Source |
| CVE-2026-64515 | suse_vex | SUSE CVE CVE-2026-64515 | known affected: 425 known not affected: 327 recommended: 311 | 2026-10-03T00:42:33+00:00 | Vulnerability · Source |
| CVE-2026-64517 | suse_vex | SUSE CVE CVE-2026-64517 | known affected: 396 known not affected: 356 recommended: 228 | 2026-10-03T00:42:30+00:00 | Vulnerability · Source |
| CVE-2026-64518 | suse_vex | SUSE CVE CVE-2026-64518 | known affected: 31 known not affected: 347 recommended: 145 | 2026-10-03T00:42:27+00:00 | Vulnerability · Source |
| CVE-2026-64519 | suse_vex | SUSE CVE CVE-2026-64519 | known affected: 31 known not affected: 347 recommended: 145 | 2026-10-03T00:42:25+00:00 | Vulnerability · Source |
| CVE-2026-64524 | suse_vex | SUSE CVE CVE-2026-64524 | known affected: 442 known not affected: 263 recommended: 283 | 2026-10-03T00:42:23+00:00 | Vulnerability · Source |
| CVE-2026-64525 | suse_vex | SUSE CVE CVE-2026-64525 | known affected: 2 known not affected: 376 recommended: 145 | 2026-10-03T00:42:21+00:00 | Vulnerability · Source |
| CVE-2026-64526 | suse_vex | SUSE CVE CVE-2026-64526 | known affected: 31 known not affected: 347 recommended: 145 | 2026-10-03T00:42:18+00:00 | Vulnerability · Source |