VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291314 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-48881 | suse_vex | SUSE CVE CVE-2022-48881 | known affected: 340 known not affected: 249 recommended: 288 | 2026-08-14T01:24:51+00:00 | Vulnerability · Source |
| CVE-2022-48882 | suse_vex | SUSE CVE CVE-2022-48882 | known affected: 340 known not affected: 248 recommended: 288 | 2026-08-14T01:24:50+00:00 | Vulnerability · Source |
| CVE-2022-48891 | suse_vex | SUSE CVE CVE-2022-48891 | known affected: 397 known not affected: 195 recommended: 411 | 2026-08-14T01:24:48+00:00 | Vulnerability · Source |
| CVE-2022-48899 | suse_vex | SUSE CVE CVE-2022-48899 | known affected: 425 known not affected: 78 recommended: 495 | 2026-08-14T01:24:47+00:00 | Vulnerability · Source |
| CVE-2022-48900 | suse_vex | SUSE CVE CVE-2022-48900 | known not affected: 303 | 2026-08-14T01:24:45+00:00 | Vulnerability · Source |
| CVE-2022-48901 | suse_vex | SUSE CVE CVE-2022-48901 | known affected: 404 known not affected: 244 recommended: 417 | 2026-08-14T01:24:44+00:00 | Vulnerability · Source |
| CVE-2022-48914 | suse_vex | SUSE CVE CVE-2022-48914 | known affected: 310 known not affected: 195 recommended: 411 | 2026-08-14T01:24:42+00:00 | Vulnerability · Source |
| CVE-2022-48917 | suse_vex | SUSE CVE CVE-2022-48917 | known affected: 310 known not affected: 191 recommended: 496 | 2026-08-14T01:24:40+00:00 | Vulnerability · Source |
| CVE-2022-48924 | suse_vex | SUSE CVE CVE-2022-48924 | known affected: 359 known not affected: 142 recommended: 411 | 2026-08-14T01:24:38+00:00 | Vulnerability · Source |
| CVE-2022-48930 | suse_vex | SUSE CVE CVE-2022-48930 | known affected: 384 known not affected: 96 recommended: 580 | 2026-08-14T01:24:37+00:00 | Vulnerability · Source |
| CVE-2022-48932 | suse_vex | SUSE CVE CVE-2022-48932 | known affected: 310 known not affected: 195 recommended: 411 | 2026-08-14T01:24:35+00:00 | Vulnerability · Source |
| CVE-2022-48938 | suse_vex | SUSE CVE CVE-2022-48938 | known affected: 421 known not affected: 79 recommended: 495 | 2026-08-14T01:24:33+00:00 | Vulnerability · Source |
| CVE-2022-48943 | suse_vex | SUSE CVE CVE-2022-48943 | known affected: 437 known not affected: 70 recommended: 537 | 2026-08-14T01:24:31+00:00 | Vulnerability · Source |
| CVE-2022-48947 | suse_vex | SUSE CVE CVE-2022-48947 | known affected: 20 known not affected: 222 recommended: 502 | 2026-08-14T01:24:29+00:00 | Vulnerability · Source |
| CVE-2022-48948 | suse_vex | SUSE CVE CVE-2022-48948 | known affected: 451 known not affected: 149 recommended: 394 | 2026-08-14T01:24:28+00:00 | Vulnerability · Source |
| CVE-2022-48954 | suse_vex | SUSE CVE CVE-2022-48954 | known affected: 324 known not affected: 287 recommended: 394 | 2026-08-14T01:24:26+00:00 | Vulnerability · Source |
| CVE-2022-48955 | suse_vex | SUSE CVE CVE-2022-48955 | known affected: 324 known not affected: 289 recommended: 394 | 2026-08-14T01:24:24+00:00 | Vulnerability · Source |
| CVE-2022-48958 | suse_vex | SUSE CVE CVE-2022-48958 | known affected: 354 known not affected: 323 recommended: 311 | 2026-08-14T01:24:22+00:00 | Vulnerability · Source |
| CVE-2022-48962 | suse_vex | SUSE CVE CVE-2022-48962 | known affected: 382 known not affected: 151 recommended: 549 | 2026-08-14T01:24:20+00:00 | Vulnerability · Source |
| CVE-2022-48970 | suse_vex | SUSE CVE CVE-2022-48970 | known not affected: 236 recommended: 453 | 2026-08-14T01:24:18+00:00 | Vulnerability · Source |
| CVE-2022-48979 | suse_vex | SUSE CVE CVE-2022-48979 | known affected: 354 known not affected: 260 recommended: 269 | 2026-08-14T01:24:17+00:00 | Vulnerability · Source |
| CVE-2022-48983 | suse_vex | SUSE CVE CVE-2022-48983 | known affected: 354 known not affected: 340 recommended: 269 | 2026-08-14T01:24:15+00:00 | Vulnerability · Source |
| CVE-2022-48989 | suse_vex | SUSE CVE CVE-2022-48989 | known affected: 354 known not affected: 340 recommended: 312 | 2026-08-14T01:24:13+00:00 | Vulnerability · Source |
| CVE-2022-48990 | suse_vex | SUSE CVE CVE-2022-48990 | known affected: 354 known not affected: 337 recommended: 269 | 2026-08-14T01:24:12+00:00 | Vulnerability · Source |
| CVE-2022-49003 | suse_vex | SUSE CVE CVE-2022-49003 | known affected: 324 known not affected: 204 recommended: 523 | 2026-08-14T01:24:09+00:00 | Vulnerability · Source |
| CVE-2022-49005 | suse_vex | SUSE CVE CVE-2022-49005 | known affected: 324 known not affected: 233 recommended: 394 | 2026-08-14T01:24:08+00:00 | Vulnerability · Source |
| CVE-2022-49007 | suse_vex | SUSE CVE CVE-2022-49007 | known affected: 324 known not affected: 227 recommended: 394 | 2026-08-14T01:24:06+00:00 | Vulnerability · Source |
| CVE-2022-49016 | suse_vex | SUSE CVE CVE-2022-49016 | known affected: 324 known not affected: 289 recommended: 394 | 2026-08-14T01:24:04+00:00 | Vulnerability · Source |
| CVE-2022-49024 | suse_vex | SUSE CVE CVE-2022-49024 | known affected: 324 known not affected: 268 recommended: 435 | 2026-08-14T01:24:02+00:00 | Vulnerability · Source |
| CVE-2022-49026 | suse_vex | SUSE CVE CVE-2022-49026 | known affected: 480 known not affected: 118 recommended: 434 | 2026-08-14T01:24:00+00:00 | Vulnerability · Source |
| CVE-2022-49028 | suse_vex | SUSE CVE CVE-2022-49028 | known affected: 480 known not affected: 70 recommended: 483 | 2026-08-14T01:23:57+00:00 | Vulnerability · Source |
| CVE-2022-49033 | suse_vex | SUSE CVE CVE-2022-49033 | known affected: 649 known not affected: 55 recommended: 150 | 2026-08-14T01:23:56+00:00 | Vulnerability · Source |
| CVE-2022-49044 | suse_vex | SUSE CVE CVE-2022-49044 | known affected: 377 known not affected: 239 recommended: 359 | 2026-08-14T01:23:54+00:00 | Vulnerability · Source |
| CVE-2022-49046 | suse_vex | SUSE CVE CVE-2022-49046 | known affected: 599 known not affected: 120 recommended: 26 | 2026-08-14T01:23:52+00:00 | Vulnerability · Source |
| CVE-2022-49051 | suse_vex | SUSE CVE CVE-2022-49051 | known affected: 358 known not affected: 216 recommended: 331 | 2026-08-14T01:23:50+00:00 | Vulnerability · Source |
| CVE-2022-49058 | suse_vex | SUSE CVE CVE-2022-49058 | known affected: 415 known not affected: 161 recommended: 380 | 2026-08-14T01:23:48+00:00 | Vulnerability · Source |
| CVE-2022-49059 | suse_vex | SUSE CVE CVE-2022-49059 | known affected: 417 known not affected: 191 recommended: 333 | 2026-08-14T01:23:46+00:00 | Vulnerability · Source |
| CVE-2022-49062 | suse_vex | SUSE CVE CVE-2022-49062 | known affected: 364 known not affected: 302 recommended: 100 | 2026-08-14T01:23:44+00:00 | Vulnerability · Source |
| CVE-2022-49066 | suse_vex | SUSE CVE CVE-2022-49066 | known affected: 452 known not affected: 154 recommended: 305 | 2026-08-14T01:23:42+00:00 | Vulnerability · Source |
| CVE-2022-49069 | suse_vex | SUSE CVE CVE-2022-49069 | known not affected: 352 | 2026-08-14T01:23:40+00:00 | Vulnerability · Source |
| CVE-2022-49077 | suse_vex | SUSE CVE CVE-2022-49077 | known not affected: 118 | 2026-08-14T01:23:38+00:00 | Vulnerability · Source |
| CVE-2022-49080 | suse_vex | SUSE CVE CVE-2022-49080 | known affected: 434 known not affected: 88 recommended: 447 | 2026-08-14T01:23:35+00:00 | Vulnerability · Source |
| CVE-2022-49091 | suse_vex | SUSE CVE CVE-2022-49091 | known affected: 381 known not affected: 256 recommended: 293 | 2026-08-14T01:23:33+00:00 | Vulnerability · Source |
| CVE-2022-49096 | suse_vex | SUSE CVE CVE-2022-49096 | known affected: 385 known not affected: 243 recommended: 223 | 2026-08-14T01:23:31+00:00 | Vulnerability · Source |
| CVE-2022-49102 | suse_vex | SUSE CVE CVE-2022-49102 | known affected: 385 known not affected: 243 recommended: 223 | 2026-08-14T01:23:29+00:00 | Vulnerability · Source |
| CVE-2022-49104 | suse_vex | SUSE CVE CVE-2022-49104 | known affected: 334 known not affected: 349 recommended: 223 | 2026-08-14T01:23:28+00:00 | Vulnerability · Source |
| CVE-2022-49105 | suse_vex | SUSE CVE CVE-2022-49105 | known affected: 334 known not affected: 297 recommended: 223 | 2026-08-14T01:23:26+00:00 | Vulnerability · Source |
| CVE-2022-49107 | suse_vex | SUSE CVE CVE-2022-49107 | known affected: 524 known not affected: 82 recommended: 285 | 2026-08-14T01:23:25+00:00 | Vulnerability · Source |
| CVE-2022-49109 | suse_vex | SUSE CVE CVE-2022-49109 | known affected: 470 known not affected: 230 recommended: 271 | 2026-08-14T01:23:23+00:00 | Vulnerability · Source |
| CVE-2022-49111 | suse_vex | SUSE CVE CVE-2022-49111 | known affected: 419 known not affected: 193 recommended: 393 | 2026-08-14T01:23:22+00:00 | Vulnerability · Source |