VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291717 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49908 | suse_vex | SUSE CVE CVE-2022-49908 | known not affected: 297 recommended: 206 | 2026-08-13T02:22:46+00:00 | Vulnerability · Source |
| CVE-2022-49913 | suse_vex | SUSE CVE CVE-2022-49913 | known affected: 562 known not affected: 198 recommended: 37 | 2026-08-13T02:22:44+00:00 | Vulnerability · Source |
| CVE-2022-49915 | suse_vex | SUSE CVE CVE-2022-49915 | known affected: 424 known not affected: 152 recommended: 318 | 2026-08-13T02:22:43+00:00 | Vulnerability · Source |
| CVE-2022-49916 | suse_vex | SUSE CVE CVE-2022-49916 | known affected: 339 known not affected: 292 recommended: 214 | 2026-08-13T02:22:41+00:00 | Vulnerability · Source |
| CVE-2022-49925 | suse_vex | SUSE CVE CVE-2022-49925 | known affected: 455 known not affected: 148 recommended: 298 | 2026-08-13T02:22:40+00:00 | Vulnerability · Source |
| CVE-2022-49936 | suse_vex | SUSE CVE CVE-2022-49936 | known not affected: 418 recommended: 319 | 2026-08-13T02:22:38+00:00 | Vulnerability · Source |
| CVE-2022-49940 | suse_vex | SUSE CVE CVE-2022-49940 | known affected: 344 known not affected: 296 recommended: 255 | 2026-08-13T02:22:36+00:00 | Vulnerability · Source |
| CVE-2022-49943 | suse_vex | SUSE CVE CVE-2022-49943 | known affected: 369 known not affected: 268 recommended: 235 | 2026-08-13T02:22:34+00:00 | Vulnerability · Source |
| CVE-2022-49949 | suse_vex | SUSE CVE CVE-2022-49949 | known affected: 369 known not affected: 346 recommended: 92 | 2026-08-13T02:22:32+00:00 | Vulnerability · Source |
| CVE-2022-49951 | suse_vex | SUSE CVE CVE-2022-49951 | known affected: 369 known not affected: 347 recommended: 139 | 2026-08-13T02:22:31+00:00 | Vulnerability · Source |
| CVE-2022-49952 | suse_vex | SUSE CVE CVE-2022-49952 | known affected: 358 known not affected: 279 recommended: 273 | 2026-08-13T02:22:30+00:00 | Vulnerability · Source |
| CVE-2022-49962 | suse_vex | SUSE CVE CVE-2022-49962 | known affected: 369 known not affected: 347 recommended: 139 | 2026-08-13T02:22:28+00:00 | Vulnerability · Source |
| CVE-2022-49965 | suse_vex | SUSE CVE CVE-2022-49965 | known affected: 369 known not affected: 346 recommended: 139 | 2026-08-13T02:22:27+00:00 | Vulnerability · Source |
| CVE-2022-49966 | suse_vex | SUSE CVE CVE-2022-49966 | known affected: 344 known not affected: 298 recommended: 253 | 2026-08-13T02:22:25+00:00 | Vulnerability · Source |
| CVE-2022-49969 | suse_vex | SUSE CVE CVE-2022-49969 | known affected: 416 known not affected: 200 recommended: 276 | 2026-08-13T02:22:24+00:00 | Vulnerability · Source |
| CVE-2022-49977 | suse_vex | SUSE CVE CVE-2022-49977 | known affected: 419 known not affected: 204 recommended: 359 | 2026-08-13T02:22:22+00:00 | Vulnerability · Source |
| CVE-2022-49978 | suse_vex | SUSE CVE CVE-2022-49978 | known affected: 344 known not affected: 268 recommended: 296 | 2026-08-13T02:22:20+00:00 | Vulnerability · Source |
| CVE-2022-49981 | suse_vex | SUSE CVE CVE-2022-49981 | known affected: 423 known not affected: 250 recommended: 337 | 2026-08-13T02:22:19+00:00 | Vulnerability · Source |
| CVE-2022-49984 | suse_vex | SUSE CVE CVE-2022-49984 | known affected: 358 known not affected: 280 recommended: 300 | 2026-08-13T02:22:17+00:00 | Vulnerability · Source |
| CVE-2022-49990 | suse_vex | SUSE CVE CVE-2022-49990 | known affected: 405 known not affected: 220 recommended: 323 | 2026-08-13T02:22:15+00:00 | Vulnerability · Source |
| CVE-2022-49994 | suse_vex | SUSE CVE CVE-2022-49994 | known affected: 55 known not affected: 346 recommended: 27 | 2026-08-13T02:22:14+00:00 | Vulnerability · Source |
| CVE-2022-50006 | suse_vex | SUSE CVE CVE-2022-50006 | known affected: 344 known not affected: 297 recommended: 233 | 2026-08-13T02:22:11+00:00 | Vulnerability · Source |
| CVE-2022-50008 | suse_vex | SUSE CVE CVE-2022-50008 | known affected: 456 known not affected: 171 recommended: 243 | 2026-08-13T02:22:10+00:00 | Vulnerability · Source |
| CVE-2022-50012 | suse_vex | SUSE CVE CVE-2022-50012 | known affected: 419 known not affected: 207 recommended: 296 | 2026-08-13T02:22:08+00:00 | Vulnerability · Source |
| CVE-2022-50013 | suse_vex | SUSE CVE CVE-2022-50013 | known not affected: 401 | 2026-08-13T02:22:07+00:00 | Vulnerability · Source |
| CVE-2022-50015 | suse_vex | SUSE CVE CVE-2022-50015 | known affected: 475 known not affected: 240 recommended: 139 | 2026-08-13T02:22:05+00:00 | Vulnerability · Source |
| CVE-2022-50019 | suse_vex | SUSE CVE CVE-2022-50019 | known affected: 344 known not affected: 292 recommended: 273 | 2026-08-13T02:22:04+00:00 | Vulnerability · Source |
| CVE-2022-50020 | suse_vex | SUSE CVE CVE-2022-50020 | known affected: 452 known not affected: 171 recommended: 370 | 2026-08-13T02:22:02+00:00 | Vulnerability · Source |
| CVE-2022-50027 | suse_vex | SUSE CVE CVE-2022-50027 | known affected: 359 known not affected: 263 recommended: 338 | 2026-08-13T02:22:00+00:00 | Vulnerability · Source |
| CVE-2022-50031 | suse_vex | SUSE CVE CVE-2022-50031 | known affected: 344 known not affected: 311 recommended: 206 | 2026-08-13T02:21:59+00:00 | Vulnerability · Source |
| CVE-2022-50036 | suse_vex | SUSE CVE CVE-2022-50036 | known affected: 344 known not affected: 307 recommended: 273 | 2026-08-13T02:21:57+00:00 | Vulnerability · Source |
| CVE-2022-50050 | suse_vex | SUSE CVE CVE-2022-50050 | known affected: 461 known not affected: 254 recommended: 139 | 2026-08-13T02:21:54+00:00 | Vulnerability · Source |
| CVE-2022-50052 | suse_vex | SUSE CVE CVE-2022-50052 | known affected: 369 known not affected: 347 recommended: 139 | 2026-08-13T02:21:52+00:00 | Vulnerability · Source |
| CVE-2022-50054 | suse_vex | SUSE CVE CVE-2022-50054 | known affected: 369 known not affected: 346 recommended: 139 | 2026-08-13T02:21:50+00:00 | Vulnerability · Source |
| CVE-2022-50061 | suse_vex | SUSE CVE CVE-2022-50061 | known affected: 344 known not affected: 309 recommended: 273 | 2026-08-13T02:21:48+00:00 | Vulnerability · Source |
| CVE-2022-50067 | suse_vex | SUSE CVE CVE-2022-50067 | known not affected: 418 recommended: 286 | 2026-08-13T02:21:47+00:00 | Vulnerability · Source |
| CVE-2022-50073 | suse_vex | SUSE CVE CVE-2022-50073 | known affected: 344 known not affected: 270 recommended: 249 | 2026-08-13T02:21:45+00:00 | Vulnerability · Source |
| CVE-2022-50078 | suse_vex | SUSE CVE CVE-2022-50078 | known not affected: 401 | 2026-08-13T02:21:44+00:00 | Vulnerability · Source |
| CVE-2022-50080 | suse_vex | SUSE CVE CVE-2022-50080 | known affected: 533 known not affected: 263 recommended: 52 | 2026-08-13T02:21:42+00:00 | Vulnerability · Source |
| CVE-2022-50092 | suse_vex | SUSE CVE CVE-2022-50092 | known affected: 419 known not affected: 254 recommended: 352 | 2026-08-13T02:21:41+00:00 | Vulnerability · Source |
| CVE-2022-50094 | suse_vex | SUSE CVE CVE-2022-50094 | known affected: 419 known not affected: 204 recommended: 310 | 2026-08-13T02:21:40+00:00 | Vulnerability · Source |
| CVE-2022-50097 | suse_vex | SUSE CVE CVE-2022-50097 | known affected: 344 known not affected: 281 recommended: 296 | 2026-08-13T02:21:38+00:00 | Vulnerability · Source |
| CVE-2022-50103 | suse_vex | SUSE CVE CVE-2022-50103 | known affected: 480 known not affected: 148 recommended: 243 | 2026-08-13T02:21:37+00:00 | Vulnerability · Source |
| CVE-2022-50108 | suse_vex | SUSE CVE CVE-2022-50108 | known affected: 344 known not affected: 307 recommended: 273 | 2026-08-13T02:21:35+00:00 | Vulnerability · Source |
| CVE-2022-50109 | suse_vex | SUSE CVE CVE-2022-50109 | known affected: 344 known not affected: 283 recommended: 296 | 2026-08-13T02:21:34+00:00 | Vulnerability · Source |
| CVE-2022-50111 | suse_vex | SUSE CVE CVE-2022-50111 | known affected: 344 known not affected: 298 recommended: 253 | 2026-08-13T02:21:32+00:00 | Vulnerability · Source |
| CVE-2022-50131 | suse_vex | SUSE CVE CVE-2022-50131 | known affected: 344 known not affected: 296 recommended: 253 | 2026-08-13T02:21:31+00:00 | Vulnerability · Source |
| CVE-2022-50133 | suse_vex | SUSE CVE CVE-2022-50133 | known affected: 369 known not affected: 347 recommended: 139 | 2026-08-13T02:21:29+00:00 | Vulnerability · Source |
| CVE-2022-50134 | suse_vex | SUSE CVE CVE-2022-50134 | known affected: 446 known not affected: 183 recommended: 229 | 2026-08-13T02:21:28+00:00 | Vulnerability · Source |
| CVE-2022-50140 | suse_vex | SUSE CVE CVE-2022-50140 | known affected: 419 known not affected: 234 recommended: 273 | 2026-08-13T02:21:27+00:00 | Vulnerability · Source |