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-50144 | suse_vex | SUSE CVE CVE-2022-50144 | known affected: 475 known not affected: 240 recommended: 92 | 2026-08-13T02:21:25+00:00 | Vulnerability · Source |
| CVE-2022-50153 | suse_vex | SUSE CVE CVE-2022-50153 | known affected: 425 known not affected: 198 recommended: 357 | 2026-08-13T02:21:24+00:00 | Vulnerability · Source |
| CVE-2022-50160 | suse_vex | SUSE CVE CVE-2022-50160 | known affected: 405 known not affected: 247 recommended: 273 | 2026-08-13T02:21:22+00:00 | Vulnerability · Source |
| CVE-2022-50161 | suse_vex | SUSE CVE CVE-2022-50161 | known affected: 405 known not affected: 246 recommended: 273 | 2026-08-13T02:21:21+00:00 | Vulnerability · Source |
| CVE-2022-50164 | suse_vex | SUSE CVE CVE-2022-50164 | known affected: 358 known not affected: 278 recommended: 320 | 2026-08-13T02:21:19+00:00 | Vulnerability · Source |
| CVE-2022-50175 | suse_vex | SUSE CVE CVE-2022-50175 | known affected: 442 known not affected: 215 recommended: 206 | 2026-08-13T02:21:17+00:00 | Vulnerability · Source |
| CVE-2022-50176 | suse_vex | SUSE CVE CVE-2022-50176 | known affected: 358 known not affected: 279 recommended: 273 | 2026-08-13T02:21:15+00:00 | Vulnerability · Source |
| CVE-2022-50185 | suse_vex | SUSE CVE CVE-2022-50185 | known affected: 423 known not affected: 248 recommended: 357 | 2026-08-13T02:21:14+00:00 | Vulnerability · Source |
| CVE-2022-50189 | suse_vex | SUSE CVE CVE-2022-50189 | known not affected: 401 recommended: 47 | 2026-08-13T02:21:13+00:00 | Vulnerability · Source |
| CVE-2022-50190 | suse_vex | SUSE CVE CVE-2022-50190 | known affected: 344 known not affected: 298 recommended: 233 | 2026-08-13T02:21:11+00:00 | Vulnerability · Source |
| CVE-2022-50191 | suse_vex | SUSE CVE CVE-2022-50191 | known affected: 423 known not affected: 219 recommended: 325 | 2026-08-13T02:21:10+00:00 | Vulnerability · Source |
| CVE-2022-50192 | suse_vex | SUSE CVE CVE-2022-50192 | known affected: 344 known not affected: 296 recommended: 206 | 2026-08-13T02:21:09+00:00 | Vulnerability · Source |
| CVE-2022-50198 | suse_vex | SUSE CVE CVE-2022-50198 | known affected: 348 known not affected: 307 recommended: 206 | 2026-08-13T02:21:08+00:00 | Vulnerability · Source |
| CVE-2022-50199 | suse_vex | SUSE CVE CVE-2022-50199 | known affected: 395 known not affected: 245 recommended: 206 | 2026-08-13T02:21:06+00:00 | Vulnerability · Source |
| CVE-2022-50207 | suse_vex | SUSE CVE CVE-2022-50207 | known affected: 348 known not affected: 307 recommended: 206 | 2026-08-13T02:21:05+00:00 | Vulnerability · Source |
| CVE-2022-50208 | suse_vex | SUSE CVE CVE-2022-50208 | known affected: 344 known not affected: 296 recommended: 206 | 2026-08-13T02:21:03+00:00 | Vulnerability · Source |
| CVE-2022-50210 | suse_vex | SUSE CVE CVE-2022-50210 | known not affected: 416 | 2026-08-13T02:21:02+00:00 | Vulnerability · Source |
| CVE-2022-50224 | suse_vex | SUSE CVE CVE-2022-50224 | known affected: 230 known not affected: 139 recommended: 27 | 2026-08-13T02:20:59+00:00 | Vulnerability · Source |
| CVE-2022-50226 | suse_vex | SUSE CVE CVE-2022-50226 | known affected: 443 known not affected: 184 recommended: 276 | 2026-08-13T02:20:58+00:00 | Vulnerability · Source |
| CVE-2022-50232 | suse_vex | SUSE CVE CVE-2022-50232 | known affected: 354 known not affected: 304 recommended: 196 | 2026-08-13T02:20:56+00:00 | Vulnerability · Source |
| CVE-2022-50242 | suse_vex | SUSE CVE CVE-2022-50242 | known affected: 548 known not affected: 181 recommended: 129 | 2026-08-13T02:20:53+00:00 | Vulnerability · Source |
| CVE-2022-50247 | suse_vex | SUSE CVE CVE-2022-50247 | known affected: 344 known not affected: 304 recommended: 255 | 2026-08-13T02:20:51+00:00 | Vulnerability · Source |
| CVE-2022-50249 | suse_vex | SUSE CVE CVE-2022-50249 | known affected: 405 known not affected: 176 recommended: 325 | 2026-08-13T02:20:49+00:00 | Vulnerability · Source |
| CVE-2022-50250 | suse_vex | SUSE CVE CVE-2022-50250 | known affected: 344 known not affected: 304 recommended: 235 | 2026-08-13T02:20:48+00:00 | Vulnerability · Source |
| CVE-2022-50251 | suse_vex | SUSE CVE CVE-2022-50251 | known affected: 344 known not affected: 304 recommended: 206 | 2026-08-13T02:20:46+00:00 | Vulnerability · Source |
| CVE-2022-50260 | suse_vex | SUSE CVE CVE-2022-50260 | known affected: 344 known not affected: 267 recommended: 273 | 2026-08-13T02:20:42+00:00 | Vulnerability · Source |
| CVE-2022-50261 | suse_vex | SUSE CVE CVE-2022-50261 | known affected: 411 known not affected: 237 recommended: 206 | 2026-08-13T02:20:41+00:00 | Vulnerability · Source |
| CVE-2022-50263 | suse_vex | SUSE CVE CVE-2022-50263 | known not affected: 416 recommended: 27 | 2026-08-13T02:20:40+00:00 | Vulnerability · Source |
| CVE-2022-50264 | suse_vex | SUSE CVE CVE-2022-50264 | known affected: 395 known not affected: 253 recommended: 206 | 2026-08-13T02:20:38+00:00 | Vulnerability · Source |
| CVE-2022-50272 | suse_vex | SUSE CVE CVE-2022-50272 | known affected: 75 known not affected: 181 recommended: 316 | 2026-08-13T02:20:37+00:00 | Vulnerability · Source |
| CVE-2022-50292 | suse_vex | SUSE CVE CVE-2022-50292 | known affected: 369 known not affected: 359 recommended: 92 | 2026-08-13T02:20:33+00:00 | Vulnerability · Source |
| CVE-2022-50297 | suse_vex | SUSE CVE CVE-2022-50297 | known affected: 470 known not affected: 187 recommended: 278 | 2026-08-13T02:20:31+00:00 | Vulnerability · Source |
| CVE-2022-50301 | suse_vex | SUSE CVE CVE-2022-50301 | known affected: 405 known not affected: 243 recommended: 206 | 2026-08-13T02:20:29+00:00 | Vulnerability · Source |
| CVE-2022-50323 | suse_vex | SUSE CVE CVE-2022-50323 | known affected: 369 known not affected: 359 recommended: 92 | 2026-08-13T02:20:27+00:00 | Vulnerability · Source |
| CVE-2022-50324 | suse_vex | SUSE CVE CVE-2022-50324 | known affected: 405 known not affected: 243 recommended: 206 | 2026-08-13T02:20:25+00:00 | Vulnerability · Source |
| CVE-2022-50331 | suse_vex | SUSE CVE CVE-2022-50331 | known affected: 344 known not affected: 304 recommended: 206 | 2026-08-13T02:20:23+00:00 | Vulnerability · Source |
| CVE-2022-50346 | suse_vex | SUSE CVE CVE-2022-50346 | known affected: 462 known not affected: 187 recommended: 243 | 2026-08-13T02:20:21+00:00 | Vulnerability · Source |
| CVE-2022-50347 | suse_vex | SUSE CVE CVE-2022-50347 | known affected: 462 known not affected: 191 recommended: 243 | 2026-08-13T02:20:20+00:00 | Vulnerability · Source |
| CVE-2022-50348 | suse_vex | SUSE CVE CVE-2022-50348 | known affected: 344 known not affected: 304 recommended: 253 | 2026-08-13T02:20:18+00:00 | Vulnerability · Source |
| CVE-2022-50352 | suse_vex | SUSE CVE CVE-2022-50352 | known affected: 604 known not affected: 176 recommended: 23 | 2026-08-13T02:20:17+00:00 | Vulnerability · Source |
| CVE-2022-50353 | suse_vex | SUSE CVE CVE-2022-50353 | known affected: 494 known not affected: 195 recommended: 206 | 2026-08-13T02:20:15+00:00 | Vulnerability · Source |
| CVE-2022-50356 | suse_vex | SUSE CVE CVE-2022-50356 | known affected: 548 known not affected: 181 recommended: 191 | 2026-08-13T02:20:13+00:00 | Vulnerability · Source |
| CVE-2022-50359 | suse_vex | SUSE CVE CVE-2022-50359 | known affected: 372 known not affected: 234 recommended: 310 | 2026-08-13T02:20:12+00:00 | Vulnerability · Source |
| CVE-2022-50364 | suse_vex | SUSE CVE CVE-2022-50364 | known affected: 462 known not affected: 187 recommended: 243 | 2026-08-13T02:20:11+00:00 | Vulnerability · Source |
| CVE-2022-50372 | suse_vex | SUSE CVE CVE-2022-50372 | known affected: 395 known not affected: 223 recommended: 278 | 2026-08-13T02:20:08+00:00 | Vulnerability · Source |
| CVE-2022-50376 | suse_vex | SUSE CVE CVE-2022-50376 | known affected: 478 known not affected: 209 recommended: 206 | 2026-08-13T02:20:07+00:00 | Vulnerability · Source |
| CVE-2022-50382 | suse_vex | SUSE CVE CVE-2022-50382 | known affected: 55 known not affected: 361 | 2026-08-13T02:20:05+00:00 | Vulnerability · Source |
| CVE-2022-50387 | suse_vex | SUSE CVE CVE-2022-50387 | known affected: 92 known not affected: 324 | 2026-08-13T02:20:04+00:00 | Vulnerability · Source |
| CVE-2022-50398 | suse_vex | SUSE CVE CVE-2022-50398 | known affected: 369 known not affected: 359 recommended: 92 | 2026-08-13T02:20:02+00:00 | Vulnerability · Source |
| CVE-2022-50407 | suse_vex | SUSE CVE CVE-2022-50407 | known not affected: 416 | 2026-08-13T02:19:59+00:00 | Vulnerability · Source |