VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
287117 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49055 | suse_vex | SUSE CVE CVE-2022-49055 | known affected: 421 known not affected: 193 recommended: 333 | 2026-07-31T01:31:34+00:00 | Vulnerability · Source |
| CVE-2022-49115 | suse_vex | SUSE CVE CVE-2022-49115 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-31T01:31:32+00:00 | Vulnerability · Source |
| CVE-2022-49142 | suse_vex | SUSE CVE CVE-2022-49142 | known affected: 55 known not affected: 297 recommended: 22 | 2026-07-31T01:31:29+00:00 | Vulnerability · Source |
| CVE-2022-49145 | suse_vex | SUSE CVE CVE-2022-49145 | known affected: 421 known not affected: 232 recommended: 411 | 2026-07-31T01:31:27+00:00 | Vulnerability · Source |
| CVE-2022-49146 | suse_vex | SUSE CVE CVE-2022-49146 | known not affected: 352 | 2026-07-31T01:31:25+00:00 | Vulnerability · Source |
| CVE-2022-49202 | suse_vex | SUSE CVE CVE-2022-49202 | known affected: 364 known not affected: 302 recommended: 100 | 2026-07-31T01:31:22+00:00 | Vulnerability · Source |
| CVE-2022-49383 | suse_vex | SUSE CVE CVE-2022-49383 | known not affected: 352 | 2026-07-31T01:31:19+00:00 | Vulnerability · Source |
| CVE-2022-49422 | suse_vex | SUSE CVE CVE-2022-49422 | known affected: 334 known not affected: 270 recommended: 293 | 2026-07-31T01:31:17+00:00 | Vulnerability · Source |
| CVE-2022-49497 | suse_vex | SUSE CVE CVE-2022-49497 | known affected: 545 known not affected: 91 recommended: 140 | 2026-07-31T01:31:15+00:00 | Vulnerability · Source |
| CVE-2022-49512 | suse_vex | SUSE CVE CVE-2022-49512 | known affected: 385 known not affected: 247 recommended: 223 | 2026-07-31T01:31:11+00:00 | Vulnerability · Source |
| CVE-2022-49567 | suse_vex | SUSE CVE CVE-2022-49567 | known affected: 268 known not affected: 82 recommended: 29 | 2026-07-31T01:31:06+00:00 | Vulnerability · Source |
| CVE-2022-49580 | suse_vex | SUSE CVE CVE-2022-49580 | known not affected: 163 recommended: 27 | 2026-07-31T01:31:04+00:00 | Vulnerability · Source |
| CVE-2022-49632 | suse_vex | SUSE CVE CVE-2022-49632 | known not affected: 141 recommended: 27 | 2026-07-31T01:31:01+00:00 | Vulnerability · Source |
| CVE-2022-49679 | suse_vex | SUSE CVE CVE-2022-49679 | known affected: 334 known not affected: 349 recommended: 223 | 2026-07-31T01:30:59+00:00 | Vulnerability · Source |
| CVE-2022-49825 | suse_vex | SUSE CVE CVE-2022-49825 | known affected: 424 known not affected: 168 recommended: 318 | 2026-07-31T01:30:56+00:00 | Vulnerability · Source |
| CVE-2022-49904 | suse_vex | SUSE CVE CVE-2022-49904 | known not affected: 397 | 2026-07-31T01:30:53+00:00 | Vulnerability · Source |
| CVE-2022-49955 | suse_vex | SUSE CVE CVE-2022-49955 | known not affected: 401 | 2026-07-31T01:30:51+00:00 | Vulnerability · Source |
| CVE-2022-50029 | suse_vex | SUSE CVE CVE-2022-50029 | known affected: 358 known not affected: 280 recommended: 300 | 2026-07-31T01:30:49+00:00 | Vulnerability · Source |
| CVE-2022-50043 | suse_vex | SUSE CVE CVE-2022-50043 | known affected: 55 known not affected: 346 | 2026-07-31T01:30:47+00:00 | Vulnerability · Source |
| CVE-2022-50128 | suse_vex | SUSE CVE CVE-2022-50128 | known not affected: 401 | 2026-07-31T01:30:45+00:00 | Vulnerability · Source |
| CVE-2022-50217 | suse_vex | SUSE CVE CVE-2022-50217 | known not affected: 401 | 2026-07-31T01:30:43+00:00 | Vulnerability · Source |
| CVE-2022-50246 | suse_vex | SUSE CVE CVE-2022-50246 | known affected: 395 known not affected: 253 recommended: 255 | 2026-07-31T01:30:41+00:00 | Vulnerability · Source |
| CVE-2022-50289 | suse_vex | SUSE CVE CVE-2022-50289 | known affected: 462 known not affected: 154 recommended: 229 | 2026-07-31T01:30:38+00:00 | Vulnerability · Source |
| CVE-2022-50297 | suse_vex | SUSE CVE CVE-2022-50297 | known affected: 470 known not affected: 187 recommended: 278 | 2026-07-31T01:30:37+00:00 | Vulnerability · Source |
| CVE-2022-50316 | suse_vex | SUSE CVE CVE-2022-50316 | known affected: 210 known not affected: 176 | 2026-07-31T01:30:35+00:00 | Vulnerability · Source |
| CVE-2022-50317 | suse_vex | SUSE CVE CVE-2022-50317 | known affected: 344 known not affected: 267 recommended: 322 | 2026-07-31T01:30:33+00:00 | Vulnerability · Source |
| CVE-2022-50357 | suse_vex | SUSE CVE CVE-2022-50357 | known affected: 424 known not affected: 304 recommended: 121 | 2026-07-31T01:30:31+00:00 | Vulnerability · Source |
| CVE-2022-50442 | suse_vex | SUSE CVE CVE-2022-50442 | known not affected: 416 | 2026-07-31T01:30:26+00:00 | Vulnerability · Source |
| CVE-2022-50470 | suse_vex | SUSE CVE CVE-2022-50470 | known affected: 435 known not affected: 184 recommended: 345 | 2026-07-31T01:30:24+00:00 | Vulnerability · Source |
| CVE-2022-50491 | suse_vex | SUSE CVE CVE-2022-50491 | known affected: 149 known not affected: 267 recommended: 43 | 2026-07-31T01:30:22+00:00 | Vulnerability · Source |
| CVE-2022-50503 | suse_vex | SUSE CVE CVE-2022-50503 | known affected: 354 known not affected: 304 recommended: 196 | 2026-07-31T01:30:20+00:00 | Vulnerability · Source |
| CVE-2022-50541 | suse_vex | SUSE CVE CVE-2022-50541 | known affected: 354 known not affected: 304 recommended: 196 | 2026-07-31T01:30:19+00:00 | Vulnerability · Source |
| CVE-2022-50547 | suse_vex | SUSE CVE CVE-2022-50547 | known affected: 4 known not affected: 412 | 2026-07-31T01:30:17+00:00 | Vulnerability · Source |
| CVE-2022-50628 | suse_vex | SUSE CVE CVE-2022-50628 | known affected: 112 known not affected: 296 recommended: 49 | 2026-07-31T01:30:15+00:00 | Vulnerability · Source |
| CVE-2022-50661 | suse_vex | SUSE CVE CVE-2022-50661 | known affected: 354 known not affected: 296 recommended: 223 | 2026-07-31T01:30:13+00:00 | Vulnerability · Source |
| CVE-2022-50672 | suse_vex | SUSE CVE CVE-2022-50672 | known affected: 403 known not affected: 247 recommended: 196 | 2026-07-31T01:30:11+00:00 | Vulnerability · Source |
| CVE-2022-50781 | suse_vex | SUSE CVE CVE-2022-50781 | known affected: 409 known not affected: 254 recommended: 245 | 2026-07-31T01:30:09+00:00 | Vulnerability · Source |
| CVE-2022-50830 | suse_vex | SUSE CVE CVE-2022-50830 | known affected: 354 known not affected: 336 recommended: 196 | 2026-07-31T01:30:07+00:00 | Vulnerability · Source |
| CVE-2022-50869 | suse_vex | SUSE CVE CVE-2022-50869 | known not affected: 453 | 2026-07-31T01:30:05+00:00 | Vulnerability · Source |
| CVE-2023-0030 | suse_vex | SUSE CVE CVE-2023-0030 | known not affected: 402 | 2026-07-31T01:30:04+00:00 | Vulnerability · Source |
| CVE-2023-0179 | suse_vex | SUSE CVE CVE-2023-0179 | known affected: 247 known not affected: 283 recommended: 1278 | 2026-07-31T01:30:02+00:00 | Vulnerability · Source |
| CVE-2023-1073 | suse_vex | SUSE CVE CVE-2023-1073 | known not affected: 259 recommended: 49 | 2026-07-31T01:29:59+00:00 | Vulnerability · Source |
| CVE-2023-1074 | suse_vex | SUSE CVE CVE-2023-1074 | known affected: 402 known not affected: 287 recommended: 72 | 2026-07-31T01:29:58+00:00 | Vulnerability · Source |
| CVE-2023-1075 | suse_vex | SUSE CVE CVE-2023-1075 | known affected: 285 known not affected: 362 recommended: 1063 | 2026-07-31T01:29:56+00:00 | Vulnerability · Source |
| CVE-2023-1076 | suse_vex | SUSE CVE CVE-2023-1076 | known affected: 287 known not affected: 265 recommended: 1253 | 2026-07-31T01:29:54+00:00 | Vulnerability · Source |
| CVE-2023-1193 | suse_vex | SUSE CVE CVE-2023-1193 | known not affected: 519 | 2026-07-31T01:29:52+00:00 | Vulnerability · Source |
| CVE-2023-1281 | suse_vex | SUSE CVE CVE-2023-1281 | known affected: 290 known not affected: 129 recommended: 1201 | 2026-07-31T01:29:51+00:00 | Vulnerability · Source |
| CVE-2023-1390 | suse_vex | SUSE CVE CVE-2023-1390 | known affected: 385 known not affected: 104 recommended: 636 | 2026-07-31T01:29:49+00:00 | Vulnerability · Source |
| CVE-2023-1838 | suse_vex | SUSE CVE CVE-2023-1838 | known affected: 290 known not affected: 154 recommended: 1058 | 2026-07-31T01:29:44+00:00 | Vulnerability · Source |
| CVE-2023-1994 | suse_vex | SUSE CVE CVE-2023-1994 | known affected: 41 known not affected: 74 recommended: 264 | 2026-07-31T01:29:42+00:00 | Vulnerability · Source |