VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291704 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-43208 | suse_vex | SUSE CVE CVE-2026-43208 | known not affected: 293 | 2026-08-06T01:21:00+00:00 | Vulnerability · Source |
| CVE-2026-43212 | suse_vex | SUSE CVE CVE-2026-43212 | known not affected: 293 | 2026-08-06T01:20:58+00:00 | Vulnerability · Source |
| CVE-2026-43213 | suse_vex | SUSE CVE CVE-2026-43213 | first fixed: 2 known affected: 202 known not affected: 93 recommended: 145 | 2026-08-06T01:20:57+00:00 | Vulnerability · Source |
| CVE-2026-43233 | suse_vex | SUSE CVE CVE-2026-43233 | first fixed: 2 known affected: 555 known not affected: 21 recommended: 302 | 2026-08-06T01:20:51+00:00 | Vulnerability · Source |
| CVE-2026-43237 | suse_vex | SUSE CVE CVE-2026-43237 | known not affected: 293 recommended: 27 | 2026-08-06T01:20:49+00:00 | Vulnerability · Source |
| CVE-2026-43245 | suse_vex | SUSE CVE CVE-2026-43245 | known not affected: 293 | 2026-08-06T01:20:46+00:00 | Vulnerability · Source |
| CVE-2026-43249 | suse_vex | SUSE CVE CVE-2026-43249 | known affected: 424 known not affected: 198 recommended: 122 | 2026-08-06T01:20:44+00:00 | Vulnerability · Source |
| CVE-2026-43254 | suse_vex | SUSE CVE CVE-2026-43254 | known not affected: 293 | 2026-08-06T01:20:43+00:00 | Vulnerability · Source |
| CVE-2026-43258 | suse_vex | SUSE CVE CVE-2026-43258 | known not affected: 293 | 2026-08-06T01:20:41+00:00 | Vulnerability · Source |
| CVE-2026-43263 | suse_vex | SUSE CVE CVE-2026-43263 | known affected: 72 known not affected: 223 | 2026-08-06T01:20:40+00:00 | Vulnerability · Source |
| CVE-2026-43274 | suse_vex | SUSE CVE CVE-2026-43274 | known not affected: 293 | 2026-08-06T01:20:38+00:00 | Vulnerability · Source |
| CVE-2026-43280 | suse_vex | SUSE CVE CVE-2026-43280 | known not affected: 293 | 2026-08-06T01:20:36+00:00 | Vulnerability · Source |
| CVE-2026-43283 | suse_vex | SUSE CVE CVE-2026-43283 | first fixed: 2 known affected: 291 known not affected: 4 recommended: 145 | 2026-08-06T01:20:35+00:00 | Vulnerability · Source |
| CVE-2026-43321 | suse_vex | SUSE CVE CVE-2026-43321 | known not affected: 293 | 2026-08-06T01:20:32+00:00 | Vulnerability · Source |
| CVE-2026-43322 | suse_vex | SUSE CVE CVE-2026-43322 | known not affected: 293 recommended: 42 | 2026-08-06T01:20:31+00:00 | Vulnerability · Source |
| CVE-2026-43332 | suse_vex | SUSE CVE CVE-2026-43332 | first fixed: 2 known affected: 508 known not affected: 181 recommended: 172 | 2026-08-06T01:20:28+00:00 | Vulnerability · Source |
| CVE-2026-43347 | suse_vex | SUSE CVE CVE-2026-43347 | known not affected: 293 | 2026-08-06T01:20:25+00:00 | Vulnerability · Source |
| CVE-2026-43350 | suse_vex | SUSE CVE CVE-2026-43350 | known affected: 289 known not affected: 6 recommended: 4 | 2026-08-06T01:20:24+00:00 | Vulnerability · Source |
| CVE-2026-43374 | suse_vex | SUSE CVE CVE-2026-43374 | first fixed: 2 known affected: 17 known not affected: 278 recommended: 145 | 2026-08-06T01:20:18+00:00 | Vulnerability · Source |
| CVE-2026-43376 | suse_vex | SUSE CVE CVE-2026-43376 | known not affected: 293 | 2026-08-06T01:20:16+00:00 | Vulnerability · Source |
| CVE-2026-43377 | suse_vex | SUSE CVE CVE-2026-43377 | known not affected: 293 | 2026-08-06T01:20:15+00:00 | Vulnerability · Source |
| CVE-2026-43378 | suse_vex | SUSE CVE CVE-2026-43378 | known affected: 30 known not affected: 263 | 2026-08-06T01:20:14+00:00 | Vulnerability · Source |
| CVE-2026-43379 | suse_vex | SUSE CVE CVE-2026-43379 | known affected: 17 known not affected: 278 | 2026-08-06T01:20:12+00:00 | Vulnerability · Source |
| CVE-2026-43384 | suse_vex | SUSE CVE CVE-2026-43384 | first fixed: 2 known affected: 17 known not affected: 278 recommended: 172 | 2026-08-06T01:20:10+00:00 | Vulnerability · Source |
| CVE-2026-43385 | suse_vex | SUSE CVE CVE-2026-43385 | known not affected: 293 | 2026-08-06T01:20:08+00:00 | Vulnerability · Source |
| CVE-2026-43391 | suse_vex | SUSE CVE CVE-2026-43391 | known not affected: 293 | 2026-08-06T01:20:07+00:00 | Vulnerability · Source |
| CVE-2026-43402 | suse_vex | SUSE CVE CVE-2026-43402 | known not affected: 293 | 2026-08-06T01:20:06+00:00 | Vulnerability · Source |
| CVE-2026-43403 | suse_vex | SUSE CVE CVE-2026-43403 | first fixed: 2 known not affected: 278 recommended: 145 | 2026-08-06T01:20:05+00:00 | Vulnerability · Source |
| CVE-2026-43408 | suse_vex | SUSE CVE CVE-2026-43408 | known affected: 17 known not affected: 278 | 2026-08-06T01:20:02+00:00 | Vulnerability · Source |
| CVE-2026-43433 | suse_vex | SUSE CVE CVE-2026-43433 | known not affected: 293 | 2026-08-06T01:20:00+00:00 | Vulnerability · Source |
| CVE-2026-43438 | suse_vex | SUSE CVE CVE-2026-43438 | known affected: 17 known not affected: 278 | 2026-08-06T01:19:58+00:00 | Vulnerability · Source |
| CVE-2026-43442 | suse_vex | SUSE CVE CVE-2026-43442 | known not affected: 293 | 2026-08-06T01:19:57+00:00 | Vulnerability · Source |
| CVE-2026-43454 | suse_vex | SUSE CVE CVE-2026-43454 | known not affected: 293 | 2026-08-06T01:19:54+00:00 | Vulnerability · Source |
| CVE-2026-43461 | suse_vex | SUSE CVE CVE-2026-43461 | known not affected: 293 | 2026-08-06T01:19:52+00:00 | Vulnerability · Source |
| CVE-2026-43462 | suse_vex | SUSE CVE CVE-2026-43462 | known not affected: 293 | 2026-08-06T01:19:50+00:00 | Vulnerability · Source |
| CVE-2026-43490 | suse_vex | SUSE CVE CVE-2026-43490 | known affected: 30 known not affected: 263 recommended: 4 | 2026-08-06T01:19:47+00:00 | Vulnerability · Source |
| CVE-2026-43498 | suse_vex | SUSE CVE CVE-2026-43498 | known not affected: 293 recommended: 4 | 2026-08-06T01:19:44+00:00 | Vulnerability · Source |
| CVE-2026-43500 | suse_vex | SUSE CVE CVE-2026-43500 | first fixed: 2 known affected: 394 known not affected: 159 recommended: 571 | 2026-08-06T01:19:40+00:00 | Vulnerability · Source |
| CVE-2026-43502 | suse_vex | SUSE CVE CVE-2026-43502 | first fixed: 2 known affected: 538 known not affected: 67 recommended: 269 | 2026-08-06T01:19:38+00:00 | Vulnerability · Source |
| CVE-2026-44223 | suse_vex | SUSE CVE CVE-2026-44223 | No product status | 2026-08-06T01:19:29+00:00 | Vulnerability · Source |
| CVE-2026-44945 | suse_vex | SUSE CVE CVE-2026-44945 | No product status | 2026-08-06T01:19:21+00:00 | Vulnerability · Source |
| CVE-2026-45859 | suse_vex | SUSE CVE CVE-2026-45859 | known affected: 17 known not affected: 278 | 2026-08-06T01:19:12+00:00 | Vulnerability · Source |
| CVE-2026-45861 | suse_vex | SUSE CVE CVE-2026-45861 | first fixed: 2 known affected: 17 known not affected: 278 recommended: 172 | 2026-08-06T01:19:09+00:00 | Vulnerability · Source |
| CVE-2026-45894 | suse_vex | SUSE CVE CVE-2026-45894 | first fixed: 2 known affected: 538 known not affected: 67 recommended: 294 | 2026-08-06T01:19:06+00:00 | Vulnerability · Source |
| CVE-2026-45898 | suse_vex | SUSE CVE CVE-2026-45898 | first fixed: 2 known affected: 394 known not affected: 223 recommended: 312 | 2026-08-06T01:19:05+00:00 | Vulnerability · Source |
| CVE-2026-45909 | suse_vex | SUSE CVE CVE-2026-45909 | known not affected: 293 | 2026-08-06T01:19:03+00:00 | Vulnerability · Source |
| CVE-2026-45929 | suse_vex | SUSE CVE CVE-2026-45929 | known not affected: 293 | 2026-08-06T01:19:00+00:00 | Vulnerability · Source |
| CVE-2026-45931 | suse_vex | SUSE CVE CVE-2026-45931 | known not affected: 293 | 2026-08-06T01:18:59+00:00 | Vulnerability · Source |
| CVE-2026-45933 | suse_vex | SUSE CVE CVE-2026-45933 | first fixed: 2 known affected: 17 known not affected: 278 recommended: 145 | 2026-08-06T01:18:57+00:00 | Vulnerability · Source |
| CVE-2026-45935 | suse_vex | SUSE CVE CVE-2026-45935 | known not affected: 293 | 2026-08-06T01:18:55+00:00 | Vulnerability · Source |