VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-21977 | suse_vex | SUSE CVE CVE-2025-21977 | known affected: 200 known not affected: 286 recommended: 109 | 2026-10-16T00:57:13+00:00 | Vulnerability · Source |
| CVE-2025-21989 | suse_vex | SUSE CVE CVE-2025-21989 | known affected: 0 known not affected: 456 recommended: 183 | 2026-10-16T00:57:11+00:00 | Vulnerability · Source |
| CVE-2025-22016 | suse_vex | SUSE CVE CVE-2025-22016 | known affected: 437 known not affected: 388 recommended: 415 | 2026-10-16T00:57:08+00:00 | Vulnerability · Source |
| CVE-2025-22031 | suse_vex | SUSE CVE CVE-2025-22031 | known affected: 0 known not affected: 456 | 2026-10-16T00:57:07+00:00 | Vulnerability · Source |
| CVE-2025-22047 | suse_vex | SUSE CVE CVE-2025-22047 | known affected: 394 known not affected: 423 recommended: 321 | 2026-10-16T00:57:05+00:00 | Vulnerability · Source |
| CVE-2025-22051 | suse_vex | SUSE CVE CVE-2025-22051 | known affected: 0 known not affected: 456 | 2026-10-16T00:57:03+00:00 | Vulnerability · Source |
| CVE-2025-22109 | suse_vex | SUSE CVE CVE-2025-22109 | known affected: 734 known not affected: 87 recommended: 438 | 2026-10-16T00:57:00+00:00 | Vulnerability · Source |
| CVE-2025-23048 | suse_vex | SUSE CVE CVE-2025-23048 | known affected: 436 known not affected: 97 recommended: 278 | 2026-10-16T00:56:56+00:00 | Vulnerability · Source |
| CVE-2025-23129 | suse_vex | SUSE CVE CVE-2025-23129 | known affected: 461 known not affected: 370 recommended: 521 | 2026-10-16T00:56:53+00:00 | Vulnerability · Source |
| CVE-2025-23163 | suse_vex | SUSE CVE CVE-2025-23163 | known affected: 780 recommended: 464 | 2026-10-16T00:56:51+00:00 | Vulnerability · Source |
| CVE-2025-24369 | suse_vex | SUSE CVE CVE-2025-24369 | recommended: 6 | 2026-10-16T00:56:47+00:00 | Vulnerability · Source |
| CVE-2025-24883 | suse_vex | SUSE CVE CVE-2025-24883 | recommended: 5 | 2026-10-16T00:56:44+00:00 | Vulnerability · Source |
| CVE-2025-25068 | suse_vex | SUSE CVE CVE-2025-25068 | recommended: 5 | 2026-10-16T00:56:42+00:00 | Vulnerability · Source |
| CVE-2025-26623 | suse_vex | SUSE CVE CVE-2025-26623 | known affected: 0 known not affected: 166 recommended: 18 | 2026-10-16T00:56:40+00:00 | Vulnerability · Source |
| CVE-2025-27088 | suse_vex | SUSE CVE CVE-2025-27088 | recommended: 5 | 2026-10-16T00:56:39+00:00 | Vulnerability · Source |
| CVE-2025-27152 | suse_vex | SUSE CVE CVE-2025-27152 | known affected: 163 known not affected: 248 recommended: 77 | 2026-10-16T00:56:37+00:00 | Vulnerability · Source |
| CVE-2025-30086 | suse_vex | SUSE CVE CVE-2025-30086 | recommended: 5 | 2026-10-16T00:56:34+00:00 | Vulnerability · Source |
| CVE-2025-31273 | suse_vex | SUSE CVE CVE-2025-31273 | known affected: 179 recommended: 584 | 2026-10-16T00:56:31+00:00 | Vulnerability · Source |
| CVE-2025-34410 | suse_vex | SUSE CVE CVE-2025-34410 | recommended: 2 | 2026-10-16T00:56:28+00:00 | Vulnerability · Source |
| CVE-2025-37745 | suse_vex | SUSE CVE CVE-2025-37745 | known affected: 0 known not affected: 502 recommended: 109 | 2026-10-16T00:56:26+00:00 | Vulnerability · Source |
| CVE-2025-37822 | suse_vex | SUSE CVE CVE-2025-37822 | known affected: 0 known not affected: 573 | 2026-10-16T00:56:24+00:00 | Vulnerability · Source |
| CVE-2025-37834 | suse_vex | SUSE CVE CVE-2025-37834 | known affected: 0 known not affected: 561 | 2026-10-16T00:56:22+00:00 | Vulnerability · Source |
| CVE-2025-37837 | suse_vex | SUSE CVE CVE-2025-37837 | known affected: 421 known not affected: 471 recommended: 202 | 2026-10-16T00:56:20+00:00 | Vulnerability · Source |
| CVE-2025-37854 | suse_vex | SUSE CVE CVE-2025-37854 | known affected: 461 known not affected: 375 recommended: 427 | 2026-10-16T00:56:17+00:00 | Vulnerability · Source |
| CVE-2025-37858 | suse_vex | SUSE CVE CVE-2025-37858 | known affected: 394 known not affected: 305 recommended: 318 | 2026-10-16T00:56:15+00:00 | Vulnerability · Source |
| CVE-2025-37870 | suse_vex | SUSE CVE CVE-2025-37870 | known affected: 410 known not affected: 411 recommended: 431 | 2026-10-16T00:56:13+00:00 | Vulnerability · Source |
| CVE-2025-37892 | suse_vex | SUSE CVE CVE-2025-37892 | known affected: 737 known not affected: 43 recommended: 464 | 2026-10-16T00:56:11+00:00 | Vulnerability · Source |
| CVE-2025-37897 | suse_vex | SUSE CVE CVE-2025-37897 | known affected: 394 known not affected: 427 recommended: 427 | 2026-10-16T00:56:08+00:00 | Vulnerability · Source |
| CVE-2025-37898 | suse_vex | SUSE CVE CVE-2025-37898 | known affected: 0 known not affected: 502 recommended: 109 | 2026-10-16T00:56:06+00:00 | Vulnerability · Source |
| CVE-2025-37928 | suse_vex | SUSE CVE CVE-2025-37928 | known affected: 699 known not affected: 137 recommended: 464 | 2026-10-16T00:56:04+00:00 | Vulnerability · Source |
| CVE-2025-37967 | suse_vex | SUSE CVE CVE-2025-37967 | known affected: 649 known not affected: 187 recommended: 412 | 2026-10-16T00:56:00+00:00 | Vulnerability · Source |
| CVE-2025-37978 | suse_vex | SUSE CVE CVE-2025-37978 | known affected: 461 known not affected: 360 recommended: 427 | 2026-10-16T00:55:58+00:00 | Vulnerability · Source |
| CVE-2025-37984 | suse_vex | SUSE CVE CVE-2025-37984 | known affected: 437 known not affected: 399 recommended: 427 | 2026-10-16T00:55:55+00:00 | Vulnerability · Source |
| CVE-2025-38047 | suse_vex | SUSE CVE CVE-2025-38047 | known affected: 756 known not affected: 167 recommended: 202 | 2026-10-16T00:55:51+00:00 | Vulnerability · Source |
| CVE-2025-38048 | suse_vex | SUSE CVE CVE-2025-38048 | known affected: 143 known not affected: 320 | 2026-10-16T00:55:49+00:00 | Vulnerability · Source |
| CVE-2025-38070 | suse_vex | SUSE CVE CVE-2025-38070 | known affected: 0 known not affected: 506 recommended: 58 | 2026-10-16T00:55:47+00:00 | Vulnerability · Source |
| CVE-2025-38072 | suse_vex | SUSE CVE CVE-2025-38072 | known affected: 746 known not affected: 36 recommended: 450 | 2026-10-16T00:55:45+00:00 | Vulnerability · Source |
| CVE-2025-38081 | suse_vex | SUSE CVE CVE-2025-38081 | known affected: 394 known not affected: 427 recommended: 427 | 2026-10-16T00:55:43+00:00 | Vulnerability · Source |
| CVE-2025-38155 | suse_vex | SUSE CVE CVE-2025-38155 | known affected: 396 known not affected: 442 recommended: 503 | 2026-10-16T00:55:34+00:00 | Vulnerability · Source |
| CVE-2025-38181 | suse_vex | SUSE CVE CVE-2025-38181 | known affected: 501 known not affected: 79 recommended: 907 | 2026-10-16T00:55:30+00:00 | Vulnerability · Source |
| CVE-2025-38182 | suse_vex | SUSE CVE CVE-2025-38182 | known affected: 444 known not affected: 405 recommended: 503 | 2026-10-16T00:55:28+00:00 | Vulnerability · Source |
| CVE-2025-38208 | suse_vex | SUSE CVE CVE-2025-38208 | known affected: 636 known not affected: 213 recommended: 503 | 2026-10-16T00:55:25+00:00 | Vulnerability · Source |
| CVE-2025-38237 | suse_vex | SUSE CVE CVE-2025-38237 | known affected: 0 known not affected: 575 | 2026-10-16T00:55:23+00:00 | Vulnerability · Source |
| CVE-2025-38261 | suse_vex | SUSE CVE CVE-2025-38261 | known affected: 0 known not affected: 575 | 2026-10-16T00:55:20+00:00 | Vulnerability · Source |
| CVE-2025-38284 | suse_vex | SUSE CVE CVE-2025-38284 | known affected: 0 known not affected: 563 recommended: 58 | 2026-10-16T00:55:17+00:00 | Vulnerability · Source |
| CVE-2025-38292 | suse_vex | SUSE CVE CVE-2025-38292 | known affected: 396 known not affected: 442 recommended: 589 | 2026-10-16T00:55:15+00:00 | Vulnerability · Source |
| CVE-2025-38300 | suse_vex | SUSE CVE CVE-2025-38300 | known affected: 539 known not affected: 299 recommended: 503 | 2026-10-16T00:55:13+00:00 | Vulnerability · Source |
| CVE-2025-38443 | suse_vex | SUSE CVE CVE-2025-38443 | known affected: 539 known not affected: 299 recommended: 503 | 2026-10-16T00:55:07+00:00 | Vulnerability · Source |
| CVE-2025-38467 | suse_vex | SUSE CVE CVE-2025-38467 | known affected: 673 known not affected: 165 recommended: 503 | 2026-10-16T00:55:05+00:00 | Vulnerability · Source |
| CVE-2025-38472 | suse_vex | SUSE CVE CVE-2025-38472 | known affected: 444 known not affected: 405 recommended: 589 | 2026-10-16T00:55:02+00:00 | Vulnerability · Source |