VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
76485 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-48946 | suse_vex | SUSE CVE CVE-2022-48946 | known affected: 528 known not affected: 107 recommended: 434 | 2026-10-03T01:03:57+00:00 | Vulnerability · Source |
| CVE-2022-49002 | suse_vex | SUSE CVE CVE-2022-49002 | known affected: 543 known not affected: 64 recommended: 434 | 2026-10-03T01:03:54+00:00 | Vulnerability · Source |
| CVE-2022-49027 | suse_vex | SUSE CVE CVE-2022-49027 | known affected: 541 known not affected: 69 recommended: 434 | 2026-10-03T01:03:51+00:00 | Vulnerability · Source |
| CVE-2022-49118 | suse_vex | SUSE CVE CVE-2022-49118 | known affected: 449 known not affected: 269 recommended: 249 | 2026-10-03T01:03:47+00:00 | Vulnerability · Source |
| CVE-2022-49212 | suse_vex | SUSE CVE CVE-2022-49212 | known affected: 469 known not affected: 218 recommended: 316 | 2026-10-03T01:03:44+00:00 | Vulnerability · Source |
| CVE-2022-49220 | suse_vex | SUSE CVE CVE-2022-49220 | known affected: 630 known not affected: 180 recommended: 55 | 2026-10-03T01:03:42+00:00 | Vulnerability · Source |
| CVE-2022-49272 | suse_vex | SUSE CVE CVE-2022-49272 | known affected: 227 known not affected: 84 recommended: 342 | 2026-10-03T01:03:39+00:00 | Vulnerability · Source |
| CVE-2022-49308 | suse_vex | SUSE CVE CVE-2022-49308 | known affected: 501 known not affected: 175 recommended: 263 | 2026-10-03T01:03:36+00:00 | Vulnerability · Source |
| CVE-2022-49347 | suse_vex | SUSE CVE CVE-2022-49347 | known affected: 481 known not affected: 196 recommended: 375 | 2026-10-03T01:03:34+00:00 | Vulnerability · Source |
| CVE-2022-49526 | suse_vex | SUSE CVE CVE-2022-49526 | known affected: 422 known not affected: 227 recommended: 345 | 2026-10-03T01:03:30+00:00 | Vulnerability · Source |
| CVE-2022-49733 | suse_vex | SUSE CVE CVE-2022-49733 | known not affected: 311 recommended: 300 | 2026-10-03T01:03:25+00:00 | Vulnerability · Source |
| CVE-2022-49780 | suse_vex | SUSE CVE CVE-2022-49780 | known affected: 737 known not affected: 121 recommended: 37 | 2026-10-03T01:03:22+00:00 | Vulnerability · Source |
| CVE-2022-50166 | suse_vex | SUSE CVE CVE-2022-50166 | known affected: 701 known not affected: 183 recommended: 119 | 2026-10-03T01:03:17+00:00 | Vulnerability · Source |
| CVE-2022-50249 | suse_vex | SUSE CVE CVE-2022-50249 | known affected: 465 known not affected: 173 recommended: 325 | 2026-10-03T01:03:14+00:00 | Vulnerability · Source |
| CVE-2022-50330 | suse_vex | SUSE CVE CVE-2022-50330 | known affected: 437 known not affected: 201 recommended: 296 | 2026-10-03T01:03:11+00:00 | Vulnerability · Source |
| CVE-2022-50394 | suse_vex | SUSE CVE CVE-2022-50394 | known affected: 546 known not affected: 170 recommended: 243 | 2026-10-03T01:03:08+00:00 | Vulnerability · Source |
| CVE-2022-50432 | suse_vex | SUSE CVE CVE-2022-50432 | known affected: 492 known not affected: 176 recommended: 330 | 2026-10-03T01:03:05+00:00 | Vulnerability · Source |
| CVE-2022-50485 | suse_vex | SUSE CVE CVE-2022-50485 | known affected: 556 known not affected: 170 recommended: 282 | 2026-10-03T01:03:02+00:00 | Vulnerability · Source |
| CVE-2022-50532 | suse_vex | SUSE CVE CVE-2022-50532 | known affected: 501 known not affected: 178 recommended: 345 | 2026-10-03T01:02:59+00:00 | Vulnerability · Source |
| CVE-2022-50578 | suse_vex | SUSE CVE CVE-2022-50578 | known affected: 522 known not affected: 186 recommended: 268 | 2026-10-03T01:02:56+00:00 | Vulnerability · Source |
| CVE-2022-50700 | suse_vex | SUSE CVE CVE-2022-50700 | known affected: 485 known not affected: 238 recommended: 306 | 2026-10-03T01:02:53+00:00 | Vulnerability · Source |
| CVE-2022-50709 | suse_vex | SUSE CVE CVE-2022-50709 | known affected: 501 known not affected: 214 recommended: 223 | 2026-10-03T01:02:51+00:00 | Vulnerability · Source |
| CVE-2022-50715 | suse_vex | SUSE CVE CVE-2022-50715 | known affected: 354 known not affected: 374 recommended: 266 | 2026-10-03T01:02:48+00:00 | Vulnerability · Source |
| CVE-2023-1990 | suse_vex | SUSE CVE CVE-2023-1990 | known affected: 265 known not affected: 14 recommended: 1269 | 2026-10-03T01:02:43+00:00 | Vulnerability · Source |
| CVE-2023-2124 | suse_vex | SUSE CVE CVE-2023-2124 | known affected: 300 known not affected: 6 recommended: 1263 | 2026-10-03T01:02:40+00:00 | Vulnerability · Source |
| CVE-2023-4194 | suse_vex | SUSE CVE CVE-2023-4194 | known affected: 390 known not affected: 48 recommended: 1097 | 2026-10-03T01:02:36+00:00 | Vulnerability · Source |
| CVE-2023-23559 | suse_vex | SUSE CVE CVE-2023-23559 | known affected: 178 known not affected: 63 recommended: 1459 | 2026-10-03T01:02:31+00:00 | Vulnerability · Source |
| CVE-2023-45236 | suse_vex | SUSE CVE CVE-2023-45236 | known affected: 177 recommended: 106 | 2026-10-03T01:02:23+00:00 | Vulnerability · Source |
| CVE-2023-45288 | suse_vex | SUSE CVE CVE-2023-45288 | known affected: 430 known not affected: 293 recommended: 1100 | 2026-10-03T01:02:21+00:00 | Vulnerability · Source |
| CVE-2023-52434 | suse_vex | SUSE CVE CVE-2023-52434 | known affected: 705 known not affected: 42 recommended: 400 | 2026-10-03T01:02:16+00:00 | Vulnerability · Source |
| CVE-2023-52443 | suse_vex | SUSE CVE CVE-2023-52443 | known affected: 343 known not affected: 95 recommended: 901 | 2026-10-03T01:02:14+00:00 | Vulnerability · Source |
| CVE-2023-52451 | suse_vex | SUSE CVE CVE-2023-52451 | known affected: 371 known not affected: 59 recommended: 949 | 2026-10-03T01:02:11+00:00 | Vulnerability · Source |
| CVE-2023-52470 | suse_vex | SUSE CVE CVE-2023-52470 | known affected: 375 known not affected: 59 recommended: 957 | 2026-10-03T01:02:09+00:00 | Vulnerability · Source |
| CVE-2023-52574 | suse_vex | SUSE CVE CVE-2023-52574 | known affected: 389 known not affected: 59 recommended: 972 | 2026-10-03T01:02:05+00:00 | Vulnerability · Source |
| CVE-2023-52747 | suse_vex | SUSE CVE CVE-2023-52747 | known affected: 449 known not affected: 67 recommended: 522 | 2026-10-03T01:02:01+00:00 | Vulnerability · Source |
| CVE-2023-52796 | suse_vex | SUSE CVE CVE-2023-52796 | known affected: 550 known not affected: 28 recommended: 799 | 2026-10-03T01:01:58+00:00 | Vulnerability · Source |
| CVE-2023-52855 | suse_vex | SUSE CVE CVE-2023-52855 | known affected: 471 known not affected: 28 recommended: 889 | 2026-10-03T01:01:55+00:00 | Vulnerability · Source |
| CVE-2023-52919 | suse_vex | SUSE CVE CVE-2023-52919 | known affected: 384 known not affected: 140 recommended: 938 | 2026-10-03T01:01:52+00:00 | Vulnerability · Source |
| CVE-2023-52922 | suse_vex | SUSE CVE CVE-2023-52922 | known affected: 514 known not affected: 26 recommended: 789 | 2026-10-03T01:01:49+00:00 | Vulnerability · Source |
| CVE-2023-52988 | suse_vex | SUSE CVE CVE-2023-52988 | known affected: 534 known not affected: 124 recommended: 288 | 2026-10-03T01:01:47+00:00 | Vulnerability · Source |
| CVE-2023-53031 | suse_vex | SUSE CVE CVE-2023-53031 | known affected: 592 known not affected: 122 recommended: 150 | 2026-10-03T01:01:44+00:00 | Vulnerability · Source |
| CVE-2023-53183 | suse_vex | SUSE CVE CVE-2023-53183 | known affected: 522 known not affected: 207 recommended: 333 | 2026-10-03T01:01:41+00:00 | Vulnerability · Source |
| CVE-2023-53191 | suse_vex | SUSE CVE CVE-2023-53191 | known affected: 617 known not affected: 242 recommended: 23 | 2026-10-03T01:01:39+00:00 | Vulnerability · Source |
| CVE-2023-53285 | suse_vex | SUSE CVE CVE-2023-53285 | known affected: 382 known not affected: 180 recommended: 43 | 2026-10-03T01:01:36+00:00 | Vulnerability · Source |
| CVE-2023-53332 | suse_vex | SUSE CVE CVE-2023-53332 | known affected: 592 known not affected: 175 recommended: 115 | 2026-10-03T01:01:34+00:00 | Vulnerability · Source |
| CVE-2023-53357 | suse_vex | SUSE CVE CVE-2023-53357 | known affected: 626 known not affected: 9 recommended: 425 | 2026-10-03T01:01:31+00:00 | Vulnerability · Source |
| CVE-2023-53397 | suse_vex | SUSE CVE CVE-2023-53397 | known affected: 651 known not affected: 93 recommended: 347 | 2026-10-03T01:01:28+00:00 | Vulnerability · Source |
| CVE-2023-53464 | suse_vex | SUSE CVE CVE-2023-53464 | known affected: 344 known not affected: 294 recommended: 325 | 2026-10-03T01:01:25+00:00 | Vulnerability · Source |
| CVE-2023-53683 | suse_vex | SUSE CVE CVE-2023-53683 | known affected: 354 known not affected: 337 recommended: 219 | 2026-10-03T01:01:19+00:00 | Vulnerability · Source |
| CVE-2023-53782 | suse_vex | SUSE CVE CVE-2023-53782 | known affected: 776 known not affected: 70 recommended: 212 | 2026-10-03T01:01:16+00:00 | Vulnerability · Source |