VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291709 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49422 | suse_vex | SUSE CVE CVE-2022-49422 | known affected: 334 known not affected: 268 recommended: 293 | 2026-08-13T02:25:22+00:00 | Vulnerability · Source |
| CVE-2022-49427 | suse_vex | SUSE CVE CVE-2022-49427 | known affected: 334 known not affected: 294 recommended: 223 | 2026-08-13T02:25:21+00:00 | Vulnerability · Source |
| CVE-2022-49428 | suse_vex | SUSE CVE CVE-2022-49428 | known not affected: 403 | 2026-08-13T02:25:19+00:00 | Vulnerability · Source |
| CVE-2022-49429 | suse_vex | SUSE CVE CVE-2022-49429 | known affected: 446 known not affected: 211 recommended: 310 | 2026-08-13T02:25:18+00:00 | Vulnerability · Source |
| CVE-2022-49431 | suse_vex | SUSE CVE CVE-2022-49431 | known affected: 486 known not affected: 204 recommended: 223 | 2026-08-13T02:25:17+00:00 | Vulnerability · Source |
| CVE-2022-49436 | suse_vex | SUSE CVE CVE-2022-49436 | known affected: 364 known not affected: 302 recommended: 100 | 2026-08-13T02:25:15+00:00 | Vulnerability · Source |
| CVE-2022-49437 | suse_vex | SUSE CVE CVE-2022-49437 | known affected: 395 known not affected: 181 recommended: 360 | 2026-08-13T02:25:14+00:00 | Vulnerability · Source |
| CVE-2022-49440 | suse_vex | SUSE CVE CVE-2022-49440 | known affected: 385 known not affected: 239 recommended: 245 | 2026-08-13T02:25:12+00:00 | Vulnerability · Source |
| CVE-2022-49451 | suse_vex | SUSE CVE CVE-2022-49451 | known affected: 348 known not affected: 254 recommended: 320 | 2026-08-13T02:25:10+00:00 | Vulnerability · Source |
| CVE-2022-49455 | suse_vex | SUSE CVE CVE-2022-49455 | known affected: 348 known not affected: 256 recommended: 293 | 2026-08-13T02:25:08+00:00 | Vulnerability · Source |
| CVE-2022-49458 | suse_vex | SUSE CVE CVE-2022-49458 | known affected: 364 known not affected: 301 recommended: 100 | 2026-08-13T02:25:07+00:00 | Vulnerability · Source |
| CVE-2022-49459 | suse_vex | SUSE CVE CVE-2022-49459 | known affected: 348 known not affected: 256 recommended: 293 | 2026-08-13T02:25:05+00:00 | Vulnerability · Source |
| CVE-2022-49465 | suse_vex | SUSE CVE CVE-2022-49465 | known affected: 404 known not affected: 161 recommended: 398 | 2026-08-13T02:25:03+00:00 | Vulnerability · Source |
| CVE-2022-49467 | suse_vex | SUSE CVE CVE-2022-49467 | known affected: 418 known not affected: 193 recommended: 330 | 2026-08-13T02:25:01+00:00 | Vulnerability · Source |
| CVE-2022-49470 | suse_vex | SUSE CVE CVE-2022-49470 | known affected: 470 known not affected: 192 recommended: 100 | 2026-08-13T02:24:59+00:00 | Vulnerability · Source |
| CVE-2022-49473 | suse_vex | SUSE CVE CVE-2022-49473 | known affected: 334 known not affected: 270 recommended: 293 | 2026-08-13T02:24:57+00:00 | Vulnerability · Source |
| CVE-2022-49477 | suse_vex | SUSE CVE CVE-2022-49477 | known affected: 371 known not affected: 257 recommended: 223 | 2026-08-13T02:24:55+00:00 | Vulnerability · Source |
| CVE-2022-49479 | suse_vex | SUSE CVE CVE-2022-49479 | known affected: 364 known not affected: 298 recommended: 100 | 2026-08-13T02:24:54+00:00 | Vulnerability · Source |
| CVE-2022-49480 | suse_vex | SUSE CVE CVE-2022-49480 | known affected: 334 known not affected: 298 recommended: 223 | 2026-08-13T02:24:52+00:00 | Vulnerability · Source |
| CVE-2022-49487 | suse_vex | SUSE CVE CVE-2022-49487 | known affected: 334 known not affected: 298 recommended: 223 | 2026-08-13T02:24:50+00:00 | Vulnerability · Source |
| CVE-2022-49489 | suse_vex | SUSE CVE CVE-2022-49489 | known affected: 374 known not affected: 239 recommended: 319 | 2026-08-13T02:24:48+00:00 | Vulnerability · Source |
| CVE-2022-49490 | suse_vex | SUSE CVE CVE-2022-49490 | known affected: 377 known not affected: 200 recommended: 319 | 2026-08-13T02:24:46+00:00 | Vulnerability · Source |
| CVE-2022-49501 | suse_vex | SUSE CVE CVE-2022-49501 | known affected: 334 known not affected: 294 recommended: 223 | 2026-08-13T02:24:44+00:00 | Vulnerability · Source |
| CVE-2022-49504 | suse_vex | SUSE CVE CVE-2022-49504 | known affected: 385 known not affected: 190 recommended: 341 | 2026-08-13T02:24:43+00:00 | Vulnerability · Source |
| CVE-2022-49507 | suse_vex | SUSE CVE CVE-2022-49507 | known affected: 334 known not affected: 294 recommended: 223 | 2026-08-13T02:24:41+00:00 | Vulnerability · Source |
| CVE-2022-49512 | suse_vex | SUSE CVE CVE-2022-49512 | known affected: 385 known not affected: 247 recommended: 223 | 2026-08-13T02:24:40+00:00 | Vulnerability · Source |
| CVE-2022-49513 | suse_vex | SUSE CVE CVE-2022-49513 | known affected: 556 known not affected: 163 recommended: 73 | 2026-08-13T02:24:38+00:00 | Vulnerability · Source |
| CVE-2022-49515 | suse_vex | SUSE CVE CVE-2022-49515 | known affected: 334 known not affected: 294 recommended: 265 | 2026-08-13T02:24:37+00:00 | Vulnerability · Source |
| CVE-2022-49517 | suse_vex | SUSE CVE CVE-2022-49517 | known affected: 385 known not affected: 257 recommended: 293 | 2026-08-13T02:24:35+00:00 | Vulnerability · Source |
| CVE-2022-49523 | suse_vex | SUSE CVE CVE-2022-49523 | known affected: 334 known not affected: 294 recommended: 223 | 2026-08-13T02:24:34+00:00 | Vulnerability · Source |
| CVE-2022-49524 | suse_vex | SUSE CVE CVE-2022-49524 | known affected: 403 known not affected: 171 recommended: 319 | 2026-08-13T02:24:33+00:00 | Vulnerability · Source |
| CVE-2022-49526 | suse_vex | SUSE CVE CVE-2022-49526 | known affected: 378 known not affected: 196 recommended: 345 | 2026-08-13T02:24:31+00:00 | Vulnerability · Source |
| CVE-2022-49530 | suse_vex | SUSE CVE CVE-2022-49530 | known affected: 522 known not affected: 113 recommended: 126 | 2026-08-13T02:24:30+00:00 | Vulnerability · Source |
| CVE-2022-49532 | suse_vex | SUSE CVE CVE-2022-49532 | known affected: 409 known not affected: 218 recommended: 333 | 2026-08-13T02:24:28+00:00 | Vulnerability · Source |
| CVE-2022-49540 | suse_vex | SUSE CVE CVE-2022-49540 | known not affected: 354 | 2026-08-13T02:24:27+00:00 | Vulnerability · Source |
| CVE-2022-49542 | suse_vex | SUSE CVE CVE-2022-49542 | known affected: 360 known not affected: 256 recommended: 319 | 2026-08-13T02:24:26+00:00 | Vulnerability · Source |
| CVE-2022-49543 | suse_vex | SUSE CVE CVE-2022-49543 | known affected: 419 known not affected: 243 recommended: 142 | 2026-08-13T02:24:24+00:00 | Vulnerability · Source |
| CVE-2022-49560 | suse_vex | SUSE CVE CVE-2022-49560 | known affected: 470 known not affected: 192 recommended: 100 | 2026-08-13T02:24:22+00:00 | Vulnerability · Source |
| CVE-2022-49568 | suse_vex | SUSE CVE CVE-2022-49568 | known affected: 436 known not affected: 234 recommended: 223 | 2026-08-13T02:24:21+00:00 | Vulnerability · Source |
| CVE-2022-49577 | suse_vex | SUSE CVE CVE-2022-49577 | known not affected: 163 recommended: 47 | 2026-08-13T02:24:19+00:00 | Vulnerability · Source |
| CVE-2022-49592 | suse_vex | SUSE CVE CVE-2022-49592 | known affected: 436 known not affected: 205 recommended: 293 | 2026-08-13T02:24:17+00:00 | Vulnerability · Source |
| CVE-2022-49604 | suse_vex | SUSE CVE CVE-2022-49604 | known affected: 394 known not affected: 90 recommended: 210 | 2026-08-13T02:24:14+00:00 | Vulnerability · Source |
| CVE-2022-49606 | suse_vex | SUSE CVE CVE-2022-49606 | known affected: 334 known not affected: 294 recommended: 265 | 2026-08-13T02:24:13+00:00 | Vulnerability · Source |
| CVE-2022-49611 | suse_vex | SUSE CVE CVE-2022-49611 | known not affected: 237 recommended: 305 | 2026-08-13T02:24:11+00:00 | Vulnerability · Source |
| CVE-2022-49624 | suse_vex | SUSE CVE CVE-2022-49624 | known affected: 364 known not affected: 298 recommended: 100 | 2026-08-13T02:24:10+00:00 | Vulnerability · Source |
| CVE-2022-49626 | suse_vex | SUSE CVE CVE-2022-49626 | known affected: 458 known not affected: 148 recommended: 305 | 2026-08-13T02:24:08+00:00 | Vulnerability · Source |
| CVE-2022-49627 | suse_vex | SUSE CVE CVE-2022-49627 | known affected: 348 known not affected: 254 recommended: 334 | 2026-08-13T02:24:07+00:00 | Vulnerability · Source |
| CVE-2022-49638 | suse_vex | SUSE CVE CVE-2022-49638 | known not affected: 109 recommended: 123 | 2026-08-13T02:24:05+00:00 | Vulnerability · Source |
| CVE-2022-49641 | suse_vex | SUSE CVE CVE-2022-49641 | known affected: 421 known not affected: 157 recommended: 360 | 2026-08-13T02:24:03+00:00 | Vulnerability · Source |
| CVE-2022-49644 | suse_vex | SUSE CVE CVE-2022-49644 | known affected: 399 known not affected: 242 recommended: 340 | 2026-08-13T02:24:02+00:00 | Vulnerability · Source |