VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
100938 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49138 | suse_vex | SUSE CVE CVE-2022-49138 | known affected: 568 known not affected: 119 recommended: 251 | 2026-10-16T14:28:51+00:00 | Vulnerability · Source |
| CVE-2022-49140 | suse_vex | SUSE CVE CVE-2022-49140 | No product status | 2026-10-16T14:28:49+00:00 | Vulnerability · Source |
| CVE-2022-49141 | suse_vex | SUSE CVE CVE-2022-49141 | known affected: 67 known not affected: 395 | 2026-10-16T14:28:46+00:00 | Vulnerability · Source |
| CVE-2022-49142 | suse_vex | SUSE CVE CVE-2022-49142 | known affected: 61 known not affected: 401 recommended: 22 | 2026-10-16T14:28:44+00:00 | Vulnerability · Source |
| CVE-2022-49143 | suse_vex | SUSE CVE CVE-2022-49143 | No product status | 2026-10-16T14:28:42+00:00 | Vulnerability · Source |
| CVE-2022-49144 | suse_vex | SUSE CVE CVE-2022-49144 | known affected: 425 known not affected: 338 recommended: 100 | 2026-10-16T14:28:39+00:00 | Vulnerability · Source |
| CVE-2022-49146 | suse_vex | SUSE CVE CVE-2022-49146 | known affected: 0 known not affected: 462 | 2026-10-16T14:28:34+00:00 | Vulnerability · Source |
| CVE-2022-49149 | suse_vex | SUSE CVE CVE-2022-49149 | known affected: 130 known not affected: 332 | 2026-10-16T14:28:28+00:00 | Vulnerability · Source |
| CVE-2022-49152 | suse_vex | SUSE CVE CVE-2022-49152 | known affected: 0 known not affected: 462 recommended: 22 | 2026-10-16T14:28:26+00:00 | Vulnerability · Source |
| CVE-2022-49153 | suse_vex | SUSE CVE CVE-2022-49153 | known affected: 360 known not affected: 338 recommended: 315 | 2026-10-16T14:28:24+00:00 | Vulnerability · Source |
| CVE-2022-49154 | suse_vex | SUSE CVE CVE-2022-49154 | known affected: 508 known not affected: 219 recommended: 260 | 2026-10-16T14:28:21+00:00 | Vulnerability · Source |
| CVE-2022-49155 | suse_vex | SUSE CVE CVE-2022-49155 | known affected: 453 known not affected: 192 recommended: 333 | 2026-10-16T14:28:18+00:00 | Vulnerability · Source |
| CVE-2022-49156 | suse_vex | SUSE CVE CVE-2022-49156 | known affected: 487 known not affected: 157 recommended: 375 | 2026-10-16T14:28:16+00:00 | Vulnerability · Source |
| CVE-2022-49157 | suse_vex | SUSE CVE CVE-2022-49157 | known affected: 487 known not affected: 159 recommended: 319 | 2026-10-16T14:28:13+00:00 | Vulnerability · Source |
| CVE-2022-49159 | suse_vex | SUSE CVE CVE-2022-49159 | known affected: 427 known not affected: 219 recommended: 319 | 2026-10-16T14:28:11+00:00 | Vulnerability · Source |
| CVE-2022-49162 | suse_vex | SUSE CVE CVE-2022-49162 | known affected: 461 known not affected: 231 recommended: 293 | 2026-10-16T14:28:08+00:00 | Vulnerability · Source |
| CVE-2022-49166 | suse_vex | SUSE CVE CVE-2022-49166 | known affected: 0 known not affected: 458 | 2026-10-16T14:28:03+00:00 | Vulnerability · Source |
| CVE-2022-49167 | suse_vex | SUSE CVE CVE-2022-49167 | known affected: 128 known not affected: 330 | 2026-10-16T14:28:01+00:00 | Vulnerability · Source |
| CVE-2022-49168 | suse_vex | SUSE CVE CVE-2022-49168 | known affected: 522 known not affected: 280 recommended: 37 | 2026-10-16T14:27:58+00:00 | Vulnerability · Source |
| CVE-2022-49169 | suse_vex | SUSE CVE CVE-2022-49169 | known affected: 0 known not affected: 462 | 2026-10-16T14:27:56+00:00 | Vulnerability · Source |
| CVE-2022-49172 | suse_vex | SUSE CVE CVE-2022-49172 | known affected: 0 known not affected: 462 | 2026-10-16T14:27:53+00:00 | Vulnerability · Source |
| CVE-2022-49174 | suse_vex | SUSE CVE CVE-2022-49174 | known affected: 334 known not affected: 393 recommended: 223 | 2026-10-16T14:27:51+00:00 | Vulnerability · Source |
| CVE-2022-49178 | suse_vex | SUSE CVE CVE-2022-49178 | known affected: 633 known not affected: 81 recommended: 140 | 2026-10-16T14:27:49+00:00 | Vulnerability · Source |
| CVE-2022-49182 | suse_vex | SUSE CVE CVE-2022-49182 | known affected: 448 known not affected: 232 recommended: 249 | 2026-10-16T14:27:46+00:00 | Vulnerability · Source |
| CVE-2022-49183 | suse_vex | SUSE CVE CVE-2022-49183 | known affected: 407 known not affected: 359 recommended: 100 | 2026-10-16T14:27:43+00:00 | Vulnerability · Source |
| CVE-2022-49184 | suse_vex | SUSE CVE CVE-2022-49184 | known affected: 0 known not affected: 462 | 2026-10-16T14:27:41+00:00 | Vulnerability · Source |
| CVE-2022-49185 | suse_vex | SUSE CVE CVE-2022-49185 | known affected: 334 known not affected: 362 recommended: 293 | 2026-10-16T14:27:38+00:00 | Vulnerability · Source |
| CVE-2022-49187 | suse_vex | SUSE CVE CVE-2022-49187 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:27:36+00:00 | Vulnerability · Source |
| CVE-2022-49191 | suse_vex | SUSE CVE CVE-2022-49191 | known affected: 651 known not affected: 153 recommended: 40 | 2026-10-16T14:27:34+00:00 | Vulnerability · Source |
| CVE-2022-49192 | suse_vex | SUSE CVE CVE-2022-49192 | known affected: 0 known not affected: 402 recommended: 70 | 2026-10-16T14:27:31+00:00 | Vulnerability · Source |
| CVE-2022-49193 | suse_vex | SUSE CVE CVE-2022-49193 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:27:29+00:00 | Vulnerability · Source |
| CVE-2022-49199 | suse_vex | SUSE CVE CVE-2022-49199 | known affected: 334 known not affected: 395 recommended: 265 | 2026-10-16T14:27:26+00:00 | Vulnerability · Source |
| CVE-2022-49200 | suse_vex | SUSE CVE CVE-2022-49200 | known affected: 360 known not affected: 336 recommended: 293 | 2026-10-16T14:27:23+00:00 | Vulnerability · Source |
| CVE-2022-49202 | suse_vex | SUSE CVE CVE-2022-49202 | known affected: 364 known not affected: 399 recommended: 100 | 2026-10-16T14:27:20+00:00 | Vulnerability · Source |
| CVE-2022-49204 | suse_vex | SUSE CVE CVE-2022-49204 | known affected: 539 known not affected: 177 recommended: 180 | 2026-10-16T14:27:17+00:00 | Vulnerability · Source |
| CVE-2022-49207 | suse_vex | SUSE CVE CVE-2022-49207 | known affected: 425 known not affected: 337 recommended: 154 | 2026-10-16T14:27:15+00:00 | Vulnerability · Source |
| CVE-2022-49210 | suse_vex | SUSE CVE CVE-2022-49210 | known affected: 0 known not affected: 509 | 2026-10-16T14:27:12+00:00 | Vulnerability · Source |
| CVE-2022-49211 | suse_vex | SUSE CVE CVE-2022-49211 | known affected: 0 known not affected: 508 | 2026-10-16T14:27:10+00:00 | Vulnerability · Source |
| CVE-2022-49213 | suse_vex | SUSE CVE CVE-2022-49213 | known affected: 334 known not affected: 364 recommended: 293 | 2026-10-16T14:27:08+00:00 | Vulnerability · Source |
| CVE-2022-49216 | suse_vex | SUSE CVE CVE-2022-49216 | known affected: 493 known not affected: 214 recommended: 316 | 2026-10-16T14:27:06+00:00 | Vulnerability · Source |
| CVE-2022-49217 | suse_vex | SUSE CVE CVE-2022-49217 | known affected: 481 known not affected: 163 recommended: 333 | 2026-10-16T14:27:03+00:00 | Vulnerability · Source |
| CVE-2022-49218 | suse_vex | SUSE CVE CVE-2022-49218 | known affected: 377 known not affected: 351 recommended: 223 | 2026-10-16T14:27:01+00:00 | Vulnerability · Source |
| CVE-2022-49219 | suse_vex | SUSE CVE CVE-2022-49219 | known affected: 494 known not affected: 268 recommended: 100 | 2026-10-16T14:26:59+00:00 | Vulnerability · Source |
| CVE-2022-49221 | suse_vex | SUSE CVE CVE-2022-49221 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:26:56+00:00 | Vulnerability · Source |
| CVE-2022-49222 | suse_vex | SUSE CVE CVE-2022-49222 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:26:54+00:00 | Vulnerability · Source |
| CVE-2022-49224 | suse_vex | SUSE CVE CVE-2022-49224 | known affected: 429 known not affected: 301 recommended: 293 | 2026-10-16T14:26:52+00:00 | Vulnerability · Source |
| CVE-2022-49227 | suse_vex | SUSE CVE CVE-2022-49227 | known affected: 334 known not affected: 394 recommended: 265 | 2026-10-16T14:26:47+00:00 | Vulnerability · Source |
| CVE-2022-49228 | suse_vex | SUSE CVE CVE-2022-49228 | known affected: 364 known not affected: 398 recommended: 122 | 2026-10-16T14:26:45+00:00 | Vulnerability · Source |
| CVE-2022-49231 | suse_vex | SUSE CVE CVE-2022-49231 | known affected: 0 known not affected: 462 | 2026-10-16T14:26:40+00:00 | Vulnerability · Source |
| CVE-2022-49233 | suse_vex | SUSE CVE CVE-2022-49233 | known affected: 364 known not affected: 402 recommended: 100 | 2026-10-16T14:26:38+00:00 | Vulnerability · Source |