VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283530 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2021-47023 | suse_vex | SUSE CVE CVE-2021-47023 | known not affected: 292 | 2026-07-25T17:36:28+00:00 | Vulnerability · Source |
| CVE-2021-47025 | suse_vex | SUSE CVE CVE-2021-47025 | known not affected: 292 | 2026-07-25T17:36:27+00:00 | Vulnerability · Source |
| CVE-2021-47027 | suse_vex | SUSE CVE CVE-2021-47027 | known not affected: 292 | 2026-07-25T17:36:26+00:00 | Vulnerability · Source |
| CVE-2021-47028 | suse_vex | SUSE CVE CVE-2021-47028 | known not affected: 292 | 2026-07-25T17:36:24+00:00 | Vulnerability · Source |
| CVE-2021-47033 | suse_vex | SUSE CVE CVE-2021-47033 | known not affected: 292 | 2026-07-25T17:36:23+00:00 | Vulnerability · Source |
| CVE-2021-47034 | suse_vex | SUSE CVE CVE-2021-47034 | known affected: 388 known not affected: 212 recommended: 207 | 2026-07-25T17:36:22+00:00 | Vulnerability · Source |
| CVE-2021-47037 | suse_vex | SUSE CVE CVE-2021-47037 | known not affected: 292 | 2026-07-25T17:36:20+00:00 | Vulnerability · Source |
| CVE-2021-47039 | suse_vex | SUSE CVE CVE-2021-47039 | known not affected: 292 | 2026-07-25T17:36:19+00:00 | Vulnerability · Source |
| CVE-2021-47040 | suse_vex | SUSE CVE CVE-2021-47040 | known not affected: 233 | 2026-07-25T17:36:18+00:00 | Vulnerability · Source |
| CVE-2021-47042 | suse_vex | SUSE CVE CVE-2021-47042 | known not affected: 292 | 2026-07-25T17:36:16+00:00 | Vulnerability · Source |
| CVE-2021-47048 | suse_vex | SUSE CVE CVE-2021-47048 | known not affected: 275 | 2026-07-25T17:36:15+00:00 | Vulnerability · Source |
| CVE-2021-47049 | suse_vex | SUSE CVE CVE-2021-47049 | known affected: 388 known not affected: 212 recommended: 221 | 2026-07-25T17:36:13+00:00 | Vulnerability · Source |
| CVE-2021-47050 | suse_vex | SUSE CVE CVE-2021-47050 | known not affected: 292 | 2026-07-25T17:36:12+00:00 | Vulnerability · Source |
| CVE-2021-47051 | suse_vex | SUSE CVE CVE-2021-47051 | known affected: 388 known not affected: 233 recommended: 137 | 2026-07-25T17:36:11+00:00 | Vulnerability · Source |
| CVE-2021-47056 | suse_vex | SUSE CVE CVE-2021-47056 | known affected: 439 known not affected: 242 recommended: 221 | 2026-07-25T17:36:09+00:00 | Vulnerability · Source |
| CVE-2021-47057 | suse_vex | SUSE CVE CVE-2021-47057 | known not affected: 292 | 2026-07-25T17:36:08+00:00 | Vulnerability · Source |
| CVE-2021-47058 | suse_vex | SUSE CVE CVE-2021-47058 | known affected: 388 known not affected: 233 recommended: 137 | 2026-07-25T17:36:07+00:00 | Vulnerability · Source |
| CVE-2021-47061 | suse_vex | SUSE CVE CVE-2021-47061 | known affected: 388 known not affected: 273 recommended: 258 | 2026-07-25T17:36:05+00:00 | Vulnerability · Source |
| CVE-2021-47063 | suse_vex | SUSE CVE CVE-2021-47063 | known affected: 390 known not affected: 291 recommended: 207 | 2026-07-25T17:36:04+00:00 | Vulnerability · Source |
| CVE-2021-47065 | suse_vex | SUSE CVE CVE-2021-47065 | known affected: 388 known not affected: 233 recommended: 137 | 2026-07-25T17:36:03+00:00 | Vulnerability · Source |
| CVE-2021-47066 | suse_vex | SUSE CVE CVE-2021-47066 | known not affected: 292 | 2026-07-25T17:36:01+00:00 | Vulnerability · Source |
| CVE-2021-47069 | suse_vex | SUSE CVE CVE-2021-47069 | known affected: 388 known not affected: 233 recommended: 186 | 2026-07-25T17:36:00+00:00 | Vulnerability · Source |
| CVE-2021-47070 | suse_vex | SUSE CVE CVE-2021-47070 | known affected: 388 known not affected: 212 recommended: 207 | 2026-07-25T17:35:59+00:00 | Vulnerability · Source |
| CVE-2021-47076 | suse_vex | SUSE CVE CVE-2021-47076 | known affected: 455 known not affected: 229 recommended: 256 | 2026-07-25T17:35:57+00:00 | Vulnerability · Source |
| CVE-2021-47079 | suse_vex | SUSE CVE CVE-2021-47079 | known not affected: 292 | 2026-07-25T17:35:56+00:00 | Vulnerability · Source |
| CVE-2021-47086 | suse_vex | SUSE CVE CVE-2021-47086 | known affected: 330 known not affected: 287 recommended: 298 | 2026-07-25T17:35:54+00:00 | Vulnerability · Source |
| CVE-2021-47087 | suse_vex | SUSE CVE CVE-2021-47087 | known affected: 254 known not affected: 164 recommended: 562 | 2026-07-25T17:35:53+00:00 | Vulnerability · Source |
| CVE-2021-47093 | suse_vex | SUSE CVE CVE-2021-47093 | known affected: 260 known not affected: 200 recommended: 471 | 2026-07-25T17:35:51+00:00 | Vulnerability · Source |
| CVE-2021-47096 | suse_vex | SUSE CVE CVE-2021-47096 | known affected: 260 known not affected: 200 recommended: 471 | 2026-07-25T17:35:50+00:00 | Vulnerability · Source |
| CVE-2021-47101 | suse_vex | SUSE CVE CVE-2021-47101 | known affected: 342 known not affected: 107 recommended: 652 | 2026-07-25T17:35:48+00:00 | Vulnerability · Source |
| CVE-2021-47104 | suse_vex | SUSE CVE CVE-2021-47104 | known affected: 260 known not affected: 112 recommended: 712 | 2026-07-25T17:35:47+00:00 | Vulnerability · Source |
| CVE-2021-47107 | suse_vex | SUSE CVE CVE-2021-47107 | known affected: 260 known not affected: 200 recommended: 491 | 2026-07-25T17:35:45+00:00 | Vulnerability · Source |
| CVE-2021-47110 | suse_vex | SUSE CVE CVE-2021-47110 | known affected: 479 known not affected: 198 recommended: 236 | 2026-07-25T17:35:44+00:00 | Vulnerability · Source |
| CVE-2021-47111 | suse_vex | SUSE CVE CVE-2021-47111 | known not affected: 292 | 2026-07-25T17:35:43+00:00 | Vulnerability · Source |
| CVE-2021-47112 | suse_vex | SUSE CVE CVE-2021-47112 | known affected: 483 known not affected: 198 recommended: 221 | 2026-07-25T17:35:41+00:00 | Vulnerability · Source |
| CVE-2021-47116 | suse_vex | SUSE CVE CVE-2021-47116 | known not affected: 292 | 2026-07-25T17:35:40+00:00 | Vulnerability · Source |
| CVE-2021-47120 | suse_vex | SUSE CVE CVE-2021-47120 | known affected: 388 known not affected: 233 recommended: 137 | 2026-07-25T17:35:39+00:00 | Vulnerability · Source |
| CVE-2021-47122 | suse_vex | SUSE CVE CVE-2021-47122 | known affected: 44 known not affected: 329 | 2026-07-25T17:35:37+00:00 | Vulnerability · Source |
| CVE-2021-47123 | suse_vex | SUSE CVE CVE-2021-47123 | known not affected: 292 | 2026-07-25T17:35:36+00:00 | Vulnerability · Source |
| CVE-2021-47125 | suse_vex | SUSE CVE CVE-2021-47125 | known not affected: 292 | 2026-07-25T17:35:35+00:00 | Vulnerability · Source |
| CVE-2021-47127 | suse_vex | SUSE CVE CVE-2021-47127 | known not affected: 292 | 2026-07-25T17:35:34+00:00 | Vulnerability · Source |
| CVE-2021-47133 | suse_vex | SUSE CVE CVE-2021-47133 | known not affected: 292 | 2026-07-25T17:35:32+00:00 | Vulnerability · Source |
| CVE-2021-47137 | suse_vex | SUSE CVE CVE-2021-47137 | known affected: 388 known not affected: 256 recommended: 91 | 2026-07-25T17:35:31+00:00 | Vulnerability · Source |
| CVE-2021-47145 | suse_vex | SUSE CVE CVE-2021-47145 | known affected: 530 known not affected: 208 recommended: 84 | 2026-07-25T17:35:29+00:00 | Vulnerability · Source |
| CVE-2021-47152 | suse_vex | SUSE CVE CVE-2021-47152 | known not affected: 292 | 2026-07-25T17:35:28+00:00 | Vulnerability · Source |
| CVE-2021-47153 | suse_vex | SUSE CVE CVE-2021-47153 | known affected: 473 known not affected: 204 recommended: 255 | 2026-07-25T17:35:27+00:00 | Vulnerability · Source |
| CVE-2021-47166 | suse_vex | SUSE CVE CVE-2021-47166 | known affected: 477 known not affected: 204 recommended: 221 | 2026-07-25T17:35:25+00:00 | Vulnerability · Source |
| CVE-2021-47173 | suse_vex | SUSE CVE CVE-2021-47173 | known affected: 483 known not affected: 201 recommended: 221 | 2026-07-25T17:35:24+00:00 | Vulnerability · Source |
| CVE-2021-47177 | suse_vex | SUSE CVE CVE-2021-47177 | known affected: 453 known not affected: 147 recommended: 207 | 2026-07-25T17:35:22+00:00 | Vulnerability · Source |
| CVE-2021-47178 | suse_vex | SUSE CVE CVE-2021-47178 | known not affected: 292 recommended: 20 | 2026-07-25T17:35:21+00:00 | Vulnerability · Source |