VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283447 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2022-49026 | suse_vex | SUSE CVE CVE-2022-49026 | known affected: 480 known not affected: 120 recommended: 434 | 2026-07-25T17:17:23+00:00 | Vulnerability · Source |
| CVE-2022-49031 | suse_vex | SUSE CVE CVE-2022-49031 | known affected: 396 known not affected: 151 recommended: 478 | 2026-07-25T17:17:21+00:00 | Vulnerability · Source |
| CVE-2022-49034 | suse_vex | SUSE CVE CVE-2022-49034 | known not affected: 425 | 2026-07-25T17:17:19+00:00 | Vulnerability · Source |
| CVE-2022-49046 | suse_vex | SUSE CVE CVE-2022-49046 | known affected: 602 known not affected: 120 recommended: 26 | 2026-07-25T17:17:17+00:00 | Vulnerability · Source |
| CVE-2022-49047 | suse_vex | SUSE CVE CVE-2022-49047 | known not affected: 352 | 2026-07-25T17:17:16+00:00 | Vulnerability · Source |
| CVE-2022-49051 | suse_vex | SUSE CVE CVE-2022-49051 | known affected: 358 known not affected: 218 recommended: 331 | 2026-07-25T17:17:13+00:00 | Vulnerability · Source |
| CVE-2022-49059 | suse_vex | SUSE CVE CVE-2022-49059 | known affected: 417 known not affected: 193 recommended: 333 | 2026-07-25T17:17:10+00:00 | Vulnerability · Source |
| CVE-2022-49062 | suse_vex | SUSE CVE CVE-2022-49062 | known affected: 364 known not affected: 302 recommended: 100 | 2026-07-25T17:17:08+00:00 | Vulnerability · Source |
| CVE-2022-49063 | suse_vex | SUSE CVE CVE-2022-49063 | known affected: 334 known not affected: 270 recommended: 335 | 2026-07-25T17:17:06+00:00 | Vulnerability · Source |
| CVE-2022-49065 | suse_vex | SUSE CVE CVE-2022-49065 | known affected: 365 known not affected: 213 recommended: 319 | 2026-07-25T17:17:03+00:00 | Vulnerability · Source |
| CVE-2022-49066 | suse_vex | SUSE CVE CVE-2022-49066 | known affected: 452 known not affected: 154 recommended: 305 | 2026-07-25T17:17:01+00:00 | Vulnerability · Source |
| CVE-2022-49072 | suse_vex | SUSE CVE CVE-2022-49072 | known affected: 163 known not affected: 189 recommended: 27 | 2026-07-25T17:16:59+00:00 | Vulnerability · Source |
| CVE-2022-49074 | suse_vex | SUSE CVE CVE-2022-49074 | known affected: 458 known not affected: 186 recommended: 249 | 2026-07-25T17:16:57+00:00 | Vulnerability · Source |
| CVE-2022-49080 | suse_vex | SUSE CVE CVE-2022-49080 | known affected: 438 known not affected: 88 recommended: 447 | 2026-07-25T17:16:54+00:00 | Vulnerability · Source |
| CVE-2022-49081 | suse_vex | SUSE CVE CVE-2022-49081 | known affected: 112 known not affected: 240 recommended: 47 | 2026-07-25T17:16:52+00:00 | Vulnerability · Source |
| CVE-2022-49083 | suse_vex | SUSE CVE CVE-2022-49083 | known affected: 334 known not affected: 270 recommended: 293 | 2026-07-25T17:16:49+00:00 | Vulnerability · Source |
| CVE-2022-49088 | suse_vex | SUSE CVE CVE-2022-49088 | known affected: 385 known not affected: 247 recommended: 223 | 2026-07-25T17:16:47+00:00 | Vulnerability · Source |
| CVE-2022-49089 | suse_vex | SUSE CVE CVE-2022-49089 | known affected: 414 known not affected: 192 recommended: 249 | 2026-07-25T17:16:44+00:00 | Vulnerability · Source |
| CVE-2022-49092 | suse_vex | SUSE CVE CVE-2022-49092 | known not affected: 298 recommended: 163 | 2026-07-25T17:16:42+00:00 | Vulnerability · Source |
| CVE-2022-49095 | suse_vex | SUSE CVE CVE-2022-49095 | known affected: 415 known not affected: 231 recommended: 319 | 2026-07-25T17:16:40+00:00 | Vulnerability · Source |
| CVE-2022-49096 | suse_vex | SUSE CVE CVE-2022-49096 | known affected: 385 known not affected: 247 recommended: 223 | 2026-07-25T17:16:37+00:00 | Vulnerability · Source |
| CVE-2022-49101 | suse_vex | SUSE CVE CVE-2022-49101 | known not affected: 352 | 2026-07-25T17:16:35+00:00 | Vulnerability · Source |
| CVE-2022-49103 | suse_vex | SUSE CVE CVE-2022-49103 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:16:33+00:00 | Vulnerability · Source |
| CVE-2022-49105 | suse_vex | SUSE CVE CVE-2022-49105 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:16:31+00:00 | Vulnerability · Source |
| CVE-2022-49108 | suse_vex | SUSE CVE CVE-2022-49108 | known not affected: 352 | 2026-07-25T17:16:29+00:00 | Vulnerability · Source |
| CVE-2022-49109 | suse_vex | SUSE CVE CVE-2022-49109 | known affected: 470 known not affected: 230 recommended: 271 | 2026-07-25T17:16:26+00:00 | Vulnerability · Source |
| CVE-2022-49110 | suse_vex | SUSE CVE CVE-2022-49110 | known affected: 373 known not affected: 189 recommended: 296 | 2026-07-25T17:16:25+00:00 | Vulnerability · Source |