VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283900 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49221 | suse_vex | SUSE CVE CVE-2022-49221 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:15:28+00:00 | Vulnerability · Source |
| CVE-2022-49222 | suse_vex | SUSE CVE CVE-2022-49222 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:15:27+00:00 | Vulnerability · Source |
| CVE-2022-49224 | suse_vex | SUSE CVE CVE-2022-49224 | known affected: 385 known not affected: 257 recommended: 293 | 2026-07-25T17:15:25+00:00 | Vulnerability · Source |
| CVE-2022-49229 | suse_vex | SUSE CVE CVE-2022-49229 | known affected: 112 known not affected: 240 recommended: 22 | 2026-07-25T17:15:24+00:00 | Vulnerability · Source |
| CVE-2022-49230 | suse_vex | SUSE CVE CVE-2022-49230 | known affected: 364 known not affected: 302 recommended: 100 | 2026-07-25T17:15:22+00:00 | Vulnerability · Source |
| CVE-2022-49232 | suse_vex | SUSE CVE CVE-2022-49232 | known affected: 377 known not affected: 239 recommended: 319 | 2026-07-25T17:15:21+00:00 | Vulnerability · Source |
| CVE-2022-49236 | suse_vex | SUSE CVE CVE-2022-49236 | known affected: 334 known not affected: 298 recommended: 250 | 2026-07-25T17:15:19+00:00 | Vulnerability · Source |
| CVE-2022-49238 | suse_vex | SUSE CVE CVE-2022-49238 | known affected: 364 known not affected: 302 recommended: 142 | 2026-07-25T17:15:18+00:00 | Vulnerability · Source |
| CVE-2022-49242 | suse_vex | SUSE CVE CVE-2022-49242 | known affected: 385 known not affected: 257 recommended: 293 | 2026-07-25T17:15:16+00:00 | Vulnerability · Source |
| CVE-2022-49243 | suse_vex | SUSE CVE CVE-2022-49243 | known affected: 334 known not affected: 270 recommended: 293 | 2026-07-25T17:15:15+00:00 | Vulnerability · Source |
| CVE-2022-49249 | suse_vex | SUSE CVE CVE-2022-49249 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:15:13+00:00 | Vulnerability · Source |
| CVE-2022-49252 | suse_vex | SUSE CVE CVE-2022-49252 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:15:12+00:00 | Vulnerability · Source |
| CVE-2022-49253 | suse_vex | SUSE CVE CVE-2022-49253 | known affected: 421 known not affected: 157 recommended: 352 | 2026-07-25T17:15:10+00:00 | Vulnerability · Source |
| CVE-2022-49257 | suse_vex | SUSE CVE CVE-2022-49257 | known not affected: 298 recommended: 192 | 2026-07-25T17:15:08+00:00 | Vulnerability · Source |
| CVE-2022-49261 | suse_vex | SUSE CVE CVE-2022-49261 | known affected: 394 known not affected: 270 recommended: 233 | 2026-07-25T17:15:07+00:00 | Vulnerability · Source |
| CVE-2022-49274 | suse_vex | SUSE CVE CVE-2022-49274 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:15:05+00:00 | Vulnerability · Source |
| CVE-2022-49275 | suse_vex | SUSE CVE CVE-2022-49275 | known affected: 424 known not affected: 148 recommended: 372 | 2026-07-25T17:15:04+00:00 | Vulnerability · Source |
| CVE-2022-49276 | suse_vex | SUSE CVE CVE-2022-49276 | known affected: 377 known not affected: 255 recommended: 223 | 2026-07-25T17:15:03+00:00 | Vulnerability · Source |
| CVE-2022-49279 | suse_vex | SUSE CVE CVE-2022-49279 | known affected: 348 known not affected: 254 recommended: 293 | 2026-07-25T17:15:01+00:00 | Vulnerability · Source |
| CVE-2022-49286 | suse_vex | SUSE CVE CVE-2022-49286 | known affected: 432 known not affected: 172 recommended: 249 | 2026-07-25T17:15:00+00:00 | Vulnerability · Source |
| CVE-2022-49299 | suse_vex | SUSE CVE CVE-2022-49299 | known affected: 409 known not affected: 193 recommended: 293 | 2026-07-25T17:14:58+00:00 | Vulnerability · Source |
| CVE-2022-49300 | suse_vex | SUSE CVE CVE-2022-49300 | known affected: 395 known not affected: 183 recommended: 319 | 2026-07-25T17:14:56+00:00 | Vulnerability · Source |
| CVE-2022-49303 | suse_vex | SUSE CVE CVE-2022-49303 | known not affected: 348 | 2026-07-25T17:14:55+00:00 | Vulnerability · Source |
| CVE-2022-49304 | suse_vex | SUSE CVE CVE-2022-49304 | known affected: 334 known not affected: 266 recommended: 293 | 2026-07-25T17:14:53+00:00 | Vulnerability · Source |
| CVE-2022-49305 | suse_vex | SUSE CVE CVE-2022-49305 | known affected: 356 known not affected: 218 recommended: 333 | 2026-07-25T17:14:51+00:00 | Vulnerability · Source |
| CVE-2022-49308 | suse_vex | SUSE CVE CVE-2022-49308 | known affected: 440 known not affected: 162 recommended: 263 | 2026-07-25T17:14:49+00:00 | Vulnerability · Source |
| CVE-2022-49312 | suse_vex | SUSE CVE CVE-2022-49312 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:14:47+00:00 | Vulnerability · Source |
| CVE-2022-49313 | suse_vex | SUSE CVE CVE-2022-49313 | known affected: 340 known not affected: 234 recommended: 319 | 2026-07-25T17:14:46+00:00 | Vulnerability · Source |
| CVE-2022-49316 | suse_vex | SUSE CVE CVE-2022-49316 | known affected: 334 known not affected: 321 recommended: 342 | 2026-07-25T17:14:44+00:00 | Vulnerability · Source |
| CVE-2022-49329 | suse_vex | SUSE CVE CVE-2022-49329 | known affected: 364 known not affected: 302 recommended: 100 | 2026-07-25T17:14:42+00:00 | Vulnerability · Source |
| CVE-2022-49330 | suse_vex | SUSE CVE CVE-2022-49330 | known affected: 537 known not affected: 103 recommended: 182 | 2026-07-25T17:14:41+00:00 | Vulnerability · Source |
| CVE-2022-49340 | suse_vex | SUSE CVE CVE-2022-49340 | known affected: 112 known not affected: 240 recommended: 22 | 2026-07-25T17:14:39+00:00 | Vulnerability · Source |
| CVE-2022-49343 | suse_vex | SUSE CVE CVE-2022-49343 | known not affected: 236 recommended: 327 | 2026-07-25T17:14:37+00:00 | Vulnerability · Source |
| CVE-2022-49346 | suse_vex | SUSE CVE CVE-2022-49346 | known affected: 385 known not affected: 247 recommended: 223 | 2026-07-25T17:14:35+00:00 | Vulnerability · Source |
| CVE-2022-49350 | suse_vex | SUSE CVE CVE-2022-49350 | known affected: 436 known not affected: 234 recommended: 252 | 2026-07-25T17:14:33+00:00 | Vulnerability · Source |
| CVE-2022-49352 | suse_vex | SUSE CVE CVE-2022-49352 | known affected: 350 known not affected: 288 recommended: 293 | 2026-07-25T17:14:32+00:00 | Vulnerability · Source |
| CVE-2022-49357 | suse_vex | SUSE CVE CVE-2022-49357 | known affected: 357 known not affected: 243 recommended: 334 | 2026-07-25T17:14:30+00:00 | Vulnerability · Source |
| CVE-2022-49359 | suse_vex | SUSE CVE CVE-2022-49359 | known affected: 419 known not affected: 247 recommended: 100 | 2026-07-25T17:14:28+00:00 | Vulnerability · Source |
| CVE-2022-49361 | suse_vex | SUSE CVE CVE-2022-49361 | known not affected: 348 | 2026-07-25T17:14:27+00:00 | Vulnerability · Source |
| CVE-2022-49363 | suse_vex | SUSE CVE CVE-2022-49363 | known not affected: 348 | 2026-07-25T17:14:25+00:00 | Vulnerability · Source |
| CVE-2022-49366 | suse_vex | SUSE CVE CVE-2022-49366 | known not affected: 352 | 2026-07-25T17:14:24+00:00 | Vulnerability · Source |
| CVE-2022-49368 | suse_vex | SUSE CVE CVE-2022-49368 | known affected: 422 known not affected: 248 recommended: 223 | 2026-07-25T17:14:23+00:00 | Vulnerability · Source |
| CVE-2022-49375 | suse_vex | SUSE CVE CVE-2022-49375 | known affected: 334 known not affected: 321 recommended: 293 | 2026-07-25T17:14:21+00:00 | Vulnerability · Source |
| CVE-2022-49378 | suse_vex | SUSE CVE CVE-2022-49378 | known affected: 385 known not affected: 247 recommended: 265 | 2026-07-25T17:14:20+00:00 | Vulnerability · Source |
| CVE-2022-49385 | suse_vex | SUSE CVE CVE-2022-49385 | known affected: 421 known not affected: 193 recommended: 333 | 2026-07-25T17:14:17+00:00 | Vulnerability · Source |
| CVE-2022-49386 | suse_vex | SUSE CVE CVE-2022-49386 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:14:16+00:00 | Vulnerability · Source |
| CVE-2022-49390 | suse_vex | SUSE CVE CVE-2022-49390 | known affected: 513 known not affected: 165 recommended: 126 | 2026-07-25T17:14:14+00:00 | Vulnerability · Source |
| CVE-2022-49392 | suse_vex | SUSE CVE CVE-2022-49392 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:14:13+00:00 | Vulnerability · Source |
| CVE-2022-49393 | suse_vex | SUSE CVE CVE-2022-49393 | known not affected: 352 | 2026-07-25T17:14:11+00:00 | Vulnerability · Source |
| CVE-2022-49394 | suse_vex | SUSE CVE CVE-2022-49394 | known affected: 348 known not affected: 256 recommended: 315 | 2026-07-25T17:14:10+00:00 | Vulnerability · Source |