VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
99436 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49389 | suse_vex | SUSE CVE CVE-2022-49389 | known affected: 481 known not affected: 195 recommended: 355 | 2026-10-16T14:23:42+00:00 | Vulnerability · Source |
| CVE-2022-49391 | suse_vex | SUSE CVE CVE-2022-49391 | known affected: 0 known not affected: 462 | 2026-10-16T14:23:40+00:00 | Vulnerability · Source |
| CVE-2022-49393 | suse_vex | SUSE CVE CVE-2022-49393 | known affected: 0 known not affected: 462 | 2026-10-16T14:23:38+00:00 | Vulnerability · Source |
| CVE-2022-49394 | suse_vex | SUSE CVE CVE-2022-49394 | known affected: 360 known not affected: 336 recommended: 315 | 2026-10-16T14:23:35+00:00 | Vulnerability · Source |
| CVE-2022-49396 | suse_vex | SUSE CVE CVE-2022-49396 | known affected: 465 known not affected: 215 recommended: 316 | 2026-10-16T14:23:33+00:00 | Vulnerability · Source |
| CVE-2022-49397 | suse_vex | SUSE CVE CVE-2022-49397 | known affected: 465 known not affected: 183 recommended: 319 | 2026-10-16T14:23:30+00:00 | Vulnerability · Source |
| CVE-2022-49398 | suse_vex | SUSE CVE CVE-2022-49398 | known affected: 360 known not affected: 336 recommended: 335 | 2026-10-16T14:23:27+00:00 | Vulnerability · Source |
| CVE-2022-49399 | suse_vex | SUSE CVE CVE-2022-49399 | known affected: 425 known not affected: 303 recommended: 293 | 2026-10-16T14:23:24+00:00 | Vulnerability · Source |
| CVE-2022-49401 | suse_vex | SUSE CVE CVE-2022-49401 | known affected: 0 known not affected: 462 recommended: 74 | 2026-10-16T14:23:22+00:00 | Vulnerability · Source |
| CVE-2022-49402 | suse_vex | SUSE CVE CVE-2022-49402 | known affected: 334 known not affected: 362 recommended: 293 | 2026-10-16T14:23:20+00:00 | Vulnerability · Source |
| CVE-2022-49404 | suse_vex | SUSE CVE CVE-2022-49404 | known affected: 493 known not affected: 153 recommended: 375 | 2026-10-16T14:23:18+00:00 | Vulnerability · Source |
| CVE-2022-49407 | suse_vex | SUSE CVE CVE-2022-49407 | known affected: 530 known not affected: 150 recommended: 263 | 2026-10-16T14:23:15+00:00 | Vulnerability · Source |
| CVE-2022-49408 | suse_vex | SUSE CVE CVE-2022-49408 | known affected: 0 known not affected: 462 recommended: 22 | 2026-10-16T14:23:13+00:00 | Vulnerability · Source |
| CVE-2022-49409 | suse_vex | SUSE CVE CVE-2022-49409 | known affected: 481 known not affected: 196 recommended: 375 | 2026-10-16T14:23:11+00:00 | Vulnerability · Source |
| CVE-2022-49411 | suse_vex | SUSE CVE CVE-2022-49411 | known affected: 462 known not affected: 214 recommended: 341 | 2026-10-16T14:23:10+00:00 | Vulnerability · Source |
| CVE-2022-49416 | suse_vex | SUSE CVE CVE-2022-49416 | known affected: 493 known not affected: 153 recommended: 407 | 2026-10-16T14:23:07+00:00 | Vulnerability · Source |
| CVE-2022-49419 | suse_vex | SUSE CVE CVE-2022-49419 | known affected: 364 known not affected: 398 recommended: 100 | 2026-10-16T14:23:05+00:00 | Vulnerability · Source |
| CVE-2022-49421 | suse_vex | SUSE CVE CVE-2022-49421 | known affected: 481 known not affected: 198 recommended: 319 | 2026-10-16T14:23:02+00:00 | Vulnerability · Source |
| CVE-2022-49423 | suse_vex | SUSE CVE CVE-2022-49423 | known affected: 0 known not affected: 462 | 2026-10-16T14:23:00+00:00 | Vulnerability · Source |
| CVE-2022-49428 | suse_vex | SUSE CVE CVE-2022-49428 | known affected: 0 known not affected: 506 | 2026-10-16T14:22:57+00:00 | Vulnerability · Source |
| CVE-2022-49431 | suse_vex | SUSE CVE CVE-2022-49431 | known affected: 590 known not affected: 195 recommended: 223 | 2026-10-16T14:22:55+00:00 | Vulnerability · Source |
| CVE-2022-49434 | suse_vex | SUSE CVE CVE-2022-49434 | known affected: 524 known not affected: 213 recommended: 303 | 2026-10-16T14:22:53+00:00 | Vulnerability · Source |
| CVE-2022-49438 | suse_vex | SUSE CVE CVE-2022-49438 | known affected: 334 known not affected: 406 recommended: 293 | 2026-10-16T14:22:51+00:00 | Vulnerability · Source |
| CVE-2022-49441 | suse_vex | SUSE CVE CVE-2022-49441 | known affected: 499 known not affected: 177 recommended: 330 | 2026-10-16T14:22:49+00:00 | Vulnerability · Source |
| CVE-2022-49445 | suse_vex | SUSE CVE CVE-2022-49445 | known affected: 533 known not affected: 176 recommended: 260 | 2026-10-16T14:22:47+00:00 | Vulnerability · Source |
| CVE-2022-49446 | suse_vex | SUSE CVE CVE-2022-49446 | known affected: 425 known not affected: 305 recommended: 170 | 2026-10-16T14:22:45+00:00 | Vulnerability · Source |
| CVE-2022-49448 | suse_vex | SUSE CVE CVE-2022-49448 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:22:42+00:00 | Vulnerability · Source |
| CVE-2022-49450 | suse_vex | SUSE CVE CVE-2022-49450 | known affected: 195 known not affected: 297 | 2026-10-16T14:22:40+00:00 | Vulnerability · Source |
| CVE-2022-49453 | suse_vex | SUSE CVE CVE-2022-49453 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:22:37+00:00 | Vulnerability · Source |
| CVE-2022-49455 | suse_vex | SUSE CVE CVE-2022-49455 | known affected: 360 known not affected: 336 recommended: 293 | 2026-10-16T14:22:35+00:00 | Vulnerability · Source |
| CVE-2022-49459 | suse_vex | SUSE CVE CVE-2022-49459 | known affected: 360 known not affected: 338 recommended: 293 | 2026-10-16T14:22:32+00:00 | Vulnerability · Source |
| CVE-2022-49463 | suse_vex | SUSE CVE CVE-2022-49463 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:22:30+00:00 | Vulnerability · Source |
| CVE-2022-49465 | suse_vex | SUSE CVE CVE-2022-49465 | known affected: 448 known not affected: 175 recommended: 398 | 2026-10-16T14:22:28+00:00 | Vulnerability · Source |
| CVE-2022-49467 | suse_vex | SUSE CVE CVE-2022-49467 | known affected: 490 known not affected: 185 recommended: 330 | 2026-10-16T14:22:25+00:00 | Vulnerability · Source |
| CVE-2022-49469 | suse_vex | SUSE CVE CVE-2022-49469 | known affected: 130 known not affected: 362 | 2026-10-16T14:22:23+00:00 | Vulnerability · Source |
| CVE-2022-49470 | suse_vex | SUSE CVE CVE-2022-49470 | known affected: 494 known not affected: 268 recommended: 100 | 2026-10-16T14:22:20+00:00 | Vulnerability · Source |
| CVE-2022-49471 | suse_vex | SUSE CVE CVE-2022-49471 | known affected: 128 known not affected: 330 recommended: 74 | 2026-10-16T14:22:18+00:00 | Vulnerability · Source |
| CVE-2022-49472 | suse_vex | SUSE CVE CVE-2022-49472 | known affected: 529 known not affected: 144 recommended: 263 | 2026-10-16T14:22:16+00:00 | Vulnerability · Source |
| CVE-2022-49473 | suse_vex | SUSE CVE CVE-2022-49473 | known affected: 334 known not affected: 362 recommended: 293 | 2026-10-16T14:22:13+00:00 | Vulnerability · Source |
| CVE-2022-49476 | suse_vex | SUSE CVE CVE-2022-49476 | known affected: 425 known not affected: 341 recommended: 100 | 2026-10-16T14:22:11+00:00 | Vulnerability · Source |
| CVE-2022-49478 | suse_vex | SUSE CVE CVE-2022-49478 | known affected: 499 known not affected: 179 recommended: 333 | 2026-10-16T14:22:08+00:00 | Vulnerability · Source |
| CVE-2022-49484 | suse_vex | SUSE CVE CVE-2022-49484 | known affected: 425 known not affected: 341 recommended: 100 | 2026-10-16T14:22:06+00:00 | Vulnerability · Source |
| CVE-2022-49486 | suse_vex | SUSE CVE CVE-2022-49486 | known affected: 500 known not affected: 266 recommended: 223 | 2026-10-16T14:22:03+00:00 | Vulnerability · Source |
| CVE-2022-49488 | suse_vex | SUSE CVE CVE-2022-49488 | known affected: 405 known not affected: 242 recommended: 319 | 2026-10-16T14:22:01+00:00 | Vulnerability · Source |
| CVE-2022-49490 | suse_vex | SUSE CVE CVE-2022-49490 | known affected: 405 known not affected: 240 recommended: 319 | 2026-10-16T14:21:59+00:00 | Vulnerability · Source |
| CVE-2022-49494 | suse_vex | SUSE CVE CVE-2022-49494 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:21:57+00:00 | Vulnerability · Source |
| CVE-2022-49502 | suse_vex | SUSE CVE CVE-2022-49502 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:21:54+00:00 | Vulnerability · Source |
| CVE-2022-49506 | suse_vex | SUSE CVE CVE-2022-49506 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:21:51+00:00 | Vulnerability · Source |
| CVE-2022-49507 | suse_vex | SUSE CVE CVE-2022-49507 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:21:49+00:00 | Vulnerability · Source |
| CVE-2022-49512 | suse_vex | SUSE CVE CVE-2022-49512 | known affected: 403 known not affected: 329 recommended: 223 | 2026-10-16T14:21:47+00:00 | Vulnerability · Source |