VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
90149 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-50178 | suse_vex | SUSE CVE CVE-2022-50178 | known affected: 344 known not affected: 390 recommended: 248 | 2026-10-11T01:30:05+00:00 | Vulnerability · Source |
| CVE-2022-50179 | suse_vex | SUSE CVE CVE-2022-50179 | known not affected: 326 recommended: 294 | 2026-10-11T01:30:03+00:00 | Vulnerability · Source |
| CVE-2022-50184 | suse_vex | SUSE CVE CVE-2022-50184 | known affected: 430 known not affected: 384 recommended: 92 | 2026-10-11T01:30:01+00:00 | Vulnerability · Source |
| CVE-2022-50185 | suse_vex | SUSE CVE CVE-2022-50185 | known affected: 495 known not affected: 243 recommended: 384 | 2026-10-11T01:29:59+00:00 | Vulnerability · Source |
| CVE-2022-50186 | suse_vex | SUSE CVE CVE-2022-50186 | known affected: 369 known not affected: 445 recommended: 92 | 2026-10-11T01:29:57+00:00 | Vulnerability · Source |
| CVE-2022-50187 | suse_vex | SUSE CVE CVE-2022-50187 | known affected: 344 known not affected: 390 recommended: 248 | 2026-10-11T01:29:55+00:00 | Vulnerability · Source |
| CVE-2022-50188 | suse_vex | SUSE CVE CVE-2022-50188 | known affected: 369 known not affected: 444 recommended: 92 | 2026-10-11T01:29:54+00:00 | Vulnerability · Source |
| CVE-2022-50190 | suse_vex | SUSE CVE CVE-2022-50190 | known affected: 344 known not affected: 390 recommended: 260 | 2026-10-11T01:29:52+00:00 | Vulnerability · Source |
| CVE-2022-50192 | suse_vex | SUSE CVE CVE-2022-50192 | known affected: 344 known not affected: 388 recommended: 206 | 2026-10-11T01:29:50+00:00 | Vulnerability · Source |
| CVE-2022-50201 | suse_vex | SUSE CVE CVE-2022-50201 | known affected: 344 known not affected: 388 recommended: 264 | 2026-10-11T01:29:48+00:00 | Vulnerability · Source |
| CVE-2022-50203 | suse_vex | SUSE CVE CVE-2022-50203 | known affected: 348 known not affected: 399 recommended: 206 | 2026-10-11T01:29:46+00:00 | Vulnerability · Source |
| CVE-2022-50206 | suse_vex | SUSE CVE CVE-2022-50206 | known affected: 508 known not affected: 185 recommended: 283 | 2026-10-11T01:29:44+00:00 | Vulnerability · Source |
| CVE-2022-50209 | suse_vex | SUSE CVE CVE-2022-50209 | known affected: 370 known not affected: 358 recommended: 273 | 2026-10-11T01:29:42+00:00 | Vulnerability · Source |
| CVE-2022-50211 | suse_vex | SUSE CVE CVE-2022-50211 | known affected: 446 known not affected: 347 recommended: 424 | 2026-10-11T01:29:40+00:00 | Vulnerability · Source |
| CVE-2022-50213 | suse_vex | SUSE CVE CVE-2022-50213 | known affected: 88 known not affected: 240 recommended: 314 | 2026-10-11T01:29:38+00:00 | Vulnerability · Source |
| CVE-2022-50218 | suse_vex | SUSE CVE CVE-2022-50218 | known affected: 463 known not affected: 282 recommended: 273 | 2026-10-11T01:29:35+00:00 | Vulnerability · Source |
| CVE-2022-50222 | suse_vex | SUSE CVE CVE-2022-50222 | known affected: 370 known not affected: 358 recommended: 273 | 2026-10-11T01:29:33+00:00 | Vulnerability · Source |
| CVE-2022-50229 | suse_vex | SUSE CVE CVE-2022-50229 | known affected: 495 known not affected: 192 recommended: 397 | 2026-10-11T01:29:31+00:00 | Vulnerability · Source |
| CVE-2022-50231 | suse_vex | SUSE CVE CVE-2022-50231 | known affected: 370 known not affected: 360 recommended: 273 | 2026-10-11T01:29:29+00:00 | Vulnerability · Source |
| CVE-2022-50239 | suse_vex | SUSE CVE CVE-2022-50239 | known affected: 344 known not affected: 395 recommended: 264 | 2026-10-11T01:29:27+00:00 | Vulnerability · Source |
| CVE-2022-50247 | suse_vex | SUSE CVE CVE-2022-50247 | known affected: 344 known not affected: 395 recommended: 255 | 2026-10-11T01:29:24+00:00 | Vulnerability · Source |
| CVE-2022-50253 | suse_vex | SUSE CVE CVE-2022-50253 | known affected: 697 known not affected: 36 recommended: 487 | 2026-10-11T01:29:22+00:00 | Vulnerability · Source |
| CVE-2022-50260 | suse_vex | SUSE CVE CVE-2022-50260 | known affected: 344 known not affected: 352 recommended: 273 | 2026-10-11T01:29:20+00:00 | Vulnerability · Source |
| CVE-2022-50263 | suse_vex | SUSE CVE CVE-2022-50263 | known not affected: 523 recommended: 54 | 2026-10-11T01:29:18+00:00 | Vulnerability · Source |
| CVE-2022-50267 | suse_vex | SUSE CVE CVE-2022-50267 | known affected: 344 known not affected: 395 recommended: 206 | 2026-10-11T01:29:16+00:00 | Vulnerability · Source |
| CVE-2022-50271 | suse_vex | SUSE CVE CVE-2022-50271 | known affected: 463 known not affected: 175 recommended: 343 | 2026-10-11T01:29:14+00:00 | Vulnerability · Source |
| CVE-2022-50272 | suse_vex | SUSE CVE CVE-2022-50272 | known affected: 147 known not affected: 170 recommended: 345 | 2026-10-11T01:29:12+00:00 | Vulnerability · Source |
| CVE-2022-50274 | suse_vex | SUSE CVE CVE-2022-50274 | known not affected: 523 recommended: 20 | 2026-10-11T01:29:11+00:00 | Vulnerability · Source |
| CVE-2022-50276 | suse_vex | SUSE CVE CVE-2022-50276 | known affected: 413 known not affected: 326 recommended: 264 | 2026-10-11T01:29:09+00:00 | Vulnerability · Source |
| CVE-2022-50280 | suse_vex | SUSE CVE CVE-2022-50280 | known affected: 502 known not affected: 176 recommended: 308 | 2026-10-11T01:29:07+00:00 | Vulnerability · Source |
| CVE-2022-50285 | suse_vex | SUSE CVE CVE-2022-50285 | known affected: 651 known not affected: 243 recommended: 64 | 2026-10-11T01:29:05+00:00 | Vulnerability · Source |
| CVE-2022-50287 | suse_vex | SUSE CVE CVE-2022-50287 | known affected: 369 known not affected: 456 recommended: 170 | 2026-10-11T01:29:04+00:00 | Vulnerability · Source |
| CVE-2022-50298 | suse_vex | SUSE CVE CVE-2022-50298 | known affected: 344 known not affected: 395 recommended: 206 | 2026-10-11T01:29:01+00:00 | Vulnerability · Source |
| CVE-2022-50299 | suse_vex | SUSE CVE CVE-2022-50299 | known affected: 437 known not affected: 197 recommended: 396 | 2026-10-11T01:28:59+00:00 | Vulnerability · Source |
| CVE-2022-50306 | suse_vex | SUSE CVE CVE-2022-50306 | known not affected: 523 recommended: 54 | 2026-10-11T01:28:56+00:00 | Vulnerability · Source |
| CVE-2022-50308 | suse_vex | SUSE CVE CVE-2022-50308 | known affected: 344 known not affected: 395 recommended: 253 | 2026-10-11T01:28:54+00:00 | Vulnerability · Source |
| CVE-2022-50317 | suse_vex | SUSE CVE CVE-2022-50317 | known affected: 344 known not affected: 352 recommended: 351 | 2026-10-11T01:28:51+00:00 | Vulnerability · Source |
| CVE-2022-50323 | suse_vex | SUSE CVE CVE-2022-50323 | known affected: 369 known not affected: 456 recommended: 92 | 2026-10-11T01:28:48+00:00 | Vulnerability · Source |
| CVE-2022-50324 | suse_vex | SUSE CVE CVE-2022-50324 | known affected: 465 known not affected: 274 recommended: 206 | 2026-10-11T01:28:46+00:00 | Vulnerability · Source |
| CVE-2022-50325 | suse_vex | SUSE CVE CVE-2022-50325 | known affected: 369 known not affected: 456 recommended: 166 | 2026-10-11T01:28:44+00:00 | Vulnerability · Source |
| CVE-2022-50328 | suse_vex | SUSE CVE CVE-2022-50328 | known affected: 344 known not affected: 395 recommended: 206 | 2026-10-11T01:28:42+00:00 | Vulnerability · Source |
| CVE-2022-50329 | suse_vex | SUSE CVE CVE-2022-50329 | known affected: 344 known not affected: 389 recommended: 239 | 2026-10-11T01:28:40+00:00 | Vulnerability · Source |
| CVE-2022-50334 | suse_vex | SUSE CVE CVE-2022-50334 | known affected: 354 known not affected: 322 recommended: 271 | 2026-10-11T01:28:37+00:00 | Vulnerability · Source |
| CVE-2022-50339 | suse_vex | SUSE CVE CVE-2022-50339 | known affected: 369 known not affected: 456 recommended: 92 | 2026-10-11T01:28:34+00:00 | Vulnerability · Source |
| CVE-2022-50340 | suse_vex | SUSE CVE CVE-2022-50340 | known affected: 413 known not affected: 326 recommended: 206 | 2026-10-11T01:28:32+00:00 | Vulnerability · Source |
| CVE-2022-50341 | suse_vex | SUSE CVE CVE-2022-50341 | known affected: 162 known not affected: 361 recommended: 91 | 2026-10-11T01:28:30+00:00 | Vulnerability · Source |
| CVE-2022-50350 | suse_vex | SUSE CVE CVE-2022-50350 | known affected: 724 known not affected: 170 recommended: 111 | 2026-10-11T01:28:28+00:00 | Vulnerability · Source |
| CVE-2022-50354 | suse_vex | SUSE CVE CVE-2022-50354 | known affected: 430 known not affected: 395 recommended: 141 | 2026-10-11T01:28:26+00:00 | Vulnerability · Source |
| CVE-2022-50355 | suse_vex | SUSE CVE CVE-2022-50355 | known affected: 370 known not affected: 326 recommended: 273 | 2026-10-11T01:28:25+00:00 | Vulnerability · Source |
| CVE-2022-50361 | suse_vex | SUSE CVE CVE-2022-50361 | known not affected: 523 recommended: 58 | 2026-10-11T01:28:23+00:00 | Vulnerability · Source |