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-2021-47169 | suse_vex | SUSE CVE CVE-2021-47169 | known affected: 433 known not affected: 182 recommended: 200 | 2026-07-27T23:54:53+00:00 | Vulnerability · Source |
| CVE-2021-47230 | suse_vex | SUSE CVE CVE-2021-47230 | known affected: 385 known not affected: 238 recommended: 91 | 2026-07-27T23:54:45+00:00 | Vulnerability · Source |
| CVE-2021-47233 | suse_vex | SUSE CVE CVE-2021-47233 | known not affected: 283 | 2026-07-27T23:54:43+00:00 | Vulnerability · Source |
| CVE-2021-47251 | suse_vex | SUSE CVE CVE-2021-47251 | known not affected: 283 | 2026-07-27T23:54:40+00:00 | Vulnerability · Source |
| CVE-2021-47253 | suse_vex | SUSE CVE CVE-2021-47253 | known affected: 376 known not affected: 253 recommended: 91 | 2026-07-27T23:54:39+00:00 | Vulnerability · Source |
| CVE-2021-47278 | suse_vex | SUSE CVE CVE-2021-47278 | known not affected: 283 | 2026-07-27T23:54:37+00:00 | Vulnerability · Source |
| CVE-2021-47526 | suse_vex | SUSE CVE CVE-2021-47526 | known affected: 275 known not affected: 176 recommended: 440 | 2026-07-27T23:54:17+00:00 | Vulnerability · Source |
| CVE-2021-47543 | suse_vex | SUSE CVE CVE-2021-47543 | known not affected: 60 | 2026-07-27T23:54:12+00:00 | Vulnerability · Source |
| CVE-2022-0171 | suse_vex | SUSE CVE CVE-2022-0171 | known affected: 209 known not affected: 169 recommended: 388 | 2026-07-27T23:54:00+00:00 | Vulnerability · Source |
| CVE-2022-1587 | suse_vex | SUSE CVE CVE-2022-1587 | known affected: 242 known not affected: 402 recommended: 540 | 2026-07-27T23:53:52+00:00 | Vulnerability · Source |
| CVE-2022-1664 | suse_vex | SUSE CVE CVE-2022-1664 | known not affected: 3 recommended: 124 | 2026-07-27T23:53:51+00:00 | Vulnerability · Source |
| CVE-2022-1769 | suse_vex | SUSE CVE CVE-2022-1769 | known not affected: 227 recommended: 15 | 2026-07-27T23:53:49+00:00 | Vulnerability · Source |
| CVE-2022-2571 | suse_vex | SUSE CVE CVE-2022-2571 | known affected: 237 known not affected: 2 recommended: 489 | 2026-07-27T23:53:43+00:00 | Vulnerability · Source |
| CVE-2022-2590 | suse_vex | SUSE CVE CVE-2022-2590 | known not affected: 274 recommended: 6 | 2026-07-27T23:53:42+00:00 | Vulnerability · Source |
| CVE-2022-3854 | suse_vex | SUSE CVE CVE-2022-3854 | known not affected: 442 recommended: 657 | 2026-07-27T23:53:32+00:00 | Vulnerability · Source |
| CVE-2022-4055 | suse_vex | SUSE CVE CVE-2022-4055 | recommended: 1 | 2026-07-27T23:53:30+00:00 | Vulnerability · Source |
| CVE-2022-21293 | suse_vex | SUSE CVE CVE-2022-21293 | known affected: 406 known not affected: 32 recommended: 1020 | 2026-07-27T23:53:27+00:00 | Vulnerability · Source |
| CVE-2022-21597 | suse_vex | SUSE CVE CVE-2022-21597 | known not affected: 426 | 2026-07-27T23:53:24+00:00 | Vulnerability · Source |
| CVE-2022-23133 | suse_vex | SUSE CVE CVE-2022-23133 | known not affected: 28 | 2026-07-27T23:53:20+00:00 | Vulnerability · Source |
| CVE-2022-23493 | suse_vex | SUSE CVE CVE-2022-23493 | known affected: 375 known not affected: 45 recommended: 170 | 2026-07-27T23:53:16+00:00 | Vulnerability · Source |
| CVE-2022-28286 | suse_vex | SUSE CVE CVE-2022-28286 | known affected: 3 known not affected: 128 recommended: 393 | 2026-07-27T23:53:05+00:00 | Vulnerability · Source |
| CVE-2022-34568 | suse_vex | SUSE CVE CVE-2022-34568 | known not affected: 226 recommended: 2 | 2026-07-27T23:52:53+00:00 | Vulnerability · Source |
| CVE-2022-37416 | suse_vex | SUSE CVE CVE-2022-37416 | known not affected: 306 | 2026-07-27T23:52:50+00:00 | Vulnerability · Source |
| CVE-2022-38126 | suse_vex | SUSE CVE CVE-2022-38126 | known affected: 395 known not affected: 1 recommended: 445 | 2026-07-27T23:52:48+00:00 | Vulnerability · Source |
| CVE-2022-41861 | suse_vex | SUSE CVE CVE-2022-41861 | known affected: 1 recommended: 717 | 2026-07-27T23:52:43+00:00 | Vulnerability · Source |
| CVE-2022-42319 | suse_vex | SUSE CVE CVE-2022-42319 | known affected: 253 known not affected: 7 recommended: 481 | 2026-07-27T23:52:42+00:00 | Vulnerability · Source |
| CVE-2022-44268 | suse_vex | SUSE CVE CVE-2022-44268 | known affected: 45 known not affected: 12 recommended: 534 | 2026-07-27T23:52:39+00:00 | Vulnerability · Source |
| CVE-2022-48635 | suse_vex | SUSE CVE CVE-2022-48635 | known not affected: 241 | 2026-07-27T23:52:35+00:00 | Vulnerability · Source |
| CVE-2022-48640 | suse_vex | SUSE CVE CVE-2022-48640 | known affected: 360 known not affected: 222 recommended: 313 | 2026-07-27T23:52:33+00:00 | Vulnerability · Source |
| CVE-2022-48707 | suse_vex | SUSE CVE CVE-2022-48707 | known not affected: 283 | 2026-07-27T23:52:30+00:00 | Vulnerability · Source |
| CVE-2022-48719 | suse_vex | SUSE CVE CVE-2022-48719 | known not affected: 271 | 2026-07-27T23:52:27+00:00 | Vulnerability · Source |
| CVE-2022-48854 | suse_vex | SUSE CVE CVE-2022-48854 | known not affected: 271 | 2026-07-27T23:52:21+00:00 | Vulnerability · Source |
| CVE-2022-48867 | suse_vex | SUSE CVE CVE-2022-48867 | known not affected: 263 | 2026-07-27T23:52:20+00:00 | Vulnerability · Source |
| CVE-2022-48869 | suse_vex | SUSE CVE CVE-2022-48869 | known affected: 37 known not affected: 113 recommended: 327 | 2026-07-27T23:52:18+00:00 | Vulnerability · Source |
| CVE-2022-48876 | suse_vex | SUSE CVE CVE-2022-48876 | known not affected: 264 | 2026-07-27T23:52:15+00:00 | Vulnerability · Source |
| CVE-2022-48978 | suse_vex | SUSE CVE CVE-2022-48978 | known affected: 460 known not affected: 115 recommended: 447 | 2026-07-27T23:52:08+00:00 | Vulnerability · Source |
| CVE-2022-49030 | suse_vex | SUSE CVE CVE-2022-49030 | known affected: 163 known not affected: 186 | 2026-07-27T23:52:05+00:00 | Vulnerability · Source |
| CVE-2022-49067 | suse_vex | SUSE CVE CVE-2022-49067 | known not affected: 279 | 2026-07-27T23:52:03+00:00 | Vulnerability · Source |
| CVE-2022-49068 | suse_vex | SUSE CVE CVE-2022-49068 | known not affected: 279 | 2026-07-27T23:52:02+00:00 | Vulnerability · Source |
| CVE-2022-49087 | suse_vex | SUSE CVE CVE-2022-49087 | known affected: 135 known not affected: 144 recommended: 27 | 2026-07-27T23:52:00+00:00 | Vulnerability · Source |
| CVE-2022-49217 | suse_vex | SUSE CVE CVE-2022-49217 | known affected: 373 known not affected: 161 recommended: 314 | 2026-07-27T23:51:51+00:00 | Vulnerability · Source |
| CVE-2022-49234 | suse_vex | SUSE CVE CVE-2022-49234 | known affected: 135 known not affected: 144 | 2026-07-27T23:51:49+00:00 | Vulnerability · Source |
| CVE-2022-49301 | suse_vex | SUSE CVE CVE-2022-49301 | known affected: 340 known not affected: 207 recommended: 281 | 2026-07-27T23:51:41+00:00 | Vulnerability · Source |
| CVE-2022-49342 | suse_vex | SUSE CVE CVE-2022-49342 | known affected: 392 known not affected: 215 recommended: 193 | 2026-07-27T23:51:36+00:00 | Vulnerability · Source |
| CVE-2022-49351 | suse_vex | SUSE CVE CVE-2022-49351 | known affected: 420 known not affected: 237 recommended: 237 | 2026-07-27T23:51:34+00:00 | Vulnerability · Source |
| CVE-2022-49391 | suse_vex | SUSE CVE CVE-2022-49391 | known not affected: 279 | 2026-07-27T23:51:31+00:00 | Vulnerability · Source |
| CVE-2022-49405 | suse_vex | SUSE CVE CVE-2022-49405 | known not affected: 279 | 2026-07-27T23:51:29+00:00 | Vulnerability · Source |
| CVE-2022-49415 | suse_vex | SUSE CVE CVE-2022-49415 | known not affected: 279 | 2026-07-27T23:51:25+00:00 | Vulnerability · Source |
| CVE-2022-49478 | suse_vex | SUSE CVE CVE-2022-49478 | known affected: 389 known not affected: 181 recommended: 314 | 2026-07-27T23:51:23+00:00 | Vulnerability · Source |
| CVE-2022-49486 | suse_vex | SUSE CVE CVE-2022-49486 | known affected: 436 known not affected: 232 recommended: 218 | 2026-07-27T23:51:22+00:00 | Vulnerability · Source |