VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291734 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2022-50367 | suse_vex | SUSE CVE CVE-2022-50367 | known affected: 455 known not affected: 166 recommended: 359 | 2026-08-05T01:10:17+00:00 | Vulnerability · Source |
| CVE-2022-50373 | suse_vex | SUSE CVE CVE-2022-50373 | known affected: 344 known not affected: 304 recommended: 206 | 2026-08-05T01:10:14+00:00 | Vulnerability · Source |
| CVE-2022-50386 | suse_vex | SUSE CVE CVE-2022-50386 | known affected: 405 known not affected: 166 recommended: 368 | 2026-08-05T01:10:12+00:00 | Vulnerability · Source |
| CVE-2022-50393 | suse_vex | SUSE CVE CVE-2022-50393 | known affected: 377 known not affected: 383 recommended: 141 | 2026-08-05T01:10:11+00:00 | Vulnerability · Source |
| CVE-2022-50394 | suse_vex | SUSE CVE CVE-2022-50394 | known affected: 468 known not affected: 181 recommended: 243 | 2026-08-05T01:10:09+00:00 | Vulnerability · Source |
| CVE-2022-50399 | suse_vex | SUSE CVE CVE-2022-50399 | known affected: 442 known not affected: 206 recommended: 206 | 2026-08-05T01:10:08+00:00 | Vulnerability · Source |
| CVE-2022-50405 | suse_vex | SUSE CVE CVE-2022-50405 | known affected: 624 known not affected: 187 recommended: 84 | 2026-08-05T01:10:06+00:00 | Vulnerability · Source |
| CVE-2022-50406 | suse_vex | SUSE CVE CVE-2022-50406 | known affected: 542 known not affected: 187 recommended: 191 | 2026-08-05T01:10:05+00:00 | Vulnerability · Source |
| CVE-2022-50409 | suse_vex | SUSE CVE CVE-2022-50409 | known affected: 405 known not affected: 162 recommended: 368 | 2026-08-05T01:10:03+00:00 | Vulnerability · Source |
| CVE-2022-50410 | suse_vex | SUSE CVE CVE-2022-50410 | known not affected: 233 recommended: 332 | 2026-08-05T01:10:01+00:00 | Vulnerability · Source |
| CVE-2022-50411 | suse_vex | SUSE CVE CVE-2022-50411 | known affected: 462 known not affected: 187 recommended: 243 | 2026-08-05T01:10:00+00:00 | Vulnerability · Source |
| CVE-2022-50419 | suse_vex | SUSE CVE CVE-2022-50419 | known affected: 419 known not affected: 187 recommended: 310 | 2026-08-05T01:09:57+00:00 | Vulnerability · Source |
| CVE-2022-50432 | suse_vex | SUSE CVE CVE-2022-50432 | known affected: 420 known not affected: 187 recommended: 330 | 2026-08-05T01:09:53+00:00 | Vulnerability · Source |
| CVE-2022-50440 | suse_vex | SUSE CVE CVE-2022-50440 | known affected: 6 known not affected: 227 recommended: 321 | 2026-08-05T01:09:52+00:00 | Vulnerability · Source |
| CVE-2022-50454 | suse_vex | SUSE CVE CVE-2022-50454 | known affected: 344 known not affected: 267 recommended: 273 | 2026-08-05T01:09:48+00:00 | Vulnerability · Source |
| CVE-2022-50459 | suse_vex | SUSE CVE CVE-2022-50459 | known affected: 375 known not affected: 206 recommended: 323 | 2026-08-05T01:09:47+00:00 | Vulnerability · Source |
| CVE-2022-50472 | suse_vex | SUSE CVE CVE-2022-50472 | known affected: 405 known not affected: 253 recommended: 245 | 2026-08-05T01:09:45+00:00 | Vulnerability · Source |
| CVE-2022-50488 | suse_vex | SUSE CVE CVE-2022-50488 | known affected: 357 known not affected: 267 recommended: 288 | 2026-08-05T01:09:43+00:00 | Vulnerability · Source |
| CVE-2022-50490 | suse_vex | SUSE CVE CVE-2022-50490 | known affected: 354 known not affected: 304 recommended: 219 | 2026-08-05T01:09:42+00:00 | Vulnerability · Source |