VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291942 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| 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-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-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-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-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-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-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-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 |
| CVE-2022-50326 | suse_vex | SUSE CVE CVE-2022-50326 | known not affected: 345 recommended: 27 | 2026-07-27T23:50:06+00:00 | Vulnerability · Source |
| CVE-2022-50363 | suse_vex | SUSE CVE CVE-2022-50363 | known not affected: 345 recommended: 27 | 2026-07-27T23:50:04+00:00 | Vulnerability · Source |
| CVE-2022-50366 | suse_vex | SUSE CVE CVE-2022-50366 | known affected: 166 known not affected: 160 | 2026-07-27T23:50:02+00:00 | Vulnerability · Source |
| CVE-2022-50380 | suse_vex | SUSE CVE CVE-2022-50380 | known not affected: 345 | 2026-07-27T23:49:57+00:00 | Vulnerability · Source |
| CVE-2022-50412 | suse_vex | SUSE CVE CVE-2022-50412 | known affected: 429 known not affected: 184 recommended: 198 | 2026-07-27T23:49:53+00:00 | Vulnerability · Source |
| CVE-2022-50519 | suse_vex | SUSE CVE CVE-2022-50519 | known affected: 397 known not affected: 259 recommended: 191 | 2026-07-27T23:49:45+00:00 | Vulnerability · Source |
| CVE-2022-50554 | suse_vex | SUSE CVE CVE-2022-50554 | known affected: 135 known not affected: 191 recommended: 47 | 2026-07-27T23:49:40+00:00 | Vulnerability · Source |
| CVE-2022-50558 | suse_vex | SUSE CVE CVE-2022-50558 | known not affected: 336 recommended: 29 | 2026-07-27T23:49:38+00:00 | Vulnerability · Source |
| CVE-2022-50620 | suse_vex | SUSE CVE CVE-2022-50620 | known not affected: 337 | 2026-07-27T23:49:35+00:00 | Vulnerability · Source |
| CVE-2022-50621 | suse_vex | SUSE CVE CVE-2022-50621 | known affected: 374 known not affected: 349 recommended: 87 | 2026-07-27T23:49:34+00:00 | Vulnerability · Source |