VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291949 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-23824 | suse_vex | SUSE CVE CVE-2022-23824 | known affected: 274 recommended: 381 | 2026-07-25T17:26:21+00:00 | Vulnerability · Source |
| CVE-2022-23901 | suse_vex | SUSE CVE CVE-2022-23901 | known not affected: 66 | 2026-07-25T17:26:19+00:00 | Vulnerability · Source |
| CVE-2022-23990 | suse_vex | SUSE CVE CVE-2022-23990 | known affected: 339 known not affected: 32 recommended: 373 | 2026-07-25T17:26:16+00:00 | Vulnerability · Source |
| CVE-2022-24107 | suse_vex | SUSE CVE CVE-2022-24107 | known affected: 1 known not affected: 259 | 2026-07-25T17:26:13+00:00 | Vulnerability · Source |
| CVE-2022-24765 | suse_vex | SUSE CVE CVE-2022-24765 | recommended: 1094 | 2026-07-25T17:26:09+00:00 | Vulnerability · Source |
| CVE-2022-25235 | suse_vex | SUSE CVE CVE-2022-25235 | known affected: 282 recommended: 449 | 2026-07-25T17:26:05+00:00 | Vulnerability · Source |
| CVE-2022-25265 | suse_vex | SUSE CVE CVE-2022-25265 | known not affected: 3490 recommended: 20 | 2026-07-25T17:26:00+00:00 | Vulnerability · Source |
| CVE-2022-25309 | suse_vex | SUSE CVE CVE-2022-25309 | known affected: 437 recommended: 205 | 2026-07-25T17:25:58+00:00 | Vulnerability · Source |
| CVE-2022-25310 | suse_vex | SUSE CVE CVE-2022-25310 | known affected: 437 recommended: 205 | 2026-07-25T17:25:57+00:00 | Vulnerability · Source |
| CVE-2022-25368 | suse_vex | SUSE CVE CVE-2022-25368 | known not affected: 401 | 2026-07-25T17:25:54+00:00 | Vulnerability · Source |
| CVE-2022-26356 | suse_vex | SUSE CVE CVE-2022-26356 | known affected: 349 known not affected: 46 recommended: 453 | 2026-07-25T17:25:52+00:00 | Vulnerability · Source |
| CVE-2022-26357 | suse_vex | SUSE CVE CVE-2022-26357 | known affected: 349 known not affected: 74 recommended: 446 | 2026-07-25T17:25:51+00:00 | Vulnerability · Source |
| CVE-2022-26381 | suse_vex | SUSE CVE CVE-2022-26381 | known affected: 1 recommended: 411 | 2026-07-25T17:25:49+00:00 | Vulnerability · Source |
| CVE-2022-27381 | suse_vex | SUSE CVE CVE-2022-27381 | known not affected: 93 recommended: 490 | 2026-07-25T17:25:40+00:00 | Vulnerability · Source |
| CVE-2022-27385 | suse_vex | SUSE CVE CVE-2022-27385 | known not affected: 347 recommended: 16 | 2026-07-25T17:25:37+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-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-28348 | suse_vex | SUSE CVE CVE-2022-28348 | known not affected: 390 | 2026-07-25T17:25:18+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-29187 | suse_vex | SUSE CVE CVE-2022-29187 | known affected: 1 recommended: 1047 | 2026-07-25T17:25:06+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-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-31741 | suse_vex | SUSE CVE CVE-2022-31741 | recommended: 1720 | 2026-07-25T17:24:45+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-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-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-32546 | suse_vex | SUSE CVE CVE-2022-32546 | recommended: 523 | 2026-07-25T17:24:29+00:00 | Vulnerability · Source |
| CVE-2022-33103 | suse_vex | SUSE CVE CVE-2022-33103 | known affected: 1 known not affected: 72 recommended: 344 | 2026-07-25T17:24:22+00:00 | Vulnerability · Source |
| CVE-2022-33745 | suse_vex | SUSE CVE CVE-2022-33745 | known affected: 231 recommended: 548 | 2026-07-25T17:24:19+00:00 | Vulnerability · Source |
| CVE-2022-33747 | suse_vex | SUSE CVE CVE-2022-33747 | known affected: 253 recommended: 309 | 2026-07-25T17:24:18+00:00 | Vulnerability · Source |
| CVE-2022-33748 | suse_vex | SUSE CVE CVE-2022-33748 | known affected: 252 recommended: 517 | 2026-07-25T17:24:16+00:00 | Vulnerability · Source |
| CVE-2022-33972 | suse_vex | SUSE CVE CVE-2022-33972 | known not affected: 1 recommended: 69 | 2026-07-25T17:24:15+00:00 | Vulnerability · Source |
| CVE-2022-34301 | suse_vex | SUSE CVE CVE-2022-34301 | known not affected: 59 recommended: 3 | 2026-07-25T17:24:12+00:00 | Vulnerability · Source |
| CVE-2022-34302 | suse_vex | SUSE CVE CVE-2022-34302 | known not affected: 59 recommended: 3 | 2026-07-25T17:24:11+00:00 | Vulnerability · Source |
| CVE-2022-34485 | suse_vex | SUSE CVE CVE-2022-34485 | known affected: 1 recommended: 365 | 2026-07-25T17:24:06+00:00 | Vulnerability · Source |
| CVE-2022-34495 | suse_vex | SUSE CVE CVE-2022-34495 | known not affected: 377 | 2026-07-25T17:24:05+00:00 | Vulnerability · Source |
| CVE-2022-34835 | suse_vex | SUSE CVE CVE-2022-34835 | recommended: 401 | 2026-07-25T17:24:03+00:00 | Vulnerability · Source |
| CVE-2022-35230 | suse_vex | SUSE CVE CVE-2022-35230 | known affected: 23 recommended: 15 | 2026-07-25T17:23:56+00:00 | Vulnerability · Source |
| CVE-2022-36123 | suse_vex | SUSE CVE CVE-2022-36123 | known not affected: 327 | 2026-07-25T17:23:54+00:00 | Vulnerability · Source |
| CVE-2022-36227 | suse_vex | SUSE CVE CVE-2022-36227 | known affected: 444 known not affected: 27 recommended: 138 | 2026-07-25T17:23:53+00:00 | Vulnerability · Source |
| CVE-2022-36318 | suse_vex | SUSE CVE CVE-2022-36318 | known affected: 1 recommended: 461 | 2026-07-25T17:23:52+00:00 | Vulnerability · Source |
| CVE-2022-36319 | suse_vex | SUSE CVE CVE-2022-36319 | known affected: 1 recommended: 461 | 2026-07-25T17:23:50+00:00 | Vulnerability · Source |
| CVE-2022-36648 | suse_vex | SUSE CVE CVE-2022-36648 | known affected: 1287 known not affected: 640 | 2026-07-25T17:23:47+00:00 | Vulnerability · Source |
| CVE-2022-37051 | suse_vex | SUSE CVE CVE-2022-37051 | known affected: 64 known not affected: 5 recommended: 270 | 2026-07-25T17:23:41+00:00 | Vulnerability · Source |
| CVE-2022-37052 | suse_vex | SUSE CVE CVE-2022-37052 | known affected: 202 known not affected: 5 recommended: 185 | 2026-07-25T17:23:39+00:00 | Vulnerability · Source |
| CVE-2022-38171 | suse_vex | SUSE CVE CVE-2022-38171 | known not affected: 324 | 2026-07-25T17:23:26+00:00 | Vulnerability · Source |
| CVE-2022-38228 | suse_vex | SUSE CVE CVE-2022-38228 | known not affected: 330 | 2026-07-25T17:23:23+00:00 | Vulnerability · Source |
| CVE-2022-38234 | suse_vex | SUSE CVE CVE-2022-38234 | known not affected: 330 | 2026-07-25T17:23:22+00:00 | Vulnerability · Source |