VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
306034 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-74697 | suse_vex | SUSE CVE CVE-2026-74697 | known affected: 301 known not affected: 93 | 2026-10-08T17:01:03+00:00 | Vulnerability · Source |
| CVE-2026-74700 | suse_vex | SUSE CVE CVE-2026-74700 | known affected: 301 known not affected: 93 | 2026-10-08T17:01:01+00:00 | Vulnerability · Source |
| CVE-2026-74701 | suse_vex | SUSE CVE CVE-2026-74701 | known affected: 390 known not affected: 6 | 2026-10-08T17:01:00+00:00 | Vulnerability · Source |
| CVE-2026-74710 | suse_vex | SUSE CVE CVE-2026-74710 | known affected: 155 known not affected: 239 | 2026-10-08T17:00:58+00:00 | Vulnerability · Source |
| CVE-2026-74713 | suse_vex | SUSE CVE CVE-2026-74713 | known affected: 251 known not affected: 143 | 2026-10-08T17:00:56+00:00 | Vulnerability · Source |
| CVE-2026-74718 | suse_vex | SUSE CVE CVE-2026-74718 | known affected: 155 known not affected: 239 | 2026-10-08T17:00:54+00:00 | Vulnerability · Source |
| CVE-2026-74725 | suse_vex | SUSE CVE CVE-2026-74725 | known affected: 390 known not affected: 4 | 2026-10-08T17:00:53+00:00 | Vulnerability · Source |
| CVE-2026-74726 | suse_vex | SUSE CVE CVE-2026-74726 | known affected: 396 | 2026-10-08T17:00:51+00:00 | Vulnerability · Source |
| CVE-2026-74735 | suse_vex | SUSE CVE CVE-2026-74735 | known affected: 351 known not affected: 39 | 2026-10-08T17:00:49+00:00 | Vulnerability · Source |
| CVE-2026-74739 | suse_vex | SUSE CVE CVE-2026-74739 | known affected: 388 known not affected: 4 | 2026-10-08T17:00:47+00:00 | Vulnerability · Source |
| CVE-2026-74752 | suse_vex | SUSE CVE CVE-2026-74752 | known affected: 392 | 2026-10-08T17:00:45+00:00 | Vulnerability · Source |
| CVE-2026-75029 | suse_vex | SUSE CVE CVE-2026-75029 | known affected: 761 known not affected: 1 recommended: 19 | 2026-10-08T17:00:43+00:00 | Vulnerability · Source |
| CVE-2026-76033 | suse_vex | SUSE CVE CVE-2026-76033 | recommended: 6 | 2026-10-08T17:00:41+00:00 | Vulnerability · Source |
| CVE-2026-76034 | suse_vex | SUSE CVE CVE-2026-76034 | recommended: 6 | 2026-10-08T17:00:40+00:00 | Vulnerability · Source |
| CVE-2026-76035 | suse_vex | SUSE CVE CVE-2026-76035 | recommended: 6 | 2026-10-08T17:00:38+00:00 | Vulnerability · Source |
| CVE-2026-76036 | suse_vex | SUSE CVE CVE-2026-76036 | recommended: 6 | 2026-10-08T17:00:36+00:00 | Vulnerability · Source |
| CVE-2026-76037 | suse_vex | SUSE CVE CVE-2026-76037 | recommended: 6 | 2026-10-08T17:00:34+00:00 | Vulnerability · Source |
| CVE-2026-76038 | suse_vex | SUSE CVE CVE-2026-76038 | recommended: 6 | 2026-10-08T17:00:33+00:00 | Vulnerability · Source |
| CVE-2026-76039 | suse_vex | SUSE CVE CVE-2026-76039 | recommended: 6 | 2026-10-08T17:00:31+00:00 | Vulnerability · Source |
| CVE-2026-76040 | suse_vex | SUSE CVE CVE-2026-76040 | recommended: 6 | 2026-10-08T17:00:29+00:00 | Vulnerability · Source |
| CVE-2026-76041 | suse_vex | SUSE CVE CVE-2026-76041 | known affected: 179 recommended: 14 | 2026-10-08T17:00:28+00:00 | Vulnerability · Source |
| CVE-2026-76042 | suse_vex | SUSE CVE CVE-2026-76042 | recommended: 6 | 2026-10-08T17:00:26+00:00 | Vulnerability · Source |
| CVE-2026-76043 | suse_vex | SUSE CVE CVE-2026-76043 | recommended: 6 | 2026-10-08T17:00:25+00:00 | Vulnerability · Source |
| CVE-2026-76044 | suse_vex | SUSE CVE CVE-2026-76044 | recommended: 6 | 2026-10-08T17:00:23+00:00 | Vulnerability · Source |
| CVE-2026-76045 | suse_vex | SUSE CVE CVE-2026-76045 | recommended: 6 | 2026-10-08T17:00:21+00:00 | Vulnerability · Source |
| CVE-2026-76046 | suse_vex | SUSE CVE CVE-2026-76046 | recommended: 14 | 2026-10-08T17:00:13+00:00 | Vulnerability · Source |
| CVE-2026-76047 | suse_vex | SUSE CVE CVE-2026-76047 | recommended: 6 | 2026-10-08T17:00:09+00:00 | Vulnerability · Source |
| CVE-2026-76151 | suse_vex | SUSE CVE CVE-2026-76151 | recommended: 1 | 2026-10-08T17:00:08+00:00 | Vulnerability · Source |
| CVE-2026-76163 | suse_vex | SUSE CVE CVE-2026-76163 | known affected: 426 known not affected: 324 recommended: 19 | 2026-10-08T17:00:06+00:00 | Vulnerability · Source |
| CVE-2026-76560 | suse_vex | SUSE CVE CVE-2026-76560 | known affected: 116 recommended: 54 | 2026-10-08T17:00:04+00:00 | Vulnerability · Source |
| CVE-2026-77117 | suse_vex | SUSE CVE CVE-2026-77117 | known affected: 563 recommended: 367 | 2026-10-08T17:00:02+00:00 | Vulnerability · Source |
| CVE-2026-77119 | suse_vex | SUSE CVE CVE-2026-77119 | known affected: 749 known not affected: 1 recommended: 19 | 2026-10-08T17:00:00+00:00 | Vulnerability · Source |
| CVE-2026-77214 | suse_vex | SUSE CVE CVE-2026-77214 | known affected: 327 known not affected: 7169 | 2026-10-08T16:59:57+00:00 | Vulnerability · Source |
| CVE-2026-77692 | suse_vex | SUSE CVE CVE-2026-77692 | known affected: 426 known not affected: 324 recommended: 19 | 2026-10-08T16:59:55+00:00 | Vulnerability · Source |
| CVE-2026-78301 | suse_vex | SUSE CVE CVE-2026-78301 | known affected: 761 known not affected: 1 recommended: 19 | 2026-10-08T16:59:53+00:00 | Vulnerability · Source |
| CVE-2026-80274 | suse_vex | SUSE CVE CVE-2026-80274 | known affected: 799 known not affected: 1 recommended: 44 | 2026-10-08T16:59:47+00:00 | Vulnerability · Source |
| CVE-2026-80489 | suse_vex | SUSE CVE CVE-2026-80489 | known affected: 563 recommended: 367 | 2026-10-08T16:59:45+00:00 | Vulnerability · Source |
| CVE-2026-80585 | suse_vex | SUSE CVE CVE-2026-80585 | known affected: 151 known not affected: 239 | 2026-10-08T16:59:42+00:00 | Vulnerability · Source |
| CVE-2026-80613 | suse_vex | SUSE CVE CVE-2026-80613 | known affected: 247 known not affected: 143 | 2026-10-08T16:59:39+00:00 | Vulnerability · Source |
| CVE-2026-80631 | suse_vex | SUSE CVE CVE-2026-80631 | known affected: 247 known not affected: 143 | 2026-10-08T16:59:36+00:00 | Vulnerability · Source |
| CVE-2026-80664 | suse_vex | SUSE CVE CVE-2026-80664 | known affected: 388 known not affected: 4 | 2026-10-08T16:59:33+00:00 | Vulnerability · Source |
| CVE-2026-80679 | suse_vex | SUSE CVE CVE-2026-80679 | known affected: 297 known not affected: 93 | 2026-10-08T16:59:30+00:00 | Vulnerability · Source |
| CVE-2026-80686 | suse_vex | SUSE CVE CVE-2026-80686 | known affected: 151 known not affected: 239 | 2026-10-08T16:59:28+00:00 | Vulnerability · Source |
| CVE-2026-80715 | suse_vex | SUSE CVE CVE-2026-80715 | known affected: 247 known not affected: 143 | 2026-10-08T16:59:25+00:00 | Vulnerability · Source |
| CVE-2026-80722 | suse_vex | SUSE CVE CVE-2026-80722 | known affected: 459 known not affected: 269 recommended: 99 | 2026-10-08T16:59:24+00:00 | Vulnerability · Source |
| CVE-2026-80725 | suse_vex | SUSE CVE CVE-2026-80725 | known affected: 151 known not affected: 239 | 2026-10-08T16:59:22+00:00 | Vulnerability · Source |
| CVE-2026-80747 | suse_vex | SUSE CVE CVE-2026-80747 | known affected: 388 known not affected: 4 | 2026-10-08T16:59:20+00:00 | Vulnerability · Source |
| CVE-2026-80756 | suse_vex | SUSE CVE CVE-2026-80756 | known affected: 247 known not affected: 143 | 2026-10-08T16:59:18+00:00 | Vulnerability · Source |
| CVE-2026-80789 | suse_vex | SUSE CVE CVE-2026-80789 | known affected: 386 known not affected: 6 recommended: 4 | 2026-10-08T16:59:16+00:00 | Vulnerability · Source |
| CVE-2026-80793 | suse_vex | SUSE CVE CVE-2026-80793 | known affected: 392 recommended: 4 | 2026-10-08T16:59:14+00:00 | Vulnerability · Source |