VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283871 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-48890 | suse_vex | SUSE CVE CVE-2022-48890 | known affected: 310 known not affected: 195 recommended: 411 | 2026-07-25T17:18:43+00:00 | Vulnerability · Source |
| CVE-2022-48893 | suse_vex | SUSE CVE CVE-2022-48893 | known affected: 340 known not affected: 169 recommended: 288 | 2026-07-25T17:18:41+00:00 | Vulnerability · Source |
| CVE-2022-48895 | suse_vex | SUSE CVE CVE-2022-48895 | known not affected: 310 | 2026-07-25T17:18:40+00:00 | Vulnerability · Source |
| CVE-2022-48898 | suse_vex | SUSE CVE CVE-2022-48898 | known affected: 310 known not affected: 195 recommended: 411 | 2026-07-25T17:18:38+00:00 | Vulnerability · Source |
| CVE-2022-48900 | suse_vex | SUSE CVE CVE-2022-48900 | known not affected: 301 | 2026-07-25T17:18:37+00:00 | Vulnerability · Source |
| CVE-2022-48902 | suse_vex | SUSE CVE CVE-2022-48902 | known affected: 138 known not affected: 239 | 2026-07-25T17:18:36+00:00 | Vulnerability · Source |
| CVE-2022-48905 | suse_vex | SUSE CVE CVE-2022-48905 | known affected: 384 known not affected: 98 recommended: 588 | 2026-07-25T17:18:34+00:00 | Vulnerability · Source |
| CVE-2022-48907 | suse_vex | SUSE CVE CVE-2022-48907 | known affected: 310 known not affected: 195 recommended: 411 | 2026-07-25T17:18:33+00:00 | Vulnerability · Source |
| CVE-2022-48908 | suse_vex | SUSE CVE CVE-2022-48908 | known not affected: 514 | 2026-07-25T17:18:31+00:00 | Vulnerability · Source |
| CVE-2022-48909 | suse_vex | SUSE CVE CVE-2022-48909 | known affected: 359 known not affected: 142 recommended: 411 | 2026-07-25T17:18:30+00:00 | Vulnerability · Source |
| CVE-2022-48911 | suse_vex | SUSE CVE CVE-2022-48911 | known affected: 357 known not affected: 124 recommended: 701 | 2026-07-25T17:18:28+00:00 | Vulnerability · Source |
| CVE-2022-48914 | suse_vex | SUSE CVE CVE-2022-48914 | known affected: 310 known not affected: 195 recommended: 411 | 2026-07-25T17:18:27+00:00 | Vulnerability · Source |
| CVE-2022-48917 | suse_vex | SUSE CVE CVE-2022-48917 | known affected: 310 known not affected: 191 recommended: 496 | 2026-07-25T17:18:25+00:00 | Vulnerability · Source |
| CVE-2022-48918 | suse_vex | SUSE CVE CVE-2022-48918 | known affected: 310 known not affected: 195 recommended: 453 | 2026-07-25T17:18:23+00:00 | Vulnerability · Source |
| CVE-2022-48926 | suse_vex | SUSE CVE CVE-2022-48926 | known affected: 310 known not affected: 376 recommended: 496 | 2026-07-25T17:18:22+00:00 | Vulnerability · Source |
| CVE-2022-48929 | suse_vex | SUSE CVE CVE-2022-48929 | known not affected: 195 recommended: 327 | 2026-07-25T17:18:21+00:00 | Vulnerability · Source |
| CVE-2022-48934 | suse_vex | SUSE CVE CVE-2022-48934 | known affected: 333 known not affected: 168 recommended: 523 | 2026-07-25T17:18:19+00:00 | Vulnerability · Source |
| CVE-2022-48935 | suse_vex | SUSE CVE CVE-2022-48935 | known affected: 350 known not affected: 190 recommended: 411 | 2026-07-25T17:18:18+00:00 | Vulnerability · Source |
| CVE-2022-48939 | suse_vex | SUSE CVE CVE-2022-48939 | known affected: 366 known not affected: 165 recommended: 315 | 2026-07-25T17:18:16+00:00 | Vulnerability · Source |
| CVE-2022-48941 | suse_vex | SUSE CVE CVE-2022-48941 | known affected: 310 known not affected: 195 recommended: 411 | 2026-07-25T17:18:15+00:00 | Vulnerability · Source |
| CVE-2022-48942 | suse_vex | SUSE CVE CVE-2022-48942 | known affected: 310 known not affected: 195 recommended: 438 | 2026-07-25T17:18:13+00:00 | Vulnerability · Source |
| CVE-2022-48947 | suse_vex | SUSE CVE CVE-2022-48947 | known affected: 20 known not affected: 224 recommended: 502 | 2026-07-25T17:18:12+00:00 | Vulnerability · Source |
| CVE-2022-48949 | suse_vex | SUSE CVE CVE-2022-48949 | known affected: 430 known not affected: 99 recommended: 434 | 2026-07-25T17:18:11+00:00 | Vulnerability · Source |
| CVE-2022-48953 | suse_vex | SUSE CVE CVE-2022-48953 | known affected: 462 known not affected: 117 recommended: 434 | 2026-07-25T17:18:09+00:00 | Vulnerability · Source |
| CVE-2022-48954 | suse_vex | SUSE CVE CVE-2022-48954 | known affected: 324 known not affected: 289 recommended: 394 | 2026-07-25T17:18:08+00:00 | Vulnerability · Source |
| CVE-2022-48957 | suse_vex | SUSE CVE CVE-2022-48957 | known affected: 422 known not affected: 281 recommended: 271 | 2026-07-25T17:18:07+00:00 | Vulnerability · Source |
| CVE-2022-48958 | suse_vex | SUSE CVE CVE-2022-48958 | known affected: 354 known not affected: 323 recommended: 311 | 2026-07-25T17:18:05+00:00 | Vulnerability · Source |
| CVE-2022-48961 | suse_vex | SUSE CVE CVE-2022-48961 | known affected: 324 known not affected: 395 recommended: 394 | 2026-07-25T17:18:04+00:00 | Vulnerability · Source |
| CVE-2022-48963 | suse_vex | SUSE CVE CVE-2022-48963 | known not affected: 402 | 2026-07-25T17:18:03+00:00 | Vulnerability · Source |
| CVE-2022-48964 | suse_vex | SUSE CVE CVE-2022-48964 | known not affected: 402 | 2026-07-25T17:18:02+00:00 | Vulnerability · Source |
| CVE-2022-48968 | suse_vex | SUSE CVE CVE-2022-48968 | known affected: 324 known not affected: 270 recommended: 394 | 2026-07-25T17:18:00+00:00 | Vulnerability · Source |
| CVE-2022-48976 | suse_vex | SUSE CVE CVE-2022-48976 | known not affected: 402 recommended: 27 | 2026-07-25T17:17:59+00:00 | Vulnerability · Source |
| CVE-2022-48977 | suse_vex | SUSE CVE CVE-2022-48977 | known not affected: 289 recommended: 324 | 2026-07-25T17:17:57+00:00 | Vulnerability · Source |
| CVE-2022-48983 | suse_vex | SUSE CVE CVE-2022-48983 | known affected: 354 known not affected: 340 recommended: 269 | 2026-07-25T17:17:56+00:00 | Vulnerability · Source |
| CVE-2022-48984 | suse_vex | SUSE CVE CVE-2022-48984 | known not affected: 402 | 2026-07-25T17:17:54+00:00 | Vulnerability · Source |
| CVE-2022-48985 | suse_vex | SUSE CVE CVE-2022-48985 | known affected: 385 known not affected: 147 recommended: 518 | 2026-07-25T17:17:52+00:00 | Vulnerability · Source |
| CVE-2022-48986 | suse_vex | SUSE CVE CVE-2022-48986 | known not affected: 462 | 2026-07-25T17:17:51+00:00 | Vulnerability · Source |
| CVE-2022-48992 | suse_vex | SUSE CVE CVE-2022-48992 | known affected: 480 known not affected: 120 recommended: 481 | 2026-07-25T17:17:49+00:00 | Vulnerability · Source |
| CVE-2022-48997 | suse_vex | SUSE CVE CVE-2022-48997 | known affected: 351 known not affected: 208 recommended: 469 | 2026-07-25T17:17:47+00:00 | Vulnerability · Source |
| CVE-2022-48999 | suse_vex | SUSE CVE CVE-2022-48999 | known not affected: 238 recommended: 453 | 2026-07-25T17:17:46+00:00 | Vulnerability · Source |
| CVE-2022-49002 | suse_vex | SUSE CVE CVE-2022-49002 | known affected: 481 known not affected: 72 recommended: 434 | 2026-07-25T17:17:44+00:00 | Vulnerability · Source |
| CVE-2022-49003 | suse_vex | SUSE CVE CVE-2022-49003 | known affected: 324 known not affected: 206 recommended: 523 | 2026-07-25T17:17:41+00:00 | Vulnerability · Source |
| CVE-2022-49005 | suse_vex | SUSE CVE CVE-2022-49005 | known affected: 324 known not affected: 233 recommended: 394 | 2026-07-25T17:17:40+00:00 | Vulnerability · Source |
| CVE-2022-49006 | suse_vex | SUSE CVE CVE-2022-49006 | known affected: 438 known not affected: 123 recommended: 561 | 2026-07-25T17:17:37+00:00 | Vulnerability · Source |
| CVE-2022-49009 | suse_vex | SUSE CVE CVE-2022-49009 | known not affected: 379 | 2026-07-25T17:17:35+00:00 | Vulnerability · Source |
| CVE-2022-49010 | suse_vex | SUSE CVE CVE-2022-49010 | known affected: 449 known not affected: 123 recommended: 565 | 2026-07-25T17:17:33+00:00 | Vulnerability · Source |
| CVE-2022-49011 | suse_vex | SUSE CVE CVE-2022-49011 | known affected: 443 known not affected: 129 recommended: 567 | 2026-07-25T17:17:30+00:00 | Vulnerability · Source |
| CVE-2022-49022 | suse_vex | SUSE CVE CVE-2022-49022 | known affected: 324 known not affected: 261 recommended: 505 | 2026-07-25T17:17:29+00:00 | Vulnerability · Source |
| CVE-2022-49023 | suse_vex | SUSE CVE CVE-2022-49023 | known affected: 328 known not affected: 234 recommended: 523 | 2026-07-25T17:17:27+00:00 | Vulnerability · Source |
| CVE-2022-49024 | suse_vex | SUSE CVE CVE-2022-49024 | known affected: 324 known not affected: 270 recommended: 435 | 2026-07-25T17:17:25+00:00 | Vulnerability · Source |