VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
304228 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-48920 | suse_vex | SUSE CVE CVE-2022-48920 | known affected: 576 known not affected: 83 recommended: 358 | 2026-10-02T00:34:52+00:00 | Vulnerability · Source |
| CVE-2022-48931 | suse_vex | SUSE CVE CVE-2022-48931 | known affected: 478 known not affected: 57 recommended: 495 | 2026-10-02T00:34:50+00:00 | Vulnerability · Source |
| CVE-2022-48960 | suse_vex | SUSE CVE CVE-2022-48960 | known affected: 369 known not affected: 224 recommended: 549 | 2026-10-02T00:34:48+00:00 | Vulnerability · Source |
| CVE-2022-48962 | suse_vex | SUSE CVE CVE-2022-48962 | known affected: 382 known not affected: 188 recommended: 549 | 2026-10-02T00:34:46+00:00 | Vulnerability · Source |
| CVE-2022-48967 | suse_vex | SUSE CVE CVE-2022-48967 | known affected: 455 known not affected: 109 recommended: 577 | 2026-10-02T00:34:44+00:00 | Vulnerability · Source |
| CVE-2022-48992 | suse_vex | SUSE CVE CVE-2022-48992 | known affected: 541 known not affected: 107 recommended: 481 | 2026-10-02T00:34:43+00:00 | Vulnerability · Source |
| CVE-2022-49006 | suse_vex | SUSE CVE CVE-2022-49006 | known affected: 492 known not affected: 110 recommended: 561 | 2026-10-02T00:34:41+00:00 | Vulnerability · Source |
| CVE-2022-49029 | suse_vex | SUSE CVE CVE-2022-49029 | known affected: 504 known not affected: 110 recommended: 561 | 2026-10-02T00:34:39+00:00 | Vulnerability · Source |
| CVE-2022-49043 | suse_vex | SUSE CVE CVE-2022-49043 | known affected: 462 known not affected: 473 recommended: 237 | 2026-10-02T00:34:38+00:00 | Vulnerability · Source |
| CVE-2022-49046 | suse_vex | SUSE CVE CVE-2022-49046 | known affected: 667 known not affected: 143 recommended: 26 | 2026-10-02T00:34:36+00:00 | Vulnerability · Source |
| CVE-2022-49053 | suse_vex | SUSE CVE CVE-2022-49053 | known affected: 486 known not affected: 111 recommended: 362 | 2026-10-02T00:34:34+00:00 | Vulnerability · Source |
| CVE-2022-49066 | suse_vex | SUSE CVE CVE-2022-49066 | known affected: 530 known not affected: 157 recommended: 305 | 2026-10-02T00:34:32+00:00 | Vulnerability · Source |
| CVE-2022-49075 | suse_vex | SUSE CVE CVE-2022-49075 | known affected: 600 known not affected: 118 recommended: 140 | 2026-10-02T00:34:31+00:00 | Vulnerability · Source |
| CVE-2022-49111 | suse_vex | SUSE CVE CVE-2022-49111 | known affected: 495 known not affected: 188 recommended: 393 | 2026-10-02T00:34:29+00:00 | Vulnerability · Source |
| CVE-2022-49119 | suse_vex | SUSE CVE CVE-2022-49119 | known affected: 543 known not affected: 141 recommended: 263 | 2026-10-02T00:34:27+00:00 | Vulnerability · Source |
| CVE-2022-49121 | suse_vex | SUSE CVE CVE-2022-49121 | known affected: 546 known not affected: 173 recommended: 263 | 2026-10-02T00:34:26+00:00 | Vulnerability · Source |
| CVE-2022-49122 | suse_vex | SUSE CVE CVE-2022-49122 | known affected: 481 known not affected: 170 recommended: 375 | 2026-10-02T00:34:24+00:00 | Vulnerability · Source |
| CVE-2022-49134 | suse_vex | SUSE CVE CVE-2022-49134 | known affected: 490 known not affected: 229 recommended: 140 | 2026-10-02T00:34:22+00:00 | Vulnerability · Source |
| CVE-2022-49135 | suse_vex | SUSE CVE CVE-2022-49135 | known affected: 350 known not affected: 337 recommended: 249 | 2026-10-02T00:34:21+00:00 | Vulnerability · Source |
| CVE-2022-49145 | suse_vex | SUSE CVE CVE-2022-49145 | known affected: 497 known not affected: 228 recommended: 436 | 2026-10-02T00:34:19+00:00 | Vulnerability · Source |
| CVE-2022-49156 | suse_vex | SUSE CVE CVE-2022-49156 | known affected: 487 known not affected: 164 recommended: 375 | 2026-10-02T00:34:17+00:00 | Vulnerability · Source |
| CVE-2022-49164 | suse_vex | SUSE CVE CVE-2022-49164 | known affected: 481 known not affected: 266 recommended: 319 | 2026-10-02T00:34:15+00:00 | Vulnerability · Source |
| CVE-2022-49201 | suse_vex | SUSE CVE CVE-2022-49201 | known affected: 461 known not affected: 127 recommended: 319 | 2026-10-02T00:34:13+00:00 | Vulnerability · Source |
| CVE-2022-49217 | suse_vex | SUSE CVE CVE-2022-49217 | known affected: 481 known not affected: 170 recommended: 333 | 2026-10-02T00:34:11+00:00 | Vulnerability · Source |
| CVE-2022-49248 | suse_vex | SUSE CVE CVE-2022-49248 | known affected: 494 known not affected: 186 recommended: 330 | 2026-10-02T00:34:09+00:00 | Vulnerability · Source |
| CVE-2022-49253 | suse_vex | SUSE CVE CVE-2022-49253 | known affected: 497 known not affected: 156 recommended: 352 | 2026-10-02T00:34:07+00:00 | Vulnerability · Source |
| CVE-2022-49275 | suse_vex | SUSE CVE CVE-2022-49275 | known affected: 495 known not affected: 147 recommended: 372 | 2026-10-02T00:34:05+00:00 | Vulnerability · Source |
| CVE-2022-49290 | suse_vex | SUSE CVE CVE-2022-49290 | known affected: 409 known not affected: 245 recommended: 361 | 2026-10-02T00:34:03+00:00 | Vulnerability · Source |
| CVE-2022-49305 | suse_vex | SUSE CVE CVE-2022-49305 | known affected: 372 known not affected: 272 recommended: 333 | 2026-10-02T00:34:01+00:00 | Vulnerability · Source |
| CVE-2022-49313 | suse_vex | SUSE CVE CVE-2022-49313 | known affected: 340 known not affected: 304 recommended: 319 | 2026-10-02T00:33:59+00:00 | Vulnerability · Source |
| CVE-2022-49320 | suse_vex | SUSE CVE CVE-2022-49320 | known affected: 459 known not affected: 216 recommended: 406 | 2026-10-02T00:33:57+00:00 | Vulnerability · Source |
| CVE-2022-49326 | suse_vex | SUSE CVE CVE-2022-49326 | known affected: 489 known not affected: 154 recommended: 330 | 2026-10-02T00:33:55+00:00 | Vulnerability · Source |
| CVE-2022-49335 | suse_vex | SUSE CVE CVE-2022-49335 | known affected: 334 known not affected: 309 recommended: 333 | 2026-10-02T00:33:54+00:00 | Vulnerability · Source |
| CVE-2022-49344 | suse_vex | SUSE CVE CVE-2022-49344 | known affected: 667 known not affected: 144 recommended: 69 | 2026-10-02T00:33:52+00:00 | Vulnerability · Source |
| CVE-2022-49349 | suse_vex | SUSE CVE CVE-2022-49349 | known affected: 481 known not affected: 194 recommended: 375 | 2026-10-02T00:33:50+00:00 | Vulnerability · Source |
| CVE-2022-49367 | suse_vex | SUSE CVE CVE-2022-49367 | known affected: 509 known not affected: 177 recommended: 249 | 2026-10-02T00:33:48+00:00 | Vulnerability · Source |
| CVE-2022-49372 | suse_vex | SUSE CVE CVE-2022-49372 | known affected: 658 known not affected: 150 recommended: 87 | 2026-10-02T00:33:46+00:00 | Vulnerability · Source |
| CVE-2022-49404 | suse_vex | SUSE CVE CVE-2022-49404 | known affected: 497 known not affected: 156 recommended: 375 | 2026-10-02T00:33:44+00:00 | Vulnerability · Source |
| CVE-2022-49411 | suse_vex | SUSE CVE CVE-2022-49411 | known affected: 466 known not affected: 217 recommended: 341 | 2026-10-02T00:33:42+00:00 | Vulnerability · Source |
| CVE-2022-49421 | suse_vex | SUSE CVE CVE-2022-49421 | known affected: 481 known not affected: 205 recommended: 319 | 2026-10-02T00:33:40+00:00 | Vulnerability · Source |
| CVE-2022-49433 | suse_vex | SUSE CVE CVE-2022-49433 | known affected: 540 known not affected: 147 recommended: 305 | 2026-10-02T00:33:38+00:00 | Vulnerability · Source |
| CVE-2022-49437 | suse_vex | SUSE CVE CVE-2022-49437 | known affected: 453 known not affected: 198 recommended: 360 | 2026-10-02T00:33:35+00:00 | Vulnerability · Source |
| CVE-2022-49441 | suse_vex | SUSE CVE CVE-2022-49441 | known affected: 503 known not affected: 180 recommended: 330 | 2026-10-02T00:33:33+00:00 | Vulnerability · Source |
| CVE-2022-49443 | suse_vex | SUSE CVE CVE-2022-49443 | known affected: 496 known not affected: 191 recommended: 290 | 2026-10-02T00:33:32+00:00 | Vulnerability · Source |
| CVE-2022-49445 | suse_vex | SUSE CVE CVE-2022-49445 | known affected: 537 known not affected: 179 recommended: 260 | 2026-10-02T00:33:30+00:00 | Vulnerability · Source |
| CVE-2022-49478 | suse_vex | SUSE CVE CVE-2022-49478 | known affected: 503 known not affected: 182 recommended: 333 | 2026-10-02T00:33:28+00:00 | Vulnerability · Source |
| CVE-2022-49516 | suse_vex | SUSE CVE CVE-2022-49516 | known affected: 468 known not affected: 245 recommended: 126 | 2026-10-02T00:33:25+00:00 | Vulnerability · Source |
| CVE-2022-49524 | suse_vex | SUSE CVE CVE-2022-49524 | known affected: 461 known not affected: 184 recommended: 319 | 2026-10-02T00:33:23+00:00 | Vulnerability · Source |
| CVE-2022-49546 | suse_vex | SUSE CVE CVE-2022-49546 | known affected: 493 known not affected: 156 recommended: 333 | 2026-10-02T00:33:20+00:00 | Vulnerability · Source |
| CVE-2022-49563 | suse_vex | SUSE CVE CVE-2022-49563 | known affected: 494 known not affected: 147 recommended: 370 | 2026-10-02T00:33:18+00:00 | Vulnerability · Source |