VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291210 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2022-49416 | suse_vex | SUSE CVE CVE-2022-49416 | known affected: 421 known not affected: 157 recommended: 380 | 2026-08-05T01:13:52+00:00 | Vulnerability · Source |
| CVE-2022-49452 | suse_vex | SUSE CVE CVE-2022-49452 | known not affected: 352 | 2026-08-05T01:13:45+00:00 | Vulnerability · Source |
| CVE-2022-49511 | suse_vex | SUSE CVE CVE-2022-49511 | known affected: 364 known not affected: 302 recommended: 147 | 2026-08-05T01:13:35+00:00 | Vulnerability · Source |
| CVE-2022-49533 | suse_vex | SUSE CVE CVE-2022-49533 | known affected: 419 known not affected: 247 recommended: 100 | 2026-08-05T01:13:31+00:00 | Vulnerability · Source |
| CVE-2022-49535 | suse_vex | SUSE CVE CVE-2022-49535 | known affected: 423 known not affected: 187 recommended: 319 | 2026-08-05T01:13:29+00:00 | Vulnerability · Source |
| CVE-2022-49554 | suse_vex | SUSE CVE CVE-2022-49554 | known affected: 106 known not affected: 246 | 2026-08-05T01:13:26+00:00 | Vulnerability · Source |
| CVE-2022-49622 | suse_vex | SUSE CVE CVE-2022-49622 | known affected: 633 known not affected: 140 recommended: 23 | 2026-08-05T01:13:16+00:00 | Vulnerability · Source |
| CVE-2022-49645 | suse_vex | SUSE CVE CVE-2022-49645 | known affected: 334 known not affected: 270 recommended: 293 | 2026-08-05T01:13:13+00:00 | Vulnerability · Source |
| CVE-2022-49667 | suse_vex | SUSE CVE CVE-2022-49667 | known affected: 458 known not affected: 148 recommended: 263 | 2026-08-05T01:13:10+00:00 | Vulnerability · Source |
| CVE-2022-49672 | suse_vex | SUSE CVE CVE-2022-49672 | known affected: 414 known not affected: 194 recommended: 290 | 2026-08-05T01:13:06+00:00 | Vulnerability · Source |
| CVE-2022-49701 | suse_vex | SUSE CVE CVE-2022-49701 | known affected: 334 known not affected: 270 recommended: 293 | 2026-08-05T01:13:01+00:00 | Vulnerability · Source |
| CVE-2022-49722 | suse_vex | SUSE CVE CVE-2022-49722 | known affected: 385 known not affected: 247 recommended: 265 | 2026-08-05T01:12:59+00:00 | Vulnerability · Source |
| CVE-2022-49725 | suse_vex | SUSE CVE CVE-2022-49725 | known affected: 458 known not affected: 184 recommended: 263 | 2026-08-05T01:12:57+00:00 | Vulnerability · Source |