VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49355 | suse_vex | SUSE CVE CVE-2022-49355 | known not affected: 352 | 2026-07-26T16:50:20+00:00 | Vulnerability · Source |
| CVE-2022-49407 | suse_vex | SUSE CVE CVE-2022-49407 | known affected: 452 known not affected: 154 recommended: 263 | 2026-07-26T16:50:19+00:00 | Vulnerability · Source |
| CVE-2022-49462 | suse_vex | SUSE CVE CVE-2022-49462 | known affected: 348 known not affected: 256 recommended: 293 | 2026-07-26T16:50:17+00:00 | Vulnerability · Source |
| CVE-2022-49464 | suse_vex | SUSE CVE CVE-2022-49464 | known not affected: 352 | 2026-07-26T16:50:15+00:00 | Vulnerability · Source |
| CVE-2022-49500 | suse_vex | SUSE CVE CVE-2022-49500 | known not affected: 352 | 2026-07-26T16:50:12+00:00 | Vulnerability · Source |
| CVE-2022-49557 | suse_vex | SUSE CVE CVE-2022-49557 | known not affected: 352 recommended: 42 | 2026-07-26T16:50:10+00:00 | Vulnerability · Source |
| CVE-2022-49675 | suse_vex | SUSE CVE CVE-2022-49675 | known affected: 334 known not affected: 298 recommended: 243 | 2026-07-26T16:50:06+00:00 | Vulnerability · Source |
| CVE-2022-49757 | suse_vex | SUSE CVE CVE-2022-49757 | known affected: 224 known not affected: 120 | 2026-07-26T16:50:01+00:00 | Vulnerability · Source |
| CVE-2022-49779 | suse_vex | SUSE CVE CVE-2022-49779 | known affected: 339 known not affected: 294 recommended: 214 | 2026-07-26T16:50:00+00:00 | Vulnerability · Source |
| CVE-2022-49803 | suse_vex | SUSE CVE CVE-2022-49803 | known affected: 149 known not affected: 248 | 2026-07-26T16:49:58+00:00 | Vulnerability · Source |
| CVE-2022-49995 | suse_vex | SUSE CVE CVE-2022-49995 | known affected: 344 known not affected: 298 recommended: 253 | 2026-07-26T16:49:53+00:00 | Vulnerability · Source |
| CVE-2022-50033 | suse_vex | SUSE CVE CVE-2022-50033 | known affected: 429 known not affected: 196 recommended: 337 | 2026-07-26T16:49:51+00:00 | Vulnerability · Source |
| CVE-2022-50045 | suse_vex | SUSE CVE CVE-2022-50045 | known affected: 344 known not affected: 268 recommended: 296 | 2026-07-26T16:49:49+00:00 | Vulnerability · Source |
| CVE-2022-50146 | suse_vex | SUSE CVE CVE-2022-50146 | known affected: 375 known not affected: 237 recommended: 323 | 2026-07-26T16:49:47+00:00 | Vulnerability · Source |
| CVE-2022-50152 | suse_vex | SUSE CVE CVE-2022-50152 | known affected: 344 known not affected: 283 recommended: 323 | 2026-07-26T16:49:45+00:00 | Vulnerability · Source |
| CVE-2022-50209 | suse_vex | SUSE CVE CVE-2022-50209 | known affected: 358 known not affected: 280 recommended: 273 | 2026-07-26T16:49:44+00:00 | Vulnerability · Source |
| CVE-2022-50281 | suse_vex | SUSE CVE CVE-2022-50281 | known affected: 55 known not affected: 361 | 2026-07-26T16:49:42+00:00 | Vulnerability · Source |
| CVE-2022-50296 | suse_vex | SUSE CVE CVE-2022-50296 | known affected: 10 known not affected: 406 | 2026-07-26T16:49:41+00:00 | Vulnerability · Source |
| CVE-2022-50342 | suse_vex | SUSE CVE CVE-2022-50342 | known affected: 344 known not affected: 304 recommended: 235 | 2026-07-26T16:49:39+00:00 | Vulnerability · Source |
| CVE-2022-50365 | suse_vex | SUSE CVE CVE-2022-50365 | known affected: 547 known not affected: 233 recommended: 43 | 2026-07-26T16:49:37+00:00 | Vulnerability · Source |
| CVE-2022-50383 | suse_vex | SUSE CVE CVE-2022-50383 | known not affected: 416 | 2026-07-26T16:49:35+00:00 | Vulnerability · Source |
| CVE-2022-50404 | suse_vex | SUSE CVE CVE-2022-50404 | known affected: 344 known not affected: 304 recommended: 206 | 2026-07-26T16:49:32+00:00 | Vulnerability · Source |
| CVE-2022-50437 | suse_vex | SUSE CVE CVE-2022-50437 | known affected: 344 known not affected: 267 recommended: 273 | 2026-07-26T16:49:30+00:00 | Vulnerability · Source |
| CVE-2022-50448 | suse_vex | SUSE CVE CVE-2022-50448 | known not affected: 416 | 2026-07-26T16:49:29+00:00 | Vulnerability · Source |
| CVE-2022-50518 | suse_vex | SUSE CVE CVE-2022-50518 | known not affected: 416 | 2026-07-26T16:49:22+00:00 | Vulnerability · Source |
| CVE-2022-50537 | suse_vex | SUSE CVE CVE-2022-50537 | known affected: 391 known not affected: 237 recommended: 219 | 2026-07-26T16:49:21+00:00 | Vulnerability · Source |
| CVE-2022-50638 | suse_vex | SUSE CVE CVE-2022-50638 | known affected: 470 known not affected: 188 recommended: 282 | 2026-07-26T16:49:17+00:00 | Vulnerability · Source |
| CVE-2022-50718 | suse_vex | SUSE CVE CVE-2022-50718 | known affected: 354 known not affected: 341 recommended: 245 | 2026-07-26T16:49:15+00:00 | Vulnerability · Source |
| CVE-2022-50769 | suse_vex | SUSE CVE CVE-2022-50769 | known affected: 354 known not affected: 336 recommended: 196 | 2026-07-26T16:49:13+00:00 | Vulnerability · Source |
| CVE-2023-3326 | suse_vex | SUSE CVE CVE-2023-3326 | known not affected: 1172 | 2026-07-26T16:49:06+00:00 | Vulnerability · Source |
| CVE-2023-4156 | suse_vex | SUSE CVE CVE-2023-4156 | known affected: 184 recommended: 251 | 2026-07-26T16:49:00+00:00 | Vulnerability · Source |
| CVE-2023-5676 | suse_vex | SUSE CVE CVE-2023-5676 | known affected: 394 recommended: 256 | 2026-07-26T16:48:58+00:00 | Vulnerability · Source |
| CVE-2023-23518 | suse_vex | SUSE CVE CVE-2023-23518 | known affected: 1 recommended: 859 | 2026-07-26T16:48:49+00:00 | Vulnerability · Source |
| CVE-2023-25362 | suse_vex | SUSE CVE CVE-2023-25362 | known not affected: 122 recommended: 851 | 2026-07-26T16:48:47+00:00 | Vulnerability · Source |
| CVE-2023-28176 | suse_vex | SUSE CVE CVE-2023-28176 | known affected: 1 recommended: 304 | 2026-07-26T16:48:43+00:00 | Vulnerability · Source |
| CVE-2023-29451 | suse_vex | SUSE CVE CVE-2023-29451 | known not affected: 21 | 2026-07-26T16:48:39+00:00 | Vulnerability · Source |
| CVE-2023-29491 | suse_vex | SUSE CVE CVE-2023-29491 | known affected: 696 recommended: 533 | 2026-07-26T16:48:38+00:00 | Vulnerability · Source |
| CVE-2023-34410 | suse_vex | SUSE CVE CVE-2023-34410 | known affected: 442 known not affected: 138 recommended: 2758 | 2026-07-26T16:48:30+00:00 | Vulnerability · Source |
| CVE-2023-44431 | suse_vex | SUSE CVE CVE-2023-44431 | known not affected: 196 recommended: 5 | 2026-07-26T16:48:25+00:00 | Vulnerability · Source |
| CVE-2023-44466 | suse_vex | SUSE CVE CVE-2023-44466 | known not affected: 337 recommended: 47 | 2026-07-26T16:48:23+00:00 | Vulnerability · Source |
| CVE-2023-45288 | suse_vex | SUSE CVE CVE-2023-45288 | known affected: 427 known not affected: 273 recommended: 1137 | 2026-07-26T16:48:22+00:00 | Vulnerability · Source |
| CVE-2023-45872 | suse_vex | SUSE CVE CVE-2023-45872 | known not affected: 165 | 2026-07-26T16:48:19+00:00 | Vulnerability · Source |
| CVE-2023-46842 | suse_vex | SUSE CVE CVE-2023-46842 | known affected: 407 recommended: 296 | 2026-07-26T16:48:13+00:00 | Vulnerability · Source |
| CVE-2023-52071 | suse_vex | SUSE CVE CVE-2023-52071 | known not affected: 200 | 2026-07-26T16:48:10+00:00 | Vulnerability · Source |
| CVE-2023-52463 | suse_vex | SUSE CVE CVE-2023-52463 | known affected: 249 known not affected: 138 recommended: 912 | 2026-07-26T16:48:08+00:00 | Vulnerability · Source |
| CVE-2023-52466 | suse_vex | SUSE CVE CVE-2023-52466 | known not affected: 312 | 2026-07-26T16:48:06+00:00 | Vulnerability · Source |
| CVE-2023-52648 | suse_vex | SUSE CVE CVE-2023-52648 | known affected: 471 known not affected: 321 recommended: 233 | 2026-07-26T16:47:55+00:00 | Vulnerability · Source |
| CVE-2023-52703 | suse_vex | SUSE CVE CVE-2023-52703 | known affected: 341 known not affected: 62 recommended: 542 | 2026-07-26T16:47:53+00:00 | Vulnerability · Source |
| CVE-2023-52775 | suse_vex | SUSE CVE CVE-2023-52775 | known affected: 330 known not affected: 138 recommended: 676 | 2026-07-26T16:47:50+00:00 | Vulnerability · Source |
| CVE-2023-52789 | suse_vex | SUSE CVE CVE-2023-52789 | known affected: 275 known not affected: 125 recommended: 810 | 2026-07-26T16:47:48+00:00 | Vulnerability · Source |