VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
307377 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-48925 | suse_vex | SUSE CVE CVE-2022-48925 | known affected: 312 known not affected: 162 recommended: 610 | 2026-10-11T01:43:02+00:00 | Vulnerability · Source |
| CVE-2022-48926 | suse_vex | SUSE CVE CVE-2022-48926 | known affected: 310 known not affected: 478 recommended: 496 | 2026-10-11T01:43:00+00:00 | Vulnerability · Source |
| CVE-2022-48927 | suse_vex | SUSE CVE CVE-2022-48927 | known affected: 310 known not affected: 250 recommended: 411 | 2026-10-11T01:42:58+00:00 | Vulnerability · Source |
| CVE-2022-48932 | suse_vex | SUSE CVE CVE-2022-48932 | known affected: 310 known not affected: 250 recommended: 411 | 2026-10-11T01:42:55+00:00 | Vulnerability · Source |
| CVE-2022-48935 | suse_vex | SUSE CVE CVE-2022-48935 | known affected: 356 known not affected: 239 recommended: 411 | 2026-10-11T01:42:53+00:00 | Vulnerability · Source |
| CVE-2022-48947 | suse_vex | SUSE CVE CVE-2022-48947 | known affected: 24 known not affected: 302 recommended: 531 | 2026-10-11T01:42:48+00:00 | Vulnerability · Source |
| CVE-2022-48956 | suse_vex | SUSE CVE CVE-2022-48956 | known affected: 432 known not affected: 152 recommended: 636 | 2026-10-11T01:42:46+00:00 | Vulnerability · Source |
| CVE-2022-48958 | suse_vex | SUSE CVE CVE-2022-48958 | known affected: 354 known not affected: 402 recommended: 311 | 2026-10-11T01:42:43+00:00 | Vulnerability · Source |
| CVE-2022-48966 | suse_vex | SUSE CVE CVE-2022-48966 | known affected: 390 known not affected: 335 recommended: 311 | 2026-10-11T01:42:39+00:00 | Vulnerability · Source |
| CVE-2022-48968 | suse_vex | SUSE CVE CVE-2022-48968 | known affected: 324 known not affected: 360 recommended: 394 | 2026-10-11T01:42:37+00:00 | Vulnerability · Source |
| CVE-2022-48969 | suse_vex | SUSE CVE CVE-2022-48969 | known affected: 524 known not affected: 103 recommended: 520 | 2026-10-11T01:42:35+00:00 | Vulnerability · Source |
| CVE-2022-48977 | suse_vex | SUSE CVE CVE-2022-48977 | known not affected: 378 recommended: 324 | 2026-10-11T01:42:33+00:00 | Vulnerability · Source |
| CVE-2022-48991 | suse_vex | SUSE CVE CVE-2022-48991 | known affected: 436 known not affected: 177 recommended: 607 | 2026-10-11T01:42:28+00:00 | Vulnerability · Source |
| CVE-2022-48999 | suse_vex | SUSE CVE CVE-2022-48999 | known not affected: 312 recommended: 453 | 2026-10-11T01:42:20+00:00 | Vulnerability · Source |
| CVE-2022-49002 | suse_vex | SUSE CVE CVE-2022-49002 | known affected: 543 known not affected: 64 recommended: 434 | 2026-10-11T01:42:18+00:00 | Vulnerability · Source |
| CVE-2022-49003 | suse_vex | SUSE CVE CVE-2022-49003 | known affected: 324 known not affected: 284 recommended: 523 | 2026-10-11T01:42:16+00:00 | Vulnerability · Source |
| CVE-2022-49006 | suse_vex | SUSE CVE CVE-2022-49006 | known affected: 492 known not affected: 110 recommended: 604 | 2026-10-11T01:42:13+00:00 | Vulnerability · Source |
| CVE-2022-49011 | suse_vex | SUSE CVE CVE-2022-49011 | known affected: 498 known not affected: 116 recommended: 596 | 2026-10-11T01:42:10+00:00 | Vulnerability · Source |
| CVE-2022-49015 | suse_vex | SUSE CVE CVE-2022-49015 | known affected: 471 known not affected: 92 recommended: 577 | 2026-10-11T01:42:09+00:00 | Vulnerability · Source |
| CVE-2022-49020 | suse_vex | SUSE CVE CVE-2022-49020 | known affected: 647 known not affected: 48 recommended: 311 | 2026-10-11T01:42:05+00:00 | Vulnerability · Source |
| CVE-2022-49021 | suse_vex | SUSE CVE CVE-2022-49021 | known affected: 520 known not affected: 110 recommended: 518 | 2026-10-11T01:42:02+00:00 | Vulnerability · Source |
| CVE-2022-49023 | suse_vex | SUSE CVE CVE-2022-49023 | known affected: 328 known not affected: 310 recommended: 523 | 2026-10-11T01:42:00+00:00 | Vulnerability · Source |
| CVE-2022-49024 | suse_vex | SUSE CVE CVE-2022-49024 | known affected: 324 known not affected: 360 recommended: 435 | 2026-10-11T01:41:57+00:00 | Vulnerability · Source |
| CVE-2022-49025 | suse_vex | SUSE CVE CVE-2022-49025 | known affected: 335 known not affected: 301 recommended: 531 | 2026-10-11T01:41:55+00:00 | Vulnerability · Source |
| CVE-2022-49026 | suse_vex | SUSE CVE CVE-2022-49026 | known affected: 541 known not affected: 107 recommended: 434 | 2026-10-11T01:41:53+00:00 | Vulnerability · Source |
| CVE-2022-49027 | suse_vex | SUSE CVE CVE-2022-49027 | known affected: 541 known not affected: 69 recommended: 434 | 2026-10-11T01:41:50+00:00 | Vulnerability · Source |
| CVE-2022-49035 | suse_vex | SUSE CVE CVE-2022-49035 | known affected: 502 known not affected: 244 recommended: 355 | 2026-10-11T01:41:47+00:00 | Vulnerability · Source |
| CVE-2022-49050 | suse_vex | SUSE CVE CVE-2022-49050 | known affected: 334 known not affected: 347 recommended: 223 | 2026-10-11T01:41:44+00:00 | Vulnerability · Source |
| CVE-2022-49057 | suse_vex | SUSE CVE CVE-2022-49057 | known affected: 364 known not affected: 406 recommended: 142 | 2026-10-11T01:41:42+00:00 | Vulnerability · Source |
| CVE-2022-49058 | suse_vex | SUSE CVE CVE-2022-49058 | known affected: 487 known not affected: 164 recommended: 407 | 2026-10-11T01:41:39+00:00 | Vulnerability · Source |
| CVE-2022-49062 | suse_vex | SUSE CVE CVE-2022-49062 | known affected: 364 known not affected: 409 recommended: 100 | 2026-10-11T01:41:36+00:00 | Vulnerability · Source |
| CVE-2022-49063 | suse_vex | SUSE CVE CVE-2022-49063 | known affected: 334 known not affected: 369 recommended: 335 | 2026-10-11T01:41:33+00:00 | Vulnerability · Source |
| CVE-2022-49072 | suse_vex | SUSE CVE CVE-2022-49072 | known affected: 197 known not affected: 272 recommended: 54 | 2026-10-11T01:41:29+00:00 | Vulnerability · Source |
| CVE-2022-49078 | suse_vex | SUSE CVE CVE-2022-49078 | known affected: 360 known not affected: 343 recommended: 293 | 2026-10-11T01:41:26+00:00 | Vulnerability · Source |
| CVE-2022-49080 | suse_vex | SUSE CVE CVE-2022-49080 | known affected: 506 known not affected: 81 recommended: 474 | 2026-10-11T01:41:23+00:00 | Vulnerability · Source |
| CVE-2022-49083 | suse_vex | SUSE CVE CVE-2022-49083 | known affected: 334 known not affected: 369 recommended: 293 | 2026-10-11T01:41:21+00:00 | Vulnerability · Source |
| CVE-2022-49085 | suse_vex | SUSE CVE CVE-2022-49085 | known affected: 427 known not affected: 200 recommended: 319 | 2026-10-11T01:41:18+00:00 | Vulnerability · Source |
| CVE-2022-49086 | suse_vex | SUSE CVE CVE-2022-49086 | known affected: 546 known not affected: 234 recommended: 291 | 2026-10-11T01:41:16+00:00 | Vulnerability · Source |
| CVE-2022-49088 | suse_vex | SUSE CVE CVE-2022-49088 | known affected: 403 known not affected: 332 recommended: 223 | 2026-10-11T01:41:14+00:00 | Vulnerability · Source |
| CVE-2022-49090 | suse_vex | SUSE CVE CVE-2022-49090 | known affected: 334 known not affected: 405 recommended: 245 | 2026-10-11T01:41:12+00:00 | Vulnerability · Source |
| CVE-2022-49091 | suse_vex | SUSE CVE CVE-2022-49091 | known affected: 425 known not affected: 305 recommended: 293 | 2026-10-11T01:41:09+00:00 | Vulnerability · Source |
| CVE-2022-49096 | suse_vex | SUSE CVE CVE-2022-49096 | known affected: 403 known not affected: 332 recommended: 223 | 2026-10-11T01:41:05+00:00 | Vulnerability · Source |
| CVE-2022-49097 | suse_vex | SUSE CVE CVE-2022-49097 | known affected: 399 known not affected: 340 recommended: 277 | 2026-10-11T01:41:03+00:00 | Vulnerability · Source |
| CVE-2022-49105 | suse_vex | SUSE CVE CVE-2022-49105 | known affected: 334 known not affected: 404 recommended: 223 | 2026-10-11T01:41:01+00:00 | Vulnerability · Source |
| CVE-2022-49110 | suse_vex | SUSE CVE CVE-2022-49110 | known affected: 385 known not affected: 272 recommended: 296 | 2026-10-11T01:40:58+00:00 | Vulnerability · Source |
| CVE-2022-49116 | suse_vex | SUSE CVE CVE-2022-49116 | known affected: 338 known not affected: 401 recommended: 277 | 2026-10-11T01:40:56+00:00 | Vulnerability · Source |
| CVE-2022-49130 | suse_vex | SUSE CVE CVE-2022-49130 | known affected: 334 known not affected: 401 recommended: 265 | 2026-10-11T01:40:52+00:00 | Vulnerability · Source |
| CVE-2022-49131 | suse_vex | SUSE CVE CVE-2022-49131 | known affected: 334 known not affected: 401 recommended: 223 | 2026-10-11T01:40:50+00:00 | Vulnerability · Source |
| CVE-2022-49132 | suse_vex | SUSE CVE CVE-2022-49132 | known affected: 334 known not affected: 401 recommended: 223 | 2026-10-11T01:40:47+00:00 | Vulnerability · Source |
| CVE-2022-49133 | suse_vex | SUSE CVE CVE-2022-49133 | known affected: 425 known not affected: 344 recommended: 100 | 2026-10-11T01:40:45+00:00 | Vulnerability · Source |