VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
99436 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-49230 | suse_vex | SUSE CVE CVE-2022-49230 | known affected: 364 known not affected: 398 recommended: 100 | 2026-10-16T14:26:43+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 |
| CVE-2022-49234 | suse_vex | SUSE CVE CVE-2022-49234 | known affected: 197 known not affected: 265 | 2026-10-16T14:26:36+00:00 | Vulnerability · Source |
| CVE-2022-49235 | suse_vex | SUSE CVE CVE-2022-49235 | known affected: 496 known not affected: 179 recommended: 372 | 2026-10-16T14:26:33+00:00 | Vulnerability · Source |
| CVE-2022-49237 | suse_vex | SUSE CVE CVE-2022-49237 | known affected: 364 known not affected: 398 recommended: 100 | 2026-10-16T14:26:30+00:00 | Vulnerability · Source |
| CVE-2022-49239 | suse_vex | SUSE CVE CVE-2022-49239 | known affected: 334 known not affected: 363 recommended: 293 | 2026-10-16T14:26:28+00:00 | Vulnerability · Source |
| CVE-2022-49242 | suse_vex | SUSE CVE CVE-2022-49242 | known affected: 429 known not affected: 303 recommended: 293 | 2026-10-16T14:26:25+00:00 | Vulnerability · Source |
| CVE-2022-49243 | suse_vex | SUSE CVE CVE-2022-49243 | known affected: 334 known not affected: 362 recommended: 293 | 2026-10-16T14:26:23+00:00 | Vulnerability · Source |
| CVE-2022-49244 | suse_vex | SUSE CVE CVE-2022-49244 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:26:21+00:00 | Vulnerability · Source |
| CVE-2022-49246 | suse_vex | SUSE CVE CVE-2022-49246 | known affected: 403 known not affected: 325 recommended: 223 | 2026-10-16T14:26:19+00:00 | Vulnerability · Source |
| CVE-2022-49247 | suse_vex | SUSE CVE CVE-2022-49247 | known affected: 493 known not affected: 153 recommended: 355 | 2026-10-16T14:26:17+00:00 | Vulnerability · Source |
| CVE-2022-49248 | suse_vex | SUSE CVE CVE-2022-49248 | known affected: 490 known not affected: 183 recommended: 330 | 2026-10-16T14:26:14+00:00 | Vulnerability · Source |
| CVE-2022-49255 | suse_vex | SUSE CVE CVE-2022-49255 | known affected: 0 known not affected: 462 | 2026-10-16T14:26:12+00:00 | Vulnerability · Source |
| CVE-2022-49259 | suse_vex | SUSE CVE CVE-2022-49259 | known affected: 360 known not affected: 284 recommended: 361 | 2026-10-16T14:26:08+00:00 | Vulnerability · Source |
| CVE-2022-49261 | suse_vex | SUSE CVE CVE-2022-49261 | known affected: 394 known not affected: 362 recommended: 233 | 2026-10-16T14:26:05+00:00 | Vulnerability · Source |
| CVE-2022-49263 | suse_vex | SUSE CVE CVE-2022-49263 | known affected: 360 known not affected: 336 recommended: 335 | 2026-10-16T14:26:03+00:00 | Vulnerability · Source |
| CVE-2022-49269 | suse_vex | SUSE CVE CVE-2022-49269 | known affected: 334 known not affected: 394 recommended: 264 | 2026-10-16T14:26:00+00:00 | Vulnerability · Source |
| CVE-2022-49270 | suse_vex | SUSE CVE CVE-2022-49270 | known affected: 334 known not affected: 395 recommended: 245 | 2026-10-16T14:25:57+00:00 | Vulnerability · Source |
| CVE-2022-49271 | suse_vex | SUSE CVE CVE-2022-49271 | known affected: 487 known not affected: 217 recommended: 271 | 2026-10-16T14:25:55+00:00 | Vulnerability · Source |
| CVE-2022-49274 | suse_vex | SUSE CVE CVE-2022-49274 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:25:53+00:00 | Vulnerability · Source |
| CVE-2022-49275 | suse_vex | SUSE CVE CVE-2022-49275 | known affected: 495 known not affected: 144 recommended: 399 | 2026-10-16T14:25:51+00:00 | Vulnerability · Source |