VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291709 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49213 | suse_vex | SUSE CVE CVE-2022-49213 | known affected: 334 known not affected: 270 recommended: 293 | 2026-08-13T02:26:41+00:00 | Vulnerability · Source |
| CVE-2022-49215 | suse_vex | SUSE CVE CVE-2022-49215 | known affected: 470 known not affected: 192 recommended: 122 | 2026-08-13T02:26:40+00:00 | Vulnerability · Source |
| CVE-2022-49216 | suse_vex | SUSE CVE CVE-2022-49216 | known affected: 421 known not affected: 223 recommended: 316 | 2026-08-13T02:26:39+00:00 | Vulnerability · Source |
| CVE-2022-49218 | suse_vex | SUSE CVE CVE-2022-49218 | known affected: 371 known not affected: 257 recommended: 223 | 2026-08-13T02:26:37+00:00 | Vulnerability · Source |
| CVE-2022-49223 | suse_vex | SUSE CVE CVE-2022-49223 | known affected: 112 known not affected: 240 recommended: 27 | 2026-08-13T02:26:36+00:00 | Vulnerability · Source |
| CVE-2022-49232 | suse_vex | SUSE CVE CVE-2022-49232 | known affected: 374 known not affected: 237 recommended: 319 | 2026-08-13T02:26:34+00:00 | Vulnerability · Source |
| CVE-2022-49235 | suse_vex | SUSE CVE CVE-2022-49235 | known affected: 424 known not affected: 187 recommended: 372 | 2026-08-13T02:26:32+00:00 | Vulnerability · Source |
| CVE-2022-49244 | suse_vex | SUSE CVE CVE-2022-49244 | known affected: 334 known not affected: 294 recommended: 223 | 2026-08-13T02:26:30+00:00 | Vulnerability · Source |
| CVE-2022-49247 | suse_vex | SUSE CVE CVE-2022-49247 | known affected: 421 known not affected: 157 recommended: 355 | 2026-08-13T02:26:28+00:00 | Vulnerability · Source |
| CVE-2022-49251 | suse_vex | SUSE CVE CVE-2022-49251 | known affected: 334 known not affected: 294 recommended: 223 | 2026-08-13T02:26:26+00:00 | Vulnerability · Source |
| CVE-2022-49256 | suse_vex | SUSE CVE CVE-2022-49256 | known not affected: 294 recommended: 192 | 2026-08-13T02:26:24+00:00 | Vulnerability · Source |
| CVE-2022-49257 | suse_vex | SUSE CVE CVE-2022-49257 | known not affected: 298 recommended: 192 | 2026-08-13T02:26:23+00:00 | Vulnerability · Source |
| CVE-2022-49260 | suse_vex | SUSE CVE CVE-2022-49260 | known affected: 334 known not affected: 294 recommended: 223 | 2026-08-13T02:26:21+00:00 | Vulnerability · Source |
| CVE-2022-49262 | suse_vex | SUSE CVE CVE-2022-49262 | known affected: 334 known not affected: 294 recommended: 223 | 2026-08-13T02:26:20+00:00 | Vulnerability · Source |
| CVE-2022-49265 | suse_vex | SUSE CVE CVE-2022-49265 | known affected: 334 known not affected: 294 recommended: 265 | 2026-08-13T02:26:18+00:00 | Vulnerability · Source |
| CVE-2022-49269 | suse_vex | SUSE CVE CVE-2022-49269 | known affected: 334 known not affected: 294 recommended: 264 | 2026-08-13T02:26:17+00:00 | Vulnerability · Source |
| CVE-2022-49273 | suse_vex | SUSE CVE CVE-2022-49273 | known affected: 334 known not affected: 294 recommended: 252 | 2026-08-13T02:26:16+00:00 | Vulnerability · Source |
| CVE-2022-49278 | suse_vex | SUSE CVE CVE-2022-49278 | known affected: 334 known not affected: 294 recommended: 223 | 2026-08-13T02:26:14+00:00 | Vulnerability · Source |
| CVE-2022-49280 | suse_vex | SUSE CVE CVE-2022-49280 | known affected: 415 known not affected: 157 recommended: 333 | 2026-08-13T02:26:13+00:00 | Vulnerability · Source |
| CVE-2022-49282 | suse_vex | SUSE CVE CVE-2022-49282 | known affected: 55 known not affected: 297 | 2026-08-13T02:26:11+00:00 | Vulnerability · Source |
| CVE-2022-49283 | suse_vex | SUSE CVE CVE-2022-49283 | known affected: 334 known not affected: 294 recommended: 250 | 2026-08-13T02:26:10+00:00 | Vulnerability · Source |
| CVE-2022-49292 | suse_vex | SUSE CVE CVE-2022-49292 | known affected: 423 known not affected: 149 recommended: 375 | 2026-08-13T02:26:07+00:00 | Vulnerability · Source |
| CVE-2022-49293 | suse_vex | SUSE CVE CVE-2022-49293 | known not affected: 196 recommended: 284 | 2026-08-13T02:26:05+00:00 | Vulnerability · Source |
| CVE-2022-49304 | suse_vex | SUSE CVE CVE-2022-49304 | known affected: 334 known not affected: 264 recommended: 293 | 2026-08-13T02:26:02+00:00 | Vulnerability · Source |
| CVE-2022-49305 | suse_vex | SUSE CVE CVE-2022-49305 | known affected: 356 known not affected: 217 recommended: 333 | 2026-08-13T02:26:01+00:00 | Vulnerability · Source |
| CVE-2022-49311 | suse_vex | SUSE CVE CVE-2022-49311 | known affected: 334 known not affected: 296 recommended: 223 | 2026-08-13T02:25:59+00:00 | Vulnerability · Source |
| CVE-2022-49312 | suse_vex | SUSE CVE CVE-2022-49312 | known affected: 334 known not affected: 298 recommended: 223 | 2026-08-13T02:25:58+00:00 | Vulnerability · Source |
| CVE-2022-49317 | suse_vex | SUSE CVE CVE-2022-49317 | known not affected: 352 | 2026-08-13T02:25:57+00:00 | Vulnerability · Source |
| CVE-2022-49328 | suse_vex | SUSE CVE CVE-2022-49328 | known affected: 385 known not affected: 243 recommended: 270 | 2026-08-13T02:25:54+00:00 | Vulnerability · Source |
| CVE-2022-49333 | suse_vex | SUSE CVE CVE-2022-49333 | known affected: 470 known not affected: 196 recommended: 147 | 2026-08-13T02:25:53+00:00 | Vulnerability · Source |
| CVE-2022-49335 | suse_vex | SUSE CVE CVE-2022-49335 | known affected: 334 known not affected: 238 recommended: 333 | 2026-08-13T02:25:51+00:00 | Vulnerability · Source |
| CVE-2022-49339 | suse_vex | SUSE CVE CVE-2022-49339 | known affected: 436 known not affected: 200 recommended: 272 | 2026-08-13T02:25:50+00:00 | Vulnerability · Source |
| CVE-2022-49349 | suse_vex | SUSE CVE CVE-2022-49349 | known affected: 409 known not affected: 199 recommended: 375 | 2026-08-13T02:25:49+00:00 | Vulnerability · Source |
| CVE-2022-49352 | suse_vex | SUSE CVE CVE-2022-49352 | known affected: 350 known not affected: 287 recommended: 293 | 2026-08-13T02:25:47+00:00 | Vulnerability · Source |
| CVE-2022-49359 | suse_vex | SUSE CVE CVE-2022-49359 | known affected: 419 known not affected: 243 recommended: 100 | 2026-08-13T02:25:46+00:00 | Vulnerability · Source |
| CVE-2022-49364 | suse_vex | SUSE CVE CVE-2022-49364 | known not affected: 348 | 2026-08-13T02:25:45+00:00 | Vulnerability · Source |
| CVE-2022-49369 | suse_vex | SUSE CVE CVE-2022-49369 | known not affected: 352 | 2026-08-13T02:25:43+00:00 | Vulnerability · Source |
| CVE-2022-49371 | suse_vex | SUSE CVE CVE-2022-49371 | known affected: 421 known not affected: 155 recommended: 377 | 2026-08-13T02:25:41+00:00 | Vulnerability · Source |
| CVE-2022-49373 | suse_vex | SUSE CVE CVE-2022-49373 | known affected: 385 known not affected: 255 recommended: 293 | 2026-08-13T02:25:40+00:00 | Vulnerability · Source |
| CVE-2022-49377 | suse_vex | SUSE CVE CVE-2022-49377 | known affected: 334 known not affected: 294 recommended: 223 | 2026-08-13T02:25:39+00:00 | Vulnerability · Source |
| CVE-2022-49378 | suse_vex | SUSE CVE CVE-2022-49378 | known affected: 385 known not affected: 243 recommended: 265 | 2026-08-13T02:25:37+00:00 | Vulnerability · Source |
| CVE-2022-49382 | suse_vex | SUSE CVE CVE-2022-49382 | known affected: 407 known not affected: 257 recommended: 316 | 2026-08-13T02:25:36+00:00 | Vulnerability · Source |
| CVE-2022-49389 | suse_vex | SUSE CVE CVE-2022-49389 | known affected: 409 known not affected: 203 recommended: 355 | 2026-08-13T02:25:34+00:00 | Vulnerability · Source |
| CVE-2022-49395 | suse_vex | SUSE CVE CVE-2022-49395 | known affected: 576 known not affected: 141 recommended: 60 | 2026-08-13T02:25:33+00:00 | Vulnerability · Source |
| CVE-2022-49406 | suse_vex | SUSE CVE CVE-2022-49406 | known affected: 364 known not affected: 301 recommended: 100 | 2026-08-13T02:25:31+00:00 | Vulnerability · Source |
| CVE-2022-49409 | suse_vex | SUSE CVE CVE-2022-49409 | known affected: 409 known not affected: 204 recommended: 375 | 2026-08-13T02:25:29+00:00 | Vulnerability · Source |
| CVE-2022-49410 | suse_vex | SUSE CVE CVE-2022-49410 | known affected: 348 known not affected: 254 recommended: 293 | 2026-08-13T02:25:27+00:00 | Vulnerability · Source |
| CVE-2022-49417 | suse_vex | SUSE CVE CVE-2022-49417 | known not affected: 352 | 2026-08-13T02:25:25+00:00 | Vulnerability · Source |
| CVE-2022-49418 | suse_vex | SUSE CVE CVE-2022-49418 | known affected: 334 known not affected: 297 recommended: 265 | 2026-08-13T02:25:24+00:00 | Vulnerability · Source |
| CVE-2022-49421 | suse_vex | SUSE CVE CVE-2022-49421 | known affected: 409 known not affected: 206 recommended: 319 | 2026-08-13T02:25:23+00:00 | Vulnerability · Source |