VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283840 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-2819 | suse_vex | SUSE CVE CVE-2022-2819 | known affected: 237 known not affected: 2 recommended: 505 | 2026-07-25T17:29:33+00:00 | Vulnerability · Source |
| CVE-2022-2862 | suse_vex | SUSE CVE CVE-2022-2862 | known affected: 237 known not affected: 2 recommended: 505 | 2026-07-25T17:29:32+00:00 | Vulnerability · Source |
| CVE-2022-2869 | suse_vex | SUSE CVE CVE-2022-2869 | known affected: 395 known not affected: 1 recommended: 266 | 2026-07-25T17:29:30+00:00 | Vulnerability · Source |
| CVE-2022-2874 | suse_vex | SUSE CVE CVE-2022-2874 | known affected: 237 known not affected: 2 recommended: 505 | 2026-07-25T17:29:29+00:00 | Vulnerability · Source |
| CVE-2022-2946 | suse_vex | SUSE CVE CVE-2022-2946 | known affected: 237 known not affected: 2 recommended: 505 | 2026-07-25T17:29:28+00:00 | Vulnerability · Source |
| CVE-2022-2961 | suse_vex | SUSE CVE CVE-2022-2961 | known not affected: 264 | 2026-07-25T17:29:26+00:00 | Vulnerability · Source |
| CVE-2022-2963 | suse_vex | SUSE CVE CVE-2022-2963 | known affected: 453 recommended: 111 | 2026-07-25T17:29:25+00:00 | Vulnerability · Source |
| CVE-2022-2982 | suse_vex | SUSE CVE CVE-2022-2982 | known affected: 259 known not affected: 2 recommended: 485 | 2026-07-25T17:29:23+00:00 | Vulnerability · Source |
| CVE-2022-3080 | suse_vex | SUSE CVE CVE-2022-3080 | known affected: 271 known not affected: 492 recommended: 240 | 2026-07-25T17:29:22+00:00 | Vulnerability · Source |
| CVE-2022-3094 | suse_vex | SUSE CVE CVE-2022-3094 | known affected: 272 recommended: 562 | 2026-07-25T17:29:20+00:00 | Vulnerability · Source |
| CVE-2022-3099 | suse_vex | SUSE CVE CVE-2022-3099 | known affected: 259 known not affected: 2 recommended: 485 | 2026-07-25T17:29:19+00:00 | Vulnerability · Source |
| CVE-2022-3103 | suse_vex | SUSE CVE CVE-2022-3103 | known not affected: 327 | 2026-07-25T17:29:17+00:00 | Vulnerability · Source |
| CVE-2022-3105 | suse_vex | SUSE CVE CVE-2022-3105 | known affected: 272 known not affected: 234 recommended: 900 | 2026-07-25T17:29:16+00:00 | Vulnerability · Source |
| CVE-2022-3106 | suse_vex | SUSE CVE CVE-2022-3106 | known affected: 272 known not affected: 280 recommended: 840 | 2026-07-25T17:29:14+00:00 | Vulnerability · Source |
| CVE-2022-3111 | suse_vex | SUSE CVE CVE-2022-3111 | known affected: 272 known not affected: 280 recommended: 820 | 2026-07-25T17:29:13+00:00 | Vulnerability · Source |
| CVE-2022-3114 | suse_vex | SUSE CVE CVE-2022-3114 | known affected: 284 known not affected: 305 recommended: 624 | 2026-07-25T17:29:11+00:00 | Vulnerability · Source |
| CVE-2022-3170 | suse_vex | SUSE CVE CVE-2022-3170 | known not affected: 327 | 2026-07-25T17:29:10+00:00 | Vulnerability · Source |
| CVE-2022-3219 | suse_vex | SUSE CVE CVE-2022-3219 | known affected: 1 | 2026-07-25T17:29:08+00:00 | Vulnerability · Source |
| CVE-2022-3235 | suse_vex | SUSE CVE CVE-2022-3235 | known affected: 259 known not affected: 2 recommended: 485 | 2026-07-25T17:29:07+00:00 | Vulnerability · Source |
| CVE-2022-3239 | suse_vex | SUSE CVE CVE-2022-3239 | known affected: 253 known not affected: 2 recommended: 1509 | 2026-07-25T17:29:05+00:00 | Vulnerability · Source |
| CVE-2022-3324 | suse_vex | SUSE CVE CVE-2022-3324 | known affected: 260 recommended: 464 | 2026-07-25T17:29:03+00:00 | Vulnerability · Source |
| CVE-2022-3352 | suse_vex | SUSE CVE CVE-2022-3352 | known affected: 259 known not affected: 2 recommended: 485 | 2026-07-25T17:29:02+00:00 | Vulnerability · Source |
| CVE-2022-3424 | suse_vex | SUSE CVE CVE-2022-3424 | known affected: 253 recommended: 1758 | 2026-07-25T17:29:00+00:00 | Vulnerability · Source |
| CVE-2022-3435 | suse_vex | SUSE CVE CVE-2022-3435 | known affected: 219 known not affected: 339 recommended: 1248 | 2026-07-25T17:28:58+00:00 | Vulnerability · Source |
| CVE-2022-3491 | suse_vex | SUSE CVE CVE-2022-3491 | known affected: 267 known not affected: 10 recommended: 417 | 2026-07-25T17:28:57+00:00 | Vulnerability · Source |
| CVE-2022-3521 | suse_vex | SUSE CVE CVE-2022-3521 | known affected: 255 known not affected: 153 recommended: 1416 | 2026-07-25T17:28:55+00:00 | Vulnerability · Source |
| CVE-2022-3523 | suse_vex | SUSE CVE CVE-2022-3523 | known affected: 310 known not affected: 311 recommended: 698 | 2026-07-25T17:28:54+00:00 | Vulnerability · Source |
| CVE-2022-3529 | suse_vex | SUSE CVE CVE-2022-3529 | known not affected: 117 | 2026-07-25T17:28:52+00:00 | Vulnerability · Source |
| CVE-2022-3530 | suse_vex | SUSE CVE CVE-2022-3530 | known not affected: 54 | 2026-07-25T17:28:51+00:00 | Vulnerability · Source |
| CVE-2022-3532 | suse_vex | SUSE CVE CVE-2022-3532 | known not affected: 327 | 2026-07-25T17:28:50+00:00 | Vulnerability · Source |
| CVE-2022-3535 | suse_vex | SUSE CVE CVE-2022-3535 | known affected: 279 known not affected: 297 recommended: 1137 | 2026-07-25T17:28:48+00:00 | Vulnerability · Source |
| CVE-2022-3541 | suse_vex | SUSE CVE CVE-2022-3541 | known not affected: 327 | 2026-07-25T17:28:47+00:00 | Vulnerability · Source |
| CVE-2022-3544 | suse_vex | SUSE CVE CVE-2022-3544 | known not affected: 327 | 2026-07-25T17:28:46+00:00 | Vulnerability · Source |
| CVE-2022-3553 | suse_vex | SUSE CVE CVE-2022-3553 | known not affected: 150 | 2026-07-25T17:28:44+00:00 | Vulnerability · Source |
| CVE-2022-3555 | suse_vex | SUSE CVE CVE-2022-3555 | known affected: 516 recommended: 293 | 2026-07-25T17:28:43+00:00 | Vulnerability · Source |
| CVE-2022-3563 | suse_vex | SUSE CVE CVE-2022-3563 | known not affected: 142 recommended: 50 | 2026-07-25T17:28:41+00:00 | Vulnerability · Source |
| CVE-2022-3564 | suse_vex | SUSE CVE CVE-2022-3564 | known affected: 247 known not affected: 55 recommended: 1573 | 2026-07-25T17:28:40+00:00 | Vulnerability · Source |
| CVE-2022-3570 | suse_vex | SUSE CVE CVE-2022-3570 | known affected: 424 known not affected: 1 recommended: 237 | 2026-07-25T17:28:38+00:00 | Vulnerability · Source |
| CVE-2022-3577 | suse_vex | SUSE CVE CVE-2022-3577 | known affected: 253 known not affected: 298 recommended: 1274 | 2026-07-25T17:28:37+00:00 | Vulnerability · Source |
| CVE-2022-3592 | suse_vex | SUSE CVE CVE-2022-3592 | known not affected: 2051 recommended: 377 | 2026-07-25T17:28:35+00:00 | Vulnerability · Source |
| CVE-2022-3594 | suse_vex | SUSE CVE CVE-2022-3594 | known affected: 255 known not affected: 103 recommended: 1514 | 2026-07-25T17:28:34+00:00 | Vulnerability · Source |
| CVE-2022-3606 | suse_vex | SUSE CVE CVE-2022-3606 | known affected: 382 known not affected: 462 recommended: 254 | 2026-07-25T17:28:32+00:00 | Vulnerability · Source |
| CVE-2022-3619 | suse_vex | SUSE CVE CVE-2022-3619 | known affected: 246 known not affected: 448 recommended: 844 | 2026-07-25T17:28:31+00:00 | Vulnerability · Source |
| CVE-2022-3621 | suse_vex | SUSE CVE CVE-2022-3621 | known affected: 255 known not affected: 346 recommended: 1493 | 2026-07-25T17:28:29+00:00 | Vulnerability · Source |
| CVE-2022-3626 | suse_vex | SUSE CVE CVE-2022-3626 | known affected: 395 known not affected: 1 recommended: 267 | 2026-07-25T17:28:28+00:00 | Vulnerability · Source |
| CVE-2022-3628 | suse_vex | SUSE CVE CVE-2022-3628 | known affected: 261 known not affected: 2 recommended: 1587 | 2026-07-25T17:28:26+00:00 | Vulnerability · Source |
| CVE-2022-3633 | suse_vex | SUSE CVE CVE-2022-3633 | known affected: 271 known not affected: 321 recommended: 635 | 2026-07-25T17:28:24+00:00 | Vulnerability · Source |
| CVE-2022-3637 | suse_vex | SUSE CVE CVE-2022-3637 | known not affected: 167 | 2026-07-25T17:28:23+00:00 | Vulnerability · Source |
| CVE-2022-3640 | suse_vex | SUSE CVE CVE-2022-3640 | known affected: 228 known not affected: 213 recommended: 1264 | 2026-07-25T17:28:21+00:00 | Vulnerability · Source |
| CVE-2022-3646 | suse_vex | SUSE CVE CVE-2022-3646 | known affected: 261 known not affected: 321 recommended: 1493 | 2026-07-25T17:28:20+00:00 | Vulnerability · Source |