VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291734 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49295 | suse_vex | SUSE CVE CVE-2022-49295 | known affected: 395 known not affected: 183 recommended: 319 | 2026-08-05T01:14:25+00:00 | Vulnerability · Source |
| CVE-2022-49325 | suse_vex | SUSE CVE CVE-2022-49325 | known affected: 545 known not affected: 127 recommended: 162 | 2026-08-05T01:14:21+00:00 | Vulnerability · Source |
| CVE-2022-49330 | suse_vex | SUSE CVE CVE-2022-49330 | known affected: 537 known not affected: 103 recommended: 182 | 2026-08-05T01:14:18+00:00 | Vulnerability · Source |
| CVE-2022-49336 | suse_vex | SUSE CVE CVE-2022-49336 | known affected: 418 known not affected: 212 recommended: 223 | 2026-08-05T01:14:17+00:00 | Vulnerability · Source |
| CVE-2022-49337 | suse_vex | SUSE CVE CVE-2022-49337 | known affected: 334 known not affected: 270 recommended: 249 | 2026-08-05T01:14:15+00:00 | Vulnerability · Source |
| CVE-2022-49343 | suse_vex | SUSE CVE CVE-2022-49343 | known not affected: 236 recommended: 327 | 2026-08-05T01:14:14+00:00 | Vulnerability · Source |
| CVE-2022-49356 | suse_vex | SUSE CVE CVE-2022-49356 | known affected: 334 known not affected: 298 recommended: 270 | 2026-08-05T01:14:11+00:00 | Vulnerability · Source |
| CVE-2022-49368 | suse_vex | SUSE CVE CVE-2022-49368 | known affected: 422 known not affected: 248 recommended: 223 | 2026-08-05T01:14:05+00:00 | Vulnerability · Source |
| CVE-2022-49413 | suse_vex | SUSE CVE CVE-2022-49413 | known affected: 393 known not affected: 183 recommended: 353 | 2026-08-05T01:13:53+00:00 | Vulnerability · Source |
| CVE-2022-49416 | suse_vex | SUSE CVE CVE-2022-49416 | known affected: 421 known not affected: 157 recommended: 380 | 2026-08-05T01:13:52+00:00 | Vulnerability · Source |
| CVE-2022-49452 | suse_vex | SUSE CVE CVE-2022-49452 | known not affected: 352 | 2026-08-05T01:13:45+00:00 | Vulnerability · Source |
| CVE-2022-49511 | suse_vex | SUSE CVE CVE-2022-49511 | known affected: 364 known not affected: 302 recommended: 147 | 2026-08-05T01:13:35+00:00 | Vulnerability · Source |
| CVE-2022-49533 | suse_vex | SUSE CVE CVE-2022-49533 | known affected: 419 known not affected: 247 recommended: 100 | 2026-08-05T01:13:31+00:00 | Vulnerability · Source |
| CVE-2022-49535 | suse_vex | SUSE CVE CVE-2022-49535 | known affected: 423 known not affected: 187 recommended: 319 | 2026-08-05T01:13:29+00:00 | Vulnerability · Source |
| CVE-2022-49554 | suse_vex | SUSE CVE CVE-2022-49554 | known affected: 106 known not affected: 246 | 2026-08-05T01:13:26+00:00 | Vulnerability · Source |
| CVE-2022-49622 | suse_vex | SUSE CVE CVE-2022-49622 | known affected: 633 known not affected: 140 recommended: 23 | 2026-08-05T01:13:16+00:00 | Vulnerability · Source |
| CVE-2022-49645 | suse_vex | SUSE CVE CVE-2022-49645 | known affected: 334 known not affected: 270 recommended: 293 | 2026-08-05T01:13:13+00:00 | Vulnerability · Source |
| CVE-2022-49667 | suse_vex | SUSE CVE CVE-2022-49667 | known affected: 458 known not affected: 148 recommended: 263 | 2026-08-05T01:13:10+00:00 | Vulnerability · Source |
| CVE-2022-49672 | suse_vex | SUSE CVE CVE-2022-49672 | known affected: 414 known not affected: 194 recommended: 290 | 2026-08-05T01:13:06+00:00 | Vulnerability · Source |
| CVE-2022-49701 | suse_vex | SUSE CVE CVE-2022-49701 | known affected: 334 known not affected: 270 recommended: 293 | 2026-08-05T01:13:01+00:00 | Vulnerability · Source |
| CVE-2022-49722 | suse_vex | SUSE CVE CVE-2022-49722 | known affected: 385 known not affected: 247 recommended: 265 | 2026-08-05T01:12:59+00:00 | Vulnerability · Source |
| CVE-2022-49725 | suse_vex | SUSE CVE CVE-2022-49725 | known affected: 458 known not affected: 184 recommended: 263 | 2026-08-05T01:12:57+00:00 | Vulnerability · Source |
| CVE-2022-49733 | suse_vex | SUSE CVE CVE-2022-49733 | known not affected: 236 recommended: 300 | 2026-08-05T01:12:56+00:00 | Vulnerability · Source |
| CVE-2022-49738 | suse_vex | SUSE CVE CVE-2022-49738 | known not affected: 348 | 2026-08-05T01:12:54+00:00 | Vulnerability · Source |
| CVE-2022-49763 | suse_vex | SUSE CVE CVE-2022-49763 | known affected: 369 known not affected: 343 recommended: 92 | 2026-08-05T01:12:48+00:00 | Vulnerability · Source |
| CVE-2022-49775 | suse_vex | SUSE CVE CVE-2022-49775 | known affected: 449 known not affected: 141 recommended: 330 | 2026-08-05T01:12:43+00:00 | Vulnerability · Source |
| CVE-2022-49792 | suse_vex | SUSE CVE CVE-2022-49792 | known affected: 339 known not affected: 294 recommended: 214 | 2026-08-05T01:12:40+00:00 | Vulnerability · Source |
| CVE-2022-49814 | suse_vex | SUSE CVE CVE-2022-49814 | known affected: 623 known not affected: 157 recommended: 23 | 2026-08-05T01:12:38+00:00 | Vulnerability · Source |
| CVE-2022-49834 | suse_vex | SUSE CVE CVE-2022-49834 | known affected: 339 known not affected: 251 recommended: 214 | 2026-08-05T01:12:36+00:00 | Vulnerability · Source |
| CVE-2022-49844 | suse_vex | SUSE CVE CVE-2022-49844 | known not affected: 402 | 2026-08-05T01:12:35+00:00 | Vulnerability · Source |
| CVE-2022-49905 | suse_vex | SUSE CVE CVE-2022-49905 | known affected: 339 known not affected: 294 recommended: 214 | 2026-08-05T01:12:24+00:00 | Vulnerability · Source |
| CVE-2022-49910 | suse_vex | SUSE CVE CVE-2022-49910 | known not affected: 236 recommended: 275 | 2026-08-05T01:12:23+00:00 | Vulnerability · Source |
| CVE-2022-49919 | suse_vex | SUSE CVE CVE-2022-49919 | known not affected: 397 | 2026-08-05T01:12:22+00:00 | Vulnerability · Source |
| CVE-2022-49928 | suse_vex | SUSE CVE CVE-2022-49928 | known affected: 339 known not affected: 294 recommended: 214 | 2026-08-05T01:12:19+00:00 | Vulnerability · Source |
| CVE-2022-49931 | suse_vex | SUSE CVE CVE-2022-49931 | known affected: 380 known not affected: 227 recommended: 237 | 2026-08-05T01:12:17+00:00 | Vulnerability · Source |
| CVE-2022-49935 | suse_vex | SUSE CVE CVE-2022-49935 | known affected: 461 known not affected: 255 recommended: 139 | 2026-08-05T01:12:16+00:00 | Vulnerability · Source |
| CVE-2022-49939 | suse_vex | SUSE CVE CVE-2022-49939 | known affected: 163 known not affected: 238 | 2026-08-05T01:12:14+00:00 | Vulnerability · Source |
| CVE-2022-49944 | suse_vex | SUSE CVE CVE-2022-49944 | known affected: 369 known not affected: 347 recommended: 139 | 2026-08-05T01:12:13+00:00 | Vulnerability · Source |
| CVE-2022-49950 | suse_vex | SUSE CVE CVE-2022-49950 | known affected: 358 known not affected: 280 recommended: 273 | 2026-08-05T01:12:10+00:00 | Vulnerability · Source |
| CVE-2022-49968 | suse_vex | SUSE CVE CVE-2022-49968 | known affected: 358 known not affected: 280 recommended: 273 | 2026-08-05T01:12:05+00:00 | Vulnerability · Source |
| CVE-2022-49979 | suse_vex | SUSE CVE CVE-2022-49979 | known affected: 506 known not affected: 279 recommended: 95 | 2026-08-05T01:12:02+00:00 | Vulnerability · Source |
| CVE-2022-49985 | suse_vex | SUSE CVE CVE-2022-49985 | known not affected: 292 recommended: 282 | 2026-08-05T01:12:00+00:00 | Vulnerability · Source |
| CVE-2022-49997 | suse_vex | SUSE CVE CVE-2022-49997 | known affected: 55 known not affected: 346 | 2026-08-05T01:11:57+00:00 | Vulnerability · Source |
| CVE-2022-49998 | suse_vex | SUSE CVE CVE-2022-49998 | known affected: 106 known not affected: 295 recommended: 27 | 2026-08-05T01:11:56+00:00 | Vulnerability · Source |
| CVE-2022-49999 | suse_vex | SUSE CVE CVE-2022-49999 | known affected: 344 known not affected: 298 recommended: 206 | 2026-08-05T01:11:54+00:00 | Vulnerability · Source |
| CVE-2022-50014 | suse_vex | SUSE CVE CVE-2022-50014 | known not affected: 401 recommended: 27 | 2026-08-05T01:11:52+00:00 | Vulnerability · Source |
| CVE-2022-50064 | suse_vex | SUSE CVE CVE-2022-50064 | known not affected: 416 recommended: 29 | 2026-08-05T01:11:45+00:00 | Vulnerability · Source |
| CVE-2022-50070 | suse_vex | SUSE CVE CVE-2022-50070 | known affected: 70 known not affected: 346 recommended: 47 | 2026-08-05T01:11:44+00:00 | Vulnerability · Source |
| CVE-2022-50072 | suse_vex | SUSE CVE CVE-2022-50072 | known affected: 344 known not affected: 294 recommended: 322 | 2026-08-05T01:11:42+00:00 | Vulnerability · Source |
| CVE-2022-50087 | suse_vex | SUSE CVE CVE-2022-50087 | known affected: 395 known not affected: 197 recommended: 372 | 2026-08-05T01:11:38+00:00 | Vulnerability · Source |