VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291704 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2022-49112 | suse_vex | SUSE CVE CVE-2022-49112 | known affected: 385 known not affected: 244 recommended: 223 | 2026-08-14T01:23:20+00:00 | Vulnerability · Source |
| CVE-2022-49118 | suse_vex | SUSE CVE CVE-2022-49118 | known affected: 411 known not affected: 230 recommended: 249 | 2026-08-14T01:23:18+00:00 | Vulnerability · Source |
| CVE-2022-49120 | suse_vex | SUSE CVE CVE-2022-49120 | known affected: 461 known not affected: 142 recommended: 263 | 2026-08-14T01:23:15+00:00 | Vulnerability · Source |
| CVE-2022-49123 | suse_vex | SUSE CVE CVE-2022-49123 | known affected: 419 known not affected: 243 recommended: 142 | 2026-08-14T01:23:13+00:00 | Vulnerability · Source |
| CVE-2022-49126 | suse_vex | SUSE CVE CVE-2022-49126 | known affected: 371 known not affected: 257 recommended: 223 | 2026-08-14T01:23:10+00:00 | Vulnerability · Source |
| CVE-2022-49128 | suse_vex | SUSE CVE CVE-2022-49128 | known affected: 371 known not affected: 257 recommended: 223 | 2026-08-14T01:23:08+00:00 | Vulnerability · Source |
| CVE-2022-49130 | suse_vex | SUSE CVE CVE-2022-49130 | known affected: 334 known not affected: 294 recommended: 265 | 2026-08-14T01:23:03+00:00 | Vulnerability · Source |
| CVE-2022-49132 | suse_vex | SUSE CVE CVE-2022-49132 | known affected: 334 known not affected: 294 recommended: 223 | 2026-08-14T01:23:02+00:00 | Vulnerability · Source |
| CVE-2022-49133 | suse_vex | SUSE CVE CVE-2022-49133 | known affected: 419 known not affected: 243 recommended: 100 | 2026-08-14T01:23:00+00:00 | Vulnerability · Source |
| CVE-2022-49135 | suse_vex | SUSE CVE CVE-2022-49135 | known affected: 346 known not affected: 260 recommended: 249 | 2026-08-14T01:22:59+00:00 | Vulnerability · Source |
| CVE-2022-49137 | suse_vex | SUSE CVE CVE-2022-49137 | known affected: 377 known not affected: 199 recommended: 319 | 2026-08-14T01:22:57+00:00 | Vulnerability · Source |
| CVE-2022-49138 | suse_vex | SUSE CVE CVE-2022-49138 | known affected: 490 known not affected: 126 recommended: 251 | 2026-08-14T01:22:56+00:00 | Vulnerability · Source |
| CVE-2022-49144 | suse_vex | SUSE CVE CVE-2022-49144 | known affected: 419 known not affected: 244 recommended: 100 | 2026-08-14T01:22:54+00:00 | Vulnerability · Source |
| CVE-2022-49148 | suse_vex | SUSE CVE CVE-2022-49148 | known affected: 334 known not affected: 297 recommended: 223 | 2026-08-14T01:22:52+00:00 | Vulnerability · Source |
| CVE-2022-49157 | suse_vex | SUSE CVE CVE-2022-49157 | known affected: 415 known not affected: 163 recommended: 319 | 2026-08-14T01:22:51+00:00 | Vulnerability · Source |
| CVE-2022-49159 | suse_vex | SUSE CVE CVE-2022-49159 | known affected: 381 known not affected: 197 recommended: 319 | 2026-08-14T01:22:49+00:00 | Vulnerability · Source |
| CVE-2022-49162 | suse_vex | SUSE CVE CVE-2022-49162 | known affected: 401 known not affected: 197 recommended: 293 | 2026-08-14T01:22:47+00:00 | Vulnerability · Source |
| CVE-2022-49174 | suse_vex | SUSE CVE CVE-2022-49174 | known affected: 334 known not affected: 293 recommended: 223 | 2026-08-14T01:22:44+00:00 | Vulnerability · Source |
| CVE-2022-49176 | suse_vex | SUSE CVE CVE-2022-49176 | known affected: 410 known not affected: 230 recommended: 249 | 2026-08-14T01:22:42+00:00 | Vulnerability · Source |
| CVE-2022-49180 | suse_vex | SUSE CVE CVE-2022-49180 | known affected: 385 known not affected: 247 recommended: 265 | 2026-08-14T01:22:38+00:00 | Vulnerability · Source |
| CVE-2022-49182 | suse_vex | SUSE CVE CVE-2022-49182 | known affected: 414 known not affected: 192 recommended: 249 | 2026-08-14T01:22:36+00:00 | Vulnerability · Source |
| CVE-2022-49197 | suse_vex | SUSE CVE CVE-2022-49197 | known affected: 630 known not affected: 123 recommended: 40 | 2026-08-14T01:22:33+00:00 | Vulnerability · Source |
| CVE-2022-49205 | suse_vex | SUSE CVE CVE-2022-49205 | known affected: 496 known not affected: 179 recommended: 153 | 2026-08-14T01:22:30+00:00 | Vulnerability · Source |
| CVE-2022-49208 | suse_vex | SUSE CVE CVE-2022-49208 | known affected: 334 known not affected: 294 recommended: 223 | 2026-08-14T01:22:29+00:00 | Vulnerability · Source |
| CVE-2022-49227 | suse_vex | SUSE CVE CVE-2022-49227 | known affected: 334 known not affected: 294 recommended: 265 | 2026-08-14T01:22:27+00:00 | Vulnerability · Source |
| CVE-2022-49241 | suse_vex | SUSE CVE CVE-2022-49241 | known affected: 446 known not affected: 182 recommended: 223 | 2026-08-14T01:22:25+00:00 | Vulnerability · Source |
| CVE-2022-49243 | suse_vex | SUSE CVE CVE-2022-49243 | known affected: 334 known not affected: 268 recommended: 293 | 2026-08-14T01:22:23+00:00 | Vulnerability · Source |
| CVE-2022-49246 | suse_vex | SUSE CVE CVE-2022-49246 | known affected: 385 known not affected: 243 recommended: 223 | 2026-08-14T01:22:21+00:00 | Vulnerability · Source |
| CVE-2022-49258 | suse_vex | SUSE CVE CVE-2022-49258 | known affected: 385 known not affected: 243 recommended: 223 | 2026-08-14T01:22:19+00:00 | Vulnerability · Source |
| CVE-2022-49261 | suse_vex | SUSE CVE CVE-2022-49261 | known affected: 394 known not affected: 268 recommended: 233 | 2026-08-14T01:22:17+00:00 | Vulnerability · Source |
| CVE-2022-49263 | suse_vex | SUSE CVE CVE-2022-49263 | known affected: 348 known not affected: 254 recommended: 335 | 2026-08-14T01:22:15+00:00 | Vulnerability · Source |
| CVE-2022-49268 | suse_vex | SUSE CVE CVE-2022-49268 | known affected: 385 known not affected: 243 recommended: 265 | 2026-08-14T01:22:13+00:00 | Vulnerability · Source |
| CVE-2022-49270 | suse_vex | SUSE CVE CVE-2022-49270 | known affected: 334 known not affected: 295 recommended: 245 | 2026-08-14T01:22:12+00:00 | Vulnerability · Source |
| CVE-2022-49277 | suse_vex | SUSE CVE CVE-2022-49277 | known affected: 377 known not affected: 251 recommended: 223 | 2026-08-14T01:22:10+00:00 | Vulnerability · Source |
| CVE-2022-49281 | suse_vex | SUSE CVE CVE-2022-49281 | known affected: 348 known not affected: 226 recommended: 341 | 2026-08-14T01:22:08+00:00 | Vulnerability · Source |
| CVE-2022-49285 | suse_vex | SUSE CVE CVE-2022-49285 | known affected: 334 known not affected: 264 recommended: 293 | 2026-08-14T01:22:07+00:00 | Vulnerability · Source |
| CVE-2022-49286 | suse_vex | SUSE CVE CVE-2022-49286 | known affected: 432 known not affected: 172 recommended: 249 | 2026-08-14T01:22:05+00:00 | Vulnerability · Source |
| CVE-2022-49294 | suse_vex | SUSE CVE CVE-2022-49294 | known affected: 374 known not affected: 254 recommended: 270 | 2026-08-14T01:22:04+00:00 | Vulnerability · Source |
| CVE-2022-49296 | suse_vex | SUSE CVE CVE-2022-49296 | known affected: 372 known not affected: 411 recommended: 100 | 2026-08-14T01:22:02+00:00 | Vulnerability · Source |
| CVE-2022-49299 | suse_vex | SUSE CVE CVE-2022-49299 | known affected: 409 known not affected: 191 recommended: 293 | 2026-08-14T01:22:01+00:00 | Vulnerability · Source |