VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291911 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-40131 | suse_vex | SUSE CVE CVE-2025-40131 | known not affected: 408 | 2026-08-07T23:58:53+00:00 | Vulnerability · Source |
| CVE-2025-40143 | suse_vex | SUSE CVE CVE-2025-40143 | known not affected: 408 | 2026-08-07T23:58:51+00:00 | Vulnerability · Source |
| CVE-2025-40146 | suse_vex | SUSE CVE CVE-2025-40146 | known affected: 341 known not affected: 6 | 2026-08-07T23:58:50+00:00 | Vulnerability · Source |
| CVE-2025-40265 | suse_vex | SUSE CVE CVE-2025-40265 | known not affected: 408 | 2026-08-07T23:58:40+00:00 | Vulnerability · Source |
| CVE-2025-40267 | suse_vex | SUSE CVE CVE-2025-40267 | known not affected: 408 | 2026-08-07T23:58:38+00:00 | Vulnerability · Source |
| CVE-2025-40780 | suse_vex | SUSE CVE CVE-2025-40780 | known affected: 440 known not affected: 70 recommended: 339 | 2026-08-07T23:58:34+00:00 | Vulnerability · Source |
| CVE-2025-47912 | suse_vex | SUSE CVE CVE-2025-47912 | known affected: 24 known not affected: 67 recommended: 312 | 2026-08-07T23:58:30+00:00 | Vulnerability · Source |
| CVE-2025-58187 | suse_vex | SUSE CVE CVE-2025-58187 | known affected: 39 known not affected: 94 recommended: 312 | 2026-08-07T23:58:21+00:00 | Vulnerability · Source |
| CVE-2025-58188 | suse_vex | SUSE CVE CVE-2025-58188 | known affected: 24 known not affected: 67 recommended: 312 | 2026-08-07T23:58:19+00:00 | Vulnerability · Source |
| CVE-2025-61732 | suse_vex | SUSE CVE CVE-2025-61732 | known affected: 18 known not affected: 114 recommended: 289 | 2026-08-07T23:58:15+00:00 | Vulnerability · Source |
| CVE-2025-68738 | suse_vex | SUSE CVE CVE-2025-68738 | known not affected: 453 recommended: 6 | 2026-08-07T23:58:05+00:00 | Vulnerability · Source |
| CVE-2025-68752 | suse_vex | SUSE CVE CVE-2025-68752 | known not affected: 353 recommended: 6 | 2026-08-07T23:58:03+00:00 | Vulnerability · Source |
| CVE-2025-68756 | suse_vex | SUSE CVE CVE-2025-68756 | known not affected: 217 recommended: 6 | 2026-08-07T23:58:02+00:00 | Vulnerability · Source |
| CVE-2025-71298 | suse_vex | SUSE CVE CVE-2025-71298 | known not affected: 295 | 2026-08-07T23:57:57+00:00 | Vulnerability · Source |
| CVE-2026-18220 | suse_vex | SUSE CVE CVE-2026-18220 | known affected: 155 | 2026-08-07T23:57:08+00:00 | Vulnerability · Source |
| CVE-2026-19079 | suse_vex | SUSE CVE CVE-2026-19079 | No product status | 2026-08-07T23:57:06+00:00 | Vulnerability · Source |
| CVE-2026-23008 | suse_vex | SUSE CVE CVE-2026-23008 | known not affected: 336 | 2026-08-07T23:55:43+00:00 | Vulnerability · Source |
| CVE-2026-23036 | suse_vex | SUSE CVE CVE-2026-23036 | known not affected: 336 | 2026-08-07T23:55:41+00:00 | Vulnerability · Source |
| CVE-2026-23040 | suse_vex | SUSE CVE CVE-2026-23040 | known not affected: 336 | 2026-08-07T23:55:39+00:00 | Vulnerability · Source |
| CVE-2026-23052 | suse_vex | SUSE CVE CVE-2026-23052 | known not affected: 336 | 2026-08-07T23:55:37+00:00 | Vulnerability · Source |
| CVE-2026-23130 | suse_vex | SUSE CVE CVE-2026-23130 | known not affected: 332 | 2026-08-07T23:55:31+00:00 | Vulnerability · Source |
| CVE-2026-23162 | suse_vex | SUSE CVE CVE-2026-23162 | known not affected: 336 | 2026-08-07T23:55:28+00:00 | Vulnerability · Source |
| CVE-2026-23183 | suse_vex | SUSE CVE CVE-2026-23183 | known not affected: 332 | 2026-08-07T23:55:26+00:00 | Vulnerability · Source |
| CVE-2026-23332 | suse_vex | SUSE CVE CVE-2026-23332 | known not affected: 332 | 2026-08-07T23:55:11+00:00 | Vulnerability · Source |
| CVE-2026-23338 | suse_vex | SUSE CVE CVE-2026-23338 | known not affected: 340 | 2026-08-07T23:55:09+00:00 | Vulnerability · Source |
| CVE-2026-23341 | suse_vex | SUSE CVE CVE-2026-23341 | known not affected: 332 | 2026-08-07T23:55:07+00:00 | Vulnerability · Source |
| CVE-2026-23366 | suse_vex | SUSE CVE CVE-2026-23366 | known not affected: 340 | 2026-08-07T23:55:02+00:00 | Vulnerability · Source |
| CVE-2026-23376 | suse_vex | SUSE CVE CVE-2026-23376 | known affected: 140 known not affected: 200 | 2026-08-07T23:55:00+00:00 | Vulnerability · Source |
| CVE-2026-23469 | suse_vex | SUSE CVE CVE-2026-23469 | known affected: 17 known not affected: 304 | 2026-08-07T23:54:46+00:00 | Vulnerability · Source |
| CVE-2026-31399 | suse_vex | SUSE CVE CVE-2026-31399 | known affected: 315 known not affected: 6 | 2026-08-07T23:54:35+00:00 | Vulnerability · Source |
| CVE-2026-31514 | suse_vex | SUSE CVE CVE-2026-31514 | known not affected: 316 | 2026-08-07T23:54:15+00:00 | Vulnerability · Source |
| CVE-2026-43396 | suse_vex | SUSE CVE CVE-2026-43396 | known not affected: 293 | 2026-08-07T23:52:30+00:00 | Vulnerability · Source |
| CVE-2026-43401 | suse_vex | SUSE CVE CVE-2026-43401 | known not affected: 293 | 2026-08-07T23:52:28+00:00 | Vulnerability · Source |
| CVE-2021-47483 | redhat_vex | kernel: regmap: Fix possible double-free in regcache_rbtree_exit() | fixed: 120 known affected: 152 known not affected: 14 | 2026-08-07T23:51:52+00:00 | Vulnerability · Source |
| CVE-2026-45968 | suse_vex | SUSE CVE CVE-2026-45968 | known affected: 228 known not affected: 67 | 2026-08-07T23:51:29+00:00 | Vulnerability · Source |
| CVE-2026-53141 | suse_vex | SUSE CVE CVE-2026-53141 | known not affected: 295 | 2026-08-07T23:49:46+00:00 | Vulnerability · Source |
| CVE-2026-53364 | suse_vex | SUSE CVE CVE-2026-53364 | known affected: 86 known not affected: 197 | 2026-08-07T23:49:13+00:00 | Vulnerability · Source |
| CVE-2026-53401 | suse_vex | SUSE CVE CVE-2026-53401 | known not affected: 298 recommended: 4 | 2026-08-07T23:48:44+00:00 | Vulnerability · Source |
| CVE-2026-56818 | suse_vex | SUSE CVE CVE-2026-56818 | known not affected: 42 recommended: 22 | 2026-08-07T23:48:30+00:00 | Vulnerability · Source |
| CVE-2026-63838 | suse_vex | SUSE CVE CVE-2026-63838 | known affected: 72 known not affected: 214 | 2026-08-07T23:47:40+00:00 | Vulnerability · Source |
| CVE-2026-63841 | suse_vex | SUSE CVE CVE-2026-63841 | known not affected: 284 | 2026-08-07T23:47:38+00:00 | Vulnerability · Source |
| CVE-2026-63849 | suse_vex | SUSE CVE CVE-2026-63849 | known not affected: 284 | 2026-08-07T23:47:26+00:00 | Vulnerability · Source |
| CVE-2026-63873 | suse_vex | SUSE CVE CVE-2026-63873 | known not affected: 286 | 2026-08-07T23:47:08+00:00 | Vulnerability · Source |
| CVE-2026-63978 | suse_vex | SUSE CVE CVE-2026-63978 | known affected: 119 known not affected: 167 | 2026-08-07T23:45:48+00:00 | Vulnerability · Source |
| CVE-2026-63979 | suse_vex | SUSE CVE CVE-2026-63979 | known affected: 119 known not affected: 167 | 2026-08-07T23:45:46+00:00 | Vulnerability · Source |
| CVE-2026-63980 | suse_vex | SUSE CVE CVE-2026-63980 | known affected: 117 known not affected: 167 | 2026-08-07T23:45:45+00:00 | Vulnerability · Source |
| CVE-2026-64019 | suse_vex | SUSE CVE CVE-2026-64019 | known not affected: 284 | 2026-08-07T23:45:37+00:00 | Vulnerability · Source |
| CVE-2026-64020 | suse_vex | SUSE CVE CVE-2026-64020 | known not affected: 274 | 2026-08-07T23:45:35+00:00 | Vulnerability · Source |
| CVE-2026-64080 | suse_vex | SUSE CVE CVE-2026-64080 | known not affected: 284 | 2026-08-07T23:45:28+00:00 | Vulnerability · Source |
| CVE-2026-64082 | suse_vex | SUSE CVE CVE-2026-64082 | known not affected: 298 | 2026-08-07T23:45:26+00:00 | Vulnerability · Source |