VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283924 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49804 | suse_vex | SUSE CVE CVE-2022-49804 | known not affected: 402 recommended: 43 | 2026-07-25T17:11:08+00:00 | Vulnerability · Source |
| CVE-2022-49812 | suse_vex | SUSE CVE CVE-2022-49812 | known affected: 390 known not affected: 248 recommended: 214 | 2026-07-25T17:11:06+00:00 | Vulnerability · Source |
| CVE-2022-49817 | suse_vex | SUSE CVE CVE-2022-49817 | known affected: 112 known not affected: 285 | 2026-07-25T17:11:04+00:00 | Vulnerability · Source |
| CVE-2022-49821 | suse_vex | SUSE CVE CVE-2022-49821 | known affected: 424 known not affected: 153 recommended: 318 | 2026-07-25T17:11:03+00:00 | Vulnerability · Source |
| CVE-2022-49830 | suse_vex | SUSE CVE CVE-2022-49830 | known affected: 339 known not affected: 271 recommended: 281 | 2026-07-25T17:11:02+00:00 | Vulnerability · Source |
| CVE-2022-49831 | suse_vex | SUSE CVE CVE-2022-49831 | known affected: 210 known not affected: 157 | 2026-07-25T17:11:00+00:00 | Vulnerability · Source |
| CVE-2022-49832 | suse_vex | SUSE CVE CVE-2022-49832 | known affected: 418 known not affected: 161 recommended: 304 | 2026-07-25T17:10:59+00:00 | Vulnerability · Source |
| CVE-2022-49833 | suse_vex | SUSE CVE CVE-2022-49833 | known affected: 245 known not affected: 135 | 2026-07-25T17:10:57+00:00 | Vulnerability · Source |
| CVE-2022-49835 | suse_vex | SUSE CVE CVE-2022-49835 | known affected: 418 known not affected: 174 recommended: 318 | 2026-07-25T17:10:56+00:00 | Vulnerability · Source |
| CVE-2022-49838 | suse_vex | SUSE CVE CVE-2022-49838 | known not affected: 402 | 2026-07-25T17:10:55+00:00 | Vulnerability · Source |
| CVE-2022-49840 | suse_vex | SUSE CVE CVE-2022-49840 | known affected: 612 known not affected: 157 recommended: 23 | 2026-07-25T17:10:53+00:00 | Vulnerability · Source |
| CVE-2022-49851 | suse_vex | SUSE CVE CVE-2022-49851 | known not affected: 402 | 2026-07-25T17:10:52+00:00 | Vulnerability · Source |
| CVE-2022-49853 | suse_vex | SUSE CVE CVE-2022-49853 | known affected: 441 known not affected: 166 recommended: 284 | 2026-07-25T17:10:50+00:00 | Vulnerability · Source |
| CVE-2022-49861 | suse_vex | SUSE CVE CVE-2022-49861 | known affected: 404 known not affected: 175 recommended: 304 | 2026-07-25T17:10:49+00:00 | Vulnerability · Source |
| CVE-2022-49863 | suse_vex | SUSE CVE CVE-2022-49863 | known affected: 339 known not affected: 299 recommended: 214 | 2026-07-25T17:10:47+00:00 | Vulnerability · Source |
| CVE-2022-49873 | suse_vex | SUSE CVE CVE-2022-49873 | known affected: 106 known not affected: 291 recommended: 29 | 2026-07-25T17:10:46+00:00 | Vulnerability · Source |
| CVE-2022-49874 | suse_vex | SUSE CVE CVE-2022-49874 | known affected: 455 known not affected: 165 recommended: 251 | 2026-07-25T17:10:45+00:00 | Vulnerability · Source |
| CVE-2022-49879 | suse_vex | SUSE CVE CVE-2022-49879 | known affected: 424 known not affected: 168 recommended: 318 | 2026-07-25T17:10:43+00:00 | Vulnerability · Source |
| CVE-2022-49881 | suse_vex | SUSE CVE CVE-2022-49881 | known affected: 374 known not affected: 220 recommended: 304 | 2026-07-25T17:10:42+00:00 | Vulnerability · Source |
| CVE-2022-49892 | suse_vex | SUSE CVE CVE-2022-49892 | known affected: 414 known not affected: 178 recommended: 318 | 2026-07-25T17:10:40+00:00 | Vulnerability · Source |
| CVE-2022-49896 | suse_vex | SUSE CVE CVE-2022-49896 | known not affected: 397 | 2026-07-25T17:10:39+00:00 | Vulnerability · Source |
| CVE-2022-49898 | suse_vex | SUSE CVE CVE-2022-49898 | known affected: 565 known not affected: 198 recommended: 37 | 2026-07-25T17:10:37+00:00 | Vulnerability · Source |
| CVE-2022-49899 | suse_vex | SUSE CVE CVE-2022-49899 | known affected: 55 known not affected: 342 | 2026-07-25T17:10:36+00:00 | Vulnerability · Source |
| CVE-2022-49903 | suse_vex | SUSE CVE CVE-2022-49903 | known affected: 245 known not affected: 131 recommended: 47 | 2026-07-25T17:10:35+00:00 | Vulnerability · Source |
| CVE-2022-49905 | suse_vex | SUSE CVE CVE-2022-49905 | known affected: 339 known not affected: 294 recommended: 214 | 2026-07-25T17:10:33+00:00 | Vulnerability · Source |
| CVE-2022-49915 | suse_vex | SUSE CVE CVE-2022-49915 | known affected: 424 known not affected: 153 recommended: 318 | 2026-07-25T17:10:32+00:00 | Vulnerability · Source |
| CVE-2022-49918 | suse_vex | SUSE CVE CVE-2022-49918 | known affected: 369 known not affected: 348 recommended: 92 | 2026-07-25T17:10:30+00:00 | Vulnerability · Source |
| CVE-2022-49929 | suse_vex | SUSE CVE CVE-2022-49929 | known affected: 369 known not affected: 343 recommended: 92 | 2026-07-25T17:10:29+00:00 | Vulnerability · Source |
| CVE-2022-49931 | suse_vex | SUSE CVE CVE-2022-49931 | known affected: 380 known not affected: 227 recommended: 237 | 2026-07-25T17:10:27+00:00 | Vulnerability · Source |
| CVE-2022-49935 | suse_vex | SUSE CVE CVE-2022-49935 | known affected: 461 known not affected: 255 recommended: 139 | 2026-07-25T17:10:25+00:00 | Vulnerability · Source |
| CVE-2022-49937 | suse_vex | SUSE CVE CVE-2022-49937 | known not affected: 260 recommended: 286 | 2026-07-25T17:10:24+00:00 | Vulnerability · Source |
| CVE-2022-49945 | suse_vex | SUSE CVE CVE-2022-49945 | known affected: 419 known not affected: 219 recommended: 273 | 2026-07-25T17:10:22+00:00 | Vulnerability · Source |
| CVE-2022-49947 | suse_vex | SUSE CVE CVE-2022-49947 | known not affected: 401 | 2026-07-25T17:10:21+00:00 | Vulnerability · Source |
| CVE-2022-49949 | suse_vex | SUSE CVE CVE-2022-49949 | known affected: 369 known not affected: 347 recommended: 92 | 2026-07-25T17:10:20+00:00 | Vulnerability · Source |
| CVE-2022-49950 | suse_vex | SUSE CVE CVE-2022-49950 | known affected: 358 known not affected: 280 recommended: 273 | 2026-07-25T17:10:18+00:00 | Vulnerability · Source |
| CVE-2022-49957 | suse_vex | SUSE CVE CVE-2022-49957 | known affected: 395 known not affected: 221 recommended: 229 | 2026-07-25T17:10:17+00:00 | Vulnerability · Source |
| CVE-2022-49962 | suse_vex | SUSE CVE CVE-2022-49962 | known affected: 369 known not affected: 347 recommended: 139 | 2026-07-25T17:10:15+00:00 | Vulnerability · Source |
| CVE-2022-49963 | suse_vex | SUSE CVE CVE-2022-49963 | known affected: 369 known not affected: 347 recommended: 92 | 2026-07-25T17:10:14+00:00 | Vulnerability · Source |
| CVE-2022-49964 | suse_vex | SUSE CVE CVE-2022-49964 | known affected: 348 known not affected: 294 recommended: 253 | 2026-07-25T17:10:13+00:00 | Vulnerability · Source |
| CVE-2022-49965 | suse_vex | SUSE CVE CVE-2022-49965 | known affected: 369 known not affected: 347 recommended: 139 | 2026-07-25T17:10:11+00:00 | Vulnerability · Source |
| CVE-2022-49966 | suse_vex | SUSE CVE CVE-2022-49966 | known affected: 344 known not affected: 298 recommended: 253 | 2026-07-25T17:10:10+00:00 | Vulnerability · Source |
| CVE-2022-49969 | suse_vex | SUSE CVE CVE-2022-49969 | known affected: 416 known not affected: 200 recommended: 276 | 2026-07-25T17:10:08+00:00 | Vulnerability · Source |
| CVE-2022-49976 | suse_vex | SUSE CVE CVE-2022-49976 | known not affected: 401 | 2026-07-25T17:10:07+00:00 | Vulnerability · Source |
| CVE-2022-49984 | suse_vex | SUSE CVE CVE-2022-49984 | known affected: 358 known not affected: 280 recommended: 300 | 2026-07-25T17:10:05+00:00 | Vulnerability · Source |
| CVE-2022-49987 | suse_vex | SUSE CVE CVE-2022-49987 | known affected: 405 known not affected: 268 recommended: 310 | 2026-07-25T17:10:04+00:00 | Vulnerability · Source |
| CVE-2022-50000 | suse_vex | SUSE CVE CVE-2022-50000 | known affected: 92 known not affected: 309 recommended: 42 | 2026-07-25T17:10:02+00:00 | Vulnerability · Source |
| CVE-2022-50003 | suse_vex | SUSE CVE CVE-2022-50003 | known affected: 475 known not affected: 241 recommended: 139 | 2026-07-25T17:10:01+00:00 | Vulnerability · Source |
| CVE-2022-50011 | suse_vex | SUSE CVE CVE-2022-50011 | known affected: 344 known not affected: 298 recommended: 206 | 2026-07-25T17:10:00+00:00 | Vulnerability · Source |
| CVE-2022-50015 | suse_vex | SUSE CVE CVE-2022-50015 | known affected: 475 known not affected: 241 recommended: 139 | 2026-07-25T17:09:58+00:00 | Vulnerability · Source |
| CVE-2022-50016 | suse_vex | SUSE CVE CVE-2022-50016 | known affected: 475 known not affected: 241 recommended: 139 | 2026-07-25T17:09:57+00:00 | Vulnerability · Source |