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-2024-53196 | suse_vex | SUSE CVE CVE-2024-53196 | known affected: 600 known not affected: 321 recommended: 358 | 2026-10-16T01:24:55+00:00 | Vulnerability · Source |
| CVE-2024-53198 | suse_vex | SUSE CVE CVE-2024-53198 | known affected: 827 known not affected: 32 recommended: 398 | 2026-10-16T01:24:53+00:00 | Vulnerability · Source |
| CVE-2024-53200 | suse_vex | SUSE CVE CVE-2024-53200 | known affected: 394 known not affected: 481 recommended: 358 | 2026-10-16T01:24:51+00:00 | Vulnerability · Source |
| CVE-2024-53201 | suse_vex | SUSE CVE CVE-2024-53201 | known affected: 515 known not affected: 360 recommended: 358 | 2026-10-16T01:24:49+00:00 | Vulnerability · Source |
| CVE-2024-53202 | suse_vex | SUSE CVE CVE-2024-53202 | known affected: 394 known not affected: 481 recommended: 358 | 2026-10-16T01:24:47+00:00 | Vulnerability · Source |
| CVE-2024-53204 | suse_vex | SUSE CVE CVE-2024-53204 | known not affected: 547 recommended: 78 | 2026-10-16T01:24:45+00:00 | Vulnerability · Source |
| CVE-2024-53205 | suse_vex | SUSE CVE CVE-2024-53205 | known not affected: 547 recommended: 78 | 2026-10-16T01:24:43+00:00 | Vulnerability · Source |
| CVE-2024-53206 | suse_vex | SUSE CVE CVE-2024-53206 | known affected: 84 known not affected: 302 recommended: 521 | 2026-10-16T01:24:41+00:00 | Vulnerability · Source |
| CVE-2024-53207 | suse_vex | SUSE CVE CVE-2024-53207 | known affected: 394 known not affected: 481 recommended: 358 | 2026-10-16T01:24:39+00:00 | Vulnerability · Source |
| CVE-2024-53208 | suse_vex | SUSE CVE CVE-2024-53208 | known affected: 364 known not affected: 417 recommended: 569 | 2026-10-16T01:24:37+00:00 | Vulnerability · Source |
| CVE-2024-53211 | suse_vex | SUSE CVE CVE-2024-53211 | known not affected: 547 recommended: 78 | 2026-10-16T01:24:36+00:00 | Vulnerability · Source |
| CVE-2024-53214 | suse_vex | SUSE CVE CVE-2024-53214 | known affected: 572 known not affected: 38 recommended: 777 | 2026-10-16T01:24:34+00:00 | Vulnerability · Source |
| CVE-2024-53216 | suse_vex | SUSE CVE CVE-2024-53216 | known affected: 666 known not affected: 221 recommended: 486 | 2026-10-16T01:24:32+00:00 | Vulnerability · Source |
| CVE-2024-53217 | suse_vex | SUSE CVE CVE-2024-53217 | known affected: 666 known not affected: 73 recommended: 499 | 2026-10-16T01:24:30+00:00 | Vulnerability · Source |
| CVE-2024-53219 | suse_vex | SUSE CVE CVE-2024-53219 | known affected: 382 known not affected: 263 recommended: 78 | 2026-10-16T01:24:28+00:00 | Vulnerability · Source |
| CVE-2024-53220 | suse_vex | SUSE CVE CVE-2024-53220 | known affected: 151 known not affected: 395 | 2026-10-16T01:24:26+00:00 | Vulnerability · Source |
| CVE-2024-53222 | suse_vex | SUSE CVE CVE-2024-53222 | known affected: 398 known not affected: 511 recommended: 486 | 2026-10-16T01:24:24+00:00 | Vulnerability · Source |
| CVE-2024-53223 | suse_vex | SUSE CVE CVE-2024-53223 | known not affected: 547 recommended: 78 | 2026-10-16T01:24:22+00:00 | Vulnerability · Source |
| CVE-2024-53230 | suse_vex | SUSE CVE CVE-2024-53230 | known affected: 394 known not affected: 515 recommended: 358 | 2026-10-16T01:24:20+00:00 | Vulnerability · Source |
| CVE-2024-53231 | suse_vex | SUSE CVE CVE-2024-53231 | known affected: 394 known not affected: 515 recommended: 358 | 2026-10-16T01:24:19+00:00 | Vulnerability · Source |
| CVE-2024-53234 | suse_vex | SUSE CVE CVE-2024-53234 | known affected: 398 known not affected: 512 recommended: 358 | 2026-10-16T01:24:17+00:00 | Vulnerability · Source |
| CVE-2024-53235 | suse_vex | SUSE CVE CVE-2024-53235 | known not affected: 546 recommended: 78 | 2026-10-16T01:24:15+00:00 | Vulnerability · Source |
| CVE-2024-53241 | suse_vex | SUSE CVE CVE-2024-53241 | known affected: 324 known not affected: 300 recommended: 775 | 2026-10-16T01:24:12+00:00 | Vulnerability · Source |
| CVE-2024-53257 | suse_vex | SUSE CVE CVE-2024-53257 | recommended: 4 | 2026-10-16T01:24:10+00:00 | Vulnerability · Source |
| CVE-2024-53259 | suse_vex | SUSE CVE CVE-2024-53259 | recommended: 17 | 2026-10-16T01:24:08+00:00 | Vulnerability · Source |
| CVE-2024-53263 | suse_vex | SUSE CVE CVE-2024-53263 | recommended: 11 | 2026-10-16T01:24:06+00:00 | Vulnerability · Source |
| CVE-2024-53264 | suse_vex | SUSE CVE CVE-2024-53264 | recommended: 4 | 2026-10-16T01:24:04+00:00 | Vulnerability · Source |
| CVE-2024-53427 | suse_vex | SUSE CVE CVE-2024-53427 | known affected: 0 known not affected: 77 recommended: 76 | 2026-10-16T01:24:02+00:00 | Vulnerability · Source |
| CVE-2024-53589 | suse_vex | SUSE CVE CVE-2024-53589 | known not affected: 245 | 2026-10-16T01:24:00+00:00 | Vulnerability · Source |
| CVE-2024-53681 | suse_vex | SUSE CVE CVE-2024-53681 | known affected: 0 known not affected: 456 recommended: 195 | 2026-10-16T01:23:57+00:00 | Vulnerability · Source |
| CVE-2024-53682 | suse_vex | SUSE CVE CVE-2024-53682 | known affected: 0 known not affected: 456 recommended: 109 | 2026-10-16T01:23:55+00:00 | Vulnerability · Source |
| CVE-2024-53685 | suse_vex | SUSE CVE CVE-2024-53685 | known affected: 394 known not affected: 394 recommended: 389 | 2026-10-16T01:23:53+00:00 | Vulnerability · Source |
| CVE-2024-53687 | suse_vex | SUSE CVE CVE-2024-53687 | known affected: 0 known not affected: 373 | 2026-10-16T01:23:51+00:00 | Vulnerability · Source |
| CVE-2024-53846 | suse_vex | SUSE CVE CVE-2024-53846 | known not affected: 100 | 2026-10-16T01:23:49+00:00 | Vulnerability · Source |
| CVE-2024-53858 | suse_vex | SUSE CVE CVE-2024-53858 | recommended: 4 | 2026-10-16T01:23:47+00:00 | Vulnerability · Source |
| CVE-2024-53861 | suse_vex | SUSE CVE CVE-2024-53861 | known affected: 394 known not affected: 122 recommended: 8 | 2026-10-16T01:23:45+00:00 | Vulnerability · Source |
| CVE-2024-53862 | suse_vex | SUSE CVE CVE-2024-53862 | recommended: 4 | 2026-10-16T01:23:44+00:00 | Vulnerability · Source |
| CVE-2024-53869 | suse_vex | SUSE CVE CVE-2024-53869 | known affected: 119 recommended: 289 | 2026-10-16T01:23:42+00:00 | Vulnerability · Source |
| CVE-2024-53920 | suse_vex | SUSE CVE CVE-2024-53920 | known not affected: 191 recommended: 204 | 2026-10-16T01:23:40+00:00 | Vulnerability · Source |
| CVE-2024-53981 | suse_vex | SUSE CVE CVE-2024-53981 | recommended: 9 | 2026-10-16T01:23:38+00:00 | Vulnerability · Source |
| CVE-2024-54031 | suse_vex | SUSE CVE CVE-2024-54031 | known affected: 2 known not affected: 337 recommended: 363 | 2026-10-16T01:23:36+00:00 | Vulnerability · Source |
| CVE-2024-54083 | suse_vex | SUSE CVE CVE-2024-54083 | recommended: 5 | 2026-10-16T01:23:35+00:00 | Vulnerability · Source |
| CVE-2024-54148 | suse_vex | SUSE CVE CVE-2024-54148 | recommended: 5 | 2026-10-16T01:23:33+00:00 | Vulnerability · Source |
| CVE-2024-54191 | suse_vex | SUSE CVE CVE-2024-54191 | known affected: 0 known not affected: 456 recommended: 109 | 2026-10-16T01:23:31+00:00 | Vulnerability · Source |
| CVE-2024-54193 | suse_vex | SUSE CVE CVE-2024-54193 | known affected: 0 known not affected: 456 recommended: 156 | 2026-10-16T01:23:29+00:00 | Vulnerability · Source |
| CVE-2024-54458 | suse_vex | SUSE CVE CVE-2024-54458 | known affected: 636 known not affected: 193 recommended: 431 | 2026-10-16T01:23:27+00:00 | Vulnerability · Source |
| CVE-2024-54460 | suse_vex | SUSE CVE CVE-2024-54460 | known affected: 0 known not affected: 456 recommended: 242 | 2026-10-16T01:23:25+00:00 | Vulnerability · Source |
| CVE-2024-54467 | suse_vex | SUSE CVE CVE-2024-54467 | known affected: 211 recommended: 584 | 2026-10-16T01:23:23+00:00 | Vulnerability · Source |
| CVE-2024-54534 | suse_vex | SUSE CVE CVE-2024-54534 | known affected: 217 recommended: 573 | 2026-10-16T01:23:21+00:00 | Vulnerability · Source |
| CVE-2024-54658 | suse_vex | SUSE CVE CVE-2024-54658 | known affected: 176 recommended: 615 | 2026-10-16T01:23:19+00:00 | Vulnerability · Source |