VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283833 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-48857 | suse_vex | SUSE CVE CVE-2022-48857 | known affected: 377 known not affected: 98 recommended: 595 | 2026-07-26T00:10:03+00:00 | Vulnerability · Source |
| CVE-2022-48874 | suse_vex | SUSE CVE CVE-2022-48874 | known not affected: 310 | 2026-07-26T00:10:01+00:00 | Vulnerability · Source |
| CVE-2022-48887 | suse_vex | SUSE CVE CVE-2022-48887 | known affected: 389 known not affected: 142 recommended: 288 | 2026-07-26T00:09:58+00:00 | Vulnerability · Source |
| CVE-2022-48894 | suse_vex | SUSE CVE CVE-2022-48894 | known not affected: 310 | 2026-07-26T00:09:56+00:00 | Vulnerability · Source |
| CVE-2022-48899 | suse_vex | SUSE CVE CVE-2022-48899 | known affected: 425 known not affected: 78 recommended: 495 | 2026-07-26T00:09:54+00:00 | Vulnerability · Source |
| CVE-2022-48916 | suse_vex | SUSE CVE CVE-2022-48916 | known affected: 310 known not affected: 195 recommended: 411 | 2026-07-26T00:09:51+00:00 | Vulnerability · Source |
| CVE-2022-48927 | suse_vex | SUSE CVE CVE-2022-48927 | known affected: 310 known not affected: 195 recommended: 411 | 2026-07-26T00:09:49+00:00 | Vulnerability · Source |
| CVE-2022-48932 | suse_vex | SUSE CVE CVE-2022-48932 | known affected: 310 known not affected: 195 recommended: 411 | 2026-07-26T00:09:46+00:00 | Vulnerability · Source |
| CVE-2022-48938 | suse_vex | SUSE CVE CVE-2022-48938 | known affected: 421 known not affected: 79 recommended: 495 | 2026-07-26T00:09:44+00:00 | Vulnerability · Source |
| CVE-2022-49025 | suse_vex | SUSE CVE CVE-2022-49025 | known affected: 337 known not affected: 225 recommended: 531 | 2026-07-26T00:09:40+00:00 | Vulnerability · Source |
| CVE-2022-49161 | suse_vex | SUSE CVE CVE-2022-49161 | known affected: 112 known not affected: 240 | 2026-07-26T00:09:38+00:00 | Vulnerability · Source |
| CVE-2022-49209 | suse_vex | SUSE CVE CVE-2022-49209 | known affected: 499 known not affected: 143 recommended: 126 | 2026-07-26T00:09:35+00:00 | Vulnerability · Source |
| CVE-2022-49251 | suse_vex | SUSE CVE CVE-2022-49251 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-26T00:09:32+00:00 | Vulnerability · Source |
| CVE-2022-49324 | suse_vex | SUSE CVE CVE-2022-49324 | known not affected: 348 | 2026-07-26T00:09:29+00:00 | Vulnerability · Source |
| CVE-2022-49331 | suse_vex | SUSE CVE CVE-2022-49331 | known affected: 421 known not affected: 245 recommended: 319 | 2026-07-26T00:09:27+00:00 | Vulnerability · Source |
| CVE-2022-49387 | suse_vex | SUSE CVE CVE-2022-49387 | known not affected: 352 | 2026-07-26T00:09:24+00:00 | Vulnerability · Source |
| CVE-2022-49389 | suse_vex | SUSE CVE CVE-2022-49389 | known affected: 409 known not affected: 205 recommended: 355 | 2026-07-26T00:09:22+00:00 | Vulnerability · Source |
| CVE-2022-49399 | suse_vex | SUSE CVE CVE-2022-49399 | known affected: 381 known not affected: 257 recommended: 293 | 2026-07-26T00:09:20+00:00 | Vulnerability · Source |
| CVE-2022-49445 | suse_vex | SUSE CVE CVE-2022-49445 | known affected: 458 known not affected: 184 recommended: 260 | 2026-07-26T00:09:17+00:00 | Vulnerability · Source |
| CVE-2022-49531 | suse_vex | SUSE CVE CVE-2022-49531 | known affected: 230 known not affected: 88 recommended: 22 | 2026-07-26T00:09:14+00:00 | Vulnerability · Source |
| CVE-2022-49536 | suse_vex | SUSE CVE CVE-2022-49536 | known affected: 385 known not affected: 193 recommended: 361 | 2026-07-26T00:09:12+00:00 | Vulnerability · Source |
| CVE-2022-49661 | suse_vex | SUSE CVE CVE-2022-49661 | known affected: 421 known not affected: 157 recommended: 333 | 2026-07-26T00:09:09+00:00 | Vulnerability · Source |
| CVE-2022-49676 | suse_vex | SUSE CVE CVE-2022-49676 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-26T00:09:06+00:00 | Vulnerability · Source |
| CVE-2022-49686 | suse_vex | SUSE CVE CVE-2022-49686 | known affected: 364 known not affected: 302 recommended: 100 | 2026-07-26T00:09:03+00:00 | Vulnerability · Source |
| CVE-2022-49754 | suse_vex | SUSE CVE CVE-2022-49754 | known not affected: 344 recommended: 29 | 2026-07-26T00:09:01+00:00 | Vulnerability · Source |
| CVE-2022-49760 | suse_vex | SUSE CVE CVE-2022-49760 | known not affected: 344 recommended: 29 | 2026-07-26T00:08:59+00:00 | Vulnerability · Source |
| CVE-2022-49778 | suse_vex | SUSE CVE CVE-2022-49778 | known not affected: 397 recommended: 43 | 2026-07-26T00:08:56+00:00 | Vulnerability · Source |
| CVE-2022-49782 | suse_vex | SUSE CVE CVE-2022-49782 | known not affected: 397 | 2026-07-26T00:08:54+00:00 | Vulnerability · Source |
| CVE-2022-49859 | suse_vex | SUSE CVE CVE-2022-49859 | known affected: 55 known not affected: 342 | 2026-07-26T00:08:51+00:00 | Vulnerability · Source |
| CVE-2022-49889 | suse_vex | SUSE CVE CVE-2022-49889 | known affected: 339 known not affected: 240 recommended: 304 | 2026-07-26T00:08:49+00:00 | Vulnerability · Source |
| CVE-2022-49893 | suse_vex | SUSE CVE CVE-2022-49893 | known not affected: 397 | 2026-07-26T00:08:47+00:00 | Vulnerability · Source |
| CVE-2022-49934 | suse_vex | SUSE CVE CVE-2022-49934 | known affected: 429 known not affected: 196 recommended: 357 | 2026-07-26T00:08:45+00:00 | Vulnerability · Source |
| CVE-2022-49956 | suse_vex | SUSE CVE CVE-2022-49956 | known not affected: 264 recommended: 272 | 2026-07-26T00:08:44+00:00 | Vulnerability · Source |
| CVE-2022-50028 | suse_vex | SUSE CVE CVE-2022-50028 | known affected: 425 known not affected: 228 recommended: 300 | 2026-07-26T00:08:42+00:00 | Vulnerability · Source |
| CVE-2022-50106 | suse_vex | SUSE CVE CVE-2022-50106 | known affected: 61 known not affected: 355 | 2026-07-26T00:08:40+00:00 | Vulnerability · Source |
| CVE-2022-50123 | suse_vex | SUSE CVE CVE-2022-50123 | known affected: 61 known not affected: 353 recommended: 27 | 2026-07-26T00:08:38+00:00 | Vulnerability · Source |
| CVE-2022-50132 | suse_vex | SUSE CVE CVE-2022-50132 | known affected: 344 known not affected: 298 recommended: 233 | 2026-07-26T00:08:36+00:00 | Vulnerability · Source |
| CVE-2022-50171 | suse_vex | SUSE CVE CVE-2022-50171 | known affected: 381 known not affected: 261 recommended: 206 | 2026-07-26T00:08:33+00:00 | Vulnerability · Source |
| CVE-2022-50173 | suse_vex | SUSE CVE CVE-2022-50173 | known affected: 344 known not affected: 283 recommended: 296 | 2026-07-26T00:08:31+00:00 | Vulnerability · Source |
| CVE-2022-50185 | suse_vex | SUSE CVE CVE-2022-50185 | known affected: 423 known not affected: 250 recommended: 357 | 2026-07-26T00:08:29+00:00 | Vulnerability · Source |
| CVE-2022-50225 | suse_vex | SUSE CVE CVE-2022-50225 | known affected: 55 known not affected: 346 | 2026-07-26T00:08:26+00:00 | Vulnerability · Source |
| CVE-2022-50278 | suse_vex | SUSE CVE CVE-2022-50278 | known affected: 468 known not affected: 181 recommended: 243 | 2026-07-26T00:08:23+00:00 | Vulnerability · Source |
| CVE-2022-50282 | suse_vex | SUSE CVE CVE-2022-50282 | known affected: 442 known not affected: 207 recommended: 233 | 2026-07-26T00:08:21+00:00 | Vulnerability · Source |
| CVE-2022-50319 | suse_vex | SUSE CVE CVE-2022-50319 | known affected: 55 known not affected: 361 recommended: 43 | 2026-07-26T00:08:19+00:00 | Vulnerability · Source |
| CVE-2022-50350 | suse_vex | SUSE CVE CVE-2022-50350 | known affected: 630 known not affected: 181 recommended: 84 | 2026-07-26T00:08:16+00:00 | Vulnerability · Source |
| CVE-2022-50449 | suse_vex | SUSE CVE CVE-2022-50449 | known affected: 456 known not affected: 160 recommended: 206 | 2026-07-26T00:08:13+00:00 | Vulnerability · Source |
| CVE-2022-50536 | suse_vex | SUSE CVE CVE-2022-50536 | known affected: 55 known not affected: 331 recommended: 72 | 2026-07-26T00:08:10+00:00 | Vulnerability · Source |
| CVE-2022-50580 | suse_vex | SUSE CVE CVE-2022-50580 | known affected: 472 known not affected: 171 recommended: 260 | 2026-07-26T00:08:07+00:00 | Vulnerability · Source |
| CVE-2022-50667 | suse_vex | SUSE CVE CVE-2022-50667 | known affected: 374 known not affected: 351 recommended: 136 | 2026-07-26T00:08:04+00:00 | Vulnerability · Source |
| CVE-2022-50668 | suse_vex | SUSE CVE CVE-2022-50668 | known affected: 429 known not affected: 222 recommended: 284 | 2026-07-26T00:08:02+00:00 | Vulnerability · Source |