VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291890 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-48744 | suse_vex | SUSE CVE CVE-2022-48744 | known affected: 433 known not affected: 133 recommended: 391 | 2026-08-05T01:17:45+00:00 | Vulnerability · Source |
| CVE-2022-48751 | suse_vex | SUSE CVE CVE-2022-48751 | known affected: 437 known not affected: 97 recommended: 461 | 2026-08-05T01:17:43+00:00 | Vulnerability · Source |
| CVE-2022-48762 | suse_vex | SUSE CVE CVE-2022-48762 | known not affected: 318 | 2026-08-05T01:17:36+00:00 | Vulnerability · Source |
| CVE-2022-48771 | suse_vex | SUSE CVE CVE-2022-48771 | known not affected: 139 recommended: 546 | 2026-08-05T01:17:35+00:00 | Vulnerability · Source |
| CVE-2022-48788 | suse_vex | SUSE CVE CVE-2022-48788 | known affected: 385 known not affected: 116 recommended: 619 | 2026-08-05T01:17:28+00:00 | Vulnerability · Source |
| CVE-2022-48790 | suse_vex | SUSE CVE CVE-2022-48790 | known affected: 381 known not affected: 119 recommended: 605 | 2026-08-05T01:17:25+00:00 | Vulnerability · Source |
| CVE-2022-48796 | suse_vex | SUSE CVE CVE-2022-48796 | known affected: 366 known not affected: 136 recommended: 426 | 2026-08-05T01:17:21+00:00 | Vulnerability · Source |
| CVE-2022-48808 | suse_vex | SUSE CVE CVE-2022-48808 | known affected: 401 known not affected: 245 recommended: 288 | 2026-08-05T01:17:15+00:00 | Vulnerability · Source |
| CVE-2022-48822 | suse_vex | SUSE CVE CVE-2022-48822 | known affected: 292 known not affected: 192 recommended: 584 | 2026-08-05T01:17:10+00:00 | Vulnerability · Source |
| CVE-2022-48851 | suse_vex | SUSE CVE CVE-2022-48851 | known affected: 295 known not affected: 392 recommended: 511 | 2026-08-05T01:16:57+00:00 | Vulnerability · Source |
| CVE-2022-48858 | suse_vex | SUSE CVE CVE-2022-48858 | known affected: 295 known not affected: 201 recommended: 511 | 2026-08-05T01:16:56+00:00 | Vulnerability · Source |
| CVE-2022-48864 | suse_vex | SUSE CVE CVE-2022-48864 | known affected: 330 known not affected: 256 recommended: 298 | 2026-08-05T01:16:54+00:00 | Vulnerability · Source |
| CVE-2022-48871 | suse_vex | SUSE CVE CVE-2022-48871 | known affected: 310 known not affected: 195 recommended: 411 | 2026-08-05T01:16:52+00:00 | Vulnerability · Source |
| CVE-2022-48883 | suse_vex | SUSE CVE CVE-2022-48883 | known affected: 340 known not affected: 249 recommended: 335 | 2026-08-05T01:16:45+00:00 | Vulnerability · Source |
| CVE-2022-48887 | suse_vex | SUSE CVE CVE-2022-48887 | known affected: 389 known not affected: 142 recommended: 288 | 2026-08-05T01:16:43+00:00 | Vulnerability · Source |
| CVE-2022-48911 | suse_vex | SUSE CVE CVE-2022-48911 | known affected: 357 known not affected: 124 recommended: 701 | 2026-08-05T01:16:38+00:00 | Vulnerability · Source |
| CVE-2022-48919 | suse_vex | SUSE CVE CVE-2022-48919 | known affected: 359 known not affected: 102 recommended: 672 | 2026-08-05T01:16:34+00:00 | Vulnerability · Source |
| CVE-2022-48941 | suse_vex | SUSE CVE CVE-2022-48941 | known affected: 310 known not affected: 195 recommended: 411 | 2026-08-05T01:16:23+00:00 | Vulnerability · Source |
| CVE-2022-48945 | suse_vex | SUSE CVE CVE-2022-48945 | known affected: 386 known not affected: 133 recommended: 638 | 2026-08-05T01:16:20+00:00 | Vulnerability · Source |
| CVE-2022-48991 | suse_vex | SUSE CVE CVE-2022-48991 | known affected: 409 known not affected: 154 recommended: 578 | 2026-08-05T01:16:01+00:00 | Vulnerability · Source |
| CVE-2022-48999 | suse_vex | SUSE CVE CVE-2022-48999 | known not affected: 238 recommended: 453 | 2026-08-05T01:15:59+00:00 | Vulnerability · Source |
| CVE-2022-49001 | suse_vex | SUSE CVE CVE-2022-49001 | known not affected: 379 | 2026-08-05T01:15:58+00:00 | Vulnerability · Source |
| CVE-2022-49022 | suse_vex | SUSE CVE CVE-2022-49022 | known affected: 324 known not affected: 261 recommended: 505 | 2026-08-05T01:15:50+00:00 | Vulnerability · Source |
| CVE-2022-49023 | suse_vex | SUSE CVE CVE-2022-49023 | known affected: 328 known not affected: 234 recommended: 523 | 2026-08-05T01:15:49+00:00 | Vulnerability · Source |
| CVE-2022-49025 | suse_vex | SUSE CVE CVE-2022-49025 | known affected: 337 known not affected: 225 recommended: 531 | 2026-08-05T01:15:47+00:00 | Vulnerability · Source |
| CVE-2022-49052 | suse_vex | SUSE CVE CVE-2022-49052 | known affected: 163 known not affected: 189 | 2026-08-05T01:15:41+00:00 | Vulnerability · Source |
| CVE-2022-49054 | suse_vex | SUSE CVE CVE-2022-49054 | known affected: 334 known not affected: 298 recommended: 223 | 2026-08-05T01:15:39+00:00 | Vulnerability · Source |
| CVE-2022-49065 | suse_vex | SUSE CVE CVE-2022-49065 | known affected: 365 known not affected: 213 recommended: 319 | 2026-08-05T01:15:35+00:00 | Vulnerability · Source |
| CVE-2022-49075 | suse_vex | SUSE CVE CVE-2022-49075 | known affected: 529 known not affected: 111 recommended: 140 | 2026-08-05T01:15:31+00:00 | Vulnerability · Source |
| CVE-2022-49089 | suse_vex | SUSE CVE CVE-2022-49089 | known affected: 414 known not affected: 192 recommended: 249 | 2026-08-05T01:15:24+00:00 | Vulnerability · Source |
| CVE-2022-49097 | suse_vex | SUSE CVE CVE-2022-49097 | known affected: 381 known not affected: 251 recommended: 250 | 2026-08-05T01:15:16+00:00 | Vulnerability · Source |
| CVE-2022-49110 | suse_vex | SUSE CVE CVE-2022-49110 | known affected: 373 known not affected: 189 recommended: 296 | 2026-08-05T01:15:14+00:00 | Vulnerability · Source |
| CVE-2022-49114 | suse_vex | SUSE CVE CVE-2022-49114 | known affected: 415 known not affected: 199 recommended: 380 | 2026-08-05T01:15:13+00:00 | Vulnerability · Source |
| CVE-2022-49149 | suse_vex | SUSE CVE CVE-2022-49149 | known affected: 106 known not affected: 246 | 2026-08-05T01:15:06+00:00 | Vulnerability · Source |
| CVE-2022-49154 | suse_vex | SUSE CVE CVE-2022-49154 | known affected: 444 known not affected: 213 recommended: 260 | 2026-08-05T01:15:05+00:00 | Vulnerability · Source |
| CVE-2022-49160 | suse_vex | SUSE CVE CVE-2022-49160 | known affected: 379 known not affected: 199 recommended: 361 | 2026-08-05T01:15:02+00:00 | Vulnerability · Source |
| CVE-2022-49167 | suse_vex | SUSE CVE CVE-2022-49167 | known affected: 112 known not affected: 236 | 2026-08-05T01:14:58+00:00 | Vulnerability · Source |
| CVE-2022-49168 | suse_vex | SUSE CVE CVE-2022-49168 | known affected: 506 known not affected: 212 recommended: 37 | 2026-08-05T01:14:56+00:00 | Vulnerability · Source |
| CVE-2022-49178 | suse_vex | SUSE CVE CVE-2022-49178 | known affected: 549 known not affected: 91 recommended: 140 | 2026-08-05T01:14:52+00:00 | Vulnerability · Source |
| CVE-2022-49194 | suse_vex | SUSE CVE CVE-2022-49194 | known affected: 406 known not affected: 192 recommended: 223 | 2026-08-05T01:14:47+00:00 | Vulnerability · Source |
| CVE-2022-49201 | suse_vex | SUSE CVE CVE-2022-49201 | known affected: 403 known not affected: 120 recommended: 319 | 2026-08-05T01:14:46+00:00 | Vulnerability · Source |
| CVE-2022-49295 | suse_vex | SUSE CVE CVE-2022-49295 | known affected: 395 known not affected: 183 recommended: 319 | 2026-08-05T01:14:25+00:00 | Vulnerability · Source |
| CVE-2022-49325 | suse_vex | SUSE CVE CVE-2022-49325 | known affected: 545 known not affected: 127 recommended: 162 | 2026-08-05T01:14:21+00:00 | Vulnerability · Source |
| CVE-2022-49330 | suse_vex | SUSE CVE CVE-2022-49330 | known affected: 537 known not affected: 103 recommended: 182 | 2026-08-05T01:14:18+00:00 | Vulnerability · Source |
| CVE-2022-49336 | suse_vex | SUSE CVE CVE-2022-49336 | known affected: 418 known not affected: 212 recommended: 223 | 2026-08-05T01:14:17+00:00 | Vulnerability · Source |
| CVE-2022-49337 | suse_vex | SUSE CVE CVE-2022-49337 | known affected: 334 known not affected: 270 recommended: 249 | 2026-08-05T01:14:15+00:00 | Vulnerability · Source |
| CVE-2022-49343 | suse_vex | SUSE CVE CVE-2022-49343 | known not affected: 236 recommended: 327 | 2026-08-05T01:14:14+00:00 | Vulnerability · Source |
| CVE-2022-49356 | suse_vex | SUSE CVE CVE-2022-49356 | known affected: 334 known not affected: 298 recommended: 270 | 2026-08-05T01:14:11+00:00 | Vulnerability · Source |
| CVE-2022-49368 | suse_vex | SUSE CVE CVE-2022-49368 | known affected: 422 known not affected: 248 recommended: 223 | 2026-08-05T01:14:05+00:00 | Vulnerability · Source |
| CVE-2022-49413 | suse_vex | SUSE CVE CVE-2022-49413 | known affected: 393 known not affected: 183 recommended: 353 | 2026-08-05T01:13:53+00:00 | Vulnerability · Source |