VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283990 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-50160 | suse_vex | SUSE CVE CVE-2022-50160 | known affected: 405 known not affected: 248 recommended: 273 | 2026-07-25T17:08:53+00:00 | Vulnerability · Source |
| CVE-2022-50163 | suse_vex | SUSE CVE CVE-2022-50163 | known affected: 92 known not affected: 309 | 2026-07-25T17:08:51+00:00 | Vulnerability · Source |
| CVE-2022-50165 | suse_vex | SUSE CVE CVE-2022-50165 | known affected: 405 known not affected: 246 recommended: 273 | 2026-07-25T17:08:50+00:00 | Vulnerability · Source |
| CVE-2022-50172 | suse_vex | SUSE CVE CVE-2022-50172 | known affected: 358 known not affected: 280 recommended: 320 | 2026-07-25T17:08:48+00:00 | Vulnerability · Source |
| CVE-2022-50174 | suse_vex | SUSE CVE CVE-2022-50174 | known affected: 106 known not affected: 295 | 2026-07-25T17:08:47+00:00 | Vulnerability · Source |
| CVE-2022-50175 | suse_vex | SUSE CVE CVE-2022-50175 | known affected: 442 known not affected: 215 recommended: 206 | 2026-07-25T17:08:46+00:00 | Vulnerability · Source |
| CVE-2022-50184 | suse_vex | SUSE CVE CVE-2022-50184 | known affected: 424 known not affected: 292 recommended: 92 | 2026-07-25T17:08:44+00:00 | Vulnerability · Source |
| CVE-2022-50186 | suse_vex | SUSE CVE CVE-2022-50186 | known affected: 369 known not affected: 347 recommended: 92 | 2026-07-25T17:08:43+00:00 | Vulnerability · Source |
| CVE-2022-50187 | suse_vex | SUSE CVE CVE-2022-50187 | known affected: 344 known not affected: 298 recommended: 248 | 2026-07-25T17:08:41+00:00 | Vulnerability · Source |
| CVE-2022-50194 | suse_vex | SUSE CVE CVE-2022-50194 | known affected: 344 known not affected: 298 recommended: 233 | 2026-07-25T17:08:39+00:00 | Vulnerability · Source |
| CVE-2022-50195 | suse_vex | SUSE CVE CVE-2022-50195 | known affected: 55 known not affected: 346 | 2026-07-25T17:08:38+00:00 | Vulnerability · Source |
| CVE-2022-50196 | suse_vex | SUSE CVE CVE-2022-50196 | known affected: 344 known not affected: 298 recommended: 233 | 2026-07-25T17:08:37+00:00 | Vulnerability · Source |
| CVE-2022-50198 | suse_vex | SUSE CVE CVE-2022-50198 | known affected: 348 known not affected: 309 recommended: 206 | 2026-07-25T17:08:35+00:00 | Vulnerability · Source |
| CVE-2022-50201 | suse_vex | SUSE CVE CVE-2022-50201 | known affected: 344 known not affected: 298 recommended: 235 | 2026-07-25T17:08:34+00:00 | Vulnerability · Source |
| CVE-2022-50203 | suse_vex | SUSE CVE CVE-2022-50203 | known affected: 348 known not affected: 309 recommended: 206 | 2026-07-25T17:08:32+00:00 | Vulnerability · Source |
| CVE-2022-50204 | suse_vex | SUSE CVE CVE-2022-50204 | known affected: 344 known not affected: 298 recommended: 206 | 2026-07-25T17:08:31+00:00 | Vulnerability · Source |
| CVE-2022-50205 | suse_vex | SUSE CVE CVE-2022-50205 | known affected: 245 known not affected: 171 | 2026-07-25T17:08:30+00:00 | Vulnerability · Source |
| CVE-2022-50206 | suse_vex | SUSE CVE CVE-2022-50206 | known affected: 442 known not affected: 189 recommended: 256 | 2026-07-25T17:08:28+00:00 | Vulnerability · Source |
| CVE-2022-50211 | suse_vex | SUSE CVE CVE-2022-50211 | known affected: 400 known not affected: 316 recommended: 397 | 2026-07-25T17:08:27+00:00 | Vulnerability · Source |
| CVE-2022-50212 | suse_vex | SUSE CVE CVE-2022-50212 | known not affected: 294 recommended: 245 | 2026-07-25T17:08:25+00:00 | Vulnerability · Source |
| CVE-2022-50213 | suse_vex | SUSE CVE CVE-2022-50213 | known affected: 44 known not affected: 220 recommended: 314 | 2026-07-25T17:08:24+00:00 | Vulnerability · Source |
| CVE-2022-50215 | suse_vex | SUSE CVE CVE-2022-50215 | known affected: 425 known not affected: 248 recommended: 337 | 2026-07-25T17:08:22+00:00 | Vulnerability · Source |
| CVE-2022-50219 | suse_vex | SUSE CVE CVE-2022-50219 | known affected: 92 known not affected: 309 recommended: 47 | 2026-07-25T17:08:21+00:00 | Vulnerability · Source |
| CVE-2022-50221 | suse_vex | SUSE CVE CVE-2022-50221 | known affected: 369 known not affected: 347 recommended: 139 | 2026-07-25T17:08:19+00:00 | Vulnerability · Source |
| CVE-2022-50222 | suse_vex | SUSE CVE CVE-2022-50222 | known affected: 358 known not affected: 280 recommended: 273 | 2026-07-25T17:08:18+00:00 | Vulnerability · Source |
| CVE-2022-50223 | suse_vex | SUSE CVE CVE-2022-50223 | known not affected: 401 | 2026-07-25T17:08:17+00:00 | Vulnerability · Source |
| CVE-2022-50226 | suse_vex | SUSE CVE CVE-2022-50226 | known affected: 446 known not affected: 185 recommended: 276 | 2026-07-25T17:08:15+00:00 | Vulnerability · Source |
| CVE-2022-50228 | suse_vex | SUSE CVE CVE-2022-50228 | known affected: 472 known not affected: 205 recommended: 290 | 2026-07-25T17:08:14+00:00 | Vulnerability · Source |
| CVE-2022-50230 | suse_vex | SUSE CVE CVE-2022-50230 | known not affected: 401 | 2026-07-25T17:08:12+00:00 | Vulnerability · Source |
| CVE-2022-50231 | suse_vex | SUSE CVE CVE-2022-50231 | known affected: 358 known not affected: 280 recommended: 273 | 2026-07-25T17:08:11+00:00 | Vulnerability · Source |
| CVE-2022-50235 | suse_vex | SUSE CVE CVE-2022-50235 | known not affected: 233 recommended: 319 | 2026-07-25T17:08:09+00:00 | Vulnerability · Source |
| CVE-2022-50236 | suse_vex | SUSE CVE CVE-2022-50236 | known affected: 604 known not affected: 176 recommended: 23 | 2026-07-25T17:08:08+00:00 | Vulnerability · Source |
| CVE-2022-50240 | suse_vex | SUSE CVE CVE-2022-50240 | known not affected: 416 | 2026-07-25T17:08:07+00:00 | Vulnerability · Source |
| CVE-2022-50243 | suse_vex | SUSE CVE CVE-2022-50243 | known affected: 112 known not affected: 304 recommended: 47 | 2026-07-25T17:08:05+00:00 | Vulnerability · Source |
| CVE-2022-50244 | suse_vex | SUSE CVE CVE-2022-50244 | known affected: 604 known not affected: 176 recommended: 23 | 2026-07-25T17:08:04+00:00 | Vulnerability · Source |
| CVE-2022-50253 | suse_vex | SUSE CVE CVE-2022-50253 | first fixed: 2 known affected: 615 known not affected: 22 recommended: 523 | 2026-07-25T17:08:02+00:00 | Vulnerability · Source |
| CVE-2022-50254 | suse_vex | SUSE CVE CVE-2022-50254 | known not affected: 416 | 2026-07-25T17:08:01+00:00 | Vulnerability · Source |
| CVE-2022-50259 | suse_vex | SUSE CVE CVE-2022-50259 | known affected: 163 known not affected: 253 | 2026-07-25T17:08:00+00:00 | Vulnerability · Source |
| CVE-2022-50260 | suse_vex | SUSE CVE CVE-2022-50260 | known affected: 344 known not affected: 267 recommended: 273 | 2026-07-25T17:07:58+00:00 | Vulnerability · Source |
| CVE-2022-50262 | suse_vex | SUSE CVE CVE-2022-50262 | known not affected: 416 | 2026-07-25T17:07:57+00:00 | Vulnerability · Source |
| CVE-2022-50269 | suse_vex | SUSE CVE CVE-2022-50269 | known affected: 344 known not affected: 304 recommended: 255 | 2026-07-25T17:07:55+00:00 | Vulnerability · Source |
| CVE-2022-50271 | suse_vex | SUSE CVE CVE-2022-50271 | known affected: 405 known not affected: 176 recommended: 343 | 2026-07-25T17:07:54+00:00 | Vulnerability · Source |
| CVE-2022-50272 | suse_vex | SUSE CVE CVE-2022-50272 | known affected: 75 known not affected: 181 recommended: 316 | 2026-07-25T17:07:52+00:00 | Vulnerability · Source |
| CVE-2022-50273 | suse_vex | SUSE CVE CVE-2022-50273 | known affected: 169 known not affected: 286 | 2026-07-25T17:07:51+00:00 | Vulnerability · Source |
| CVE-2022-50279 | suse_vex | SUSE CVE CVE-2022-50279 | known affected: 344 known not affected: 304 recommended: 255 | 2026-07-25T17:07:50+00:00 | Vulnerability · Source |
| CVE-2022-50280 | suse_vex | SUSE CVE CVE-2022-50280 | known affected: 430 known not affected: 187 recommended: 308 | 2026-07-25T17:07:48+00:00 | Vulnerability · Source |
| CVE-2022-50285 | suse_vex | SUSE CVE CVE-2022-50285 | known affected: 567 known not affected: 244 recommended: 64 | 2026-07-25T17:07:47+00:00 | Vulnerability · Source |
| CVE-2022-50287 | suse_vex | SUSE CVE CVE-2022-50287 | known affected: 369 known not affected: 359 recommended: 141 | 2026-07-25T17:07:45+00:00 | Vulnerability · Source |
| CVE-2022-50292 | suse_vex | SUSE CVE CVE-2022-50292 | known affected: 369 known not affected: 359 recommended: 92 | 2026-07-25T17:07:44+00:00 | Vulnerability · Source |
| CVE-2022-50293 | suse_vex | SUSE CVE CVE-2022-50293 | known affected: 604 known not affected: 174 recommended: 37 | 2026-07-25T17:07:42+00:00 | Vulnerability · Source |