VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283448 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49368 | suse_vex | SUSE CVE CVE-2022-49368 | known affected: 422 known not affected: 248 recommended: 223 | 2026-07-25T17:14:23+00:00 | Vulnerability · Source |
| CVE-2022-49375 | suse_vex | SUSE CVE CVE-2022-49375 | known affected: 334 known not affected: 321 recommended: 293 | 2026-07-25T17:14:21+00:00 | Vulnerability · Source |
| CVE-2022-49378 | suse_vex | SUSE CVE CVE-2022-49378 | known affected: 385 known not affected: 247 recommended: 265 | 2026-07-25T17:14:20+00:00 | Vulnerability · Source |
| CVE-2022-49385 | suse_vex | SUSE CVE CVE-2022-49385 | known affected: 421 known not affected: 193 recommended: 333 | 2026-07-25T17:14:17+00:00 | Vulnerability · Source |
| CVE-2022-49386 | suse_vex | SUSE CVE CVE-2022-49386 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:14:16+00:00 | Vulnerability · Source |
| CVE-2022-49390 | suse_vex | SUSE CVE CVE-2022-49390 | known affected: 513 known not affected: 165 recommended: 126 | 2026-07-25T17:14:14+00:00 | Vulnerability · Source |
| CVE-2022-49392 | suse_vex | SUSE CVE CVE-2022-49392 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:14:13+00:00 | Vulnerability · Source |
| CVE-2022-49393 | suse_vex | SUSE CVE CVE-2022-49393 | known not affected: 352 | 2026-07-25T17:14:11+00:00 | Vulnerability · Source |
| CVE-2022-49394 | suse_vex | SUSE CVE CVE-2022-49394 | known affected: 348 known not affected: 256 recommended: 315 | 2026-07-25T17:14:10+00:00 | Vulnerability · Source |
| CVE-2022-49397 | suse_vex | SUSE CVE CVE-2022-49397 | known affected: 407 known not affected: 173 recommended: 319 | 2026-07-25T17:14:08+00:00 | Vulnerability · Source |
| CVE-2022-49401 | suse_vex | SUSE CVE CVE-2022-49401 | known not affected: 352 recommended: 47 | 2026-07-25T17:14:07+00:00 | Vulnerability · Source |
| CVE-2022-49404 | suse_vex | SUSE CVE CVE-2022-49404 | known affected: 421 known not affected: 157 recommended: 375 | 2026-07-25T17:14:05+00:00 | Vulnerability · Source |
| CVE-2022-49406 | suse_vex | SUSE CVE CVE-2022-49406 | known affected: 364 known not affected: 302 recommended: 100 | 2026-07-25T17:14:04+00:00 | Vulnerability · Source |
| CVE-2022-49409 | suse_vex | SUSE CVE CVE-2022-49409 | known affected: 409 known not affected: 205 recommended: 375 | 2026-07-25T17:14:01+00:00 | Vulnerability · Source |
| CVE-2022-49412 | suse_vex | SUSE CVE CVE-2022-49412 | known affected: 334 known not affected: 298 recommended: 245 | 2026-07-25T17:14:00+00:00 | Vulnerability · Source |
| CVE-2022-49419 | suse_vex | SUSE CVE CVE-2022-49419 | known affected: 364 known not affected: 302 recommended: 100 | 2026-07-25T17:13:58+00:00 | Vulnerability · Source |
| CVE-2022-49421 | suse_vex | SUSE CVE CVE-2022-49421 | known affected: 409 known not affected: 207 recommended: 319 | 2026-07-25T17:13:57+00:00 | Vulnerability · Source |
| CVE-2022-49425 | suse_vex | SUSE CVE CVE-2022-49425 | known not affected: 403 | 2026-07-25T17:13:56+00:00 | Vulnerability · Source |
| CVE-2022-49427 | suse_vex | SUSE CVE CVE-2022-49427 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:13:54+00:00 | Vulnerability · Source |
| CVE-2022-49429 | suse_vex | SUSE CVE CVE-2022-49429 | known affected: 446 known not affected: 211 recommended: 310 | 2026-07-25T17:13:53+00:00 | Vulnerability · Source |
| CVE-2022-49433 | suse_vex | SUSE CVE CVE-2022-49433 | known affected: 458 known not affected: 148 recommended: 305 | 2026-07-25T17:13:51+00:00 | Vulnerability · Source |
| CVE-2022-49434 | suse_vex | SUSE CVE CVE-2022-49434 | known affected: 446 known not affected: 222 recommended: 276 | 2026-07-25T17:13:50+00:00 | Vulnerability · Source |
| CVE-2022-49436 | suse_vex | SUSE CVE CVE-2022-49436 | known affected: 364 known not affected: 302 recommended: 100 | 2026-07-25T17:13:48+00:00 | Vulnerability · Source |
| CVE-2022-49439 | suse_vex | SUSE CVE CVE-2022-49439 | known affected: 171 known not affected: 219 | 2026-07-25T17:13:47+00:00 | Vulnerability · Source |
| CVE-2022-49444 | suse_vex | SUSE CVE CVE-2022-49444 | known affected: 397 known not affected: 211 recommended: 249 | 2026-07-25T17:13:45+00:00 | Vulnerability · Source |
| CVE-2022-49447 | suse_vex | SUSE CVE CVE-2022-49447 | known affected: 334 known not affected: 294 recommended: 223 | 2026-07-25T17:13:44+00:00 | Vulnerability · Source |
| CVE-2022-49449 | suse_vex | SUSE CVE CVE-2022-49449 | known affected: 385 known not affected: 243 recommended: 223 | 2026-07-25T17:13:42+00:00 | Vulnerability · Source |
| CVE-2022-49450 | suse_vex | SUSE CVE CVE-2022-49450 | known affected: 139 known not affected: 247 | 2026-07-25T17:13:41+00:00 | Vulnerability · Source |
| CVE-2022-49451 | suse_vex | SUSE CVE CVE-2022-49451 | known affected: 348 known not affected: 256 recommended: 320 | 2026-07-25T17:13:40+00:00 | Vulnerability · Source |
| CVE-2022-49456 | suse_vex | SUSE CVE CVE-2022-49456 | known not affected: 352 | 2026-07-25T17:13:38+00:00 | Vulnerability · Source |
| CVE-2022-49457 | suse_vex | SUSE CVE CVE-2022-49457 | known not affected: 348 | 2026-07-25T17:13:37+00:00 | Vulnerability · Source |
| CVE-2022-49459 | suse_vex | SUSE CVE CVE-2022-49459 | known affected: 348 known not affected: 256 recommended: 293 | 2026-07-25T17:13:35+00:00 | Vulnerability · Source |
| CVE-2022-49463 | suse_vex | SUSE CVE CVE-2022-49463 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:13:34+00:00 | Vulnerability · Source |
| CVE-2022-49468 | suse_vex | SUSE CVE CVE-2022-49468 | known affected: 385 known not affected: 247 recommended: 223 | 2026-07-25T17:13:32+00:00 | Vulnerability · Source |
| CVE-2022-49470 | suse_vex | SUSE CVE CVE-2022-49470 | known affected: 470 known not affected: 196 recommended: 100 | 2026-07-25T17:13:31+00:00 | Vulnerability · Source |
| CVE-2022-49473 | suse_vex | SUSE CVE CVE-2022-49473 | known affected: 334 known not affected: 270 recommended: 293 | 2026-07-25T17:13:29+00:00 | Vulnerability · Source |
| CVE-2022-49474 | suse_vex | SUSE CVE CVE-2022-49474 | known affected: 360 known not affected: 256 recommended: 316 | 2026-07-25T17:13:28+00:00 | Vulnerability · Source |
| CVE-2022-49475 | suse_vex | SUSE CVE CVE-2022-49475 | known affected: 334 known not affected: 270 recommended: 293 | 2026-07-25T17:13:27+00:00 | Vulnerability · Source |
| CVE-2022-49477 | suse_vex | SUSE CVE CVE-2022-49477 | known affected: 371 known not affected: 261 recommended: 223 | 2026-07-25T17:13:25+00:00 | Vulnerability · Source |
| CVE-2022-49482 | suse_vex | SUSE CVE CVE-2022-49482 | known affected: 385 known not affected: 257 recommended: 293 | 2026-07-25T17:13:23+00:00 | Vulnerability · Source |
| CVE-2022-49489 | suse_vex | SUSE CVE CVE-2022-49489 | known affected: 377 known not affected: 239 recommended: 319 | 2026-07-25T17:13:21+00:00 | Vulnerability · Source |
| CVE-2022-49490 | suse_vex | SUSE CVE CVE-2022-49490 | known affected: 377 known not affected: 201 recommended: 319 | 2026-07-25T17:13:20+00:00 | Vulnerability · Source |
| CVE-2022-49494 | suse_vex | SUSE CVE CVE-2022-49494 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:13:18+00:00 | Vulnerability · Source |
| CVE-2022-49497 | suse_vex | SUSE CVE CVE-2022-49497 | known affected: 545 known not affected: 91 recommended: 140 | 2026-07-25T17:13:17+00:00 | Vulnerability · Source |
| CVE-2022-49498 | suse_vex | SUSE CVE CVE-2022-49498 | known affected: 334 known not affected: 270 recommended: 293 | 2026-07-25T17:13:16+00:00 | Vulnerability · Source |
| CVE-2022-49513 | suse_vex | SUSE CVE CVE-2022-49513 | known affected: 559 known not affected: 163 recommended: 73 | 2026-07-25T17:13:14+00:00 | Vulnerability · Source |
| CVE-2022-49517 | suse_vex | SUSE CVE CVE-2022-49517 | known affected: 385 known not affected: 257 recommended: 293 | 2026-07-25T17:13:12+00:00 | Vulnerability · Source |
| CVE-2022-49519 | suse_vex | SUSE CVE CVE-2022-49519 | known affected: 454 known not affected: 148 recommended: 310 | 2026-07-25T17:13:11+00:00 | Vulnerability · Source |
| CVE-2022-49522 | suse_vex | SUSE CVE CVE-2022-49522 | known affected: 365 known not affected: 235 recommended: 293 | 2026-07-25T17:13:09+00:00 | Vulnerability · Source |
| CVE-2022-49523 | suse_vex | SUSE CVE CVE-2022-49523 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:13:08+00:00 | Vulnerability · Source |