VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
289981 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2021-46983 | suse_vex | SUSE CVE CVE-2021-46983 | known affected: 388 known not affected: 256 recommended: 111 | 2026-08-06T02:09:09+00:00 | Vulnerability · Source |
| CVE-2021-46989 | suse_vex | SUSE CVE CVE-2021-46989 | known affected: 404 known not affected: 301 recommended: 152 | 2026-08-06T02:09:06+00:00 | Vulnerability · Source |
| CVE-2021-46992 | suse_vex | SUSE CVE CVE-2021-46992 | known affected: 477 known not affected: 213 recommended: 201 | 2026-08-06T02:09:05+00:00 | Vulnerability · Source |
| CVE-2021-46998 | suse_vex | SUSE CVE CVE-2021-46998 | known affected: 388 known not affected: 212 recommended: 207 | 2026-08-06T02:09:02+00:00 | Vulnerability · Source |
| CVE-2021-47001 | suse_vex | SUSE CVE CVE-2021-47001 | known affected: 411 known not affected: 296 recommended: 91 | 2026-08-06T02:09:00+00:00 | Vulnerability · Source |
| CVE-2021-47012 | suse_vex | SUSE CVE CVE-2021-47012 | known affected: 396 known not affected: 309 recommended: 152 | 2026-08-06T02:08:58+00:00 | Vulnerability · Source |
| CVE-2021-47013 | suse_vex | SUSE CVE CVE-2021-47013 | known affected: 455 known not affected: 210 recommended: 250 | 2026-08-06T02:08:56+00:00 | Vulnerability · Source |
| CVE-2021-47017 | suse_vex | SUSE CVE CVE-2021-47017 | known affected: 388 known not affected: 256 recommended: 91 | 2026-08-06T02:08:53+00:00 | Vulnerability · Source |
| CVE-2021-47055 | suse_vex | SUSE CVE CVE-2021-47055 | known affected: 388 known not affected: 212 recommended: 227 | 2026-08-06T02:08:45+00:00 | Vulnerability · Source |
| CVE-2021-47078 | suse_vex | SUSE CVE CVE-2021-47078 | known affected: 455 known not affected: 210 recommended: 236 | 2026-08-06T02:08:37+00:00 | Vulnerability · Source |
| CVE-2021-47106 | suse_vex | SUSE CVE CVE-2021-47106 | known affected: 340 known not affected: 287 recommended: 288 | 2026-08-06T02:08:22+00:00 | Vulnerability · Source |
| CVE-2021-47130 | suse_vex | SUSE CVE CVE-2021-47130 | known affected: 388 known not affected: 256 recommended: 91 | 2026-08-06T02:08:11+00:00 | Vulnerability · Source |
| CVE-2021-47131 | suse_vex | SUSE CVE CVE-2021-47131 | known affected: 421 known not affected: 286 recommended: 205 | 2026-08-06T02:08:10+00:00 | Vulnerability · Source |
| CVE-2021-47137 | suse_vex | SUSE CVE CVE-2021-47137 | known affected: 388 known not affected: 256 recommended: 91 | 2026-08-06T02:08:06+00:00 | Vulnerability · Source |
| CVE-2021-47168 | suse_vex | SUSE CVE CVE-2021-47168 | known affected: 483 known not affected: 198 recommended: 221 | 2026-08-06T02:07:57+00:00 | Vulnerability · Source |
| CVE-2021-47191 | suse_vex | SUSE CVE CVE-2021-47191 | known affected: 397 known not affected: 75 recommended: 547 | 2026-08-06T02:07:44+00:00 | Vulnerability · Source |
| CVE-2021-47194 | suse_vex | SUSE CVE CVE-2021-47194 | known affected: 330 known not affected: 98 recommended: 681 | 2026-08-06T02:07:42+00:00 | Vulnerability · Source |
| CVE-2021-47291 | suse_vex | SUSE CVE CVE-2021-47291 | known affected: 391 known not affected: 274 recommended: 198 | 2026-08-06T02:07:11+00:00 | Vulnerability · Source |
| CVE-2021-47397 | suse_vex | SUSE CVE CVE-2021-47397 | known affected: 365 known not affected: 100 recommended: 522 | 2026-08-06T02:06:35+00:00 | Vulnerability · Source |
| CVE-2021-47433 | suse_vex | SUSE CVE CVE-2021-47433 | known affected: 338 known not affected: 145 recommended: 452 | 2026-08-06T02:06:20+00:00 | Vulnerability · Source |
| CVE-2021-47438 | suse_vex | SUSE CVE CVE-2021-47438 | known affected: 407 known not affected: 60 recommended: 537 | 2026-08-06T02:06:18+00:00 | Vulnerability · Source |
| CVE-2021-47450 | suse_vex | SUSE CVE CVE-2021-47450 | known affected: 275 known not affected: 217 recommended: 452 | 2026-08-06T02:06:12+00:00 | Vulnerability · Source |
| CVE-2021-47458 | suse_vex | SUSE CVE CVE-2021-47458 | known affected: 361 known not affected: 68 recommended: 613 | 2026-08-06T02:06:09+00:00 | Vulnerability · Source |
| CVE-2021-47493 | suse_vex | SUSE CVE CVE-2021-47493 | known affected: 269 known not affected: 181 recommended: 543 | 2026-08-06T02:05:55+00:00 | Vulnerability · Source |
| CVE-2021-47494 | suse_vex | SUSE CVE CVE-2021-47494 | known affected: 269 known not affected: 181 recommended: 543 | 2026-08-06T02:05:54+00:00 | Vulnerability · Source |
| CVE-2021-47536 | suse_vex | SUSE CVE CVE-2021-47536 | known affected: 292 known not affected: 158 recommended: 543 | 2026-08-06T02:05:35+00:00 | Vulnerability · Source |
| CVE-2021-47544 | suse_vex | SUSE CVE CVE-2021-47544 | known affected: 415 known not affected: 66 recommended: 556 | 2026-08-06T02:05:31+00:00 | Vulnerability · Source |
| CVE-2021-47577 | suse_vex | SUSE CVE CVE-2021-47577 | known affected: 391 known not affected: 245 recommended: 298 | 2026-08-06T02:05:20+00:00 | Vulnerability · Source |
| CVE-2021-47598 | suse_vex | SUSE CVE CVE-2021-47598 | known affected: 292 known not affected: 146 recommended: 686 | 2026-08-06T02:05:13+00:00 | Vulnerability · Source |
| CVE-2021-47614 | suse_vex | SUSE CVE CVE-2021-47614 | known affected: 330 known not affected: 205 recommended: 411 | 2026-08-06T02:05:04+00:00 | Vulnerability · Source |
| CVE-2021-47633 | suse_vex | SUSE CVE CVE-2021-47633 | known affected: 409 known not affected: 163 recommended: 374 | 2026-08-06T02:04:59+00:00 | Vulnerability · Source |
| CVE-2021-47656 | suse_vex | SUSE CVE CVE-2021-47656 | known affected: 334 known not affected: 255 recommended: 223 | 2026-08-06T02:04:50+00:00 | Vulnerability · Source |
| CVE-2022-1679 | suse_vex | SUSE CVE CVE-2022-1679 | known affected: 194 known not affected: 6 recommended: 2031 | 2026-08-06T02:04:39+00:00 | Vulnerability · Source |
| CVE-2022-3234 | suse_vex | SUSE CVE CVE-2022-3234 | known affected: 259 known not affected: 2 recommended: 485 | 2026-08-06T02:04:30+00:00 | Vulnerability · Source |
| CVE-2022-3520 | suse_vex | SUSE CVE CVE-2022-3520 | known affected: 267 known not affected: 26 recommended: 417 | 2026-08-06T02:04:28+00:00 | Vulnerability · Source |
| CVE-2022-21549 | suse_vex | SUSE CVE CVE-2022-21549 | known affected: 395 known not affected: 393 recommended: 512 | 2026-08-06T02:04:21+00:00 | Vulnerability · Source |
| CVE-2022-24130 | suse_vex | SUSE CVE CVE-2022-24130 | known affected: 418 known not affected: 4 recommended: 86 | 2026-08-06T02:04:16+00:00 | Vulnerability · Source |
| CVE-2022-25636 | suse_vex | SUSE CVE CVE-2022-25636 | known affected: 350 known not affected: 372 recommended: 924 | 2026-08-06T02:04:14+00:00 | Vulnerability · Source |
| CVE-2022-27405 | suse_vex | SUSE CVE CVE-2022-27405 | known affected: 237 known not affected: 130 recommended: 460 | 2026-08-06T02:04:10+00:00 | Vulnerability · Source |
| CVE-2022-27664 | suse_vex | SUSE CVE CVE-2022-27664 | known not affected: 71 recommended: 630 | 2026-08-06T02:04:09+00:00 | Vulnerability · Source |
| CVE-2022-35737 | suse_vex | SUSE CVE CVE-2022-35737 | known affected: 244 known not affected: 5 recommended: 544 | 2026-08-06T02:04:00+00:00 | Vulnerability · Source |
| CVE-2022-37966 | suse_vex | SUSE CVE CVE-2022-37966 | known affected: 272 known not affected: 103 recommended: 2274 | 2026-08-06T02:03:56+00:00 | Vulnerability · Source |
| CVE-2022-39306 | suse_vex | SUSE CVE CVE-2022-39306 | known not affected: 5 recommended: 112 | 2026-08-06T02:03:52+00:00 | Vulnerability · Source |
| CVE-2022-39307 | suse_vex | SUSE CVE CVE-2022-39307 | known not affected: 5 recommended: 112 | 2026-08-06T02:03:50+00:00 | Vulnerability · Source |
| CVE-2022-40151 | suse_vex | SUSE CVE CVE-2022-40151 | known affected: 399 recommended: 53 | 2026-08-06T02:03:48+00:00 | Vulnerability · Source |
| CVE-2022-41715 | suse_vex | SUSE CVE CVE-2022-41715 | recommended: 592 | 2026-08-06T02:03:46+00:00 | Vulnerability · Source |
| CVE-2022-41881 | suse_vex | SUSE CVE CVE-2022-41881 | known not affected: 36 recommended: 58 | 2026-08-06T02:03:43+00:00 | Vulnerability · Source |
| CVE-2022-48174 | suse_vex | SUSE CVE CVE-2022-48174 | known affected: 17 recommended: 312 | 2026-08-06T02:03:36+00:00 | Vulnerability · Source |
| CVE-2022-48522 | suse_vex | SUSE CVE CVE-2022-48522 | known not affected: 231 | 2026-08-06T02:03:34+00:00 | Vulnerability · Source |
| CVE-2022-48957 | suse_vex | SUSE CVE CVE-2022-48957 | known affected: 422 known not affected: 281 recommended: 271 | 2026-08-06T02:02:59+00:00 | Vulnerability · Source |