VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
99436 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-45299 | suse_vex | SUSE CVE CVE-2022-45299 | recommended: 15 | 2026-10-16T14:41:56+00:00 | Vulnerability · Source |
| CVE-2022-45403 | suse_vex | SUSE CVE CVE-2022-45403 | known affected: 1 recommended: 407 | 2026-10-16T14:41:53+00:00 | Vulnerability · Source |
| CVE-2022-45404 | suse_vex | SUSE CVE CVE-2022-45404 | known affected: 1 recommended: 407 | 2026-10-16T14:41:50+00:00 | Vulnerability · Source |
| CVE-2022-45406 | suse_vex | SUSE CVE CVE-2022-45406 | known affected: 1 recommended: 407 | 2026-10-16T14:41:47+00:00 | Vulnerability · Source |
| CVE-2022-45408 | suse_vex | SUSE CVE CVE-2022-45408 | known affected: 1 recommended: 407 | 2026-10-16T14:41:44+00:00 | Vulnerability · Source |
| CVE-2022-45412 | suse_vex | SUSE CVE CVE-2022-45412 | known affected: 1 recommended: 407 | 2026-10-16T14:41:41+00:00 | Vulnerability · Source |
| CVE-2022-45420 | suse_vex | SUSE CVE CVE-2022-45420 | known affected: 1 recommended: 407 | 2026-10-16T14:41:38+00:00 | Vulnerability · Source |
| CVE-2022-45421 | suse_vex | SUSE CVE CVE-2022-45421 | known affected: 1 recommended: 407 | 2026-10-16T14:41:36+00:00 | Vulnerability · Source |
| CVE-2022-45748 | suse_vex | SUSE CVE CVE-2022-45748 | recommended: 6 | 2026-10-16T14:41:33+00:00 | Vulnerability · Source |
| CVE-2022-45786 | suse_vex | SUSE CVE CVE-2022-45786 | recommended: 2 | 2026-10-16T14:41:30+00:00 | Vulnerability · Source |
| CVE-2022-45869 | suse_vex | SUSE CVE CVE-2022-45869 | known affected: 279 known not affected: 327 recommended: 660 | 2026-10-16T14:41:27+00:00 | Vulnerability · Source |
| CVE-2022-45873 | suse_vex | SUSE CVE CVE-2022-45873 | known affected: 0 known not affected: 646 recommended: 20 | 2026-10-16T14:41:24+00:00 | Vulnerability · Source |
| CVE-2022-45884 | suse_vex | SUSE CVE CVE-2022-45884 | known affected: 192 known not affected: 4 recommended: 1322 | 2026-10-16T14:41:21+00:00 | Vulnerability · Source |
| CVE-2022-45886 | suse_vex | SUSE CVE CVE-2022-45886 | known affected: 198 known not affected: 12 recommended: 1322 | 2026-10-16T14:41:18+00:00 | Vulnerability · Source |
| CVE-2022-45939 | suse_vex | SUSE CVE CVE-2022-45939 | known affected: 137 recommended: 464 | 2026-10-16T14:41:15+00:00 | Vulnerability · Source |
| CVE-2022-46285 | suse_vex | SUSE CVE CVE-2022-46285 | known affected: 394 recommended: 170 | 2026-10-16T14:41:12+00:00 | Vulnerability · Source |
| CVE-2022-46340 | suse_vex | SUSE CVE CVE-2022-46340 | known affected: 407 known not affected: 25 recommended: 347 | 2026-10-16T14:41:10+00:00 | Vulnerability · Source |
| CVE-2022-46341 | suse_vex | SUSE CVE CVE-2022-46341 | known affected: 394 known not affected: 49 recommended: 318 | 2026-10-16T14:41:08+00:00 | Vulnerability · Source |
| CVE-2022-46343 | suse_vex | SUSE CVE CVE-2022-46343 | known affected: 395 recommended: 321 | 2026-10-16T14:41:05+00:00 | Vulnerability · Source |
| CVE-2022-46344 | suse_vex | SUSE CVE CVE-2022-46344 | known affected: 395 recommended: 321 | 2026-10-16T14:41:02+00:00 | Vulnerability · Source |
| CVE-2022-46663 | suse_vex | SUSE CVE CVE-2022-46663 | known affected: 284 known not affected: 40 recommended: 146 | 2026-10-16T14:41:00+00:00 | Vulnerability · Source |
| CVE-2022-46871 | suse_vex | SUSE CVE CVE-2022-46871 | known affected: 21 recommended: 322 | 2026-10-16T14:40:57+00:00 | Vulnerability · Source |
| CVE-2022-46874 | suse_vex | SUSE CVE CVE-2022-46874 | known affected: 21 recommended: 380 | 2026-10-16T14:40:54+00:00 | Vulnerability · Source |
| CVE-2022-46908 | suse_vex | SUSE CVE CVE-2022-46908 | known affected: 175 known not affected: 13 recommended: 565 | 2026-10-16T14:40:52+00:00 | Vulnerability · Source |
| CVE-2022-47015 | suse_vex | SUSE CVE CVE-2022-47015 | known affected: 29 known not affected: 139 recommended: 383 | 2026-10-16T14:40:48+00:00 | Vulnerability · Source |
| CVE-2022-47016 | suse_vex | SUSE CVE CVE-2022-47016 | recommended: 13 | 2026-10-16T14:40:45+00:00 | Vulnerability · Source |
| CVE-2022-47518 | suse_vex | SUSE CVE CVE-2022-47518 | known affected: 0 known not affected: 392 | 2026-10-16T14:40:42+00:00 | Vulnerability · Source |
| CVE-2022-47519 | suse_vex | SUSE CVE CVE-2022-47519 | known affected: 0 known not affected: 392 | 2026-10-16T14:40:39+00:00 | Vulnerability · Source |
| CVE-2022-47520 | suse_vex | SUSE CVE CVE-2022-47520 | known affected: 272 known not affected: 199 recommended: 851 | 2026-10-16T14:40:37+00:00 | Vulnerability · Source |
| CVE-2022-47629 | suse_vex | SUSE CVE CVE-2022-47629 | known affected: 267 recommended: 256 | 2026-10-16T14:40:34+00:00 | Vulnerability · Source |
| CVE-2022-47630 | suse_vex | SUSE CVE CVE-2022-47630 | recommended: 9 | 2026-10-16T14:40:31+00:00 | Vulnerability · Source |
| CVE-2022-47673 | suse_vex | SUSE CVE CVE-2022-47673 | known affected: 394 known not affected: 69 recommended: 327 | 2026-10-16T14:40:29+00:00 | Vulnerability · Source |
| CVE-2022-47696 | suse_vex | SUSE CVE CVE-2022-47696 | known affected: 394 known not affected: 69 recommended: 327 | 2026-10-16T14:40:26+00:00 | Vulnerability · Source |
| CVE-2022-47929 | suse_vex | SUSE CVE CVE-2022-47929 | known affected: 287 known not affected: 37 recommended: 1164 | 2026-10-16T14:40:23+00:00 | Vulnerability · Source |
| CVE-2022-47930 | suse_vex | SUSE CVE CVE-2022-47930 | recommended: 5 | 2026-10-16T14:40:21+00:00 | Vulnerability · Source |
| CVE-2022-47939 | suse_vex | SUSE CVE CVE-2022-47939 | known affected: 0 known not affected: 392 | 2026-10-16T14:40:18+00:00 | Vulnerability · Source |
| CVE-2022-47940 | suse_vex | SUSE CVE CVE-2022-47940 | known affected: 0 known not affected: 392 | 2026-10-16T14:40:15+00:00 | Vulnerability · Source |
| CVE-2022-47946 | suse_vex | SUSE CVE CVE-2022-47946 | known affected: 0 known not affected: 392 | 2026-10-16T14:40:12+00:00 | Vulnerability · Source |
| CVE-2022-48174 | suse_vex | SUSE CVE CVE-2022-48174 | known affected: 19 recommended: 314 | 2026-10-16T14:40:10+00:00 | Vulnerability · Source |
| CVE-2022-48281 | suse_vex | SUSE CVE CVE-2022-48281 | known affected: 394 known not affected: 1 recommended: 225 | 2026-10-16T14:40:07+00:00 | Vulnerability · Source |
| CVE-2022-48303 | suse_vex | SUSE CVE CVE-2022-48303 | known affected: 355 recommended: 250 | 2026-10-16T14:40:05+00:00 | Vulnerability · Source |
| CVE-2022-48337 | suse_vex | SUSE CVE CVE-2022-48337 | known affected: 50 recommended: 377 | 2026-10-16T14:40:02+00:00 | Vulnerability · Source |
| CVE-2022-48338 | suse_vex | SUSE CVE CVE-2022-48338 | known affected: 0 known not affected: 202 recommended: 183 | 2026-10-16T14:39:59+00:00 | Vulnerability · Source |
| CVE-2022-48339 | suse_vex | SUSE CVE CVE-2022-48339 | known affected: 1 known not affected: 1 recommended: 384 | 2026-10-16T14:39:57+00:00 | Vulnerability · Source |
| CVE-2022-48423 | suse_vex | SUSE CVE CVE-2022-48423 | known affected: 0 known not affected: 591 | 2026-10-16T14:39:55+00:00 | Vulnerability · Source |
| CVE-2022-48502 | suse_vex | SUSE CVE CVE-2022-48502 | known affected: 0 known not affected: 430 | 2026-10-16T14:39:53+00:00 | Vulnerability · Source |
| CVE-2022-48522 | suse_vex | SUSE CVE CVE-2022-48522 | known affected: 0 known not affected: 254 | 2026-10-16T14:39:51+00:00 | Vulnerability · Source |
| CVE-2022-48554 | suse_vex | SUSE CVE CVE-2022-48554 | known affected: 0 known not affected: 274 recommended: 8 | 2026-10-16T14:39:49+00:00 | Vulnerability · Source |
| CVE-2022-48560 | suse_vex | SUSE CVE CVE-2022-48560 | known affected: 394 known not affected: 777 recommended: 209 | 2026-10-16T14:39:46+00:00 | Vulnerability · Source |
| CVE-2022-48565 | suse_vex | SUSE CVE CVE-2022-48565 | known affected: 571 known not affected: 409 recommended: 238 | 2026-10-16T14:39:44+00:00 | Vulnerability · Source |