VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
290591 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-4379 | suse_vex | SUSE CVE CVE-2022-4379 | known affected: 284 known not affected: 297 recommended: 683 | 2026-08-13T02:35:31+00:00 | Vulnerability · Source |
| CVE-2026-19548 | redhat_vex | binutils: binutils: Multiple Use-After-Free in add_archive_element via LTO plugin processing | known affected: 55 | 2026-08-13T02:35:30+00:00 | Vulnerability · Source |
| CVE-2026-19139 | redhat_vex | chromium-browser: Google Chrome: OS-level privilege escalation due to a race condition via a malicious file | known not affected: 1 | 2026-08-13T02:35:29+00:00 | Vulnerability · Source |
| CVE-2022-4382 | suse_vex | SUSE CVE CVE-2022-4382 | known affected: 235 known not affected: 522 recommended: 827 | 2026-08-13T02:35:29+00:00 | Vulnerability · Source |
| CVE-2022-4645 | suse_vex | SUSE CVE CVE-2022-4645 | known not affected: 154 recommended: 6 | 2026-08-13T02:35:27+00:00 | Vulnerability · Source |
| CVE-2026-19167 | redhat_vex | chromium-browser: Google Chrome: Cross-origin data leakage via integer overflow in GPU | known not affected: 1 | 2026-08-13T02:35:25+00:00 | Vulnerability · Source |
| CVE-2026-19146 | redhat_vex | chromium-browser: Google Chrome (Android): Information disclosure via uninitialized GPU memory use | known not affected: 1 | 2026-08-13T02:35:25+00:00 | Vulnerability · Source |
| CVE-2022-4662 | suse_vex | SUSE CVE CVE-2022-4662 | known affected: 255 known not affected: 102 recommended: 1369 | 2026-08-13T02:35:25+00:00 | Vulnerability · Source |
| CVE-2022-4743 | suse_vex | SUSE CVE CVE-2022-4743 | known affected: 68 known not affected: 225 recommended: 70 | 2026-08-13T02:35:24+00:00 | Vulnerability · Source |
| CVE-2022-4744 | suse_vex | SUSE CVE CVE-2022-4744 | known affected: 201 known not affected: 126 recommended: 1318 | 2026-08-13T02:35:22+00:00 | Vulnerability · Source |
| CVE-2022-4842 | suse_vex | SUSE CVE CVE-2022-4842 | known not affected: 362 | 2026-08-13T02:35:20+00:00 | Vulnerability · Source |
| CVE-2022-4886 | suse_vex | SUSE CVE CVE-2022-4886 | known not affected: 322 | 2026-08-13T02:35:18+00:00 | Vulnerability · Source |
| CVE-2022-20132 | suse_vex | SUSE CVE CVE-2022-20132 | known affected: 219 recommended: 1558 | 2026-08-13T02:35:16+00:00 | Vulnerability · Source |
| CVE-2022-20369 | suse_vex | SUSE CVE CVE-2022-20369 | known affected: 237 recommended: 1509 | 2026-08-13T02:35:12+00:00 | Vulnerability · Source |
| CVE-2022-20567 | suse_vex | SUSE CVE CVE-2022-20567 | known affected: 394 known not affected: 186 recommended: 204 | 2026-08-13T02:35:11+00:00 | Vulnerability · Source |
| CVE-2022-21125 | suse_vex | SUSE CVE CVE-2022-21125 | known affected: 254 recommended: 1953 | 2026-08-13T02:35:09+00:00 | Vulnerability · Source |
| CVE-2022-21127 | suse_vex | SUSE CVE CVE-2022-21127 | recommended: 1381 | 2026-08-13T02:35:07+00:00 | Vulnerability · Source |
| CVE-2022-21294 | suse_vex | SUSE CVE CVE-2022-21294 | known affected: 406 known not affected: 32 recommended: 1069 | 2026-08-13T02:35:00+00:00 | Vulnerability · Source |
| CVE-2022-21341 | suse_vex | SUSE CVE CVE-2022-21341 | known affected: 406 known not affected: 32 recommended: 1076 | 2026-08-13T02:34:58+00:00 | Vulnerability · Source |
| CVE-2022-21455 | suse_vex | SUSE CVE CVE-2022-21455 | recommended: 17 | 2026-08-13T02:34:50+00:00 | Vulnerability · Source |
| CVE-2022-21504 | suse_vex | SUSE CVE CVE-2022-21504 | known not affected: 233 | 2026-08-13T02:34:47+00:00 | Vulnerability · Source |
| CVE-2022-21505 | suse_vex | SUSE CVE CVE-2022-21505 | known affected: 234 known not affected: 175 recommended: 1137 | 2026-08-13T02:34:45+00:00 | Vulnerability · Source |
| CVE-2022-21569 | suse_vex | SUSE CVE CVE-2022-21569 | recommended: 17 | 2026-08-13T02:34:43+00:00 | Vulnerability · Source |
| CVE-2022-21658 | suse_vex | SUSE CVE CVE-2022-21658 | recommended: 355 | 2026-08-13T02:34:40+00:00 | Vulnerability · Source |
| CVE-2022-22637 | suse_vex | SUSE CVE CVE-2022-22637 | known affected: 24 known not affected: 374 recommended: 942 | 2026-08-13T02:34:39+00:00 | Vulnerability · Source |
| CVE-2022-22739 | suse_vex | SUSE CVE CVE-2022-22739 | recommended: 413 | 2026-08-13T02:34:36+00:00 | Vulnerability · Source |
| CVE-2022-22936 | suse_vex | SUSE CVE CVE-2022-22936 | known affected: 394 known not affected: 116 recommended: 799 | 2026-08-13T02:34:29+00:00 | Vulnerability · Source |
| CVE-2022-23036 | suse_vex | SUSE CVE CVE-2022-23036 | known affected: 344 known not affected: 61 recommended: 1327 | 2026-08-13T02:34:27+00:00 | Vulnerability · Source |
| CVE-2022-23037 | suse_vex | SUSE CVE CVE-2022-23037 | known affected: 344 known not affected: 61 recommended: 1327 | 2026-08-13T02:34:26+00:00 | Vulnerability · Source |
| CVE-2022-23039 | suse_vex | SUSE CVE CVE-2022-23039 | known affected: 344 known not affected: 61 recommended: 1327 | 2026-08-13T02:34:24+00:00 | Vulnerability · Source |
| CVE-2022-23222 | suse_vex | SUSE CVE CVE-2022-23222 | known not affected: 368 recommended: 580 | 2026-08-13T02:34:22+00:00 | Vulnerability · Source |
| CVE-2022-23484 | suse_vex | SUSE CVE CVE-2022-23484 | known affected: 395 known not affected: 1 recommended: 202 | 2026-08-13T02:34:20+00:00 | Vulnerability · Source |
| CVE-2022-23639 | suse_vex | SUSE CVE CVE-2022-23639 | known affected: 62 known not affected: 343 | 2026-08-13T02:34:18+00:00 | Vulnerability · Source |
| CVE-2022-23772 | suse_vex | SUSE CVE CVE-2022-23772 | recommended: 180 | 2026-08-13T02:34:16+00:00 | Vulnerability · Source |
| CVE-2022-23820 | suse_vex | SUSE CVE CVE-2022-23820 | known affected: 22 recommended: 1381 | 2026-08-13T02:34:14+00:00 | Vulnerability · Source |
| CVE-2022-24048 | suse_vex | SUSE CVE CVE-2022-24048 | known affected: 1 recommended: 505 | 2026-08-13T02:34:12+00:00 | Vulnerability · Source |
| CVE-2022-24051 | suse_vex | SUSE CVE CVE-2022-24051 | known affected: 1 recommended: 505 | 2026-08-13T02:34:09+00:00 | Vulnerability · Source |
| CVE-2022-24769 | suse_vex | SUSE CVE CVE-2022-24769 | known affected: 350 recommended: 434 | 2026-08-13T02:34:05+00:00 | Vulnerability · Source |
| CVE-2022-24795 | suse_vex | SUSE CVE CVE-2022-24795 | known affected: 267 recommended: 293 | 2026-08-13T02:34:03+00:00 | Vulnerability · Source |
| CVE-2022-24834 | suse_vex | SUSE CVE CVE-2022-24834 | recommended: 39 | 2026-08-13T02:34:01+00:00 | Vulnerability · Source |
| CVE-2022-24883 | suse_vex | SUSE CVE CVE-2022-24883 | recommended: 185 | 2026-08-13T02:33:59+00:00 | Vulnerability · Source |
| CVE-2022-24921 | suse_vex | SUSE CVE CVE-2022-24921 | recommended: 188 | 2026-08-13T02:33:57+00:00 | Vulnerability · Source |
| CVE-2022-25375 | suse_vex | SUSE CVE CVE-2022-25375 | known affected: 207 known not affected: 252 recommended: 927 | 2026-08-13T02:33:48+00:00 | Vulnerability · Source |
| CVE-2022-25634 | suse_vex | SUSE CVE CVE-2022-25634 | known not affected: 2075 | 2026-08-13T02:33:47+00:00 | Vulnerability · Source |
| CVE-2022-25881 | suse_vex | SUSE CVE CVE-2022-25881 | known not affected: 17 recommended: 450 | 2026-08-13T02:33:45+00:00 | Vulnerability · Source |
| CVE-2022-26362 | suse_vex | SUSE CVE CVE-2022-26362 | known affected: 215 recommended: 564 | 2026-08-13T02:33:41+00:00 | Vulnerability · Source |
| CVE-2022-26365 | suse_vex | SUSE CVE CVE-2022-26365 | known affected: 249 known not affected: 216 recommended: 1575 | 2026-08-13T02:33:38+00:00 | Vulnerability · Source |
| CVE-2022-26373 | suse_vex | SUSE CVE CVE-2022-26373 | known affected: 236 recommended: 1565 | 2026-08-13T02:33:36+00:00 | Vulnerability · Source |
| CVE-2022-26384 | suse_vex | SUSE CVE CVE-2022-26384 | known affected: 1 recommended: 411 | 2026-08-13T02:33:34+00:00 | Vulnerability · Source |
| CVE-2022-26488 | suse_vex | SUSE CVE CVE-2022-26488 | known not affected: 508 | 2026-08-13T02:33:32+00:00 | Vulnerability · Source |