VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291321 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49322 | suse_vex | SUSE CVE CVE-2022-49322 | known affected: 432 known not affected: 168 recommended: 292 | 2026-08-14T01:21:54+00:00 | Vulnerability · Source |
| CVE-2022-49326 | suse_vex | SUSE CVE CVE-2022-49326 | known affected: 417 known not affected: 155 recommended: 330 | 2026-08-14T01:21:53+00:00 | Vulnerability · Source |
| CVE-2022-49327 | suse_vex | SUSE CVE CVE-2022-49327 | known affected: 409 known not affected: 209 recommended: 293 | 2026-08-14T01:21:51+00:00 | Vulnerability · Source |
| CVE-2022-49329 | suse_vex | SUSE CVE CVE-2022-49329 | known affected: 364 known not affected: 299 recommended: 100 | 2026-08-14T01:21:50+00:00 | Vulnerability · Source |
| CVE-2022-49344 | suse_vex | SUSE CVE CVE-2022-49344 | known affected: 579 known not affected: 141 recommended: 69 | 2026-08-14T01:21:48+00:00 | Vulnerability · Source |
| CVE-2022-49346 | suse_vex | SUSE CVE CVE-2022-49346 | known affected: 385 known not affected: 243 recommended: 223 | 2026-08-14T01:21:46+00:00 | Vulnerability · Source |
| CVE-2022-49350 | suse_vex | SUSE CVE CVE-2022-49350 | known affected: 436 known not affected: 234 recommended: 252 | 2026-08-14T01:21:45+00:00 | Vulnerability · Source |
| CVE-2022-49357 | suse_vex | SUSE CVE CVE-2022-49357 | known affected: 355 known not affected: 243 recommended: 334 | 2026-08-14T01:21:43+00:00 | Vulnerability · Source |
| CVE-2022-49360 | suse_vex | SUSE CVE CVE-2022-49360 | known not affected: 348 | 2026-08-14T01:21:42+00:00 | Vulnerability · Source |
| CVE-2022-49362 | suse_vex | SUSE CVE CVE-2022-49362 | known affected: 364 known not affected: 302 recommended: 127 | 2026-08-14T01:21:40+00:00 | Vulnerability · Source |
| CVE-2022-49365 | suse_vex | SUSE CVE CVE-2022-49365 | known affected: 364 known not affected: 294 recommended: 147 | 2026-08-14T01:21:38+00:00 | Vulnerability · Source |
| CVE-2022-49367 | suse_vex | SUSE CVE CVE-2022-49367 | known affected: 441 known not affected: 164 recommended: 249 | 2026-08-14T01:21:37+00:00 | Vulnerability · Source |
| CVE-2022-49372 | suse_vex | SUSE CVE CVE-2022-49372 | known affected: 570 known not affected: 147 recommended: 87 | 2026-08-14T01:21:35+00:00 | Vulnerability · Source |
| CVE-2022-49375 | suse_vex | SUSE CVE CVE-2022-49375 | known affected: 334 known not affected: 321 recommended: 293 | 2026-08-14T01:21:34+00:00 | Vulnerability · Source |
| CVE-2022-49380 | suse_vex | SUSE CVE CVE-2022-49380 | known not affected: 348 | 2026-08-14T01:21:32+00:00 | Vulnerability · Source |
| CVE-2022-49381 | suse_vex | SUSE CVE CVE-2022-49381 | known affected: 377 known not affected: 254 recommended: 223 | 2026-08-14T01:21:31+00:00 | Vulnerability · Source |
| CVE-2022-49384 | suse_vex | SUSE CVE CVE-2022-49384 | known affected: 334 known not affected: 298 recommended: 223 | 2026-08-14T01:21:29+00:00 | Vulnerability · Source |
| CVE-2022-49385 | suse_vex | SUSE CVE CVE-2022-49385 | known affected: 421 known not affected: 191 recommended: 333 | 2026-08-14T01:21:27+00:00 | Vulnerability · Source |
| CVE-2022-49386 | suse_vex | SUSE CVE CVE-2022-49386 | known affected: 334 known not affected: 294 recommended: 223 | 2026-08-14T01:21:25+00:00 | Vulnerability · Source |
| CVE-2022-49392 | suse_vex | SUSE CVE CVE-2022-49392 | known affected: 334 known not affected: 294 recommended: 223 | 2026-08-14T01:21:23+00:00 | Vulnerability · Source |
| CVE-2022-49399 | suse_vex | SUSE CVE CVE-2022-49399 | known affected: 381 known not affected: 257 recommended: 293 | 2026-08-14T01:21:21+00:00 | Vulnerability · Source |
| CVE-2022-49403 | suse_vex | SUSE CVE CVE-2022-49403 | known not affected: 352 | 2026-08-14T01:21:20+00:00 | Vulnerability · Source |
| CVE-2022-49404 | suse_vex | SUSE CVE CVE-2022-49404 | known affected: 421 known not affected: 157 recommended: 375 | 2026-08-14T01:21:18+00:00 | Vulnerability · Source |
| CVE-2022-49408 | suse_vex | SUSE CVE CVE-2022-49408 | known not affected: 352 recommended: 22 | 2026-08-14T01:21:17+00:00 | Vulnerability · Source |
| CVE-2022-49426 | suse_vex | SUSE CVE CVE-2022-49426 | known affected: 334 known not affected: 294 recommended: 265 | 2026-08-14T01:21:15+00:00 | Vulnerability · Source |
| CVE-2022-49430 | suse_vex | SUSE CVE CVE-2022-49430 | known affected: 334 known not affected: 398 recommended: 223 | 2026-08-14T01:21:13+00:00 | Vulnerability · Source |
| CVE-2022-49432 | suse_vex | SUSE CVE CVE-2022-49432 | known affected: 432 known not affected: 170 recommended: 290 | 2026-08-14T01:21:11+00:00 | Vulnerability · Source |
| CVE-2022-49433 | suse_vex | SUSE CVE CVE-2022-49433 | known affected: 458 known not affected: 148 recommended: 305 | 2026-08-14T01:21:08+00:00 | Vulnerability · Source |
| CVE-2022-49448 | suse_vex | SUSE CVE CVE-2022-49448 | known affected: 334 known not affected: 294 recommended: 223 | 2026-08-14T01:21:07+00:00 | Vulnerability · Source |
| CVE-2022-49460 | suse_vex | SUSE CVE CVE-2022-49460 | known affected: 407 known not affected: 209 recommended: 316 | 2026-08-14T01:21:03+00:00 | Vulnerability · Source |
| CVE-2022-49466 | suse_vex | SUSE CVE CVE-2022-49466 | known affected: 334 known not affected: 298 recommended: 252 | 2026-08-14T01:21:01+00:00 | Vulnerability · Source |
| CVE-2022-49484 | suse_vex | SUSE CVE CVE-2022-49484 | known affected: 419 known not affected: 247 recommended: 100 | 2026-08-14T01:20:59+00:00 | Vulnerability · Source |
| CVE-2022-49494 | suse_vex | SUSE CVE CVE-2022-49494 | known affected: 334 known not affected: 294 recommended: 223 | 2026-08-14T01:20:58+00:00 | Vulnerability · Source |
| CVE-2022-49498 | suse_vex | SUSE CVE CVE-2022-49498 | known affected: 334 known not affected: 270 recommended: 293 | 2026-08-14T01:20:56+00:00 | Vulnerability · Source |
| CVE-2022-49508 | suse_vex | SUSE CVE CVE-2022-49508 | known affected: 348 known not affected: 255 recommended: 293 | 2026-08-14T01:20:54+00:00 | Vulnerability · Source |
| CVE-2022-49525 | suse_vex | SUSE CVE CVE-2022-49525 | known affected: 427 known not affected: 187 recommended: 333 | 2026-08-14T01:20:52+00:00 | Vulnerability · Source |
| CVE-2022-49537 | suse_vex | SUSE CVE CVE-2022-49537 | known affected: 360 known not affected: 218 recommended: 361 | 2026-08-14T01:20:49+00:00 | Vulnerability · Source |
| CVE-2022-49544 | suse_vex | SUSE CVE CVE-2022-49544 | known affected: 427 known not affected: 149 recommended: 333 | 2026-08-14T01:20:48+00:00 | Vulnerability · Source |
| CVE-2022-49555 | suse_vex | SUSE CVE CVE-2022-49555 | known affected: 409 known not affected: 220 recommended: 333 | 2026-08-14T01:20:47+00:00 | Vulnerability · Source |
| CVE-2022-49559 | suse_vex | SUSE CVE CVE-2022-49559 | known affected: 334 known not affected: 294 recommended: 265 | 2026-08-14T01:20:45+00:00 | Vulnerability · Source |
| CVE-2022-49581 | suse_vex | SUSE CVE CVE-2022-49581 | known affected: 461 known not affected: 142 recommended: 263 | 2026-08-14T01:20:42+00:00 | Vulnerability · Source |
| CVE-2022-49589 | suse_vex | SUSE CVE CVE-2022-49589 | known affected: 570 known not affected: 147 recommended: 67 | 2026-08-14T01:20:41+00:00 | Vulnerability · Source |
| CVE-2022-49595 | suse_vex | SUSE CVE CVE-2022-49595 | known not affected: 147 recommended: 27 | 2026-08-14T01:20:39+00:00 | Vulnerability · Source |
| CVE-2022-49607 | suse_vex | SUSE CVE CVE-2022-49607 | known affected: 455 known not affected: 148 recommended: 263 | 2026-08-14T01:20:37+00:00 | Vulnerability · Source |
| CVE-2022-49609 | suse_vex | SUSE CVE CVE-2022-49609 | known affected: 399 known not affected: 243 recommended: 293 | 2026-08-14T01:20:35+00:00 | Vulnerability · Source |
| CVE-2022-49616 | suse_vex | SUSE CVE CVE-2022-49616 | known affected: 371 known not affected: 257 recommended: 243 | 2026-08-14T01:20:34+00:00 | Vulnerability · Source |
| CVE-2022-49617 | suse_vex | SUSE CVE CVE-2022-49617 | known affected: 371 known not affected: 257 recommended: 223 | 2026-08-14T01:20:32+00:00 | Vulnerability · Source |
| CVE-2022-49623 | suse_vex | SUSE CVE CVE-2022-49623 | known affected: 395 known not affected: 344 recommended: 360 | 2026-08-14T01:20:29+00:00 | Vulnerability · Source |
| CVE-2022-49625 | suse_vex | SUSE CVE CVE-2022-49625 | known affected: 458 known not affected: 148 recommended: 302 | 2026-08-14T01:20:27+00:00 | Vulnerability · Source |
| CVE-2022-49628 | suse_vex | SUSE CVE CVE-2022-49628 | known affected: 334 known not affected: 294 recommended: 223 | 2026-08-14T01:20:25+00:00 | Vulnerability · Source |