VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283871 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49026 | suse_vex | SUSE CVE CVE-2022-49026 | known affected: 480 known not affected: 120 recommended: 434 | 2026-07-25T17:17:23+00:00 | Vulnerability · Source |
| CVE-2022-49031 | suse_vex | SUSE CVE CVE-2022-49031 | known affected: 396 known not affected: 151 recommended: 478 | 2026-07-25T17:17:21+00:00 | Vulnerability · Source |
| CVE-2022-49034 | suse_vex | SUSE CVE CVE-2022-49034 | known not affected: 425 | 2026-07-25T17:17:19+00:00 | Vulnerability · Source |
| CVE-2022-49046 | suse_vex | SUSE CVE CVE-2022-49046 | known affected: 602 known not affected: 120 recommended: 26 | 2026-07-25T17:17:17+00:00 | Vulnerability · Source |
| CVE-2022-49047 | suse_vex | SUSE CVE CVE-2022-49047 | known not affected: 352 | 2026-07-25T17:17:16+00:00 | Vulnerability · Source |
| CVE-2022-49051 | suse_vex | SUSE CVE CVE-2022-49051 | known affected: 358 known not affected: 218 recommended: 331 | 2026-07-25T17:17:13+00:00 | Vulnerability · Source |
| CVE-2022-49059 | suse_vex | SUSE CVE CVE-2022-49059 | known affected: 417 known not affected: 193 recommended: 333 | 2026-07-25T17:17:10+00:00 | Vulnerability · Source |
| CVE-2022-49062 | suse_vex | SUSE CVE CVE-2022-49062 | known affected: 364 known not affected: 302 recommended: 100 | 2026-07-25T17:17:08+00:00 | Vulnerability · Source |
| CVE-2022-49063 | suse_vex | SUSE CVE CVE-2022-49063 | known affected: 334 known not affected: 270 recommended: 335 | 2026-07-25T17:17:06+00:00 | Vulnerability · Source |
| CVE-2022-49065 | suse_vex | SUSE CVE CVE-2022-49065 | known affected: 365 known not affected: 213 recommended: 319 | 2026-07-25T17:17:03+00:00 | Vulnerability · Source |
| CVE-2022-49066 | suse_vex | SUSE CVE CVE-2022-49066 | known affected: 452 known not affected: 154 recommended: 305 | 2026-07-25T17:17:01+00:00 | Vulnerability · Source |
| CVE-2022-49072 | suse_vex | SUSE CVE CVE-2022-49072 | known affected: 163 known not affected: 189 recommended: 27 | 2026-07-25T17:16:59+00:00 | Vulnerability · Source |
| CVE-2022-49074 | suse_vex | SUSE CVE CVE-2022-49074 | known affected: 458 known not affected: 186 recommended: 249 | 2026-07-25T17:16:57+00:00 | Vulnerability · Source |
| CVE-2022-49080 | suse_vex | SUSE CVE CVE-2022-49080 | known affected: 438 known not affected: 88 recommended: 447 | 2026-07-25T17:16:54+00:00 | Vulnerability · Source |
| CVE-2022-49081 | suse_vex | SUSE CVE CVE-2022-49081 | known affected: 112 known not affected: 240 recommended: 47 | 2026-07-25T17:16:52+00:00 | Vulnerability · Source |
| CVE-2022-49083 | suse_vex | SUSE CVE CVE-2022-49083 | known affected: 334 known not affected: 270 recommended: 293 | 2026-07-25T17:16:49+00:00 | Vulnerability · Source |
| CVE-2022-49088 | suse_vex | SUSE CVE CVE-2022-49088 | known affected: 385 known not affected: 247 recommended: 223 | 2026-07-25T17:16:47+00:00 | Vulnerability · Source |
| CVE-2022-49089 | suse_vex | SUSE CVE CVE-2022-49089 | known affected: 414 known not affected: 192 recommended: 249 | 2026-07-25T17:16:44+00:00 | Vulnerability · Source |
| CVE-2022-49092 | suse_vex | SUSE CVE CVE-2022-49092 | known not affected: 298 recommended: 163 | 2026-07-25T17:16:42+00:00 | Vulnerability · Source |
| CVE-2022-49095 | suse_vex | SUSE CVE CVE-2022-49095 | known affected: 415 known not affected: 231 recommended: 319 | 2026-07-25T17:16:40+00:00 | Vulnerability · Source |
| CVE-2022-49096 | suse_vex | SUSE CVE CVE-2022-49096 | known affected: 385 known not affected: 247 recommended: 223 | 2026-07-25T17:16:37+00:00 | Vulnerability · Source |
| CVE-2022-49101 | suse_vex | SUSE CVE CVE-2022-49101 | known not affected: 352 | 2026-07-25T17:16:35+00:00 | Vulnerability · Source |
| CVE-2022-49103 | suse_vex | SUSE CVE CVE-2022-49103 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:16:33+00:00 | Vulnerability · Source |
| CVE-2022-49105 | suse_vex | SUSE CVE CVE-2022-49105 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:16:31+00:00 | Vulnerability · Source |
| CVE-2022-49108 | suse_vex | SUSE CVE CVE-2022-49108 | known not affected: 352 | 2026-07-25T17:16:29+00:00 | Vulnerability · Source |
| CVE-2022-49109 | suse_vex | SUSE CVE CVE-2022-49109 | known affected: 470 known not affected: 230 recommended: 271 | 2026-07-25T17:16:26+00:00 | Vulnerability · Source |
| CVE-2022-49110 | suse_vex | SUSE CVE CVE-2022-49110 | known affected: 373 known not affected: 189 recommended: 296 | 2026-07-25T17:16:25+00:00 | Vulnerability · Source |
| CVE-2022-49113 | suse_vex | SUSE CVE CVE-2022-49113 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:16:23+00:00 | Vulnerability · Source |
| CVE-2022-49118 | suse_vex | SUSE CVE CVE-2022-49118 | known affected: 414 known not affected: 230 recommended: 249 | 2026-07-25T17:16:22+00:00 | Vulnerability · Source |
| CVE-2022-49125 | suse_vex | SUSE CVE CVE-2022-49125 | known affected: 364 known not affected: 302 recommended: 100 | 2026-07-25T17:16:20+00:00 | Vulnerability · Source |
| CVE-2022-49129 | suse_vex | SUSE CVE CVE-2022-49129 | known affected: 385 known not affected: 247 recommended: 265 | 2026-07-25T17:16:19+00:00 | Vulnerability · Source |
| CVE-2022-49135 | suse_vex | SUSE CVE CVE-2022-49135 | known affected: 346 known not affected: 260 recommended: 249 | 2026-07-25T17:16:17+00:00 | Vulnerability · Source |
| CVE-2022-49138 | suse_vex | SUSE CVE CVE-2022-49138 | known affected: 490 known not affected: 126 recommended: 251 | 2026-07-25T17:16:16+00:00 | Vulnerability · Source |
| CVE-2022-49144 | suse_vex | SUSE CVE CVE-2022-49144 | known affected: 419 known not affected: 247 recommended: 100 | 2026-07-25T17:16:14+00:00 | Vulnerability · Source |
| CVE-2022-49150 | suse_vex | SUSE CVE CVE-2022-49150 | known not affected: 352 | 2026-07-25T17:16:13+00:00 | Vulnerability · Source |
| CVE-2022-49152 | suse_vex | SUSE CVE CVE-2022-49152 | known not affected: 352 recommended: 22 | 2026-07-25T17:16:11+00:00 | Vulnerability · Source |
| CVE-2022-49154 | suse_vex | SUSE CVE CVE-2022-49154 | known affected: 444 known not affected: 213 recommended: 260 | 2026-07-25T17:16:10+00:00 | Vulnerability · Source |
| CVE-2022-49156 | suse_vex | SUSE CVE CVE-2022-49156 | known affected: 415 known not affected: 163 recommended: 375 | 2026-07-25T17:16:08+00:00 | Vulnerability · Source |
| CVE-2022-49158 | suse_vex | SUSE CVE CVE-2022-49158 | known affected: 395 known not affected: 181 recommended: 375 | 2026-07-25T17:16:07+00:00 | Vulnerability · Source |
| CVE-2022-49160 | suse_vex | SUSE CVE CVE-2022-49160 | known affected: 379 known not affected: 199 recommended: 361 | 2026-07-25T17:16:05+00:00 | Vulnerability · Source |
| CVE-2022-49162 | suse_vex | SUSE CVE CVE-2022-49162 | known affected: 401 known not affected: 199 recommended: 293 | 2026-07-25T17:16:04+00:00 | Vulnerability · Source |
| CVE-2022-49165 | suse_vex | SUSE CVE CVE-2022-49165 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:16:02+00:00 | Vulnerability · Source |
| CVE-2022-49166 | suse_vex | SUSE CVE CVE-2022-49166 | known not affected: 348 | 2026-07-25T17:16:01+00:00 | Vulnerability · Source |
| CVE-2022-49170 | suse_vex | SUSE CVE CVE-2022-49170 | known not affected: 352 | 2026-07-25T17:16:00+00:00 | Vulnerability · Source |
| CVE-2022-49171 | suse_vex | SUSE CVE CVE-2022-49171 | known affected: 475 known not affected: 241 recommended: 40 | 2026-07-25T17:15:58+00:00 | Vulnerability · Source |
| CVE-2022-49173 | suse_vex | SUSE CVE CVE-2022-49173 | known not affected: 348 | 2026-07-25T17:15:57+00:00 | Vulnerability · Source |
| CVE-2022-49174 | suse_vex | SUSE CVE CVE-2022-49174 | known affected: 334 known not affected: 294 recommended: 223 | 2026-07-25T17:15:55+00:00 | Vulnerability · Source |
| CVE-2022-49176 | suse_vex | SUSE CVE CVE-2022-49176 | known affected: 410 known not affected: 230 recommended: 249 | 2026-07-25T17:15:54+00:00 | Vulnerability · Source |
| CVE-2022-49181 | suse_vex | SUSE CVE CVE-2022-49181 | known not affected: 352 | 2026-07-25T17:15:52+00:00 | Vulnerability · Source |
| CVE-2022-49182 | suse_vex | SUSE CVE CVE-2022-49182 | known affected: 414 known not affected: 192 recommended: 249 | 2026-07-25T17:15:51+00:00 | Vulnerability · Source |