VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286510 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-49410 | suse_vex | SUSE CVE CVE-2022-49410 | known affected: 342 known not affected: 205 recommended: 281 | 2026-07-27T23:51:28+00:00 | Vulnerability · Source |
| CVE-2022-49413 | suse_vex | SUSE CVE CVE-2022-49413 | known affected: 364 known not affected: 168 recommended: 341 | 2026-07-27T23:51:26+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 |
| CVE-2022-49504 | suse_vex | SUSE CVE CVE-2022-49504 | known affected: 361 known not affected: 173 recommended: 329 | 2026-07-27T23:51:20+00:00 | Vulnerability · Source |
| CVE-2022-49571 | suse_vex | SUSE CVE CVE-2022-49571 | known not affected: 137 | 2026-07-27T23:51:18+00:00 | Vulnerability · Source |
| CVE-2022-49588 | suse_vex | SUSE CVE CVE-2022-49588 | known affected: 49 known not affected: 230 recommended: 27 | 2026-07-27T23:51:16+00:00 | Vulnerability · Source |
| CVE-2022-49593 | suse_vex | SUSE CVE CVE-2022-49593 | known not affected: 137 recommended: 27 | 2026-07-27T23:51:15+00:00 | Vulnerability · Source |
| CVE-2022-49604 | suse_vex | SUSE CVE CVE-2022-49604 | known affected: 389 known not affected: 90 recommended: 210 | 2026-07-27T23:51:13+00:00 | Vulnerability · Source |
| CVE-2022-49617 | suse_vex | SUSE CVE CVE-2022-49617 | known affected: 365 known not affected: 204 recommended: 211 | 2026-07-27T23:51:11+00:00 | Vulnerability · Source |
| CVE-2022-49618 | suse_vex | SUSE CVE CVE-2022-49618 | known affected: 334 known not affected: 235 recommended: 211 | 2026-07-27T23:51:10+00:00 | Vulnerability · Source |
| CVE-2022-49643 | suse_vex | SUSE CVE CVE-2022-49643 | known affected: 342 known not affected: 205 recommended: 314 | 2026-07-27T23:51:08+00:00 | Vulnerability · Source |
| CVE-2022-49698 | suse_vex | SUSE CVE CVE-2022-49698 | known not affected: 275 recommended: 42 | 2026-07-27T23:51:06+00:00 | Vulnerability · Source |
| CVE-2022-49701 | suse_vex | SUSE CVE CVE-2022-49701 | known affected: 334 known not affected: 213 recommended: 281 | 2026-07-27T23:51:04+00:00 | Vulnerability · Source |
| CVE-2022-49720 | suse_vex | SUSE CVE CVE-2022-49720 | known affected: 366 known not affected: 324 recommended: 288 | 2026-07-27T23:51:03+00:00 | Vulnerability · Source |
| CVE-2022-49728 | suse_vex | SUSE CVE CVE-2022-49728 | known affected: 564 known not affected: 112 recommended: 33 | 2026-07-27T23:51:01+00:00 | Vulnerability · Source |
| CVE-2022-49730 | suse_vex | SUSE CVE CVE-2022-49730 | known affected: 367 known not affected: 203 recommended: 307 | 2026-07-27T23:50:59+00:00 | Vulnerability · Source |
| CVE-2022-49753 | suse_vex | SUSE CVE CVE-2022-49753 | known affected: 408 known not affected: 141 recommended: 270 | 2026-07-27T23:50:58+00:00 | Vulnerability · Source |
| CVE-2022-49764 | suse_vex | SUSE CVE CVE-2022-49764 | known affected: 588 known not affected: 187 recommended: 23 | 2026-07-27T23:50:56+00:00 | Vulnerability · Source |
| CVE-2022-49793 | suse_vex | SUSE CVE CVE-2022-49793 | known affected: 339 known not affected: 217 recommended: 269 | 2026-07-27T23:50:54+00:00 | Vulnerability · Source |
| CVE-2022-49824 | suse_vex | SUSE CVE CVE-2022-49824 | known affected: 339 known not affected: 232 recommended: 269 | 2026-07-27T23:50:52+00:00 | Vulnerability · Source |
| CVE-2022-49829 | suse_vex | SUSE CVE CVE-2022-49829 | known affected: 517 known not affected: 178 recommended: 23 | 2026-07-27T23:50:51+00:00 | Vulnerability · Source |
| CVE-2022-49848 | suse_vex | SUSE CVE CVE-2022-49848 | known not affected: 326 recommended: 27 | 2026-07-27T23:50:49+00:00 | Vulnerability · Source |
| CVE-2022-49856 | suse_vex | SUSE CVE CVE-2022-49856 | known not affected: 326 | 2026-07-27T23:50:47+00:00 | Vulnerability · Source |
| CVE-2022-49876 | suse_vex | SUSE CVE CVE-2022-49876 | known not affected: 326 | 2026-07-27T23:50:46+00:00 | Vulnerability · Source |
| CVE-2022-49910 | suse_vex | SUSE CVE CVE-2022-49910 | known not affected: 200 recommended: 268 | 2026-07-27T23:50:44+00:00 | Vulnerability · Source |
| CVE-2022-49913 | suse_vex | SUSE CVE CVE-2022-49913 | known affected: 487 known not affected: 188 recommended: 30 | 2026-07-27T23:50:42+00:00 | Vulnerability · Source |
| CVE-2022-49914 | suse_vex | SUSE CVE CVE-2022-49914 | known affected: 575 known not affected: 198 recommended: 30 | 2026-07-27T23:50:41+00:00 | Vulnerability · Source |
| CVE-2022-49917 | suse_vex | SUSE CVE CVE-2022-49917 | known affected: 503 known not affected: 138 recommended: 112 | 2026-07-27T23:50:39+00:00 | Vulnerability · Source |
| CVE-2022-49921 | suse_vex | SUSE CVE CVE-2022-49921 | known affected: 493 known not affected: 153 recommended: 110 | 2026-07-27T23:50:38+00:00 | Vulnerability · Source |
| CVE-2022-49928 | suse_vex | SUSE CVE CVE-2022-49928 | known affected: 339 known not affected: 239 recommended: 184 | 2026-07-27T23:50:36+00:00 | Vulnerability · Source |
| CVE-2022-49982 | suse_vex | SUSE CVE CVE-2022-49982 | known affected: 344 known not affected: 311 recommended: 253 | 2026-07-27T23:50:34+00:00 | Vulnerability · Source |
| CVE-2022-49991 | suse_vex | SUSE CVE CVE-2022-49991 | known affected: 49 known not affected: 281 recommended: 27 | 2026-07-27T23:50:33+00:00 | Vulnerability · Source |
| CVE-2022-50001 | suse_vex | SUSE CVE CVE-2022-50001 | known affected: 88 known not affected: 242 recommended: 42 | 2026-07-27T23:50:31+00:00 | Vulnerability · Source |
| CVE-2022-50007 | suse_vex | SUSE CVE CVE-2022-50007 | known affected: 524 known not affected: 224 recommended: 77 | 2026-07-27T23:50:30+00:00 | Vulnerability · Source |
| CVE-2022-50056 | suse_vex | SUSE CVE CVE-2022-50056 | known not affected: 330 | 2026-07-27T23:50:28+00:00 | Vulnerability · Source |
| CVE-2022-50058 | suse_vex | SUSE CVE CVE-2022-50058 | known not affected: 330 recommended: 27 | 2026-07-27T23:50:26+00:00 | Vulnerability · Source |
| CVE-2022-50063 | suse_vex | SUSE CVE CVE-2022-50063 | known not affected: 330 | 2026-07-27T23:50:25+00:00 | Vulnerability · Source |
| CVE-2022-50104 | suse_vex | SUSE CVE CVE-2022-50104 | known affected: 376 known not affected: 194 recommended: 284 | 2026-07-27T23:50:23+00:00 | Vulnerability · Source |
| CVE-2022-50129 | suse_vex | SUSE CVE CVE-2022-50129 | known affected: 375 known not affected: 208 recommended: 233 | 2026-07-27T23:50:21+00:00 | Vulnerability · Source |
| CVE-2022-50143 | suse_vex | SUSE CVE CVE-2022-50143 | known affected: 352 known not affected: 231 recommended: 284 | 2026-07-27T23:50:19+00:00 | Vulnerability · Source |
| CVE-2022-50168 | suse_vex | SUSE CVE CVE-2022-50168 | known affected: 47 known not affected: 298 recommended: 27 | 2026-07-27T23:50:17+00:00 | Vulnerability · Source |
| CVE-2022-50192 | suse_vex | SUSE CVE CVE-2022-50192 | known affected: 344 known not affected: 243 recommended: 194 | 2026-07-27T23:50:15+00:00 | Vulnerability · Source |
| CVE-2022-50218 | suse_vex | SUSE CVE CVE-2022-50218 | known affected: 376 known not affected: 222 recommended: 261 | 2026-07-27T23:50:14+00:00 | Vulnerability · Source |
| CVE-2022-50255 | suse_vex | SUSE CVE CVE-2022-50255 | known affected: 344 known not affected: 249 recommended: 194 | 2026-07-27T23:50:12+00:00 | Vulnerability · Source |
| CVE-2022-50275 | suse_vex | SUSE CVE CVE-2022-50275 | known affected: 420 known not affected: 154 recommended: 243 | 2026-07-27T23:50:10+00:00 | Vulnerability · Source |
| CVE-2022-50313 | suse_vex | SUSE CVE CVE-2022-50313 | known affected: 88 known not affected: 257 recommended: 29 | 2026-07-27T23:50:08+00:00 | Vulnerability · Source |