VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283445 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-27405 | suse_vex | SUSE CVE CVE-2022-27405 | known affected: 237 known not affected: 130 recommended: 460 | 2026-07-25T17:25:34+00:00 | Vulnerability · Source |
| CVE-2022-27406 | suse_vex | SUSE CVE CVE-2022-27406 | known affected: 248 known not affected: 65 recommended: 466 | 2026-07-25T17:25:33+00:00 | Vulnerability · Source |
| CVE-2022-27446 | suse_vex | SUSE CVE CVE-2022-27446 | known not affected: 216 recommended: 378 | 2026-07-25T17:25:32+00:00 | Vulnerability · Source |
| CVE-2022-27447 | suse_vex | SUSE CVE CVE-2022-27447 | known not affected: 93 recommended: 378 | 2026-07-25T17:25:30+00:00 | Vulnerability · Source |
| CVE-2022-27455 | suse_vex | SUSE CVE CVE-2022-27455 | known not affected: 216 recommended: 378 | 2026-07-25T17:25:29+00:00 | Vulnerability · Source |
| CVE-2022-27456 | suse_vex | SUSE CVE CVE-2022-27456 | known not affected: 93 recommended: 378 | 2026-07-25T17:25:28+00:00 | Vulnerability · Source |
| CVE-2022-27775 | suse_vex | SUSE CVE CVE-2022-27775 | known affected: 280 known not affected: 140 recommended: 313 | 2026-07-25T17:25:26+00:00 | Vulnerability · Source |
| CVE-2022-27779 | suse_vex | SUSE CVE CVE-2022-27779 | known affected: 304 known not affected: 209 recommended: 174 | 2026-07-25T17:25:25+00:00 | Vulnerability · Source |
| CVE-2022-27780 | suse_vex | SUSE CVE CVE-2022-27780 | known affected: 304 known not affected: 209 recommended: 174 | 2026-07-25T17:25:24+00:00 | Vulnerability · Source |
| CVE-2022-27781 | suse_vex | SUSE CVE CVE-2022-27781 | known affected: 263 known not affected: 32 recommended: 458 | 2026-07-25T17:25:22+00:00 | Vulnerability · Source |
| CVE-2022-27782 | suse_vex | SUSE CVE CVE-2022-27782 | known affected: 263 known not affected: 32 recommended: 467 | 2026-07-25T17:25:21+00:00 | Vulnerability · Source |
| CVE-2022-27943 | suse_vex | SUSE CVE CVE-2022-27943 | known affected: 407 known not affected: 6 recommended: 461 | 2026-07-25T17:25:20+00:00 | Vulnerability · Source |
| CVE-2022-28348 | suse_vex | SUSE CVE CVE-2022-28348 | known not affected: 390 | 2026-07-25T17:25:18+00:00 | Vulnerability · Source |
| CVE-2022-28390 | suse_vex | SUSE CVE CVE-2022-28390 | known affected: 216 known not affected: 4 recommended: 1543 | 2026-07-25T17:25:16+00:00 | Vulnerability · Source |
| CVE-2022-28506 | suse_vex | SUSE CVE CVE-2022-28506 | known not affected: 171 recommended: 98 | 2026-07-25T17:25:15+00:00 | Vulnerability · Source |
| CVE-2022-28615 | suse_vex | SUSE CVE CVE-2022-28615 | known affected: 395 recommended: 544 | 2026-07-25T17:25:13+00:00 | Vulnerability · Source |
| CVE-2022-28693 | suse_vex | SUSE CVE CVE-2022-28693 | known affected: 251 known not affected: 34 recommended: 1533 | 2026-07-25T17:25:11+00:00 | Vulnerability · Source |
| CVE-2022-28733 | suse_vex | SUSE CVE CVE-2022-28733 | known affected: 353 recommended: 737 | 2026-07-25T17:25:10+00:00 | Vulnerability · Source |
| CVE-2022-28736 | suse_vex | SUSE CVE CVE-2022-28736 | known affected: 353 recommended: 724 | 2026-07-25T17:25:08+00:00 | Vulnerability · Source |
| CVE-2022-29154 | suse_vex | SUSE CVE CVE-2022-29154 | known affected: 395 recommended: 95 | 2026-07-25T17:25:07+00:00 | Vulnerability · Source |
| CVE-2022-29187 | suse_vex | SUSE CVE CVE-2022-29187 | known affected: 1 recommended: 1047 | 2026-07-25T17:25:06+00:00 | Vulnerability · Source |
| CVE-2022-29404 | suse_vex | SUSE CVE CVE-2022-29404 | known affected: 395 known not affected: 1 recommended: 538 | 2026-07-25T17:25:04+00:00 | Vulnerability · Source |
| CVE-2022-29582 | suse_vex | SUSE CVE CVE-2022-29582 | known affected: 193 known not affected: 343 recommended: 679 | 2026-07-25T17:25:03+00:00 | Vulnerability · Source |
| CVE-2022-29900 | suse_vex | SUSE CVE CVE-2022-29900 | known affected: 189 recommended: 2218 | 2026-07-25T17:25:01+00:00 | Vulnerability · Source |
| CVE-2022-29909 | suse_vex | SUSE CVE CVE-2022-29909 | known not affected: 2 recommended: 405 | 2026-07-25T17:24:59+00:00 | Vulnerability · Source |
| CVE-2022-29911 | suse_vex | SUSE CVE CVE-2022-29911 | known not affected: 2 recommended: 405 | 2026-07-25T17:24:58+00:00 | Vulnerability · Source |
| CVE-2022-29912 | suse_vex | SUSE CVE CVE-2022-29912 | known not affected: 2 recommended: 405 | 2026-07-25T17:24:57+00:00 | Vulnerability · Source |
| CVE-2022-29914 | suse_vex | SUSE CVE CVE-2022-29914 | known not affected: 2 recommended: 405 | 2026-07-25T17:24:56+00:00 | Vulnerability · Source |
| CVE-2022-30115 | suse_vex | SUSE CVE CVE-2022-30115 | known affected: 304 known not affected: 209 recommended: 174 | 2026-07-25T17:24:54+00:00 | Vulnerability · Source |
| CVE-2022-30550 | suse_vex | SUSE CVE CVE-2022-30550 | known affected: 13 known not affected: 61 recommended: 523 | 2026-07-25T17:24:52+00:00 | Vulnerability · Source |
| CVE-2022-30556 | suse_vex | SUSE CVE CVE-2022-30556 | known affected: 395 known not affected: 1 recommended: 538 | 2026-07-25T17:24:51+00:00 | Vulnerability · Source |
| CVE-2022-30786 | suse_vex | SUSE CVE CVE-2022-30786 | recommended: 247 | 2026-07-25T17:24:50+00:00 | Vulnerability · Source |
| CVE-2022-31736 | suse_vex | SUSE CVE CVE-2022-31736 | known not affected: 1 recommended: 405 | 2026-07-25T17:24:48+00:00 | Vulnerability · Source |
| CVE-2022-31738 | suse_vex | SUSE CVE CVE-2022-31738 | known not affected: 1 recommended: 405 | 2026-07-25T17:24:46+00:00 | Vulnerability · Source |
| CVE-2022-31741 | suse_vex | SUSE CVE CVE-2022-31741 | recommended: 1720 | 2026-07-25T17:24:45+00:00 | Vulnerability · Source |
| CVE-2022-31744 | suse_vex | SUSE CVE CVE-2022-31744 | known not affected: 1 recommended: 405 | 2026-07-25T17:24:44+00:00 | Vulnerability · Source |
| CVE-2022-31747 | suse_vex | SUSE CVE CVE-2022-31747 | known not affected: 1 recommended: 405 | 2026-07-25T17:24:42+00:00 | Vulnerability · Source |
| CVE-2022-31782 | suse_vex | SUSE CVE CVE-2022-31782 | known not affected: 57 recommended: 10 | 2026-07-25T17:24:41+00:00 | Vulnerability · Source |
| CVE-2022-31783 | suse_vex | SUSE CVE CVE-2022-31783 | known not affected: 63 recommended: 247 | 2026-07-25T17:24:40+00:00 | Vulnerability · Source |
| CVE-2022-31813 | suse_vex | SUSE CVE CVE-2022-31813 | known affected: 394 recommended: 544 | 2026-07-25T17:24:39+00:00 | Vulnerability · Source |
| CVE-2022-32081 | suse_vex | SUSE CVE CVE-2022-32081 | known not affected: 217 recommended: 387 | 2026-07-25T17:24:37+00:00 | Vulnerability · Source |
| CVE-2022-32084 | suse_vex | SUSE CVE CVE-2022-32084 | known not affected: 94 recommended: 455 | 2026-07-25T17:24:36+00:00 | Vulnerability · Source |
| CVE-2022-32089 | suse_vex | SUSE CVE CVE-2022-32089 | known not affected: 217 recommended: 387 | 2026-07-25T17:24:35+00:00 | Vulnerability · Source |
| CVE-2022-32091 | suse_vex | SUSE CVE CVE-2022-32091 | known not affected: 217 recommended: 387 | 2026-07-25T17:24:34+00:00 | Vulnerability · Source |
| CVE-2022-32205 | suse_vex | SUSE CVE CVE-2022-32205 | known affected: 254 known not affected: 171 recommended: 270 | 2026-07-25T17:24:32+00:00 | Vulnerability · Source |
| CVE-2022-32250 | suse_vex | SUSE CVE CVE-2022-32250 | known affected: 237 recommended: 1400 | 2026-07-25T17:24:30+00:00 | Vulnerability · Source |
| CVE-2022-32546 | suse_vex | SUSE CVE CVE-2022-32546 | recommended: 523 | 2026-07-25T17:24:29+00:00 | Vulnerability · Source |
| CVE-2022-32745 | suse_vex | SUSE CVE CVE-2022-32745 | known affected: 231 known not affected: 1783 recommended: 1289 | 2026-07-25T17:24:27+00:00 | Vulnerability · Source |
| CVE-2022-32792 | suse_vex | SUSE CVE CVE-2022-32792 | known affected: 1 recommended: 981 | 2026-07-25T17:24:26+00:00 | Vulnerability · Source |
| CVE-2022-33068 | suse_vex | SUSE CVE CVE-2022-33068 | known affected: 394 known not affected: 139 recommended: 469 | 2026-07-25T17:24:24+00:00 | Vulnerability · Source |