VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
103255 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49021 | suse_vex | SUSE CVE CVE-2022-49021 | known affected: 520 known not affected: 110 recommended: 518 | 2026-10-17T01:20:48+00:00 | Vulnerability · Source |
| CVE-2022-49061 | suse_vex | SUSE CVE CVE-2022-49061 | known affected: 377 known not affected: 351 recommended: 223 | 2026-10-17T01:20:46+00:00 | Vulnerability · Source |
| CVE-2022-49076 | suse_vex | SUSE CVE CVE-2022-49076 | known affected: 465 known not affected: 179 recommended: 333 | 2026-10-17T01:20:45+00:00 | Vulnerability · Source |
| CVE-2022-49077 | suse_vex | SUSE CVE CVE-2022-49077 | known affected: 0 known not affected: 104 | 2026-10-17T01:20:43+00:00 | Vulnerability · Source |
| CVE-2022-49104 | suse_vex | SUSE CVE CVE-2022-49104 | known affected: 334 known not affected: 442 recommended: 223 | 2026-10-17T01:20:41+00:00 | Vulnerability · Source |
| CVE-2022-49127 | suse_vex | SUSE CVE CVE-2022-49127 | known affected: 67 known not affected: 395 | 2026-10-17T01:20:40+00:00 | Vulnerability · Source |
| CVE-2022-49148 | suse_vex | SUSE CVE CVE-2022-49148 | known affected: 334 known not affected: 397 recommended: 223 | 2026-10-17T01:20:38+00:00 | Vulnerability · Source |
| CVE-2022-49188 | suse_vex | SUSE CVE CVE-2022-49188 | known affected: 505 known not affected: 206 recommended: 271 | 2026-10-17T01:20:36+00:00 | Vulnerability · Source |
| CVE-2022-49197 | suse_vex | SUSE CVE CVE-2022-49197 | known affected: 724 known not affected: 109 recommended: 40 | 2026-10-17T01:20:34+00:00 | Vulnerability · Source |
| CVE-2022-49201 | suse_vex | SUSE CVE CVE-2022-49201 | known affected: 461 known not affected: 124 recommended: 319 | 2026-10-17T01:20:33+00:00 | Vulnerability · Source |
| CVE-2022-49212 | suse_vex | SUSE CVE CVE-2022-49212 | known affected: 465 known not affected: 215 recommended: 316 | 2026-10-17T01:20:30+00:00 | Vulnerability · Source |
| CVE-2022-49256 | suse_vex | SUSE CVE CVE-2022-49256 | known affected: 0 known not affected: 394 recommended: 221 | 2026-10-17T01:20:27+00:00 | Vulnerability · Source |
| CVE-2022-49267 | suse_vex | SUSE CVE CVE-2022-49267 | known affected: 339 known not affected: 110 | 2026-10-17T01:20:26+00:00 | Vulnerability · Source |
| CVE-2022-49279 | suse_vex | SUSE CVE CVE-2022-49279 | known affected: 360 known not affected: 334 recommended: 293 | 2026-10-17T01:20:24+00:00 | Vulnerability · Source |
| CVE-2022-49286 | suse_vex | SUSE CVE CVE-2022-49286 | known affected: 496 known not affected: 182 recommended: 249 | 2026-10-17T01:20:22+00:00 | Vulnerability · Source |
| CVE-2022-49308 | suse_vex | SUSE CVE CVE-2022-49308 | known affected: 501 known not affected: 172 recommended: 263 | 2026-10-17T01:20:20+00:00 | Vulnerability · Source |
| CVE-2022-49326 | suse_vex | SUSE CVE CVE-2022-49326 | known affected: 489 known not affected: 151 recommended: 330 | 2026-10-17T01:20:19+00:00 | Vulnerability · Source |
| CVE-2022-49354 | suse_vex | SUSE CVE CVE-2022-49354 | known affected: 334 known not affected: 393 recommended: 223 | 2026-10-17T01:20:17+00:00 | Vulnerability · Source |
| CVE-2022-49382 | suse_vex | SUSE CVE CVE-2022-49382 | known affected: 465 known not affected: 266 recommended: 316 | 2026-10-17T01:20:14+00:00 | Vulnerability · Source |
| CVE-2022-49383 | suse_vex | SUSE CVE CVE-2022-49383 | known affected: 0 known not affected: 462 | 2026-10-17T01:20:13+00:00 | Vulnerability · Source |
| CVE-2022-49385 | suse_vex | SUSE CVE CVE-2022-49385 | known affected: 493 known not affected: 183 recommended: 333 | 2026-10-17T01:20:11+00:00 | Vulnerability · Source |
| CVE-2022-49429 | suse_vex | SUSE CVE CVE-2022-49429 | known affected: 524 known not affected: 203 recommended: 337 | 2026-10-17T01:20:09+00:00 | Vulnerability · Source |
| CVE-2022-49436 | suse_vex | SUSE CVE CVE-2022-49436 | known affected: 364 known not affected: 402 recommended: 100 | 2026-10-17T01:20:08+00:00 | Vulnerability · Source |
| CVE-2022-49439 | suse_vex | SUSE CVE CVE-2022-49439 | known affected: 255 known not affected: 241 | 2026-10-17T01:20:07+00:00 | Vulnerability · Source |
| CVE-2022-49444 | suse_vex | SUSE CVE CVE-2022-49444 | known affected: 400 known not affected: 279 recommended: 249 | 2026-10-17T01:20:05+00:00 | Vulnerability · Source |
| CVE-2022-49454 | suse_vex | SUSE CVE CVE-2022-49454 | known affected: 0 known not affected: 462 | 2026-10-17T01:20:04+00:00 | Vulnerability · Source |
| CVE-2022-49461 | suse_vex | SUSE CVE CVE-2022-49461 | known affected: 0 known not affected: 462 | 2026-10-17T01:20:02+00:00 | Vulnerability · Source |
| CVE-2022-49477 | suse_vex | SUSE CVE CVE-2022-49477 | known affected: 377 known not affected: 351 recommended: 223 | 2026-10-17T01:20:01+00:00 | Vulnerability · Source |
| CVE-2022-49480 | suse_vex | SUSE CVE CVE-2022-49480 | known affected: 334 known not affected: 398 recommended: 223 | 2026-10-17T01:19:59+00:00 | Vulnerability · Source |
| CVE-2022-49491 | suse_vex | SUSE CVE CVE-2022-49491 | known affected: 493 known not affected: 213 recommended: 316 | 2026-10-17T01:19:57+00:00 | Vulnerability · Source |
| CVE-2022-49505 | suse_vex | SUSE CVE CVE-2022-49505 | known affected: 493 known not affected: 151 recommended: 333 | 2026-10-17T01:19:55+00:00 | Vulnerability · Source |
| CVE-2022-49519 | suse_vex | SUSE CVE CVE-2022-49519 | known affected: 529 known not affected: 144 recommended: 337 | 2026-10-17T01:19:53+00:00 | Vulnerability · Source |
| CVE-2022-49521 | suse_vex | SUSE CVE CVE-2022-49521 | known affected: 487 known not affected: 154 recommended: 333 | 2026-10-17T01:19:51+00:00 | Vulnerability · Source |
| CVE-2022-49538 | suse_vex | SUSE CVE CVE-2022-49538 | known affected: 627 known not affected: 87 recommended: 182 | 2026-10-17T01:19:49+00:00 | Vulnerability · Source |
| CVE-2022-49595 | suse_vex | SUSE CVE CVE-2022-49595 | known affected: 0 known not affected: 147 recommended: 54 | 2026-10-17T01:19:47+00:00 | Vulnerability · Source |
| CVE-2022-49652 | suse_vex | SUSE CVE CVE-2022-49652 | known affected: 462 known not affected: 215 recommended: 316 | 2026-10-17T01:19:44+00:00 | Vulnerability · Source |
| CVE-2022-49664 | suse_vex | SUSE CVE CVE-2022-49664 | known affected: 61 known not affected: 401 recommended: 42 | 2026-10-17T01:19:42+00:00 | Vulnerability · Source |
| CVE-2022-49692 | suse_vex | SUSE CVE CVE-2022-49692 | known affected: 0 known not affected: 462 | 2026-10-17T01:19:41+00:00 | Vulnerability · Source |
| CVE-2022-49693 | suse_vex | SUSE CVE CVE-2022-49693 | known affected: 462 known not affected: 215 recommended: 319 | 2026-10-17T01:19:39+00:00 | Vulnerability · Source |
| CVE-2022-49696 | suse_vex | SUSE CVE CVE-2022-49696 | known affected: 61 known not affected: 401 | 2026-10-17T01:19:38+00:00 | Vulnerability · Source |
| CVE-2022-49713 | suse_vex | SUSE CVE CVE-2022-49713 | known affected: 334 known not affected: 310 recommended: 319 | 2026-10-17T01:19:36+00:00 | Vulnerability · Source |
| CVE-2022-49726 | suse_vex | SUSE CVE CVE-2022-49726 | known affected: 407 known not affected: 267 recommended: 297 | 2026-10-17T01:19:34+00:00 | Vulnerability · Source |
| CVE-2022-49730 | suse_vex | SUSE CVE CVE-2022-49730 | known affected: 433 known not affected: 243 recommended: 319 | 2026-10-17T01:19:33+00:00 | Vulnerability · Source |
| CVE-2022-49747 | suse_vex | SUSE CVE CVE-2022-49747 | known affected: 0 known not affected: 456 recommended: 86 | 2026-10-17T01:19:32+00:00 | Vulnerability · Source |
| CVE-2022-49767 | suse_vex | SUSE CVE CVE-2022-49767 | known affected: 377 known not affected: 324 recommended: 296 | 2026-10-17T01:19:30+00:00 | Vulnerability · Source |
| CVE-2022-49810 | suse_vex | SUSE CVE CVE-2022-49810 | known affected: 339 known not affected: 383 recommended: 214 | 2026-10-17T01:19:28+00:00 | Vulnerability · Source |
| CVE-2022-49842 | suse_vex | SUSE CVE CVE-2022-49842 | known affected: 494 known not affected: 141 recommended: 318 | 2026-10-17T01:19:26+00:00 | Vulnerability · Source |
| CVE-2022-49843 | suse_vex | SUSE CVE CVE-2022-49843 | known affected: 0 known not affected: 504 | 2026-10-17T01:19:25+00:00 | Vulnerability · Source |
| CVE-2022-49844 | suse_vex | SUSE CVE CVE-2022-49844 | known affected: 0 known not affected: 507 | 2026-10-17T01:19:23+00:00 | Vulnerability · Source |
| CVE-2022-49848 | suse_vex | SUSE CVE CVE-2022-49848 | known affected: 0 known not affected: 502 recommended: 54 | 2026-10-17T01:19:22+00:00 | Vulnerability · Source |