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-49278 | suse_vex | SUSE CVE CVE-2022-49278 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:25:48+00:00 | Vulnerability · Source |
| CVE-2022-49281 | suse_vex | SUSE CVE CVE-2022-49281 | known affected: 360 known not affected: 282 recommended: 341 | 2026-10-16T14:25:45+00:00 | Vulnerability · Source |
| CVE-2022-49283 | suse_vex | SUSE CVE CVE-2022-49283 | known affected: 334 known not affected: 394 recommended: 277 | 2026-10-16T14:25:42+00:00 | Vulnerability · Source |
| CVE-2022-49284 | suse_vex | SUSE CVE CVE-2022-49284 | known affected: 0 known not affected: 462 | 2026-10-16T14:25:39+00:00 | Vulnerability · Source |
| CVE-2022-49285 | suse_vex | SUSE CVE CVE-2022-49285 | known affected: 334 known not affected: 358 recommended: 293 | 2026-10-16T14:25:36+00:00 | Vulnerability · Source |
| CVE-2022-49288 | suse_vex | SUSE CVE CVE-2022-49288 | known affected: 0 known not affected: 302 recommended: 342 | 2026-10-16T14:25:33+00:00 | Vulnerability · Source |
| CVE-2022-49289 | suse_vex | SUSE CVE CVE-2022-49289 | known affected: 0 known not affected: 458 | 2026-10-16T14:25:31+00:00 | Vulnerability · Source |
| CVE-2022-49292 | suse_vex | SUSE CVE CVE-2022-49292 | known affected: 495 known not affected: 145 recommended: 375 | 2026-10-16T14:25:28+00:00 | Vulnerability · Source |
| CVE-2022-49294 | suse_vex | SUSE CVE CVE-2022-49294 | known affected: 400 known not affected: 328 recommended: 297 | 2026-10-16T14:25:26+00:00 | Vulnerability · Source |
| CVE-2022-49299 | suse_vex | SUSE CVE CVE-2022-49299 | known affected: 481 known not affected: 213 recommended: 293 | 2026-10-16T14:25:23+00:00 | Vulnerability · Source |
| CVE-2022-49300 | suse_vex | SUSE CVE CVE-2022-49300 | known affected: 453 known not affected: 193 recommended: 319 | 2026-10-16T14:25:21+00:00 | Vulnerability · Source |
| CVE-2022-49302 | suse_vex | SUSE CVE CVE-2022-49302 | known affected: 334 known not affected: 358 recommended: 293 | 2026-10-16T14:25:18+00:00 | Vulnerability · Source |
| CVE-2022-49303 | suse_vex | SUSE CVE CVE-2022-49303 | known affected: 0 known not affected: 458 | 2026-10-16T14:25:16+00:00 | Vulnerability · Source |
| CVE-2022-49305 | suse_vex | SUSE CVE CVE-2022-49305 | known affected: 372 known not affected: 269 recommended: 333 | 2026-10-16T14:25:13+00:00 | Vulnerability · Source |
| CVE-2022-49306 | suse_vex | SUSE CVE CVE-2022-49306 | known affected: 364 known not affected: 394 recommended: 122 | 2026-10-16T14:25:11+00:00 | Vulnerability · Source |
| CVE-2022-49307 | suse_vex | SUSE CVE CVE-2022-49307 | known affected: 340 known not affected: 358 recommended: 293 | 2026-10-16T14:25:09+00:00 | Vulnerability · Source |
| CVE-2022-49311 | suse_vex | SUSE CVE CVE-2022-49311 | known affected: 334 known not affected: 396 recommended: 223 | 2026-10-16T14:25:07+00:00 | Vulnerability · Source |
| CVE-2022-49315 | suse_vex | SUSE CVE CVE-2022-49315 | known affected: 334 known not affected: 358 recommended: 293 | 2026-10-16T14:25:05+00:00 | Vulnerability · Source |
| CVE-2022-49316 | suse_vex | SUSE CVE CVE-2022-49316 | known affected: 334 known not affected: 407 recommended: 371 | 2026-10-16T14:25:02+00:00 | Vulnerability · Source |
| CVE-2022-49318 | suse_vex | SUSE CVE CVE-2022-49318 | known affected: 0 known not affected: 462 | 2026-10-16T14:25:00+00:00 | Vulnerability · Source |
| CVE-2022-49321 | suse_vex | SUSE CVE CVE-2022-49321 | known affected: 393 known not affected: 249 recommended: 377 | 2026-10-16T14:24:57+00:00 | Vulnerability · Source |
| CVE-2022-49322 | suse_vex | SUSE CVE CVE-2022-49322 | known affected: 496 known not affected: 178 recommended: 321 | 2026-10-16T14:24:55+00:00 | Vulnerability · Source |
| CVE-2022-49324 | suse_vex | SUSE CVE CVE-2022-49324 | known affected: 0 known not affected: 458 | 2026-10-16T14:24:53+00:00 | Vulnerability · Source |
| CVE-2022-49325 | suse_vex | SUSE CVE CVE-2022-49325 | known affected: 629 known not affected: 113 recommended: 162 | 2026-10-16T14:24:51+00:00 | Vulnerability · Source |
| CVE-2022-49327 | suse_vex | SUSE CVE CVE-2022-49327 | known affected: 481 known not affected: 201 recommended: 293 | 2026-10-16T14:24:48+00:00 | Vulnerability · Source |
| CVE-2022-49328 | suse_vex | SUSE CVE CVE-2022-49328 | known affected: 403 known not affected: 325 recommended: 297 | 2026-10-16T14:24:46+00:00 | Vulnerability · Source |
| CVE-2022-49333 | suse_vex | SUSE CVE CVE-2022-49333 | known affected: 494 known not affected: 272 recommended: 174 | 2026-10-16T14:24:40+00:00 | Vulnerability · Source |
| CVE-2022-49337 | suse_vex | SUSE CVE CVE-2022-49337 | known affected: 334 known not affected: 344 recommended: 249 | 2026-10-16T14:24:38+00:00 | Vulnerability · Source |
| CVE-2022-49339 | suse_vex | SUSE CVE CVE-2022-49339 | known affected: 500 known not affected: 206 recommended: 301 | 2026-10-16T14:24:35+00:00 | Vulnerability · Source |
| CVE-2022-49342 | suse_vex | SUSE CVE CVE-2022-49342 | known affected: 472 known not affected: 294 recommended: 223 | 2026-10-16T14:24:32+00:00 | Vulnerability · Source |
| CVE-2022-49344 | suse_vex | SUSE CVE CVE-2022-49344 | known affected: 663 known not affected: 141 recommended: 98 | 2026-10-16T14:24:30+00:00 | Vulnerability · Source |
| CVE-2022-49345 | suse_vex | SUSE CVE CVE-2022-49345 | known affected: 596 known not affected: 240 recommended: 277 | 2026-10-16T14:24:27+00:00 | Vulnerability · Source |
| CVE-2022-49346 | suse_vex | SUSE CVE CVE-2022-49346 | known affected: 403 known not affected: 325 recommended: 223 | 2026-10-16T14:24:25+00:00 | Vulnerability · Source |
| CVE-2022-49347 | suse_vex | SUSE CVE CVE-2022-49347 | known affected: 481 known not affected: 193 recommended: 375 | 2026-10-16T14:24:22+00:00 | Vulnerability · Source |
| CVE-2022-49351 | suse_vex | SUSE CVE CVE-2022-49351 | known affected: 542 known not affected: 238 recommended: 249 | 2026-10-16T14:24:20+00:00 | Vulnerability · Source |
| CVE-2022-49353 | suse_vex | SUSE CVE CVE-2022-49353 | known affected: 364 known not affected: 398 recommended: 141 | 2026-10-16T14:24:18+00:00 | Vulnerability · Source |
| CVE-2022-49357 | suse_vex | SUSE CVE CVE-2022-49357 | known affected: 367 known not affected: 325 recommended: 334 | 2026-10-16T14:24:15+00:00 | Vulnerability · Source |
| CVE-2022-49359 | suse_vex | SUSE CVE CVE-2022-49359 | known affected: 425 known not affected: 337 recommended: 100 | 2026-10-16T14:24:13+00:00 | Vulnerability · Source |
| CVE-2022-49361 | suse_vex | SUSE CVE CVE-2022-49361 | known affected: 0 known not affected: 458 | 2026-10-16T14:24:10+00:00 | Vulnerability · Source |
| CVE-2022-49365 | suse_vex | SUSE CVE CVE-2022-49365 | known affected: 364 known not affected: 394 recommended: 174 | 2026-10-16T14:24:07+00:00 | Vulnerability · Source |
| CVE-2022-49366 | suse_vex | SUSE CVE CVE-2022-49366 | known affected: 0 known not affected: 462 | 2026-10-16T14:24:05+00:00 | Vulnerability · Source |
| CVE-2022-49367 | suse_vex | SUSE CVE CVE-2022-49367 | known affected: 505 known not affected: 174 recommended: 249 | 2026-10-16T14:24:03+00:00 | Vulnerability · Source |
| CVE-2022-49368 | suse_vex | SUSE CVE CVE-2022-49368 | known affected: 472 known not affected: 294 recommended: 223 | 2026-10-16T14:24:00+00:00 | Vulnerability · Source |
| CVE-2022-49370 | suse_vex | SUSE CVE CVE-2022-49370 | known affected: 495 known not affected: 145 recommended: 333 | 2026-10-16T14:23:57+00:00 | Vulnerability · Source |
| CVE-2022-49371 | suse_vex | SUSE CVE CVE-2022-49371 | known affected: 493 known not affected: 151 recommended: 404 | 2026-10-16T14:23:55+00:00 | Vulnerability · Source |
| CVE-2022-49372 | suse_vex | SUSE CVE CVE-2022-49372 | known affected: 654 known not affected: 147 recommended: 114 | 2026-10-16T14:23:52+00:00 | Vulnerability · Source |
| CVE-2022-49378 | suse_vex | SUSE CVE CVE-2022-49378 | known affected: 403 known not affected: 325 recommended: 265 | 2026-10-16T14:23:49+00:00 | Vulnerability · Source |
| CVE-2022-49379 | suse_vex | SUSE CVE CVE-2022-49379 | known affected: 334 known not affected: 394 recommended: 277 | 2026-10-16T14:23:47+00:00 | Vulnerability · Source |
| CVE-2022-49380 | suse_vex | SUSE CVE CVE-2022-49380 | known affected: 0 known not affected: 458 | 2026-10-16T14:23:45+00:00 | Vulnerability · Source |
| CVE-2022-49388 | suse_vex | SUSE CVE CVE-2022-49388 | known affected: 629 known not affected: 177 recommended: 26 | 2026-10-16T14:23:43+00:00 | Vulnerability · Source |