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-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-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-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 |
| CVE-2022-49389 | suse_vex | SUSE CVE CVE-2022-49389 | known affected: 481 known not affected: 195 recommended: 355 | 2026-10-16T14:23:42+00:00 | Vulnerability · Source |
| CVE-2022-49391 | suse_vex | SUSE CVE CVE-2022-49391 | known affected: 0 known not affected: 462 | 2026-10-16T14:23:40+00:00 | Vulnerability · Source |
| CVE-2022-49393 | suse_vex | SUSE CVE CVE-2022-49393 | known affected: 0 known not affected: 462 | 2026-10-16T14:23:38+00:00 | Vulnerability · Source |
| CVE-2022-49394 | suse_vex | SUSE CVE CVE-2022-49394 | known affected: 360 known not affected: 336 recommended: 315 | 2026-10-16T14:23:35+00:00 | Vulnerability · Source |
| CVE-2022-49396 | suse_vex | SUSE CVE CVE-2022-49396 | known affected: 465 known not affected: 215 recommended: 316 | 2026-10-16T14:23:33+00:00 | Vulnerability · Source |
| CVE-2022-49397 | suse_vex | SUSE CVE CVE-2022-49397 | known affected: 465 known not affected: 183 recommended: 319 | 2026-10-16T14:23:30+00:00 | Vulnerability · Source |
| CVE-2022-49398 | suse_vex | SUSE CVE CVE-2022-49398 | known affected: 360 known not affected: 336 recommended: 335 | 2026-10-16T14:23:27+00:00 | Vulnerability · Source |
| CVE-2022-49399 | suse_vex | SUSE CVE CVE-2022-49399 | known affected: 425 known not affected: 303 recommended: 293 | 2026-10-16T14:23:24+00:00 | Vulnerability · Source |
| CVE-2022-49401 | suse_vex | SUSE CVE CVE-2022-49401 | known affected: 0 known not affected: 462 recommended: 74 | 2026-10-16T14:23:22+00:00 | Vulnerability · Source |
| CVE-2022-49402 | suse_vex | SUSE CVE CVE-2022-49402 | known affected: 334 known not affected: 362 recommended: 293 | 2026-10-16T14:23:20+00:00 | Vulnerability · Source |
| CVE-2022-49404 | suse_vex | SUSE CVE CVE-2022-49404 | known affected: 493 known not affected: 153 recommended: 375 | 2026-10-16T14:23:18+00:00 | Vulnerability · Source |
| CVE-2022-49407 | suse_vex | SUSE CVE CVE-2022-49407 | known affected: 530 known not affected: 150 recommended: 263 | 2026-10-16T14:23:15+00:00 | Vulnerability · Source |
| CVE-2022-49408 | suse_vex | SUSE CVE CVE-2022-49408 | known affected: 0 known not affected: 462 recommended: 22 | 2026-10-16T14:23:13+00:00 | Vulnerability · Source |
| CVE-2022-49409 | suse_vex | SUSE CVE CVE-2022-49409 | known affected: 481 known not affected: 196 recommended: 375 | 2026-10-16T14:23:11+00:00 | Vulnerability · Source |
| CVE-2022-49411 | suse_vex | SUSE CVE CVE-2022-49411 | known affected: 462 known not affected: 214 recommended: 341 | 2026-10-16T14:23:10+00:00 | Vulnerability · Source |
| CVE-2022-49416 | suse_vex | SUSE CVE CVE-2022-49416 | known affected: 493 known not affected: 153 recommended: 407 | 2026-10-16T14:23:07+00:00 | Vulnerability · Source |
| CVE-2022-49419 | suse_vex | SUSE CVE CVE-2022-49419 | known affected: 364 known not affected: 398 recommended: 100 | 2026-10-16T14:23:05+00:00 | Vulnerability · Source |
| CVE-2022-49421 | suse_vex | SUSE CVE CVE-2022-49421 | known affected: 481 known not affected: 198 recommended: 319 | 2026-10-16T14:23:02+00:00 | Vulnerability · Source |
| CVE-2022-49423 | suse_vex | SUSE CVE CVE-2022-49423 | known affected: 0 known not affected: 462 | 2026-10-16T14:23:00+00:00 | Vulnerability · Source |
| CVE-2022-49428 | suse_vex | SUSE CVE CVE-2022-49428 | known affected: 0 known not affected: 506 | 2026-10-16T14:22:57+00:00 | Vulnerability · Source |
| CVE-2022-49431 | suse_vex | SUSE CVE CVE-2022-49431 | known affected: 590 known not affected: 195 recommended: 223 | 2026-10-16T14:22:55+00:00 | Vulnerability · Source |