VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291265 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49910 | suse_vex | SUSE CVE CVE-2022-49910 | known not affected: 236 recommended: 275 | 2026-08-05T01:12:23+00:00 | Vulnerability · Source |
| CVE-2022-49919 | suse_vex | SUSE CVE CVE-2022-49919 | known not affected: 397 | 2026-08-05T01:12:22+00:00 | Vulnerability · Source |
| CVE-2022-49928 | suse_vex | SUSE CVE CVE-2022-49928 | known affected: 339 known not affected: 294 recommended: 214 | 2026-08-05T01:12:19+00:00 | Vulnerability · Source |
| CVE-2022-49931 | suse_vex | SUSE CVE CVE-2022-49931 | known affected: 380 known not affected: 227 recommended: 237 | 2026-08-05T01:12:17+00:00 | Vulnerability · Source |
| CVE-2022-49935 | suse_vex | SUSE CVE CVE-2022-49935 | known affected: 461 known not affected: 255 recommended: 139 | 2026-08-05T01:12:16+00:00 | Vulnerability · Source |
| CVE-2022-49939 | suse_vex | SUSE CVE CVE-2022-49939 | known affected: 163 known not affected: 238 | 2026-08-05T01:12:14+00:00 | Vulnerability · Source |
| CVE-2022-49944 | suse_vex | SUSE CVE CVE-2022-49944 | known affected: 369 known not affected: 347 recommended: 139 | 2026-08-05T01:12:13+00:00 | Vulnerability · Source |
| CVE-2022-49950 | suse_vex | SUSE CVE CVE-2022-49950 | known affected: 358 known not affected: 280 recommended: 273 | 2026-08-05T01:12:10+00:00 | Vulnerability · Source |
| CVE-2022-49968 | suse_vex | SUSE CVE CVE-2022-49968 | known affected: 358 known not affected: 280 recommended: 273 | 2026-08-05T01:12:05+00:00 | Vulnerability · Source |
| CVE-2022-49979 | suse_vex | SUSE CVE CVE-2022-49979 | known affected: 506 known not affected: 279 recommended: 95 | 2026-08-05T01:12:02+00:00 | Vulnerability · Source |
| CVE-2022-49985 | suse_vex | SUSE CVE CVE-2022-49985 | known not affected: 292 recommended: 282 | 2026-08-05T01:12:00+00:00 | Vulnerability · Source |
| CVE-2022-49997 | suse_vex | SUSE CVE CVE-2022-49997 | known affected: 55 known not affected: 346 | 2026-08-05T01:11:57+00:00 | Vulnerability · Source |
| CVE-2022-49998 | suse_vex | SUSE CVE CVE-2022-49998 | known affected: 106 known not affected: 295 recommended: 27 | 2026-08-05T01:11:56+00:00 | Vulnerability · Source |
| CVE-2022-49999 | suse_vex | SUSE CVE CVE-2022-49999 | known affected: 344 known not affected: 298 recommended: 206 | 2026-08-05T01:11:54+00:00 | Vulnerability · Source |
| CVE-2022-50014 | suse_vex | SUSE CVE CVE-2022-50014 | known not affected: 401 recommended: 27 | 2026-08-05T01:11:52+00:00 | Vulnerability · Source |
| CVE-2022-50064 | suse_vex | SUSE CVE CVE-2022-50064 | known not affected: 416 recommended: 29 | 2026-08-05T01:11:45+00:00 | Vulnerability · Source |
| CVE-2022-50070 | suse_vex | SUSE CVE CVE-2022-50070 | known affected: 70 known not affected: 346 recommended: 47 | 2026-08-05T01:11:44+00:00 | Vulnerability · Source |
| CVE-2022-50072 | suse_vex | SUSE CVE CVE-2022-50072 | known affected: 344 known not affected: 294 recommended: 322 | 2026-08-05T01:11:42+00:00 | Vulnerability · Source |
| CVE-2022-50087 | suse_vex | SUSE CVE CVE-2022-50087 | known affected: 395 known not affected: 197 recommended: 372 | 2026-08-05T01:11:38+00:00 | Vulnerability · Source |
| CVE-2022-50095 | suse_vex | SUSE CVE CVE-2022-50095 | known affected: 4 known not affected: 309 recommended: 178 | 2026-08-05T01:11:36+00:00 | Vulnerability · Source |
| CVE-2022-50099 | suse_vex | SUSE CVE CVE-2022-50099 | known affected: 344 known not affected: 283 recommended: 296 | 2026-08-05T01:11:31+00:00 | Vulnerability · Source |
| CVE-2022-50136 | suse_vex | SUSE CVE CVE-2022-50136 | known affected: 358 known not affected: 280 recommended: 320 | 2026-08-05T01:11:25+00:00 | Vulnerability · Source |
| CVE-2022-50145 | suse_vex | SUSE CVE CVE-2022-50145 | known affected: 344 known not affected: 298 recommended: 206 | 2026-08-05T01:11:22+00:00 | Vulnerability · Source |
| CVE-2022-50156 | suse_vex | SUSE CVE CVE-2022-50156 | known affected: 358 known not affected: 280 recommended: 300 | 2026-08-05T01:11:20+00:00 | Vulnerability · Source |
| CVE-2022-50200 | suse_vex | SUSE CVE CVE-2022-50200 | known affected: 419 known not affected: 148 recommended: 365 | 2026-08-05T01:11:14+00:00 | Vulnerability · Source |
| CVE-2022-50212 | suse_vex | SUSE CVE CVE-2022-50212 | known not affected: 294 recommended: 245 | 2026-08-05T01:11:12+00:00 | Vulnerability · Source |
| CVE-2022-50213 | suse_vex | SUSE CVE CVE-2022-50213 | known affected: 44 known not affected: 220 recommended: 314 | 2026-08-05T01:11:10+00:00 | Vulnerability · Source |
| CVE-2022-50214 | suse_vex | SUSE CVE CVE-2022-50214 | known affected: 106 known not affected: 295 recommended: 43 | 2026-08-05T01:11:08+00:00 | Vulnerability · Source |
| CVE-2022-50227 | suse_vex | SUSE CVE CVE-2022-50227 | known not affected: 401 recommended: 27 | 2026-08-05T01:11:03+00:00 | Vulnerability · Source |
| CVE-2022-50231 | suse_vex | SUSE CVE CVE-2022-50231 | known affected: 358 known not affected: 280 recommended: 273 | 2026-08-05T01:11:01+00:00 | Vulnerability · Source |
| CVE-2022-50233 | suse_vex | SUSE CVE CVE-2022-50233 | known affected: 361 known not affected: 200 recommended: 329 | 2026-08-05T01:10:59+00:00 | Vulnerability · Source |
| CVE-2022-50234 | suse_vex | SUSE CVE CVE-2022-50234 | known not affected: 265 recommended: 264 | 2026-08-05T01:10:58+00:00 | Vulnerability · Source |
| CVE-2022-50235 | suse_vex | SUSE CVE CVE-2022-50235 | known not affected: 233 recommended: 319 | 2026-08-05T01:10:56+00:00 | Vulnerability · Source |
| CVE-2022-50241 | suse_vex | SUSE CVE CVE-2022-50241 | known affected: 348 known not affected: 462 recommended: 233 | 2026-08-05T01:10:54+00:00 | Vulnerability · Source |
| CVE-2022-50248 | suse_vex | SUSE CVE CVE-2022-50248 | known affected: 389 known not affected: 253 recommended: 297 | 2026-08-05T01:10:52+00:00 | Vulnerability · Source |
| CVE-2022-50252 | suse_vex | SUSE CVE CVE-2022-50252 | known affected: 405 known not affected: 150 recommended: 385 | 2026-08-05T01:10:51+00:00 | Vulnerability · Source |
| CVE-2022-50255 | suse_vex | SUSE CVE CVE-2022-50255 | known affected: 344 known not affected: 304 recommended: 206 | 2026-08-05T01:10:47+00:00 | Vulnerability · Source |
| CVE-2022-50270 | suse_vex | SUSE CVE CVE-2022-50270 | known not affected: 416 | 2026-08-05T01:10:44+00:00 | Vulnerability · Source |
| CVE-2022-50274 | suse_vex | SUSE CVE CVE-2022-50274 | known not affected: 416 recommended: 20 | 2026-08-05T01:10:43+00:00 | Vulnerability · Source |
| CVE-2022-50283 | suse_vex | SUSE CVE CVE-2022-50283 | known not affected: 416 | 2026-08-05T01:10:41+00:00 | Vulnerability · Source |
| CVE-2022-50286 | suse_vex | SUSE CVE CVE-2022-50286 | known affected: 395 known not affected: 253 recommended: 235 | 2026-08-05T01:10:39+00:00 | Vulnerability · Source |
| CVE-2022-50300 | suse_vex | SUSE CVE CVE-2022-50300 | known affected: 106 known not affected: 310 | 2026-08-05T01:10:37+00:00 | Vulnerability · Source |
| CVE-2022-50325 | suse_vex | SUSE CVE CVE-2022-50325 | known affected: 369 known not affected: 359 recommended: 139 | 2026-08-05T01:10:32+00:00 | Vulnerability · Source |
| CVE-2022-50328 | suse_vex | SUSE CVE CVE-2022-50328 | known affected: 344 known not affected: 304 recommended: 206 | 2026-08-05T01:10:30+00:00 | Vulnerability · Source |
| CVE-2022-50330 | suse_vex | SUSE CVE CVE-2022-50330 | known affected: 391 known not affected: 190 recommended: 296 | 2026-08-05T01:10:27+00:00 | Vulnerability · Source |
| CVE-2022-50333 | suse_vex | SUSE CVE CVE-2022-50333 | known affected: 344 known not affected: 304 recommended: 206 | 2026-08-05T01:10:26+00:00 | Vulnerability · Source |
| CVE-2022-50339 | suse_vex | SUSE CVE CVE-2022-50339 | known affected: 369 known not affected: 359 recommended: 92 | 2026-08-05T01:10:24+00:00 | Vulnerability · Source |
| CVE-2022-50354 | suse_vex | SUSE CVE CVE-2022-50354 | known affected: 424 known not affected: 304 recommended: 141 | 2026-08-05T01:10:22+00:00 | Vulnerability · Source |
| CVE-2022-50355 | suse_vex | SUSE CVE CVE-2022-50355 | known affected: 358 known not affected: 253 recommended: 273 | 2026-08-05T01:10:20+00:00 | Vulnerability · Source |
| CVE-2022-50362 | suse_vex | SUSE CVE CVE-2022-50362 | known affected: 344 known not affected: 304 recommended: 206 | 2026-08-05T01:10:19+00:00 | Vulnerability · Source |