VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291994 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-1925 | suse_vex | SUSE CVE CVE-2022-1925 | known affected: 2 known not affected: 10 recommended: 166 | 2026-07-26T23:39:56+00:00 | Vulnerability · Source |
| CVE-2022-2320 | suse_vex | SUSE CVE CVE-2022-2320 | known affected: 401 recommended: 277 | 2026-07-26T23:39:52+00:00 | Vulnerability · Source |
| CVE-2022-20118 | suse_vex | SUSE CVE CVE-2022-20118 | known not affected: 390 | 2026-07-26T23:39:43+00:00 | Vulnerability · Source |
| CVE-2022-23305 | suse_vex | SUSE CVE CVE-2022-23305 | known affected: 395 known not affected: 36 recommended: 351 | 2026-07-26T23:39:38+00:00 | Vulnerability · Source |
| CVE-2022-23481 | suse_vex | SUSE CVE CVE-2022-23481 | known affected: 395 known not affected: 1 recommended: 202 | 2026-07-26T23:39:37+00:00 | Vulnerability · Source |
| CVE-2022-24349 | suse_vex | SUSE CVE CVE-2022-24349 | known affected: 21 recommended: 15 | 2026-07-26T23:39:36+00:00 | Vulnerability · Source |
| CVE-2022-28321 | suse_vex | SUSE CVE CVE-2022-28321 | known not affected: 250 | 2026-07-26T23:39:30+00:00 | Vulnerability · Source |
| CVE-2022-29824 | suse_vex | SUSE CVE CVE-2022-29824 | known affected: 216 known not affected: 60 recommended: 702 | 2026-07-26T23:39:28+00:00 | Vulnerability · Source |
| CVE-2022-36320 | suse_vex | SUSE CVE CVE-2022-36320 | known not affected: 173 recommended: 9 | 2026-07-26T23:39:22+00:00 | Vulnerability · Source |
| CVE-2022-40090 | suse_vex | SUSE CVE CVE-2022-40090 | known affected: 454 recommended: 141 | 2026-07-26T23:39:19+00:00 | Vulnerability · Source |
| CVE-2022-48649 | suse_vex | SUSE CVE CVE-2022-48649 | known not affected: 288 | 2026-07-26T23:39:15+00:00 | Vulnerability · Source |
| CVE-2022-48782 | suse_vex | SUSE CVE CVE-2022-48782 | known not affected: 318 | 2026-07-26T23:39:12+00:00 | Vulnerability · Source |
| CVE-2022-48802 | suse_vex | SUSE CVE CVE-2022-48802 | known not affected: 359 recommended: 456 | 2026-07-26T23:39:10+00:00 | Vulnerability · Source |
| CVE-2022-48965 | suse_vex | SUSE CVE CVE-2022-48965 | known not affected: 365 | 2026-07-26T23:39:02+00:00 | Vulnerability · Source |
| CVE-2022-49070 | suse_vex | SUSE CVE CVE-2022-49070 | known affected: 364 known not affected: 302 recommended: 127 | 2026-07-26T23:38:57+00:00 | Vulnerability · Source |
| CVE-2022-49284 | suse_vex | SUSE CVE CVE-2022-49284 | known not affected: 352 | 2026-07-26T23:38:46+00:00 | Vulnerability · Source |
| CVE-2022-49307 | suse_vex | SUSE CVE CVE-2022-49307 | known affected: 340 known not affected: 264 recommended: 293 | 2026-07-26T23:38:44+00:00 | Vulnerability · Source |
| CVE-2022-49461 | suse_vex | SUSE CVE CVE-2022-49461 | known not affected: 352 | 2026-07-26T23:38:36+00:00 | Vulnerability · Source |
| CVE-2022-49539 | suse_vex | SUSE CVE CVE-2022-49539 | known affected: 112 known not affected: 240 recommended: 47 | 2026-07-26T23:38:31+00:00 | Vulnerability · Source |
| CVE-2022-49574 | suse_vex | SUSE CVE CVE-2022-49574 | known not affected: 147 recommended: 27 | 2026-07-26T23:38:26+00:00 | Vulnerability · Source |
| CVE-2022-49895 | suse_vex | SUSE CVE CVE-2022-49895 | known not affected: 397 | 2026-07-26T23:38:10+00:00 | Vulnerability · Source |
| CVE-2022-49900 | suse_vex | SUSE CVE CVE-2022-49900 | known affected: 339 known not affected: 294 recommended: 214 | 2026-07-26T23:38:08+00:00 | Vulnerability · Source |
| CVE-2022-49901 | suse_vex | SUSE CVE CVE-2022-49901 | known affected: 475 known not affected: 237 recommended: 92 | 2026-07-26T23:38:06+00:00 | Vulnerability · Source |
| CVE-2022-49972 | suse_vex | SUSE CVE CVE-2022-49972 | known affected: 369 known not affected: 347 recommended: 92 | 2026-07-26T23:38:04+00:00 | Vulnerability · Source |
| CVE-2022-50017 | suse_vex | SUSE CVE CVE-2022-50017 | known not affected: 401 | 2026-07-26T23:38:02+00:00 | Vulnerability · Source |
| CVE-2022-50220 | suse_vex | SUSE CVE CVE-2022-50220 | known affected: 425 known not affected: 248 recommended: 310 | 2026-07-26T23:37:53+00:00 | Vulnerability · Source |
| CVE-2022-50299 | suse_vex | SUSE CVE CVE-2022-50299 | known affected: 391 known not affected: 186 recommended: 369 | 2026-07-26T23:37:51+00:00 | Vulnerability · Source |
| CVE-2022-50369 | suse_vex | SUSE CVE CVE-2022-50369 | known affected: 401 known not affected: 286 recommended: 255 | 2026-07-26T23:37:46+00:00 | Vulnerability · Source |
| CVE-2022-50486 | suse_vex | SUSE CVE CVE-2022-50486 | known not affected: 416 | 2026-07-26T23:37:42+00:00 | Vulnerability · Source |
| CVE-2022-50669 | suse_vex | SUSE CVE CVE-2022-50669 | known affected: 403 known not affected: 247 recommended: 196 | 2026-07-26T23:37:37+00:00 | Vulnerability · Source |
| CVE-2022-50738 | suse_vex | SUSE CVE CVE-2022-50738 | known affected: 374 known not affected: 391 recommended: 114 | 2026-07-26T23:37:34+00:00 | Vulnerability · Source |
| CVE-2022-50832 | suse_vex | SUSE CVE CVE-2022-50832 | known affected: 502 known not affected: 195 recommended: 225 | 2026-07-26T23:37:32+00:00 | Vulnerability · Source |
| CVE-2022-50835 | suse_vex | SUSE CVE CVE-2022-50835 | known affected: 354 known not affected: 341 recommended: 223 | 2026-07-26T23:37:31+00:00 | Vulnerability · Source |
| CVE-2023-0615 | suse_vex | SUSE CVE CVE-2023-0615 | known not affected: 272 | 2026-07-26T23:37:28+00:00 | Vulnerability · Source |
| CVE-2023-25363 | suse_vex | SUSE CVE CVE-2023-25363 | known not affected: 122 recommended: 851 | 2026-07-26T23:37:10+00:00 | Vulnerability · Source |
| CVE-2023-26931 | suse_vex | SUSE CVE CVE-2023-26931 | known not affected: 351 | 2026-07-26T23:37:08+00:00 | Vulnerability · Source |
| CVE-2023-26935 | suse_vex | SUSE CVE CVE-2023-26935 | known not affected: 351 | 2026-07-26T23:37:07+00:00 | Vulnerability · Source |
| CVE-2023-32257 | suse_vex | SUSE CVE CVE-2023-32257 | known not affected: 416 | 2026-07-26T23:37:03+00:00 | Vulnerability · Source |
| CVE-2023-43010 | suse_vex | SUSE CVE CVE-2023-43010 | known affected: 88 recommended: 524 | 2026-07-26T23:36:59+00:00 | Vulnerability · Source |
| CVE-2023-52706 | suse_vex | SUSE CVE CVE-2023-52706 | known not affected: 330 | 2026-07-26T23:36:46+00:00 | Vulnerability · Source |
| CVE-2023-52802 | suse_vex | SUSE CVE CVE-2023-52802 | known not affected: 324 recommended: 42 | 2026-07-26T23:36:44+00:00 | Vulnerability · Source |
| CVE-2023-52909 | suse_vex | SUSE CVE CVE-2023-52909 | known affected: 340 known not affected: 248 recommended: 288 | 2026-07-26T23:36:40+00:00 | Vulnerability · Source |
| CVE-2023-52983 | suse_vex | SUSE CVE CVE-2023-52983 | known affected: 334 known not affected: 243 recommended: 226 | 2026-07-26T23:36:38+00:00 | Vulnerability · Source |
| CVE-2023-53186 | suse_vex | SUSE CVE CVE-2023-53186 | known affected: 55 known not affected: 361 | 2026-07-26T23:36:34+00:00 | Vulnerability · Source |
| CVE-2023-53202 | suse_vex | SUSE CVE CVE-2023-53202 | known affected: 112 known not affected: 304 recommended: 49 | 2026-07-26T23:36:32+00:00 | Vulnerability · Source |
| CVE-2023-53203 | suse_vex | SUSE CVE CVE-2023-53203 | known not affected: 416 | 2026-07-26T23:36:31+00:00 | Vulnerability · Source |
| CVE-2023-53381 | suse_vex | SUSE CVE CVE-2023-53381 | known affected: 344 known not affected: 304 recommended: 233 | 2026-07-26T23:36:28+00:00 | Vulnerability · Source |
| CVE-2023-53439 | suse_vex | SUSE CVE CVE-2023-53439 | known not affected: 416 | 2026-07-26T23:36:27+00:00 | Vulnerability · Source |
| CVE-2023-53473 | suse_vex | SUSE CVE CVE-2023-53473 | known affected: 395 known not affected: 253 recommended: 235 | 2026-07-26T23:36:25+00:00 | Vulnerability · Source |
| CVE-2023-53498 | suse_vex | SUSE CVE CVE-2023-53498 | known affected: 381 known not affected: 267 recommended: 206 | 2026-07-26T23:36:23+00:00 | Vulnerability · Source |