VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49211 | suse_vex | SUSE CVE CVE-2022-49211 | known affected: 0 known not affected: 508 | 2026-10-16T14:27:10+00:00 | Vulnerability · Source |
| CVE-2022-49213 | suse_vex | SUSE CVE CVE-2022-49213 | known affected: 334 known not affected: 364 recommended: 293 | 2026-10-16T14:27:08+00:00 | Vulnerability · Source |
| CVE-2022-49216 | suse_vex | SUSE CVE CVE-2022-49216 | known affected: 493 known not affected: 214 recommended: 316 | 2026-10-16T14:27:06+00:00 | Vulnerability · Source |
| CVE-2022-49217 | suse_vex | SUSE CVE CVE-2022-49217 | known affected: 481 known not affected: 163 recommended: 333 | 2026-10-16T14:27:03+00:00 | Vulnerability · Source |
| CVE-2022-49218 | suse_vex | SUSE CVE CVE-2022-49218 | known affected: 377 known not affected: 351 recommended: 223 | 2026-10-16T14:27:01+00:00 | Vulnerability · Source |
| CVE-2022-49219 | suse_vex | SUSE CVE CVE-2022-49219 | known affected: 494 known not affected: 268 recommended: 100 | 2026-10-16T14:26:59+00:00 | Vulnerability · Source |
| CVE-2022-49221 | suse_vex | SUSE CVE CVE-2022-49221 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:26:56+00:00 | Vulnerability · Source |
| CVE-2022-49222 | suse_vex | SUSE CVE CVE-2022-49222 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:26:54+00:00 | Vulnerability · Source |
| CVE-2022-49224 | suse_vex | SUSE CVE CVE-2022-49224 | known affected: 429 known not affected: 301 recommended: 293 | 2026-10-16T14:26:52+00:00 | Vulnerability · Source |
| CVE-2022-49227 | suse_vex | SUSE CVE CVE-2022-49227 | known affected: 334 known not affected: 394 recommended: 265 | 2026-10-16T14:26:47+00:00 | Vulnerability · Source |
| CVE-2022-49228 | suse_vex | SUSE CVE CVE-2022-49228 | known affected: 364 known not affected: 398 recommended: 122 | 2026-10-16T14:26:45+00:00 | Vulnerability · Source |
| CVE-2022-49231 | suse_vex | SUSE CVE CVE-2022-49231 | known affected: 0 known not affected: 462 | 2026-10-16T14:26:40+00:00 | Vulnerability · Source |
| CVE-2022-49233 | suse_vex | SUSE CVE CVE-2022-49233 | known affected: 364 known not affected: 402 recommended: 100 | 2026-10-16T14:26:38+00:00 | Vulnerability · Source |
| CVE-2022-49234 | suse_vex | SUSE CVE CVE-2022-49234 | known affected: 197 known not affected: 265 | 2026-10-16T14:26:36+00:00 | Vulnerability · Source |
| CVE-2022-49235 | suse_vex | SUSE CVE CVE-2022-49235 | known affected: 496 known not affected: 179 recommended: 372 | 2026-10-16T14:26:33+00:00 | Vulnerability · Source |
| CVE-2022-49237 | suse_vex | SUSE CVE CVE-2022-49237 | known affected: 364 known not affected: 398 recommended: 100 | 2026-10-16T14:26:30+00:00 | Vulnerability · Source |
| CVE-2022-49239 | suse_vex | SUSE CVE CVE-2022-49239 | known affected: 334 known not affected: 363 recommended: 293 | 2026-10-16T14:26:28+00:00 | Vulnerability · Source |
| CVE-2022-49242 | suse_vex | SUSE CVE CVE-2022-49242 | known affected: 429 known not affected: 303 recommended: 293 | 2026-10-16T14:26:25+00:00 | Vulnerability · Source |
| CVE-2022-49243 | suse_vex | SUSE CVE CVE-2022-49243 | known affected: 334 known not affected: 362 recommended: 293 | 2026-10-16T14:26:23+00:00 | Vulnerability · Source |
| CVE-2022-49244 | suse_vex | SUSE CVE CVE-2022-49244 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:26:21+00:00 | Vulnerability · Source |
| CVE-2022-49246 | suse_vex | SUSE CVE CVE-2022-49246 | known affected: 403 known not affected: 325 recommended: 223 | 2026-10-16T14:26:19+00:00 | Vulnerability · Source |
| CVE-2022-49247 | suse_vex | SUSE CVE CVE-2022-49247 | known affected: 493 known not affected: 153 recommended: 355 | 2026-10-16T14:26:17+00:00 | Vulnerability · Source |
| CVE-2022-49248 | suse_vex | SUSE CVE CVE-2022-49248 | known affected: 490 known not affected: 183 recommended: 330 | 2026-10-16T14:26:14+00:00 | Vulnerability · Source |
| CVE-2022-49255 | suse_vex | SUSE CVE CVE-2022-49255 | known affected: 0 known not affected: 462 | 2026-10-16T14:26:12+00:00 | Vulnerability · Source |
| CVE-2022-49261 | suse_vex | SUSE CVE CVE-2022-49261 | known affected: 394 known not affected: 362 recommended: 233 | 2026-10-16T14:26:05+00:00 | Vulnerability · Source |
| CVE-2022-49263 | suse_vex | SUSE CVE CVE-2022-49263 | known affected: 360 known not affected: 336 recommended: 335 | 2026-10-16T14:26:03+00:00 | Vulnerability · Source |
| CVE-2022-49269 | suse_vex | SUSE CVE CVE-2022-49269 | known affected: 334 known not affected: 394 recommended: 264 | 2026-10-16T14:26:00+00:00 | Vulnerability · Source |
| CVE-2022-49271 | suse_vex | SUSE CVE CVE-2022-49271 | known affected: 487 known not affected: 217 recommended: 271 | 2026-10-16T14:25:55+00:00 | Vulnerability · Source |
| CVE-2022-49274 | suse_vex | SUSE CVE CVE-2022-49274 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:25:53+00:00 | Vulnerability · Source |
| CVE-2022-49275 | suse_vex | SUSE CVE CVE-2022-49275 | known affected: 495 known not affected: 144 recommended: 399 | 2026-10-16T14:25:51+00:00 | Vulnerability · Source |
| CVE-2022-49278 | suse_vex | SUSE CVE CVE-2022-49278 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:25:48+00:00 | Vulnerability · Source |
| CVE-2022-49281 | suse_vex | SUSE CVE CVE-2022-49281 | known affected: 360 known not affected: 282 recommended: 341 | 2026-10-16T14:25:45+00:00 | Vulnerability · Source |
| CVE-2022-49283 | suse_vex | SUSE CVE CVE-2022-49283 | known affected: 334 known not affected: 394 recommended: 277 | 2026-10-16T14:25:42+00:00 | Vulnerability · Source |
| CVE-2022-49284 | suse_vex | SUSE CVE CVE-2022-49284 | known affected: 0 known not affected: 462 | 2026-10-16T14:25:39+00:00 | Vulnerability · Source |
| CVE-2022-49285 | suse_vex | SUSE CVE CVE-2022-49285 | known affected: 334 known not affected: 358 recommended: 293 | 2026-10-16T14:25:36+00:00 | Vulnerability · Source |
| CVE-2022-49288 | suse_vex | SUSE CVE CVE-2022-49288 | known affected: 0 known not affected: 302 recommended: 342 | 2026-10-16T14:25:33+00:00 | Vulnerability · Source |
| CVE-2022-49289 | suse_vex | SUSE CVE CVE-2022-49289 | known affected: 0 known not affected: 458 | 2026-10-16T14:25:31+00:00 | Vulnerability · Source |
| CVE-2022-49292 | suse_vex | SUSE CVE CVE-2022-49292 | known affected: 495 known not affected: 145 recommended: 375 | 2026-10-16T14:25:28+00:00 | Vulnerability · Source |
| CVE-2022-49294 | suse_vex | SUSE CVE CVE-2022-49294 | known affected: 400 known not affected: 328 recommended: 297 | 2026-10-16T14:25:26+00:00 | Vulnerability · Source |
| CVE-2022-49300 | suse_vex | SUSE CVE CVE-2022-49300 | known affected: 453 known not affected: 193 recommended: 319 | 2026-10-16T14:25:21+00:00 | Vulnerability · Source |
| CVE-2022-49302 | suse_vex | SUSE CVE CVE-2022-49302 | known affected: 334 known not affected: 358 recommended: 293 | 2026-10-16T14:25:18+00:00 | Vulnerability · Source |
| CVE-2022-49303 | suse_vex | SUSE CVE CVE-2022-49303 | known affected: 0 known not affected: 458 | 2026-10-16T14:25:16+00:00 | Vulnerability · Source |
| CVE-2022-49305 | suse_vex | SUSE CVE CVE-2022-49305 | known affected: 372 known not affected: 269 recommended: 333 | 2026-10-16T14:25:13+00:00 | Vulnerability · Source |
| CVE-2022-49307 | suse_vex | SUSE CVE CVE-2022-49307 | known affected: 340 known not affected: 358 recommended: 293 | 2026-10-16T14:25:09+00:00 | Vulnerability · Source |
| CVE-2022-49311 | suse_vex | SUSE CVE CVE-2022-49311 | known affected: 334 known not affected: 396 recommended: 223 | 2026-10-16T14:25:07+00:00 | Vulnerability · Source |
| CVE-2022-49315 | suse_vex | SUSE CVE CVE-2022-49315 | known affected: 334 known not affected: 358 recommended: 293 | 2026-10-16T14:25:05+00:00 | Vulnerability · Source |
| CVE-2022-49316 | suse_vex | SUSE CVE CVE-2022-49316 | known affected: 334 known not affected: 407 recommended: 371 | 2026-10-16T14:25:02+00:00 | Vulnerability · Source |
| CVE-2022-49318 | suse_vex | SUSE CVE CVE-2022-49318 | known affected: 0 known not affected: 462 | 2026-10-16T14:25:00+00:00 | Vulnerability · Source |
| CVE-2022-49321 | suse_vex | SUSE CVE CVE-2022-49321 | known affected: 393 known not affected: 249 recommended: 377 | 2026-10-16T14:24:57+00:00 | Vulnerability · Source |
| CVE-2022-49322 | suse_vex | SUSE CVE CVE-2022-49322 | known affected: 496 known not affected: 178 recommended: 321 | 2026-10-16T14:24:55+00:00 | Vulnerability · Source |