VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286443 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-14740 | suse_vex | SUSE CVE CVE-2026-14740 | first fixed: 7 known affected: 31 recommended: 5 | 2026-07-27T17:08:35+00:00 | Vulnerability · Source |
| CVE-2026-21441 | suse_vex | SUSE CVE CVE-2026-21441 | known affected: 370 recommended: 222 | 2026-07-27T17:08:29+00:00 | Vulnerability · Source |
| CVE-2026-48524 | redhat_vex | python-pyjwt: PyJWT: Denial of Service via unverified JSON Web Token key IDs | known affected: 181 known not affected: 8 | 2026-07-27T17:08:24+00:00 | Vulnerability · Source |
| CVE-2026-23490 | suse_vex | SUSE CVE CVE-2026-23490 | known affected: 394 recommended: 254 | 2026-07-27T17:08:23+00:00 | Vulnerability · Source |
| CVE-2026-23745 | suse_vex | SUSE CVE CVE-2026-23745 | known affected: 16 known not affected: 219 recommended: 14 | 2026-07-27T17:08:22+00:00 | Vulnerability · Source |
| CVE-2026-24842 | suse_vex | SUSE CVE CVE-2026-24842 | known not affected: 235 recommended: 18 | 2026-07-27T17:08:19+00:00 | Vulnerability · Source |
| CVE-2026-25679 | suse_vex | SUSE CVE CVE-2026-25679 | known affected: 12 known not affected: 81 recommended: 382 | 2026-07-27T17:08:15+00:00 | Vulnerability · Source |
| CVE-2026-27135 | suse_vex | SUSE CVE CVE-2026-27135 | known affected: 707 known not affected: 97 recommended: 294 | 2026-07-27T17:08:08+00:00 | Vulnerability · Source |
| CVE-2026-27137 | suse_vex | SUSE CVE CVE-2026-27137 | known not affected: 177 recommended: 159 | 2026-07-27T17:08:06+00:00 | Vulnerability · Source |
| CVE-2026-29518 | suse_vex | SUSE CVE CVE-2026-29518 | known affected: 406 recommended: 42 | 2026-07-27T17:08:00+00:00 | Vulnerability · Source |
| CVE-2026-31579 | suse_vex | SUSE CVE CVE-2026-31579 | first fixed: 2 known affected: 644 known not affected: 65 recommended: 149 | 2026-07-27T17:07:55+00:00 | Vulnerability · Source |
| CVE-2026-31664 | suse_vex | SUSE CVE CVE-2026-31664 | first fixed: 55 known affected: 612 recommended: 275 | 2026-07-27T17:07:53+00:00 | Vulnerability · Source |
| CVE-2026-31670 | suse_vex | SUSE CVE CVE-2026-31670 | first fixed: 55 known affected: 612 recommended: 246 | 2026-07-27T17:07:52+00:00 | Vulnerability · Source |
| CVE-2026-31812 | suse_vex | SUSE CVE CVE-2026-31812 | known affected: 8 known not affected: 284 recommended: 154 | 2026-07-27T17:07:48+00:00 | Vulnerability · Source |
| CVE-2026-32280 | suse_vex | SUSE CVE CVE-2026-32280 | known affected: 24 known not affected: 95 recommended: 308 | 2026-07-27T17:07:47+00:00 | Vulnerability · Source |
| CVE-2026-32283 | suse_vex | SUSE CVE CVE-2026-32283 | known affected: 86 known not affected: 47 recommended: 319 | 2026-07-27T17:07:46+00:00 | Vulnerability · Source |
| CVE-2026-32286 | suse_vex | SUSE CVE CVE-2026-32286 | known affected: 8 recommended: 3 | 2026-07-27T17:07:44+00:00 | Vulnerability · Source |
| CVE-2026-33810 | suse_vex | SUSE CVE CVE-2026-33810 | known affected: 30 known not affected: 163 recommended: 109 | 2026-07-27T17:07:37+00:00 | Vulnerability · Source |
| CVE-2026-33811 | suse_vex | SUSE CVE CVE-2026-33811 | known affected: 67 known not affected: 51 recommended: 316 | 2026-07-27T17:07:35+00:00 | Vulnerability · Source |
| CVE-2026-33816 | suse_vex | SUSE CVE CVE-2026-33816 | known not affected: 32 recommended: 8 | 2026-07-27T17:07:32+00:00 | Vulnerability · Source |
| CVE-2026-33845 | suse_vex | SUSE CVE CVE-2026-33845 | known affected: 448 recommended: 251 | 2026-07-27T17:07:31+00:00 | Vulnerability · Source |
| CVE-2026-33846 | suse_vex | SUSE CVE CVE-2026-33846 | known affected: 448 recommended: 251 | 2026-07-27T17:07:30+00:00 | Vulnerability · Source |
| CVE-2026-33997 | suse_vex | SUSE CVE CVE-2026-33997 | known affected: 139 recommended: 70 | 2026-07-27T17:07:28+00:00 | Vulnerability · Source |
| CVE-2026-34040 | suse_vex | SUSE CVE CVE-2026-34040 | known affected: 138 recommended: 64 | 2026-07-27T17:07:27+00:00 | Vulnerability · Source |
| CVE-2026-34180 | suse_vex | SUSE CVE CVE-2026-34180 | known affected: 503 known not affected: 84 recommended: 362 | 2026-07-27T17:07:26+00:00 | Vulnerability · Source |
| CVE-2026-34182 | suse_vex | SUSE CVE CVE-2026-34182 | first fixed: 45 known affected: 443 known not affected: 388 recommended: 108 | 2026-07-27T17:07:24+00:00 | Vulnerability · Source |
| CVE-2026-34980 | suse_vex | SUSE CVE CVE-2026-34980 | known affected: 623 recommended: 159 | 2026-07-27T17:07:21+00:00 | Vulnerability · Source |
| CVE-2026-39820 | suse_vex | SUSE CVE CVE-2026-39820 | known affected: 67 known not affected: 51 recommended: 275 | 2026-07-27T17:07:11+00:00 | Vulnerability · Source |
| CVE-2026-39829 | suse_vex | SUSE CVE CVE-2026-39829 | known affected: 754 known not affected: 254 recommended: 484 | 2026-07-27T17:07:07+00:00 | Vulnerability · Source |
| CVE-2026-39830 | suse_vex | SUSE CVE CVE-2026-39830 | known affected: 754 known not affected: 254 recommended: 485 | 2026-07-27T17:07:06+00:00 | Vulnerability · Source |
| CVE-2026-39832 | suse_vex | SUSE CVE CVE-2026-39832 | known affected: 362 known not affected: 254 recommended: 445 | 2026-07-27T17:07:04+00:00 | Vulnerability · Source |
| CVE-2026-39835 | suse_vex | SUSE CVE CVE-2026-39835 | known affected: 362 known not affected: 254 recommended: 420 | 2026-07-27T17:07:02+00:00 | Vulnerability · Source |
| CVE-2026-40033 | suse_vex | SUSE CVE CVE-2026-40033 | known affected: 90 recommended: 73 | 2026-07-27T17:07:00+00:00 | Vulnerability · Source |
| CVE-2026-41035 | suse_vex | SUSE CVE CVE-2026-41035 | known affected: 407 recommended: 43 | 2026-07-27T17:06:55+00:00 | Vulnerability · Source |
| CVE-2026-41568 | suse_vex | SUSE CVE CVE-2026-41568 | known affected: 181 | 2026-07-27T17:06:50+00:00 | Vulnerability · Source |
| CVE-2026-41603 | suse_vex | SUSE CVE CVE-2026-41603 | known affected: 30 known not affected: 408 recommended: 132 | 2026-07-27T17:06:48+00:00 | Vulnerability · Source |
| CVE-2026-41636 | suse_vex | SUSE CVE CVE-2026-41636 | known affected: 66 known not affected: 408 recommended: 10 | 2026-07-27T17:06:46+00:00 | Vulnerability · Source |
| CVE-2026-41991 | suse_vex | SUSE CVE CVE-2026-41991 | first fixed: 24 known affected: 32 recommended: 7 | 2026-07-27T17:06:35+00:00 | Vulnerability · Source |
| CVE-2026-41992 | suse_vex | SUSE CVE CVE-2026-41992 | known affected: 38 | 2026-07-27T17:06:34+00:00 | Vulnerability · Source |
| CVE-2026-42009 | suse_vex | SUSE CVE CVE-2026-42009 | known affected: 448 recommended: 251 | 2026-07-27T17:06:31+00:00 | Vulnerability · Source |
| CVE-2026-42010 | suse_vex | SUSE CVE CVE-2026-42010 | known affected: 469 recommended: 225 | 2026-07-27T17:06:30+00:00 | Vulnerability · Source |
| CVE-2026-42011 | suse_vex | SUSE CVE CVE-2026-42011 | known affected: 466 recommended: 242 | 2026-07-27T17:06:29+00:00 | Vulnerability · Source |
| CVE-2026-42013 | suse_vex | SUSE CVE CVE-2026-42013 | known affected: 466 recommended: 242 | 2026-07-27T17:06:27+00:00 | Vulnerability · Source |
| CVE-2026-42014 | suse_vex | SUSE CVE CVE-2026-42014 | known affected: 466 recommended: 242 | 2026-07-27T17:06:26+00:00 | Vulnerability · Source |
| CVE-2026-42015 | suse_vex | SUSE CVE CVE-2026-42015 | known affected: 466 recommended: 242 | 2026-07-27T17:06:25+00:00 | Vulnerability · Source |
| CVE-2026-42041 | suse_vex | SUSE CVE CVE-2026-42041 | known affected: 134 known not affected: 258 recommended: 1 | 2026-07-27T17:06:23+00:00 | Vulnerability · Source |
| CVE-2026-42043 | suse_vex | SUSE CVE CVE-2026-42043 | known not affected: 392 | 2026-07-27T17:06:22+00:00 | Vulnerability · Source |
| CVE-2026-42151 | suse_vex | SUSE CVE CVE-2026-42151 | known affected: 3 recommended: 110 | 2026-07-27T17:06:21+00:00 | Vulnerability · Source |
| CVE-2026-42154 | suse_vex | SUSE CVE CVE-2026-42154 | known affected: 3 recommended: 110 | 2026-07-27T17:06:20+00:00 | Vulnerability · Source |
| CVE-2026-42338 | suse_vex | SUSE CVE CVE-2026-42338 | known affected: 182 recommended: 109 | 2026-07-27T17:06:17+00:00 | Vulnerability · Source |