VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
306069 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-68820 | suse_vex | SUSE CVE CVE-2025-68820 | known affected: 562 known not affected: 208 recommended: 289 | 2026-10-07T23:49:51+00:00 | Vulnerability · Source |
| CVE-2025-68821 | suse_vex | SUSE CVE CVE-2025-68821 | known affected: 7 known not affected: 431 recommended: 172 | 2026-10-07T23:49:48+00:00 | Vulnerability · Source |
| CVE-2025-71077 | suse_vex | SUSE CVE CVE-2025-71077 | known affected: 555 known not affected: 232 recommended: 289 | 2026-10-07T23:49:45+00:00 | Vulnerability · Source |
| CVE-2025-71084 | suse_vex | SUSE CVE CVE-2025-71084 | known affected: 593 known not affected: 177 recommended: 289 | 2026-10-07T23:49:42+00:00 | Vulnerability · Source |
| CVE-2025-71088 | suse_vex | SUSE CVE CVE-2025-71088 | known affected: 458 known not affected: 312 recommended: 289 | 2026-10-07T23:49:40+00:00 | Vulnerability · Source |
| CVE-2025-71100 | suse_vex | SUSE CVE CVE-2025-71100 | known affected: 396 known not affected: 317 recommended: 289 | 2026-10-07T23:49:36+00:00 | Vulnerability · Source |
| CVE-2025-71114 | suse_vex | SUSE CVE CVE-2025-71114 | known affected: 509 known not affected: 69 recommended: 289 | 2026-10-07T23:49:34+00:00 | Vulnerability · Source |
| CVE-2025-71132 | suse_vex | SUSE CVE CVE-2025-71132 | known affected: 448 known not affected: 312 recommended: 309 | 2026-10-07T23:49:31+00:00 | Vulnerability · Source |
| CVE-2025-71147 | suse_vex | SUSE CVE CVE-2025-71147 | known affected: 500 known not affected: 225 recommended: 467 | 2026-10-07T23:49:28+00:00 | Vulnerability · Source |
| CVE-2025-71148 | suse_vex | SUSE CVE CVE-2025-71148 | known affected: 451 known not affected: 312 recommended: 280 | 2026-10-07T23:49:25+00:00 | Vulnerability · Source |
| CVE-2025-71157 | suse_vex | SUSE CVE CVE-2025-71157 | known affected: 396 known not affected: 376 recommended: 265 | 2026-10-07T23:49:22+00:00 | Vulnerability · Source |
| CVE-2025-71197 | suse_vex | SUSE CVE CVE-2025-71197 | known affected: 500 known not affected: 235 recommended: 280 | 2026-10-07T23:49:19+00:00 | Vulnerability · Source |
| CVE-2025-71222 | suse_vex | SUSE CVE CVE-2025-71222 | known affected: 509 known not affected: 8 recommended: 280 | 2026-10-07T23:49:17+00:00 | Vulnerability · Source |
| CVE-2025-71225 | suse_vex | SUSE CVE CVE-2025-71225 | known affected: 699 known not affected: 4 recommended: 280 | 2026-10-07T23:49:14+00:00 | Vulnerability · Source |
| CVE-2025-71229 | suse_vex | SUSE CVE CVE-2025-71229 | known affected: 426 known not affected: 320 recommended: 284 | 2026-10-07T23:49:12+00:00 | Vulnerability · Source |
| CVE-2025-71268 | suse_vex | SUSE CVE CVE-2025-71268 | known affected: 663 known not affected: 24 recommended: 317 | 2026-10-07T23:49:08+00:00 | Vulnerability · Source |
| CVE-2026-6948 | suse_vex | SUSE CVE CVE-2026-6948 | known affected: 5 recommended: 1 | 2026-10-07T23:48:57+00:00 | Vulnerability · Source |
| CVE-2026-16461 | suse_vex | SUSE CVE CVE-2026-16461 | known affected: 412 recommended: 28 | 2026-10-07T23:48:52+00:00 | Vulnerability · Source |
| CVE-2026-17535 | suse_vex | SUSE CVE CVE-2026-17535 | known affected: 5 recommended: 1 | 2026-10-07T23:48:49+00:00 | Vulnerability · Source |
| CVE-2026-18348 | suse_vex | SUSE CVE CVE-2026-18348 | known affected: 5 recommended: 1 | 2026-10-07T23:48:46+00:00 | Vulnerability · Source |
| CVE-2026-18495 | suse_vex | SUSE CVE CVE-2026-18495 | known affected: 565 known not affected: 20 recommended: 10 | 2026-10-07T23:48:43+00:00 | Vulnerability · Source |
| CVE-2026-18636 | suse_vex | SUSE CVE CVE-2026-18636 | known affected: 5 recommended: 1 | 2026-10-07T23:48:40+00:00 | Vulnerability · Source |
| CVE-2026-18638 | suse_vex | SUSE CVE CVE-2026-18638 | known affected: 5 recommended: 1 | 2026-10-07T23:48:38+00:00 | Vulnerability · Source |
| CVE-2026-18639 | suse_vex | SUSE CVE CVE-2026-18639 | known affected: 5 recommended: 1 | 2026-10-07T23:48:36+00:00 | Vulnerability · Source |
| CVE-2026-18739 | suse_vex | SUSE CVE CVE-2026-18739 | known affected: 167 | 2026-10-07T23:48:34+00:00 | Vulnerability · Source |
| CVE-2026-18743 | suse_vex | SUSE CVE CVE-2026-18743 | known affected: 167 | 2026-10-07T23:48:32+00:00 | Vulnerability · Source |
| CVE-2026-27601 | suse_vex | SUSE CVE CVE-2026-27601 | known affected: 202 known not affected: 364 recommended: 12 | 2026-10-07T23:48:24+00:00 | Vulnerability · Source |
| CVE-2026-56864 | suse_vex | SUSE CVE CVE-2026-56864 | known affected: 12 known not affected: 139 recommended: 315 | 2026-10-07T23:47:01+00:00 | Vulnerability · Source |
| CVE-2026-64951 | suse_vex | SUSE CVE CVE-2026-64951 | known affected: 5 recommended: 1 | 2026-10-07T23:46:50+00:00 | Vulnerability · Source |
| CVE-2026-64952 | suse_vex | SUSE CVE CVE-2026-64952 | known affected: 5 recommended: 1 | 2026-10-07T23:46:47+00:00 | Vulnerability · Source |
| CVE-2026-64954 | suse_vex | SUSE CVE CVE-2026-64954 | known affected: 5 recommended: 1 | 2026-10-07T23:46:45+00:00 | Vulnerability · Source |
| CVE-2026-66339 | suse_vex | SUSE CVE CVE-2026-66339 | known affected: 208 recommended: 60 | 2026-10-07T23:46:43+00:00 | Vulnerability · Source |
| CVE-2026-98185 | suse_vex | SUSE CVE CVE-2026-98185 | known affected: 269 known not affected: 78 | 2026-10-07T23:45:54+00:00 | Vulnerability · Source |
| CVE-2026-98187 | suse_vex | SUSE CVE CVE-2026-98187 | known affected: 269 known not affected: 78 | 2026-10-07T23:45:51+00:00 | Vulnerability · Source |
| CVE-2026-98193 | suse_vex | SUSE CVE CVE-2026-98193 | known affected: 347 | 2026-10-07T23:45:48+00:00 | Vulnerability · Source |
| CVE-2026-98206 | suse_vex | SUSE CVE CVE-2026-98206 | known affected: 30 known not affected: 317 | 2026-10-07T23:45:45+00:00 | Vulnerability · Source |
| CVE-2026-98207 | suse_vex | SUSE CVE CVE-2026-98207 | known affected: 269 known not affected: 78 | 2026-10-07T23:45:43+00:00 | Vulnerability · Source |
| CVE-2026-98238 | suse_vex | SUSE CVE CVE-2026-98238 | known affected: 30 known not affected: 317 | 2026-10-07T23:45:40+00:00 | Vulnerability · Source |
| CVE-2026-98248 | suse_vex | SUSE CVE CVE-2026-98248 | known affected: 146 known not affected: 201 | 2026-10-07T23:45:37+00:00 | Vulnerability · Source |
| CVE-2026-98263 | suse_vex | SUSE CVE CVE-2026-98263 | known affected: 30 known not affected: 317 | 2026-10-07T23:45:34+00:00 | Vulnerability · Source |
| CVE-2026-98265 | suse_vex | SUSE CVE CVE-2026-98265 | known affected: 49 known not affected: 298 | 2026-10-07T23:45:31+00:00 | Vulnerability · Source |
| CVE-2026-98277 | suse_vex | SUSE CVE CVE-2026-98277 | known affected: 29 known not affected: 318 | 2026-10-07T23:45:28+00:00 | Vulnerability · Source |
| CVE-2026-98306 | suse_vex | SUSE CVE CVE-2026-98306 | known affected: 254 known not affected: 93 | 2026-10-07T23:45:25+00:00 | Vulnerability · Source |
| CVE-2026-98325 | suse_vex | SUSE CVE CVE-2026-98325 | known affected: 265 known not affected: 82 | 2026-10-07T23:45:22+00:00 | Vulnerability · Source |
| CVE-2026-98332 | suse_vex | SUSE CVE CVE-2026-98332 | known affected: 265 known not affected: 82 | 2026-10-07T23:45:20+00:00 | Vulnerability · Source |
| CVE-2026-98338 | suse_vex | SUSE CVE CVE-2026-98338 | known affected: 347 | 2026-10-07T23:45:17+00:00 | Vulnerability · Source |
| CVE-2026-98361 | suse_vex | SUSE CVE CVE-2026-98361 | known not affected: 347 | 2026-10-07T23:45:15+00:00 | Vulnerability · Source |
| CVE-2026-98368 | suse_vex | SUSE CVE CVE-2026-98368 | known affected: 108 known not affected: 239 | 2026-10-07T23:45:13+00:00 | Vulnerability · Source |
| CVE-2026-103484 | suse_vex | SUSE CVE CVE-2026-103484 | known affected: 36 recommended: 1 | 2026-10-07T23:45:09+00:00 | Vulnerability · Source |
| CVE-2026-63990 | redhat_vex | kernel: bonding: refuse to enslave CAN devices | known affected: 275 known not affected: 1 | 2026-10-07T23:37:25+00:00 | Vulnerability · Source |