VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292115 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-32547 | suse_vex | SUSE CVE CVE-2022-32547 | recommended: 523 | 2026-07-23T02:33:50+00:00 | Vulnerability · Source |
| CVE-2022-32744 | suse_vex | SUSE CVE CVE-2022-32744 | known affected: 231 known not affected: 978 recommended: 1289 | 2026-07-23T02:33:48+00:00 | Vulnerability · Source |
| CVE-2022-32886 | suse_vex | SUSE CVE CVE-2022-32886 | known affected: 1 recommended: 1041 | 2026-07-23T02:33:43+00:00 | Vulnerability · Source |
| CVE-2022-32933 | suse_vex | SUSE CVE CVE-2022-32933 | known affected: 109 recommended: 787 | 2026-07-23T02:33:38+00:00 | Vulnerability · Source |
| CVE-2022-32981 | suse_vex | SUSE CVE CVE-2022-32981 | known not affected: 381 | 2026-07-23T02:33:36+00:00 | Vulnerability · Source |
| CVE-2022-34305 | suse_vex | SUSE CVE CVE-2022-34305 | known not affected: 401 | 2026-07-23T02:33:32+00:00 | Vulnerability · Source |
| CVE-2022-36280 | suse_vex | SUSE CVE CVE-2022-36280 | known affected: 262 known not affected: 2 recommended: 1483 | 2026-07-23T02:33:20+00:00 | Vulnerability · Source |
| CVE-2022-37050 | suse_vex | SUSE CVE CVE-2022-37050 | known affected: 79 known not affected: 5 recommended: 273 | 2026-07-23T02:33:13+00:00 | Vulnerability · Source |
| CVE-2022-38128 | suse_vex | SUSE CVE CVE-2022-38128 | known not affected: 226 | 2026-07-23T02:33:07+00:00 | Vulnerability · Source |
| CVE-2022-38222 | suse_vex | SUSE CVE CVE-2022-38222 | known not affected: 330 | 2026-07-23T02:33:05+00:00 | Vulnerability · Source |
| CVE-2022-38230 | suse_vex | SUSE CVE CVE-2022-38230 | known not affected: 330 | 2026-07-23T02:33:03+00:00 | Vulnerability · Source |
| CVE-2022-38236 | suse_vex | SUSE CVE CVE-2022-38236 | known not affected: 330 | 2026-07-23T02:33:01+00:00 | Vulnerability · Source |
| CVE-2022-39842 | suse_vex | SUSE CVE CVE-2022-39842 | known not affected: 540 | 2026-07-23T02:32:55+00:00 | Vulnerability · Source |
| CVE-2022-40958 | suse_vex | SUSE CVE CVE-2022-40958 | known affected: 1 recommended: 437 | 2026-07-23T02:32:50+00:00 | Vulnerability · Source |
| CVE-2022-41843 | suse_vex | SUSE CVE CVE-2022-41843 | known not affected: 330 | 2026-07-23T02:32:48+00:00 | Vulnerability · Source |
| CVE-2022-41974 | suse_vex | SUSE CVE CVE-2022-41974 | known affected: 395 known not affected: 1 recommended: 416 | 2026-07-23T02:32:43+00:00 | Vulnerability · Source |
| CVE-2022-42313 | suse_vex | SUSE CVE CVE-2022-42313 | known affected: 253 recommended: 518 | 2026-07-23T02:32:41+00:00 | Vulnerability · Source |
| CVE-2022-42322 | suse_vex | SUSE CVE CVE-2022-42322 | known affected: 253 recommended: 518 | 2026-07-23T02:32:39+00:00 | Vulnerability · Source |
| CVE-2022-42327 | suse_vex | SUSE CVE CVE-2022-42327 | known affected: 271 known not affected: 226 recommended: 230 | 2026-07-23T02:32:36+00:00 | Vulnerability · Source |
| CVE-2022-42929 | suse_vex | SUSE CVE CVE-2022-42929 | known affected: 1 recommended: 390 | 2026-07-23T02:32:27+00:00 | Vulnerability · Source |
| CVE-2022-43295 | suse_vex | SUSE CVE CVE-2022-43295 | known not affected: 355 | 2026-07-23T02:32:23+00:00 | Vulnerability · Source |
| CVE-2022-45406 | suse_vex | SUSE CVE CVE-2022-45406 | known affected: 1 recommended: 405 | 2026-07-23T02:32:11+00:00 | Vulnerability · Source |
| CVE-2022-46781 | suse_vex | SUSE CVE CVE-2022-46781 | known not affected: 327 | 2026-07-23T02:32:03+00:00 | Vulnerability · Source |
| CVE-2022-47518 | suse_vex | SUSE CVE CVE-2022-47518 | known not affected: 362 | 2026-07-23T02:32:01+00:00 | Vulnerability · Source |
| CVE-2022-47519 | suse_vex | SUSE CVE CVE-2022-47519 | known not affected: 362 | 2026-07-23T02:31:59+00:00 | Vulnerability · Source |
| CVE-2022-47941 | suse_vex | SUSE CVE CVE-2022-47941 | known not affected: 362 | 2026-07-23T02:31:54+00:00 | Vulnerability · Source |
| CVE-2022-48566 | suse_vex | SUSE CVE CVE-2022-48566 | known affected: 565 known not affected: 279 recommended: 496 | 2026-07-23T02:31:51+00:00 | Vulnerability · Source |
| CVE-2022-48642 | suse_vex | SUSE CVE CVE-2022-48642 | known affected: 453 known not affected: 187 recommended: 318 | 2026-07-23T02:31:48+00:00 | Vulnerability · Source |
| CVE-2022-48643 | suse_vex | SUSE CVE CVE-2022-48643 | known not affected: 288 | 2026-07-23T02:31:47+00:00 | Vulnerability · Source |
| CVE-2022-48696 | suse_vex | SUSE CVE CVE-2022-48696 | known not affected: 330 recommended: 47 | 2026-07-23T02:31:38+00:00 | Vulnerability · Source |
| CVE-2022-48722 | suse_vex | SUSE CVE CVE-2022-48722 | known affected: 400 known not affected: 86 recommended: 552 | 2026-07-23T02:31:37+00:00 | Vulnerability · Source |
| CVE-2022-48764 | suse_vex | SUSE CVE CVE-2022-48764 | known not affected: 318 | 2026-07-23T02:31:31+00:00 | Vulnerability · Source |
| CVE-2022-48804 | suse_vex | SUSE CVE CVE-2022-48804 | known affected: 422 known not affected: 77 recommended: 530 | 2026-07-23T02:31:20+00:00 | Vulnerability · Source |
| CVE-2022-48824 | suse_vex | SUSE CVE CVE-2022-48824 | known affected: 318 known not affected: 178 recommended: 511 | 2026-07-23T02:31:13+00:00 | Vulnerability · Source |
| CVE-2022-48844 | suse_vex | SUSE CVE CVE-2022-48844 | known affected: 530 known not affected: 76 recommended: 382 | 2026-07-23T02:31:04+00:00 | Vulnerability · Source |
| CVE-2022-48859 | suse_vex | SUSE CVE CVE-2022-48859 | known affected: 295 known not affected: 205 recommended: 426 | 2026-07-23T02:31:00+00:00 | Vulnerability · Source |
| CVE-2022-48868 | suse_vex | SUSE CVE CVE-2022-48868 | known affected: 310 known not affected: 195 recommended: 411 | 2026-07-23T02:30:56+00:00 | Vulnerability · Source |
| CVE-2022-48896 | suse_vex | SUSE CVE CVE-2022-48896 | known affected: 376 known not affected: 104 recommended: 481 | 2026-07-23T02:30:45+00:00 | Vulnerability · Source |
| CVE-2022-48928 | suse_vex | SUSE CVE CVE-2022-48928 | known affected: 310 known not affected: 382 recommended: 496 | 2026-07-23T02:30:39+00:00 | Vulnerability · Source |
| CVE-2022-49012 | suse_vex | SUSE CVE CVE-2022-49012 | known affected: 324 known not affected: 270 recommended: 394 | 2026-07-23T02:30:26+00:00 | Vulnerability · Source |
| CVE-2022-49049 | suse_vex | SUSE CVE CVE-2022-49049 | known affected: 112 known not affected: 240 recommended: 27 | 2026-07-23T02:30:21+00:00 | Vulnerability · Source |
| CVE-2022-49094 | suse_vex | SUSE CVE CVE-2022-49094 | known affected: 163 known not affected: 189 | 2026-07-23T02:30:12+00:00 | Vulnerability · Source |
| CVE-2022-49117 | suse_vex | SUSE CVE CVE-2022-49117 | known not affected: 352 | 2026-07-23T02:30:07+00:00 | Vulnerability · Source |
| CVE-2022-49127 | suse_vex | SUSE CVE CVE-2022-49127 | known affected: 57 known not affected: 295 | 2026-07-23T02:30:03+00:00 | Vulnerability · Source |
| CVE-2022-49169 | suse_vex | SUSE CVE CVE-2022-49169 | known not affected: 352 | 2026-07-23T02:29:58+00:00 | Vulnerability · Source |
| CVE-2022-49198 | suse_vex | SUSE CVE CVE-2022-49198 | known not affected: 352 | 2026-07-23T02:29:55+00:00 | Vulnerability · Source |
| CVE-2022-49240 | suse_vex | SUSE CVE CVE-2022-49240 | known not affected: 352 | 2026-07-23T02:29:50+00:00 | Vulnerability · Source |
| CVE-2022-49267 | suse_vex | SUSE CVE CVE-2022-49267 | known affected: 245 known not affected: 124 | 2026-07-23T02:29:43+00:00 | Vulnerability · Source |
| CVE-2022-49289 | suse_vex | SUSE CVE CVE-2022-49289 | known not affected: 348 | 2026-07-23T02:29:37+00:00 | Vulnerability · Source |
| CVE-2022-49318 | suse_vex | SUSE CVE CVE-2022-49318 | known not affected: 352 | 2026-07-23T02:29:29+00:00 | Vulnerability · Source |