VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292287 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-48928 | suse_vex | SUSE CVE CVE-2022-48928 | known affected: 310 known not affected: 382 recommended: 496 | 2026-07-23T02:30:39+00:00 | Vulnerability · Source |
| CVE-2022-49012 | suse_vex | SUSE CVE CVE-2022-49012 | known affected: 324 known not affected: 270 recommended: 394 | 2026-07-23T02:30:26+00:00 | Vulnerability · Source |
| CVE-2022-49049 | suse_vex | SUSE CVE CVE-2022-49049 | known affected: 112 known not affected: 240 recommended: 27 | 2026-07-23T02:30:21+00:00 | Vulnerability · Source |
| CVE-2022-49094 | suse_vex | SUSE CVE CVE-2022-49094 | known affected: 163 known not affected: 189 | 2026-07-23T02:30:12+00:00 | Vulnerability · Source |
| CVE-2022-49117 | suse_vex | SUSE CVE CVE-2022-49117 | known not affected: 352 | 2026-07-23T02:30:07+00:00 | Vulnerability · Source |
| CVE-2022-49127 | suse_vex | SUSE CVE CVE-2022-49127 | known affected: 57 known not affected: 295 | 2026-07-23T02:30:03+00:00 | Vulnerability · Source |
| CVE-2022-49169 | suse_vex | SUSE CVE CVE-2022-49169 | known not affected: 352 | 2026-07-23T02:29:58+00:00 | Vulnerability · Source |
| CVE-2022-49198 | suse_vex | SUSE CVE CVE-2022-49198 | known not affected: 352 | 2026-07-23T02:29:55+00:00 | Vulnerability · Source |
| CVE-2022-49240 | suse_vex | SUSE CVE CVE-2022-49240 | known not affected: 352 | 2026-07-23T02:29:50+00:00 | Vulnerability · Source |
| CVE-2022-49267 | suse_vex | SUSE CVE CVE-2022-49267 | known affected: 245 known not affected: 124 | 2026-07-23T02:29:43+00:00 | Vulnerability · Source |
| CVE-2022-49289 | suse_vex | SUSE CVE CVE-2022-49289 | known not affected: 348 | 2026-07-23T02:29:37+00:00 | Vulnerability · Source |
| CVE-2022-49318 | suse_vex | SUSE CVE CVE-2022-49318 | known not affected: 352 | 2026-07-23T02:29:29+00:00 | Vulnerability · Source |
| CVE-2022-49323 | suse_vex | SUSE CVE CVE-2022-49323 | known affected: 334 known not affected: 268 recommended: 293 | 2026-07-23T02:29:27+00:00 | Vulnerability · Source |
| CVE-2022-49332 | suse_vex | SUSE CVE CVE-2022-49332 | known affected: 334 known not affected: 244 recommended: 341 | 2026-07-23T02:29:24+00:00 | Vulnerability · Source |
| CVE-2022-49334 | suse_vex | SUSE CVE CVE-2022-49334 | known not affected: 352 recommended: 22 | 2026-07-23T02:29:22+00:00 | Vulnerability · Source |
| CVE-2022-49358 | suse_vex | SUSE CVE CVE-2022-49358 | known affected: 163 known not affected: 185 | 2026-07-23T02:29:16+00:00 | Vulnerability · Source |
| CVE-2022-49388 | suse_vex | SUSE CVE CVE-2022-49388 | known affected: 559 known not affected: 163 recommended: 26 | 2026-07-23T02:29:10+00:00 | Vulnerability · Source |
| CVE-2022-49420 | suse_vex | SUSE CVE CVE-2022-49420 | known affected: 559 known not affected: 161 recommended: 37 | 2026-07-23T02:29:00+00:00 | Vulnerability · Source |
| CVE-2022-49423 | suse_vex | SUSE CVE CVE-2022-49423 | known not affected: 352 | 2026-07-23T02:28:59+00:00 | Vulnerability · Source |
| CVE-2022-49442 | suse_vex | SUSE CVE CVE-2022-49442 | known affected: 427 known not affected: 151 recommended: 360 | 2026-07-23T02:28:56+00:00 | Vulnerability · Source |
| CVE-2022-49471 | suse_vex | SUSE CVE CVE-2022-49471 | known affected: 112 known not affected: 236 recommended: 47 | 2026-07-23T02:28:51+00:00 | Vulnerability · Source |
| CVE-2022-49493 | suse_vex | SUSE CVE CVE-2022-49493 | known affected: 348 known not affected: 252 recommended: 293 | 2026-07-23T02:28:46+00:00 | Vulnerability · Source |
| CVE-2022-49496 | suse_vex | SUSE CVE CVE-2022-49496 | known affected: 212 known not affected: 174 | 2026-07-23T02:28:44+00:00 | Vulnerability · Source |
| CVE-2022-49529 | suse_vex | SUSE CVE CVE-2022-49529 | known affected: 364 known not affected: 300 recommended: 100 | 2026-07-23T02:28:41+00:00 | Vulnerability · Source |
| CVE-2022-49547 | suse_vex | SUSE CVE CVE-2022-49547 | known not affected: 352 | 2026-07-23T02:28:36+00:00 | Vulnerability · Source |
| CVE-2022-49550 | suse_vex | SUSE CVE CVE-2022-49550 | known not affected: 352 | 2026-07-23T02:28:35+00:00 | Vulnerability · Source |
| CVE-2022-49572 | suse_vex | SUSE CVE CVE-2022-49572 | known not affected: 141 recommended: 27 | 2026-07-23T02:28:29+00:00 | Vulnerability · Source |
| CVE-2022-49585 | suse_vex | SUSE CVE CVE-2022-49585 | known not affected: 163 recommended: 27 | 2026-07-23T02:28:27+00:00 | Vulnerability · Source |
| CVE-2022-49597 | suse_vex | SUSE CVE CVE-2022-49597 | known not affected: 141 | 2026-07-23T02:28:25+00:00 | Vulnerability · Source |
| CVE-2022-49613 | suse_vex | SUSE CVE CVE-2022-49613 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-23T02:28:24+00:00 | Vulnerability · Source |
| CVE-2022-49651 | suse_vex | SUSE CVE CVE-2022-49651 | known not affected: 225 recommended: 27 | 2026-07-23T02:28:15+00:00 | Vulnerability · Source |
| CVE-2022-49681 | suse_vex | SUSE CVE CVE-2022-49681 | known not affected: 352 | 2026-07-23T02:28:12+00:00 | Vulnerability · Source |
| CVE-2022-49696 | suse_vex | SUSE CVE CVE-2022-49696 | known affected: 55 known not affected: 297 | 2026-07-23T02:28:11+00:00 | Vulnerability · Source |
| CVE-2022-49716 | suse_vex | SUSE CVE CVE-2022-49716 | known affected: 371 known not affected: 261 recommended: 252 | 2026-07-23T02:28:09+00:00 | Vulnerability · Source |
| CVE-2022-49749 | suse_vex | SUSE CVE CVE-2022-49749 | known affected: 622 known not affected: 124 recommended: 40 | 2026-07-23T02:28:06+00:00 | Vulnerability · Source |
| CVE-2022-49785 | suse_vex | SUSE CVE CVE-2022-49785 | known affected: 112 known not affected: 285 | 2026-07-23T02:27:59+00:00 | Vulnerability · Source |
| CVE-2022-49790 | suse_vex | SUSE CVE CVE-2022-49790 | known affected: 353 known not affected: 252 recommended: 281 | 2026-07-23T02:27:56+00:00 | Vulnerability · Source |
| CVE-2022-49819 | suse_vex | SUSE CVE CVE-2022-49819 | known not affected: 397 | 2026-07-23T02:27:47+00:00 | Vulnerability · Source |
| CVE-2022-49843 | suse_vex | SUSE CVE CVE-2022-49843 | known not affected: 398 | 2026-07-23T02:27:43+00:00 | Vulnerability · Source |
| CVE-2022-49847 | suse_vex | SUSE CVE CVE-2022-49847 | known not affected: 397 | 2026-07-23T02:27:40+00:00 | Vulnerability · Source |
| CVE-2022-49849 | suse_vex | SUSE CVE CVE-2022-49849 | known not affected: 397 | 2026-07-23T02:27:39+00:00 | Vulnerability · Source |
| CVE-2022-49855 | suse_vex | SUSE CVE CVE-2022-49855 | known affected: 55 known not affected: 342 recommended: 29 | 2026-07-23T02:27:38+00:00 | Vulnerability · Source |
| CVE-2022-49860 | suse_vex | SUSE CVE CVE-2022-49860 | known affected: 339 known not affected: 294 recommended: 214 | 2026-07-23T02:27:36+00:00 | Vulnerability · Source |
| CVE-2022-49864 | suse_vex | SUSE CVE CVE-2022-49864 | known affected: 339 known not affected: 294 recommended: 263 | 2026-07-23T02:27:35+00:00 | Vulnerability · Source |
| CVE-2022-49882 | suse_vex | SUSE CVE CVE-2022-49882 | known not affected: 397 recommended: 29 | 2026-07-23T02:27:32+00:00 | Vulnerability · Source |
| CVE-2022-49894 | suse_vex | SUSE CVE CVE-2022-49894 | known not affected: 397 | 2026-07-23T02:27:29+00:00 | Vulnerability · Source |
| CVE-2022-49932 | suse_vex | SUSE CVE CVE-2022-49932 | known affected: 277 known not affected: 191 | 2026-07-23T02:27:23+00:00 | Vulnerability · Source |
| CVE-2022-49959 | suse_vex | SUSE CVE CVE-2022-49959 | known not affected: 401 recommended: 47 | 2026-07-23T02:27:15+00:00 | Vulnerability · Source |
| CVE-2022-49973 | suse_vex | SUSE CVE CVE-2022-49973 | known not affected: 416 recommended: 27 | 2026-07-23T02:27:12+00:00 | Vulnerability · Source |
| CVE-2022-50004 | suse_vex | SUSE CVE CVE-2022-50004 | known not affected: 401 recommended: 29 | 2026-07-23T02:27:03+00:00 | Vulnerability · Source |