VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291026 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49846 | suse_vex | SUSE CVE CVE-2022-49846 | known affected: 400 known not affected: 176 recommended: 367 | 2026-08-14T01:19:23+00:00 | Vulnerability · Source |
| CVE-2022-49861 | suse_vex | SUSE CVE CVE-2022-49861 | known affected: 404 known not affected: 172 recommended: 304 | 2026-08-14T01:19:20+00:00 | Vulnerability · Source |
| CVE-2022-49863 | suse_vex | SUSE CVE CVE-2022-49863 | known affected: 339 known not affected: 299 recommended: 214 | 2026-08-14T01:19:19+00:00 | Vulnerability · Source |
| CVE-2022-49865 | suse_vex | SUSE CVE CVE-2022-49865 | known affected: 461 known not affected: 158 recommended: 251 | 2026-08-14T01:19:17+00:00 | Vulnerability · Source |
| CVE-2022-49867 | suse_vex | SUSE CVE CVE-2022-49867 | known affected: 55 known not affected: 342 | 2026-08-14T01:19:16+00:00 | Vulnerability · Source |
| CVE-2022-49869 | suse_vex | SUSE CVE CVE-2022-49869 | known affected: 390 known not affected: 245 recommended: 214 | 2026-08-14T01:19:14+00:00 | Vulnerability · Source |
| CVE-2022-49871 | suse_vex | SUSE CVE CVE-2022-49871 | known affected: 411 known not affected: 194 recommended: 237 | 2026-08-14T01:19:12+00:00 | Vulnerability · Source |
| CVE-2022-49881 | suse_vex | SUSE CVE CVE-2022-49881 | known affected: 371 known not affected: 218 recommended: 304 | 2026-08-14T01:19:11+00:00 | Vulnerability · Source |
| CVE-2022-49888 | suse_vex | SUSE CVE CVE-2022-49888 | known affected: 339 known not affected: 292 recommended: 214 | 2026-08-14T01:19:09+00:00 | Vulnerability · Source |
| CVE-2022-49891 | suse_vex | SUSE CVE CVE-2022-49891 | known affected: 339 known not affected: 292 recommended: 214 | 2026-08-14T01:19:07+00:00 | Vulnerability · Source |
| CVE-2022-49892 | suse_vex | SUSE CVE CVE-2022-49892 | known affected: 414 known not affected: 178 recommended: 318 | 2026-08-14T01:19:06+00:00 | Vulnerability · Source |
| CVE-2022-49912 | suse_vex | SUSE CVE CVE-2022-49912 | known affected: 61 known not affected: 351 | 2026-08-14T01:19:04+00:00 | Vulnerability · Source |
| CVE-2022-49917 | suse_vex | SUSE CVE CVE-2022-49917 | known affected: 561 known not affected: 138 recommended: 129 | 2026-08-14T01:19:03+00:00 | Vulnerability · Source |
| CVE-2022-49921 | suse_vex | SUSE CVE CVE-2022-49921 | known affected: 541 known not affected: 160 recommended: 115 | 2026-08-14T01:19:01+00:00 | Vulnerability · Source |
| CVE-2022-49938 | suse_vex | SUSE CVE CVE-2022-49938 | known affected: 442 known not affected: 174 recommended: 258 | 2026-08-14T01:18:59+00:00 | Vulnerability · Source |
| CVE-2022-49942 | suse_vex | SUSE CVE CVE-2022-49942 | known affected: 419 known not affected: 200 recommended: 320 | 2026-08-14T01:18:57+00:00 | Vulnerability · Source |
| CVE-2022-49948 | suse_vex | SUSE CVE CVE-2022-49948 | known affected: 429 known not affected: 196 recommended: 310 | 2026-08-14T01:18:56+00:00 | Vulnerability · Source |
| CVE-2022-49963 | suse_vex | SUSE CVE CVE-2022-49963 | known affected: 369 known not affected: 347 recommended: 92 | 2026-08-14T01:18:54+00:00 | Vulnerability · Source |
| CVE-2022-49971 | suse_vex | SUSE CVE CVE-2022-49971 | known affected: 369 known not affected: 346 recommended: 139 | 2026-08-14T01:18:52+00:00 | Vulnerability · Source |
| CVE-2022-49975 | suse_vex | SUSE CVE CVE-2022-49975 | known affected: 639 known not affected: 187 recommended: 37 | 2026-08-14T01:18:50+00:00 | Vulnerability · Source |
| CVE-2022-49986 | suse_vex | SUSE CVE CVE-2022-49986 | known affected: 374 known not affected: 232 recommended: 369 | 2026-08-14T01:18:46+00:00 | Vulnerability · Source |
| CVE-2022-49993 | suse_vex | SUSE CVE CVE-2022-49993 | known affected: 429 known not affected: 194 recommended: 337 | 2026-08-14T01:18:44+00:00 | Vulnerability · Source |
| CVE-2022-50002 | suse_vex | SUSE CVE CVE-2022-50002 | known affected: 424 known not affected: 292 recommended: 139 | 2026-08-14T01:18:41+00:00 | Vulnerability · Source |
| CVE-2022-50022 | suse_vex | SUSE CVE CVE-2022-50022 | known affected: 419 known not affected: 254 recommended: 370 | 2026-08-14T01:18:38+00:00 | Vulnerability · Source |
| CVE-2022-50023 | suse_vex | SUSE CVE CVE-2022-50023 | known affected: 395 known not affected: 246 recommended: 206 | 2026-08-14T01:18:36+00:00 | Vulnerability · Source |
| CVE-2022-50024 | suse_vex | SUSE CVE CVE-2022-50024 | known affected: 395 known not affected: 247 recommended: 206 | 2026-08-14T01:18:34+00:00 | Vulnerability · Source |
| CVE-2022-50030 | suse_vex | SUSE CVE CVE-2022-50030 | known affected: 409 known not affected: 214 recommended: 352 | 2026-08-14T01:18:32+00:00 | Vulnerability · Source |
| CVE-2022-50035 | suse_vex | SUSE CVE CVE-2022-50035 | known affected: 369 known not affected: 346 recommended: 139 | 2026-08-14T01:18:31+00:00 | Vulnerability · Source |
| CVE-2022-50041 | suse_vex | SUSE CVE CVE-2022-50041 | known affected: 373 known not affected: 358 recommended: 139 | 2026-08-14T01:18:29+00:00 | Vulnerability · Source |
| CVE-2022-50044 | suse_vex | SUSE CVE CVE-2022-50044 | known affected: 439 known not affected: 291 recommended: 139 | 2026-08-14T01:18:28+00:00 | Vulnerability · Source |
| CVE-2022-50046 | suse_vex | SUSE CVE CVE-2022-50046 | known affected: 344 known not affected: 296 recommended: 253 | 2026-08-14T01:18:26+00:00 | Vulnerability · Source |
| CVE-2022-50049 | suse_vex | SUSE CVE CVE-2022-50049 | known affected: 369 known not affected: 347 recommended: 139 | 2026-08-14T01:18:24+00:00 | Vulnerability · Source |
| CVE-2022-50059 | suse_vex | SUSE CVE CVE-2022-50059 | known affected: 358 known not affected: 280 recommended: 273 | 2026-08-14T01:18:23+00:00 | Vulnerability · Source |
| CVE-2022-50060 | suse_vex | SUSE CVE CVE-2022-50060 | known affected: 395 known not affected: 247 recommended: 206 | 2026-08-14T01:18:21+00:00 | Vulnerability · Source |
| CVE-2022-50062 | suse_vex | SUSE CVE CVE-2022-50062 | known affected: 348 known not affected: 307 recommended: 206 | 2026-08-14T01:18:20+00:00 | Vulnerability · Source |
| CVE-2022-50076 | suse_vex | SUSE CVE CVE-2022-50076 | known affected: 344 known not affected: 298 recommended: 235 | 2026-08-14T01:18:18+00:00 | Vulnerability · Source |
| CVE-2022-50093 | suse_vex | SUSE CVE CVE-2022-50093 | known affected: 425 known not affected: 248 recommended: 357 | 2026-08-14T01:18:16+00:00 | Vulnerability · Source |
| CVE-2022-50098 | suse_vex | SUSE CVE CVE-2022-50098 | known affected: 405 known not affected: 218 recommended: 296 | 2026-08-14T01:18:14+00:00 | Vulnerability · Source |
| CVE-2022-50101 | suse_vex | SUSE CVE CVE-2022-50101 | known affected: 344 known not affected: 283 recommended: 296 | 2026-08-14T01:18:12+00:00 | Vulnerability · Source |
| CVE-2022-50115 | suse_vex | SUSE CVE CVE-2022-50115 | known affected: 369 known not affected: 346 recommended: 134 | 2026-08-14T01:18:10+00:00 | Vulnerability · Source |
| CVE-2022-50120 | suse_vex | SUSE CVE CVE-2022-50120 | known affected: 395 known not affected: 245 recommended: 233 | 2026-08-14T01:18:08+00:00 | Vulnerability · Source |
| CVE-2022-50125 | suse_vex | SUSE CVE CVE-2022-50125 | known affected: 344 known not affected: 296 recommended: 233 | 2026-08-14T01:18:07+00:00 | Vulnerability · Source |
| CVE-2022-50137 | suse_vex | SUSE CVE CVE-2022-50137 | known affected: 344 known not affected: 296 recommended: 253 | 2026-08-14T01:18:05+00:00 | Vulnerability · Source |
| CVE-2022-50139 | suse_vex | SUSE CVE CVE-2022-50139 | known affected: 344 known not affected: 296 recommended: 233 | 2026-08-14T01:18:04+00:00 | Vulnerability · Source |
| CVE-2022-50154 | suse_vex | SUSE CVE CVE-2022-50154 | known affected: 344 known not affected: 297 recommended: 233 | 2026-08-14T01:18:00+00:00 | Vulnerability · Source |
| CVE-2022-50155 | suse_vex | SUSE CVE CVE-2022-50155 | known affected: 344 known not affected: 296 recommended: 206 | 2026-08-14T01:17:59+00:00 | Vulnerability · Source |
| CVE-2022-50157 | suse_vex | SUSE CVE CVE-2022-50157 | known affected: 344 known not affected: 296 recommended: 233 | 2026-08-14T01:17:57+00:00 | Vulnerability · Source |
| CVE-2022-50162 | suse_vex | SUSE CVE CVE-2022-50162 | known affected: 423 known not affected: 250 recommended: 310 | 2026-08-14T01:17:56+00:00 | Vulnerability · Source |
| CVE-2022-50170 | suse_vex | SUSE CVE CVE-2022-50170 | known not affected: 401 | 2026-08-14T01:17:54+00:00 | Vulnerability · Source |
| CVE-2022-50171 | suse_vex | SUSE CVE CVE-2022-50171 | known affected: 381 known not affected: 259 recommended: 206 | 2026-08-14T01:17:53+00:00 | Vulnerability · Source |