VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49018 | suse_vex | SUSE CVE CVE-2022-49018 | known not affected: 477 | 2026-10-16T14:31:46+00:00 | Vulnerability · Source |
| CVE-2022-49019 | suse_vex | SUSE CVE CVE-2022-49019 | known affected: 364 known not affected: 305 recommended: 478 | 2026-10-16T14:31:43+00:00 | Vulnerability · Source |
| CVE-2022-49020 | suse_vex | SUSE CVE CVE-2022-49020 | known affected: 647 known not affected: 48 recommended: 311 | 2026-10-16T14:31:41+00:00 | Vulnerability · Source |
| CVE-2022-49023 | suse_vex | SUSE CVE CVE-2022-49023 | known affected: 328 known not affected: 310 recommended: 523 | 2026-10-16T14:31:38+00:00 | Vulnerability · Source |
| CVE-2022-49025 | suse_vex | SUSE CVE CVE-2022-49025 | known affected: 335 known not affected: 301 recommended: 531 | 2026-10-16T14:31:36+00:00 | Vulnerability · Source |
| CVE-2022-49026 | suse_vex | SUSE CVE CVE-2022-49026 | known affected: 541 known not affected: 107 recommended: 434 | 2026-10-16T14:31:33+00:00 | Vulnerability · Source |
| CVE-2022-49030 | suse_vex | SUSE CVE CVE-2022-49030 | known affected: 187 known not affected: 318 | 2026-10-16T14:31:31+00:00 | Vulnerability · Source |
| CVE-2022-49031 | suse_vex | SUSE CVE CVE-2022-49031 | known affected: 433 known not affected: 181 recommended: 478 | 2026-10-16T14:31:29+00:00 | Vulnerability · Source |
| CVE-2022-49032 | suse_vex | SUSE CVE CVE-2022-49032 | known affected: 457 known not affected: 157 recommended: 478 | 2026-10-16T14:31:26+00:00 | Vulnerability · Source |
| CVE-2022-49033 | suse_vex | SUSE CVE CVE-2022-49033 | known affected: 718 known not affected: 48 recommended: 150 | 2026-10-16T14:31:25+00:00 | Vulnerability · Source |
| CVE-2022-49035 | suse_vex | SUSE CVE CVE-2022-49035 | known affected: 502 known not affected: 241 recommended: 355 | 2026-10-16T14:31:23+00:00 | Vulnerability · Source |
| CVE-2022-49045 | suse_vex | SUSE CVE CVE-2022-49045 | known affected: 0 known not affected: 171 | 2026-10-16T14:31:19+00:00 | Vulnerability · Source |
| CVE-2022-49046 | suse_vex | SUSE CVE CVE-2022-49046 | known affected: 663 known not affected: 140 recommended: 26 | 2026-10-16T14:31:17+00:00 | Vulnerability · Source |
| CVE-2022-49047 | suse_vex | SUSE CVE CVE-2022-49047 | known affected: 0 known not affected: 462 | 2026-10-16T14:31:14+00:00 | Vulnerability · Source |
| CVE-2022-49048 | suse_vex | SUSE CVE CVE-2022-49048 | known affected: 128 known not affected: 334 | 2026-10-16T14:31:11+00:00 | Vulnerability · Source |
| CVE-2022-49052 | suse_vex | SUSE CVE CVE-2022-49052 | known affected: 197 known not affected: 265 | 2026-10-16T14:31:09+00:00 | Vulnerability · Source |
| CVE-2022-49053 | suse_vex | SUSE CVE CVE-2022-49053 | known affected: 486 known not affected: 108 recommended: 362 | 2026-10-16T14:31:06+00:00 | Vulnerability · Source |
| CVE-2022-49054 | suse_vex | SUSE CVE CVE-2022-49054 | known affected: 334 known not affected: 398 recommended: 223 | 2026-10-16T14:31:04+00:00 | Vulnerability · Source |
| CVE-2022-49059 | suse_vex | SUSE CVE CVE-2022-49059 | known affected: 489 known not affected: 183 recommended: 333 | 2026-10-16T14:31:00+00:00 | Vulnerability · Source |
| CVE-2022-49060 | suse_vex | SUSE CVE CVE-2022-49060 | known affected: 476 known not affected: 238 recommended: 291 | 2026-10-16T14:30:58+00:00 | Vulnerability · Source |
| CVE-2022-49063 | suse_vex | SUSE CVE CVE-2022-49063 | known affected: 334 known not affected: 362 recommended: 335 | 2026-10-16T14:30:56+00:00 | Vulnerability · Source |
| CVE-2022-49066 | suse_vex | SUSE CVE CVE-2022-49066 | known affected: 530 known not affected: 150 recommended: 305 | 2026-10-16T14:30:52+00:00 | Vulnerability · Source |
| CVE-2022-49067 | suse_vex | SUSE CVE CVE-2022-49067 | known affected: 0 known not affected: 462 | 2026-10-16T14:30:51+00:00 | Vulnerability · Source |
| CVE-2022-49070 | suse_vex | SUSE CVE CVE-2022-49070 | known affected: 364 known not affected: 402 recommended: 154 | 2026-10-16T14:30:49+00:00 | Vulnerability · Source |
| CVE-2022-49071 | suse_vex | SUSE CVE CVE-2022-49071 | known affected: 364 known not affected: 402 recommended: 100 | 2026-10-16T14:30:47+00:00 | Vulnerability · Source |
| CVE-2022-49073 | suse_vex | SUSE CVE CVE-2022-49073 | known affected: 360 known not affected: 336 recommended: 293 | 2026-10-16T14:30:44+00:00 | Vulnerability · Source |
| CVE-2022-49075 | suse_vex | SUSE CVE CVE-2022-49075 | known affected: 596 known not affected: 115 recommended: 140 | 2026-10-16T14:30:42+00:00 | Vulnerability · Source |
| CVE-2022-49078 | suse_vex | SUSE CVE CVE-2022-49078 | known affected: 360 known not affected: 336 recommended: 293 | 2026-10-16T14:30:39+00:00 | Vulnerability · Source |
| CVE-2022-49079 | suse_vex | SUSE CVE CVE-2022-49079 | known affected: 0 known not affected: 462 | 2026-10-16T14:30:37+00:00 | Vulnerability · Source |
| CVE-2022-49080 | suse_vex | SUSE CVE CVE-2022-49080 | known affected: 506 known not affected: 78 recommended: 474 | 2026-10-16T14:30:34+00:00 | Vulnerability · Source |
| CVE-2022-49081 | suse_vex | SUSE CVE CVE-2022-49081 | known affected: 128 known not affected: 334 recommended: 74 | 2026-10-16T14:30:32+00:00 | Vulnerability · Source |
| CVE-2022-49083 | suse_vex | SUSE CVE CVE-2022-49083 | known affected: 334 known not affected: 362 recommended: 293 | 2026-10-16T14:30:28+00:00 | Vulnerability · Source |
| CVE-2022-49086 | suse_vex | SUSE CVE CVE-2022-49086 | known affected: 542 known not affected: 231 recommended: 291 | 2026-10-16T14:30:23+00:00 | Vulnerability · Source |
| CVE-2022-49089 | suse_vex | SUSE CVE CVE-2022-49089 | known affected: 448 known not affected: 232 recommended: 249 | 2026-10-16T14:30:21+00:00 | Vulnerability · Source |
| CVE-2022-49091 | suse_vex | SUSE CVE CVE-2022-49091 | known affected: 425 known not affected: 302 recommended: 293 | 2026-10-16T14:30:19+00:00 | Vulnerability · Source |
| CVE-2022-49092 | suse_vex | SUSE CVE CVE-2022-49092 | known affected: 0 known not affected: 394 recommended: 163 | 2026-10-16T14:30:16+00:00 | Vulnerability · Source |
| CVE-2022-49093 | suse_vex | SUSE CVE CVE-2022-49093 | known affected: 334 known not affected: 394 recommended: 245 | 2026-10-16T14:30:14+00:00 | Vulnerability · Source |
| CVE-2022-49094 | suse_vex | SUSE CVE CVE-2022-49094 | known affected: 197 known not affected: 265 | 2026-10-16T14:30:11+00:00 | Vulnerability · Source |
| CVE-2022-49095 | suse_vex | SUSE CVE CVE-2022-49095 | known affected: 487 known not affected: 222 recommended: 319 | 2026-10-16T14:30:09+00:00 | Vulnerability · Source |
| CVE-2022-49096 | suse_vex | SUSE CVE CVE-2022-49096 | known affected: 403 known not affected: 325 recommended: 223 | 2026-10-16T14:30:06+00:00 | Vulnerability · Source |
| CVE-2022-49097 | suse_vex | SUSE CVE CVE-2022-49097 | known affected: 399 known not affected: 333 recommended: 277 | 2026-10-16T14:30:04+00:00 | Vulnerability · Source |
| CVE-2022-49098 | suse_vex | SUSE CVE CVE-2022-49098 | known affected: 394 known not affected: 280 recommended: 387 | 2026-10-16T14:30:01+00:00 | Vulnerability · Source |
| CVE-2022-49099 | suse_vex | SUSE CVE CVE-2022-49099 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:29:58+00:00 | Vulnerability · Source |
| CVE-2022-49100 | suse_vex | SUSE CVE CVE-2022-49100 | known affected: 487 known not affected: 245 recommended: 319 | 2026-10-16T14:29:55+00:00 | Vulnerability · Source |
| CVE-2022-49101 | suse_vex | SUSE CVE CVE-2022-49101 | known affected: 0 known not affected: 462 | 2026-10-16T14:29:53+00:00 | Vulnerability · Source |
| CVE-2022-49102 | suse_vex | SUSE CVE CVE-2022-49102 | known affected: 403 known not affected: 325 recommended: 223 | 2026-10-16T14:29:51+00:00 | Vulnerability · Source |
| CVE-2022-49105 | suse_vex | SUSE CVE CVE-2022-49105 | known affected: 334 known not affected: 397 recommended: 223 | 2026-10-16T14:29:49+00:00 | Vulnerability · Source |
| CVE-2022-49106 | suse_vex | SUSE CVE CVE-2022-49106 | known affected: 500 known not affected: 231 recommended: 223 | 2026-10-16T14:29:47+00:00 | Vulnerability · Source |
| CVE-2022-49107 | suse_vex | SUSE CVE CVE-2022-49107 | known affected: 608 known not affected: 72 recommended: 285 | 2026-10-16T14:29:44+00:00 | Vulnerability · Source |
| CVE-2022-49108 | suse_vex | SUSE CVE CVE-2022-49108 | known affected: 0 known not affected: 462 | 2026-10-16T14:29:42+00:00 | Vulnerability · Source |