VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-4207 | suse_vex | SUSE CVE CVE-2023-4207 | recommended: 91 | 2026-10-16T13:57:12+00:00 | Vulnerability · Source |
| CVE-2023-4273 | suse_vex | SUSE CVE CVE-2023-4273 | known affected: 194 known not affected: 195 recommended: 1382 | 2026-10-16T13:57:10+00:00 | Vulnerability · Source |
| CVE-2023-4504 | suse_vex | SUSE CVE CVE-2023-4504 | known affected: 336 recommended: 640 | 2026-10-16T13:57:07+00:00 | Vulnerability · Source |
| CVE-2023-4527 | suse_vex | SUSE CVE CVE-2023-4527 | known affected: 0 known not affected: 687 recommended: 852 | 2026-10-16T13:57:05+00:00 | Vulnerability · Source |
| CVE-2023-4535 | suse_vex | SUSE CVE CVE-2023-4535 | known affected: 0 known not affected: 62 recommended: 11 | 2026-10-16T13:57:03+00:00 | Vulnerability · Source |
| CVE-2023-4574 | suse_vex | SUSE CVE CVE-2023-4574 | known affected: 57 recommended: 293 | 2026-10-16T13:57:01+00:00 | Vulnerability · Source |
| CVE-2023-4576 | suse_vex | SUSE CVE CVE-2023-4576 | known affected: 57 recommended: 283 | 2026-10-16T13:56:59+00:00 | Vulnerability · Source |
| CVE-2023-4577 | suse_vex | SUSE CVE CVE-2023-4577 | known affected: 57 recommended: 290 | 2026-10-16T13:56:56+00:00 | Vulnerability · Source |
| CVE-2023-4578 | suse_vex | SUSE CVE CVE-2023-4578 | known affected: 57 recommended: 290 | 2026-10-16T13:56:54+00:00 | Vulnerability · Source |
| CVE-2023-4581 | suse_vex | SUSE CVE CVE-2023-4581 | known affected: 57 recommended: 293 | 2026-10-16T13:56:52+00:00 | Vulnerability · Source |
| CVE-2023-4583 | suse_vex | SUSE CVE CVE-2023-4583 | known affected: 57 recommended: 290 | 2026-10-16T13:56:50+00:00 | Vulnerability · Source |
| CVE-2023-4584 | suse_vex | SUSE CVE CVE-2023-4584 | known affected: 57 recommended: 293 | 2026-10-16T13:56:48+00:00 | Vulnerability · Source |
| CVE-2023-4610 | suse_vex | SUSE CVE CVE-2023-4610 | known affected: 0 known not affected: 390 | 2026-10-16T13:56:46+00:00 | Vulnerability · Source |
| CVE-2023-4611 | suse_vex | SUSE CVE CVE-2023-4611 | known affected: 0 known not affected: 404 recommended: 233 | 2026-10-16T13:56:44+00:00 | Vulnerability · Source |
| CVE-2023-4623 | suse_vex | SUSE CVE CVE-2023-4623 | known affected: 233 recommended: 1668 | 2026-10-16T13:56:41+00:00 | Vulnerability · Source |
| CVE-2023-4693 | suse_vex | SUSE CVE CVE-2023-4693 | known affected: 289 recommended: 686 | 2026-10-16T13:56:39+00:00 | Vulnerability · Source |
| CVE-2023-4732 | suse_vex | SUSE CVE CVE-2023-4732 | known affected: 0 known not affected: 404 recommended: 20 | 2026-10-16T13:56:36+00:00 | Vulnerability · Source |
| CVE-2023-4733 | suse_vex | SUSE CVE CVE-2023-4733 | known affected: 278 recommended: 438 | 2026-10-16T13:56:35+00:00 | Vulnerability · Source |
| CVE-2023-4750 | suse_vex | SUSE CVE CVE-2023-4750 | known affected: 424 recommended: 347 | 2026-10-16T13:56:33+00:00 | Vulnerability · Source |
| CVE-2023-4785 | suse_vex | SUSE CVE CVE-2023-4785 | known affected: 0 known not affected: 8 recommended: 106 | 2026-10-16T13:56:30+00:00 | Vulnerability · Source |
| CVE-2023-4807 | suse_vex | SUSE CVE CVE-2023-4807 | known affected: 0 known not affected: 764 recommended: 127 | 2026-10-16T13:56:26+00:00 | Vulnerability · Source |
| CVE-2023-4813 | suse_vex | SUSE CVE CVE-2023-4813 | known affected: 405 known not affected: 13 recommended: 1595 | 2026-10-16T13:56:25+00:00 | Vulnerability · Source |
| CVE-2023-4881 | suse_vex | SUSE CVE CVE-2023-4881 | known affected: 199 known not affected: 31 recommended: 1390 | 2026-10-16T13:56:21+00:00 | Vulnerability · Source |
| CVE-2023-4911 | suse_vex | SUSE CVE CVE-2023-4911 | known affected: 0 known not affected: 683 recommended: 852 | 2026-10-16T13:56:19+00:00 | Vulnerability · Source |
| CVE-2023-4921 | suse_vex | SUSE CVE CVE-2023-4921 | known affected: 199 known not affected: 6 recommended: 1574 | 2026-10-16T13:56:17+00:00 | Vulnerability · Source |
| CVE-2023-5156 | suse_vex | SUSE CVE CVE-2023-5156 | known affected: 0 known not affected: 663 recommended: 196 | 2026-10-16T13:56:15+00:00 | Vulnerability · Source |
| CVE-2023-5158 | suse_vex | SUSE CVE CVE-2023-5158 | known affected: 230 known not affected: 298 recommended: 923 | 2026-10-16T13:56:13+00:00 | Vulnerability · Source |
| CVE-2023-5170 | suse_vex | SUSE CVE CVE-2023-5170 | known affected: 51 recommended: 9 | 2026-10-16T13:56:12+00:00 | Vulnerability · Source |
| CVE-2023-5174 | suse_vex | SUSE CVE CVE-2023-5174 | known affected: 51 recommended: 276 | 2026-10-16T13:56:10+00:00 | Vulnerability · Source |
| CVE-2023-5178 | suse_vex | SUSE CVE CVE-2023-5178 | known affected: 215 known not affected: 356 recommended: 1092 | 2026-10-16T13:56:08+00:00 | Vulnerability · Source |
| CVE-2023-5197 | suse_vex | SUSE CVE CVE-2023-5197 | known affected: 264 known not affected: 342 recommended: 710 | 2026-10-16T13:56:07+00:00 | Vulnerability · Source |
| CVE-2023-5217 | suse_vex | SUSE CVE CVE-2023-5217 | known affected: 477 known not affected: 1 recommended: 524 | 2026-10-16T13:56:05+00:00 | Vulnerability · Source |
| CVE-2023-5344 | suse_vex | SUSE CVE CVE-2023-5344 | known affected: 288 known not affected: 1 recommended: 421 | 2026-10-16T13:56:03+00:00 | Vulnerability · Source |
| CVE-2023-5363 | suse_vex | SUSE CVE CVE-2023-5363 | known affected: 0 known not affected: 702 recommended: 157 | 2026-10-16T13:56:01+00:00 | Vulnerability · Source |
| CVE-2023-5367 | suse_vex | SUSE CVE CVE-2023-5367 | known affected: 423 known not affected: 24 recommended: 231 | 2026-10-16T13:55:59+00:00 | Vulnerability · Source |
| CVE-2023-5371 | suse_vex | SUSE CVE CVE-2023-5371 | known affected: 138 known not affected: 82 recommended: 204 | 2026-10-16T13:55:58+00:00 | Vulnerability · Source |
| CVE-2023-5380 | suse_vex | SUSE CVE CVE-2023-5380 | known affected: 409 known not affected: 8 recommended: 208 | 2026-10-16T13:55:56+00:00 | Vulnerability · Source |
| CVE-2023-5441 | suse_vex | SUSE CVE CVE-2023-5441 | known affected: 289 recommended: 421 | 2026-10-16T13:55:54+00:00 | Vulnerability · Source |
| CVE-2023-5528 | suse_vex | SUSE CVE CVE-2023-5528 | known affected: 0 known not affected: 341 recommended: 5 | 2026-10-16T13:55:53+00:00 | Vulnerability · Source |
| CVE-2023-5535 | suse_vex | SUSE CVE CVE-2023-5535 | known affected: 289 recommended: 421 | 2026-10-16T13:55:51+00:00 | Vulnerability · Source |
| CVE-2023-5568 | suse_vex | SUSE CVE CVE-2023-5568 | known affected: 0 known not affected: 2130 recommended: 293 | 2026-10-16T13:55:49+00:00 | Vulnerability · Source |
| CVE-2023-5678 | suse_vex | SUSE CVE CVE-2023-5678 | known affected: 352 known not affected: 140 recommended: 887 | 2026-10-16T13:55:44+00:00 | Vulnerability · Source |
| CVE-2023-5679 | suse_vex | SUSE CVE CVE-2023-5679 | known affected: 249 known not affected: 453 recommended: 283 | 2026-10-16T13:55:41+00:00 | Vulnerability · Source |
| CVE-2023-5717 | suse_vex | SUSE CVE CVE-2023-5717 | known affected: 284 known not affected: 6 recommended: 1451 | 2026-10-16T13:55:39+00:00 | Vulnerability · Source |
| CVE-2023-5724 | suse_vex | SUSE CVE CVE-2023-5724 | known affected: 52 recommended: 288 | 2026-10-16T13:55:38+00:00 | Vulnerability · Source |
| CVE-2023-5725 | suse_vex | SUSE CVE CVE-2023-5725 | known affected: 52 recommended: 288 | 2026-10-16T13:55:36+00:00 | Vulnerability · Source |
| CVE-2023-5727 | suse_vex | SUSE CVE CVE-2023-5727 | known affected: 52 recommended: 279 | 2026-10-16T13:55:34+00:00 | Vulnerability · Source |
| CVE-2023-5728 | suse_vex | SUSE CVE CVE-2023-5728 | known affected: 52 recommended: 288 | 2026-10-16T13:55:32+00:00 | Vulnerability · Source |
| CVE-2023-5730 | suse_vex | SUSE CVE CVE-2023-5730 | known affected: 52 recommended: 288 | 2026-10-16T13:55:30+00:00 | Vulnerability · Source |
| CVE-2023-5841 | suse_vex | SUSE CVE CVE-2023-5841 | known affected: 0 known not affected: 202 recommended: 67 | 2026-10-16T13:55:26+00:00 | Vulnerability · Source |