VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291513 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2022-49309 | suse_vex | SUSE CVE CVE-2022-49309 | known affected: 432 known not affected: 234 recommended: 223 | 2026-08-14T01:21:59+00:00 | Vulnerability · Source |
| CVE-2022-49319 | suse_vex | SUSE CVE CVE-2022-49319 | known affected: 334 known not affected: 266 recommended: 307 | 2026-08-14T01:21:57+00:00 | Vulnerability · Source |
| CVE-2022-49321 | suse_vex | SUSE CVE CVE-2022-49321 | known affected: 365 known not affected: 209 recommended: 348 | 2026-08-14T01:21:56+00:00 | Vulnerability · Source |
| CVE-2022-49322 | suse_vex | SUSE CVE CVE-2022-49322 | known affected: 432 known not affected: 168 recommended: 292 | 2026-08-14T01:21:54+00:00 | Vulnerability · Source |
| CVE-2022-49326 | suse_vex | SUSE CVE CVE-2022-49326 | known affected: 417 known not affected: 155 recommended: 330 | 2026-08-14T01:21:53+00:00 | Vulnerability · Source |
| CVE-2022-49327 | suse_vex | SUSE CVE CVE-2022-49327 | known affected: 409 known not affected: 209 recommended: 293 | 2026-08-14T01:21:51+00:00 | Vulnerability · Source |
| CVE-2022-49329 | suse_vex | SUSE CVE CVE-2022-49329 | known affected: 364 known not affected: 299 recommended: 100 | 2026-08-14T01:21:50+00:00 | Vulnerability · Source |
| CVE-2022-49344 | suse_vex | SUSE CVE CVE-2022-49344 | known affected: 579 known not affected: 141 recommended: 69 | 2026-08-14T01:21:48+00:00 | Vulnerability · Source |
| CVE-2022-49346 | suse_vex | SUSE CVE CVE-2022-49346 | known affected: 385 known not affected: 243 recommended: 223 | 2026-08-14T01:21:46+00:00 | Vulnerability · Source |
| CVE-2022-49350 | suse_vex | SUSE CVE CVE-2022-49350 | known affected: 436 known not affected: 234 recommended: 252 | 2026-08-14T01:21:45+00:00 | Vulnerability · Source |
| CVE-2022-49357 | suse_vex | SUSE CVE CVE-2022-49357 | known affected: 355 known not affected: 243 recommended: 334 | 2026-08-14T01:21:43+00:00 | Vulnerability · Source |
| CVE-2022-49360 | suse_vex | SUSE CVE CVE-2022-49360 | known not affected: 348 | 2026-08-14T01:21:42+00:00 | Vulnerability · Source |
| CVE-2022-49362 | suse_vex | SUSE CVE CVE-2022-49362 | known affected: 364 known not affected: 302 recommended: 127 | 2026-08-14T01:21:40+00:00 | Vulnerability · Source |
| CVE-2022-49365 | suse_vex | SUSE CVE CVE-2022-49365 | known affected: 364 known not affected: 294 recommended: 147 | 2026-08-14T01:21:38+00:00 | Vulnerability · Source |
| CVE-2022-49367 | suse_vex | SUSE CVE CVE-2022-49367 | known affected: 441 known not affected: 164 recommended: 249 | 2026-08-14T01:21:37+00:00 | Vulnerability · Source |
| CVE-2022-49372 | suse_vex | SUSE CVE CVE-2022-49372 | known affected: 570 known not affected: 147 recommended: 87 | 2026-08-14T01:21:35+00:00 | Vulnerability · Source |
| CVE-2022-49375 | suse_vex | SUSE CVE CVE-2022-49375 | known affected: 334 known not affected: 321 recommended: 293 | 2026-08-14T01:21:34+00:00 | Vulnerability · Source |
| CVE-2022-49380 | suse_vex | SUSE CVE CVE-2022-49380 | known not affected: 348 | 2026-08-14T01:21:32+00:00 | Vulnerability · Source |
| CVE-2022-49381 | suse_vex | SUSE CVE CVE-2022-49381 | known affected: 377 known not affected: 254 recommended: 223 | 2026-08-14T01:21:31+00:00 | Vulnerability · Source |
| CVE-2022-49384 | suse_vex | SUSE CVE CVE-2022-49384 | known affected: 334 known not affected: 298 recommended: 223 | 2026-08-14T01:21:29+00:00 | Vulnerability · Source |