VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291757 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-15269 | suse_vex | SUSE CVE CVE-2025-15269 | known affected: 7 recommended: 34 | 2026-08-13T01:40:49+00:00 | Vulnerability · Source |
| CVE-2025-15272 | suse_vex | SUSE CVE CVE-2025-15272 | known affected: 31 | 2026-08-13T01:40:48+00:00 | Vulnerability · Source |
| CVE-2025-15280 | suse_vex | SUSE CVE CVE-2025-15280 | known affected: 31 | 2026-08-13T01:40:46+00:00 | Vulnerability · Source |
| CVE-2025-15649 | suse_vex | SUSE CVE CVE-2025-15649 | known affected: 144 recommended: 13 | 2026-08-13T01:40:40+00:00 | Vulnerability · Source |
| CVE-2026-19654 | redhat_vex | rsyslog: A configuration-dependent issue in rsyslog's optional imptcp input module can allow an unauthenticated remote peer to crash rsyslogd | known affected: 99 | 2026-08-13T01:40:38+00:00 | Vulnerability · Source |
| CVE-2025-21690 | suse_vex | SUSE CVE CVE-2025-21690 | known affected: 354 known not affected: 109 recommended: 712 | 2026-08-13T01:40:34+00:00 | Vulnerability · Source |
| CVE-2025-21726 | suse_vex | SUSE CVE CVE-2025-21726 | known affected: 368 known not affected: 166 recommended: 746 | 2026-08-13T01:40:30+00:00 | Vulnerability · Source |
| CVE-2025-22026 | suse_vex | SUSE CVE CVE-2025-22026 | known not affected: 433 recommended: 76 | 2026-08-13T01:40:14+00:00 | Vulnerability · Source |
| CVE-2025-22031 | suse_vex | SUSE CVE CVE-2025-22031 | known not affected: 344 | 2026-08-13T01:40:12+00:00 | Vulnerability · Source |
| CVE-2025-22620 | suse_vex | SUSE CVE CVE-2025-22620 | recommended: 2 | 2026-08-13T01:40:04+00:00 | Vulnerability · Source |
| CVE-2025-22889 | suse_vex | SUSE CVE CVE-2025-22889 | known affected: 14 recommended: 43 | 2026-08-13T01:40:01+00:00 | Vulnerability · Source |
| CVE-2025-23090 | suse_vex | SUSE CVE CVE-2025-23090 | known not affected: 212 | 2026-08-13T01:39:59+00:00 | Vulnerability · Source |
| CVE-2025-23279 | suse_vex | SUSE CVE CVE-2025-23279 | known affected: 17 recommended: 231 | 2026-08-13T01:39:55+00:00 | Vulnerability · Source |
| CVE-2025-24150 | suse_vex | SUSE CVE CVE-2025-24150 | known affected: 88 recommended: 603 | 2026-08-13T01:39:53+00:00 | Vulnerability · Source |
| CVE-2025-27209 | suse_vex | SUSE CVE CVE-2025-27209 | known not affected: 274 | 2026-08-13T01:39:47+00:00 | Vulnerability · Source |
| CVE-2025-27463 | suse_vex | SUSE CVE CVE-2025-27463 | known not affected: 218 | 2026-08-13T01:39:46+00:00 | Vulnerability · Source |
| CVE-2025-29087 | suse_vex | SUSE CVE CVE-2025-29087 | known affected: 380 known not affected: 1 recommended: 250 | 2026-08-13T01:39:44+00:00 | Vulnerability · Source |
| CVE-2025-29482 | suse_vex | SUSE CVE CVE-2025-29482 | known not affected: 71 | 2026-08-13T01:39:43+00:00 | Vulnerability · Source |
| CVE-2025-31179 | suse_vex | SUSE CVE CVE-2025-31179 | known affected: 33 known not affected: 7 recommended: 24 | 2026-08-13T01:39:41+00:00 | Vulnerability · Source |
| CVE-2025-37835 | suse_vex | SUSE CVE CVE-2025-37835 | known affected: 127 known not affected: 277 | 2026-08-13T01:39:32+00:00 | Vulnerability · Source |
| CVE-2025-37962 | suse_vex | SUSE CVE CVE-2025-37962 | known not affected: 375 | 2026-08-13T01:39:24+00:00 | Vulnerability · Source |
| CVE-2025-38088 | suse_vex | SUSE CVE CVE-2025-38088 | first fixed: 2 known affected: 344 known not affected: 226 recommended: 714 | 2026-08-13T01:39:16+00:00 | Vulnerability · Source |
| CVE-2025-38128 | suse_vex | SUSE CVE CVE-2025-38128 | first fixed: 2 known not affected: 416 recommended: 154 | 2026-08-13T01:39:13+00:00 | Vulnerability · Source |
| CVE-2025-38266 | suse_vex | SUSE CVE CVE-2025-38266 | known not affected: 416 | 2026-08-13T01:39:00+00:00 | Vulnerability · Source |
| CVE-2025-38288 | suse_vex | SUSE CVE CVE-2025-38288 | first fixed: 2 known affected: 394 known not affected: 383 recommended: 348 | 2026-08-13T01:38:58+00:00 | Vulnerability · Source |
| CVE-2025-38468 | suse_vex | SUSE CVE CVE-2025-38468 | first fixed: 2 known affected: 465 known not affected: 46 recommended: 872 | 2026-08-13T01:38:43+00:00 | Vulnerability · Source |
| CVE-2025-38564 | suse_vex | SUSE CVE CVE-2025-38564 | first fixed: 2 known not affected: 425 recommended: 154 | 2026-08-13T01:38:34+00:00 | Vulnerability · Source |
| CVE-2025-38617 | suse_vex | SUSE CVE CVE-2025-38617 | first fixed: 2 known affected: 344 known not affected: 380 recommended: 949 | 2026-08-13T01:38:30+00:00 | Vulnerability · Source |
| CVE-2025-38683 | suse_vex | SUSE CVE CVE-2025-38683 | first fixed: 2 known affected: 369 known not affected: 205 recommended: 634 | 2026-08-13T01:38:25+00:00 | Vulnerability · Source |
| CVE-2025-38726 | suse_vex | SUSE CVE CVE-2025-38726 | known affected: 57 known not affected: 378 | 2026-08-13T01:38:19+00:00 | Vulnerability · Source |
| CVE-2025-39733 | suse_vex | SUSE CVE CVE-2025-39733 | known not affected: 407 | 2026-08-13T01:38:13+00:00 | Vulnerability · Source |
| CVE-2025-39807 | suse_vex | SUSE CVE CVE-2025-39807 | first fixed: 2 known affected: 399 known not affected: 376 recommended: 265 | 2026-08-13T01:38:06+00:00 | Vulnerability · Source |
| CVE-2025-39914 | suse_vex | SUSE CVE CVE-2025-39914 | known affected: 9 known not affected: 262 | 2026-08-13T01:37:53+00:00 | Vulnerability · Source |
| CVE-2025-39921 | suse_vex | SUSE CVE CVE-2025-39921 | known not affected: 416 | 2026-08-13T01:37:52+00:00 | Vulnerability · Source |
| CVE-2025-40007 | suse_vex | SUSE CVE CVE-2025-40007 | known not affected: 416 | 2026-08-13T01:37:43+00:00 | Vulnerability · Source |
| CVE-2025-40057 | suse_vex | SUSE CVE CVE-2025-40057 | known affected: 192 known not affected: 156 recommended: 6 | 2026-08-13T01:37:35+00:00 | Vulnerability · Source |
| CVE-2025-40150 | suse_vex | SUSE CVE CVE-2025-40150 | known not affected: 408 | 2026-08-13T01:37:26+00:00 | Vulnerability · Source |
| CVE-2025-40197 | suse_vex | SUSE CVE CVE-2025-40197 | first fixed: 2 known not affected: 405 recommended: 154 | 2026-08-13T01:37:19+00:00 | Vulnerability · Source |
| CVE-2025-40234 | suse_vex | SUSE CVE CVE-2025-40234 | known not affected: 408 | 2026-08-13T01:37:16+00:00 | Vulnerability · Source |
| CVE-2025-40237 | suse_vex | SUSE CVE CVE-2025-40237 | first fixed: 2 known affected: 394 known not affected: 431 recommended: 214 | 2026-08-13T01:37:14+00:00 | Vulnerability · Source |
| CVE-2025-40246 | suse_vex | SUSE CVE CVE-2025-40246 | first fixed: 2 known affected: 394 known not affected: 431 recommended: 172 | 2026-08-13T01:37:12+00:00 | Vulnerability · Source |
| CVE-2025-40294 | suse_vex | SUSE CVE CVE-2025-40294 | first fixed: 2 known affected: 394 known not affected: 354 recommended: 366 | 2026-08-13T01:37:09+00:00 | Vulnerability · Source |
| CVE-2025-40298 | suse_vex | SUSE CVE CVE-2025-40298 | known not affected: 414 | 2026-08-13T01:37:08+00:00 | Vulnerability · Source |
| CVE-2025-40332 | suse_vex | SUSE CVE CVE-2025-40332 | first fixed: 2 known affected: 394 known not affected: 396 recommended: 283 | 2026-08-13T01:37:06+00:00 | Vulnerability · Source |
| CVE-2025-40348 | suse_vex | SUSE CVE CVE-2025-40348 | known not affected: 418 | 2026-08-13T01:37:04+00:00 | Vulnerability · Source |
| CVE-2025-41244 | suse_vex | SUSE CVE CVE-2025-41244 | known affected: 26 known not affected: 16 recommended: 256 | 2026-08-13T01:37:02+00:00 | Vulnerability · Source |
| CVE-2025-43023 | suse_vex | SUSE CVE CVE-2025-43023 | known not affected: 32 recommended: 139 | 2026-08-13T01:37:01+00:00 | Vulnerability · Source |
| CVE-2025-43427 | suse_vex | SUSE CVE CVE-2025-43427 | known affected: 124 recommended: 632 | 2026-08-13T01:36:58+00:00 | Vulnerability · Source |
| CVE-2025-47290 | suse_vex | SUSE CVE CVE-2025-47290 | known not affected: 86 recommended: 7 | 2026-08-13T01:36:53+00:00 | Vulnerability · Source |
| CVE-2025-48073 | suse_vex | SUSE CVE CVE-2025-48073 | known not affected: 143 recommended: 30 | 2026-08-13T01:36:50+00:00 | Vulnerability · Source |