VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291717 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49606 | suse_vex | SUSE CVE CVE-2022-49606 | known affected: 334 known not affected: 294 recommended: 265 | 2026-08-13T02:24:13+00:00 | Vulnerability · Source |
| CVE-2022-49611 | suse_vex | SUSE CVE CVE-2022-49611 | known not affected: 237 recommended: 305 | 2026-08-13T02:24:11+00:00 | Vulnerability · Source |
| CVE-2022-49624 | suse_vex | SUSE CVE CVE-2022-49624 | known affected: 364 known not affected: 298 recommended: 100 | 2026-08-13T02:24:10+00:00 | Vulnerability · Source |
| CVE-2022-49626 | suse_vex | SUSE CVE CVE-2022-49626 | known affected: 458 known not affected: 148 recommended: 305 | 2026-08-13T02:24:08+00:00 | Vulnerability · Source |
| CVE-2022-49627 | suse_vex | SUSE CVE CVE-2022-49627 | known affected: 348 known not affected: 254 recommended: 334 | 2026-08-13T02:24:07+00:00 | Vulnerability · Source |
| CVE-2022-49638 | suse_vex | SUSE CVE CVE-2022-49638 | known not affected: 109 recommended: 123 | 2026-08-13T02:24:05+00:00 | Vulnerability · Source |
| CVE-2022-49641 | suse_vex | SUSE CVE CVE-2022-49641 | known affected: 421 known not affected: 157 recommended: 360 | 2026-08-13T02:24:03+00:00 | Vulnerability · Source |
| CVE-2022-49644 | suse_vex | SUSE CVE CVE-2022-49644 | known affected: 399 known not affected: 242 recommended: 340 | 2026-08-13T02:24:02+00:00 | Vulnerability · Source |
| CVE-2022-49646 | suse_vex | SUSE CVE CVE-2022-49646 | known affected: 348 known not affected: 254 recommended: 340 | 2026-08-13T02:24:00+00:00 | Vulnerability · Source |
| CVE-2022-49650 | suse_vex | SUSE CVE CVE-2022-49650 | known affected: 334 known not affected: 256 recommended: 222 | 2026-08-13T02:23:59+00:00 | Vulnerability · Source |
| CVE-2022-49653 | suse_vex | SUSE CVE CVE-2022-49653 | known affected: 334 known not affected: 294 recommended: 272 | 2026-08-13T02:23:57+00:00 | Vulnerability · Source |
| CVE-2022-49656 | suse_vex | SUSE CVE CVE-2022-49656 | known affected: 385 known not affected: 243 recommended: 223 | 2026-08-13T02:23:56+00:00 | Vulnerability · Source |
| CVE-2022-49657 | suse_vex | SUSE CVE CVE-2022-49657 | known affected: 409 known not affected: 169 recommended: 374 | 2026-08-13T02:23:54+00:00 | Vulnerability · Source |
| CVE-2022-49658 | suse_vex | SUSE CVE CVE-2022-49658 | known affected: 521 known not affected: 154 recommended: 126 | 2026-08-13T02:23:53+00:00 | Vulnerability · Source |
| CVE-2022-49671 | suse_vex | SUSE CVE CVE-2022-49671 | known affected: 334 known not affected: 268 recommended: 335 | 2026-08-13T02:23:51+00:00 | Vulnerability · Source |
| CVE-2022-49673 | suse_vex | SUSE CVE CVE-2022-49673 | known affected: 415 known not affected: 162 recommended: 375 | 2026-08-13T02:23:49+00:00 | Vulnerability · Source |
| CVE-2022-49678 | suse_vex | SUSE CVE CVE-2022-49678 | known affected: 348 known not affected: 254 recommended: 293 | 2026-08-13T02:23:47+00:00 | Vulnerability · Source |
| CVE-2022-49682 | suse_vex | SUSE CVE CVE-2022-49682 | known not affected: 352 | 2026-08-13T02:23:45+00:00 | Vulnerability · Source |
| CVE-2022-49688 | suse_vex | SUSE CVE CVE-2022-49688 | known affected: 334 known not affected: 294 recommended: 250 | 2026-08-13T02:23:44+00:00 | Vulnerability · Source |
| CVE-2022-49703 | suse_vex | SUSE CVE CVE-2022-49703 | known affected: 334 known not affected: 270 recommended: 293 | 2026-08-13T02:23:41+00:00 | Vulnerability · Source |
| CVE-2022-49705 | suse_vex | SUSE CVE CVE-2022-49705 | known affected: 334 known not affected: 297 recommended: 223 | 2026-08-13T02:23:40+00:00 | Vulnerability · Source |
| CVE-2022-49707 | suse_vex | SUSE CVE CVE-2022-49707 | known affected: 381 known not affected: 358 recommended: 387 | 2026-08-13T02:23:38+00:00 | Vulnerability · Source |
| CVE-2022-49711 | suse_vex | SUSE CVE CVE-2022-49711 | known affected: 407 known not affected: 169 recommended: 333 | 2026-08-13T02:23:36+00:00 | Vulnerability · Source |
| CVE-2022-49719 | suse_vex | SUSE CVE CVE-2022-49719 | known affected: 422 known not affected: 248 recommended: 223 | 2026-08-13T02:23:34+00:00 | Vulnerability · Source |
| CVE-2022-49723 | suse_vex | SUSE CVE CVE-2022-49723 | known affected: 348 known not affected: 255 recommended: 340 | 2026-08-13T02:23:33+00:00 | Vulnerability · Source |
| CVE-2022-49742 | suse_vex | SUSE CVE CVE-2022-49742 | known not affected: 397 | 2026-08-13T02:23:31+00:00 | Vulnerability · Source |
| CVE-2022-49745 | suse_vex | SUSE CVE CVE-2022-49745 | known affected: 369 known not affected: 290 recommended: 95 | 2026-08-13T02:23:30+00:00 | Vulnerability · Source |
| CVE-2022-49747 | suse_vex | SUSE CVE CVE-2022-49747 | known not affected: 344 recommended: 43 | 2026-08-13T02:23:29+00:00 | Vulnerability · Source |
| CVE-2022-49755 | suse_vex | SUSE CVE CVE-2022-49755 | known affected: 452 known not affected: 129 recommended: 222 | 2026-08-13T02:23:27+00:00 | Vulnerability · Source |
| CVE-2022-49764 | suse_vex | SUSE CVE CVE-2022-49764 | known affected: 590 known not affected: 187 recommended: 23 | 2026-08-13T02:23:25+00:00 | Vulnerability · Source |
| CVE-2022-49770 | suse_vex | SUSE CVE CVE-2022-49770 | known affected: 418 known not affected: 183 recommended: 313 | 2026-08-13T02:23:23+00:00 | Vulnerability · Source |
| CVE-2022-49773 | suse_vex | SUSE CVE CVE-2022-49773 | known affected: 369 known not affected: 342 recommended: 141 | 2026-08-13T02:23:22+00:00 | Vulnerability · Source |
| CVE-2022-49776 | suse_vex | SUSE CVE CVE-2022-49776 | known affected: 441 known not affected: 162 recommended: 251 | 2026-08-13T02:23:20+00:00 | Vulnerability · Source |
| CVE-2022-49778 | suse_vex | SUSE CVE CVE-2022-49778 | known not affected: 397 recommended: 43 | 2026-08-13T02:23:19+00:00 | Vulnerability · Source |
| CVE-2022-49783 | suse_vex | SUSE CVE CVE-2022-49783 | known affected: 339 known not affected: 292 recommended: 214 | 2026-08-13T02:23:17+00:00 | Vulnerability · Source |
| CVE-2022-49801 | suse_vex | SUSE CVE CVE-2022-49801 | known affected: 339 known not affected: 292 recommended: 214 | 2026-08-13T02:23:15+00:00 | Vulnerability · Source |
| CVE-2022-49802 | suse_vex | SUSE CVE CVE-2022-49802 | known affected: 353 known not affected: 254 recommended: 281 | 2026-08-13T02:23:13+00:00 | Vulnerability · Source |
| CVE-2022-49810 | suse_vex | SUSE CVE CVE-2022-49810 | known affected: 339 known not affected: 294 recommended: 214 | 2026-08-13T02:23:12+00:00 | Vulnerability · Source |
| CVE-2022-49827 | suse_vex | SUSE CVE CVE-2022-49827 | known affected: 339 known not affected: 264 recommended: 330 | 2026-08-13T02:23:10+00:00 | Vulnerability · Source |
| CVE-2022-49837 | suse_vex | SUSE CVE CVE-2022-49837 | known affected: 475 known not affected: 241 recommended: 121 | 2026-08-13T02:23:07+00:00 | Vulnerability · Source |
| CVE-2022-49853 | suse_vex | SUSE CVE CVE-2022-49853 | known affected: 441 known not affected: 164 recommended: 284 | 2026-08-13T02:23:04+00:00 | Vulnerability · Source |
| CVE-2022-49872 | suse_vex | SUSE CVE CVE-2022-49872 | known affected: 605 known not affected: 157 recommended: 70 | 2026-08-13T02:23:01+00:00 | Vulnerability · Source |
| CVE-2022-49874 | suse_vex | SUSE CVE CVE-2022-49874 | known affected: 455 known not affected: 165 recommended: 251 | 2026-08-13T02:22:59+00:00 | Vulnerability · Source |
| CVE-2022-49875 | suse_vex | SUSE CVE CVE-2022-49875 | known affected: 92 known not affected: 305 recommended: 29 | 2026-08-13T02:22:57+00:00 | Vulnerability · Source |
| CVE-2022-49880 | suse_vex | SUSE CVE CVE-2022-49880 | known affected: 420 known not affected: 170 recommended: 318 | 2026-08-13T02:22:56+00:00 | Vulnerability · Source |
| CVE-2022-49889 | suse_vex | SUSE CVE CVE-2022-49889 | known affected: 339 known not affected: 238 recommended: 304 | 2026-08-13T02:22:54+00:00 | Vulnerability · Source |
| CVE-2022-49890 | suse_vex | SUSE CVE CVE-2022-49890 | known affected: 390 known not affected: 241 recommended: 234 | 2026-08-13T02:22:53+00:00 | Vulnerability · Source |
| CVE-2022-49897 | suse_vex | SUSE CVE CVE-2022-49897 | known affected: 57 known not affected: 349 | 2026-08-13T02:22:50+00:00 | Vulnerability · Source |
| CVE-2022-49906 | suse_vex | SUSE CVE CVE-2022-49906 | known affected: 353 known not affected: 224 recommended: 304 | 2026-08-13T02:22:48+00:00 | Vulnerability · Source |
| CVE-2022-49907 | suse_vex | SUSE CVE CVE-2022-49907 | known affected: 586 known not affected: 192 recommended: 37 | 2026-08-13T02:22:47+00:00 | Vulnerability · Source |