VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2012-3216 | suse_vex | SUSE CVE CVE-2012-3216 | known affected: 1 known not affected: 51 recommended: 188 | 2026-07-26T01:47:10+00:00 | Vulnerability · Source |
| CVE-2012-3432 | suse_vex | SUSE CVE CVE-2012-3432 | recommended: 242 | 2026-07-26T01:47:04+00:00 | Vulnerability · Source |
| CVE-2012-3433 | suse_vex | SUSE CVE CVE-2012-3433 | recommended: 182 | 2026-07-26T01:47:02+00:00 | Vulnerability · Source |
| CVE-2012-3466 | suse_vex | SUSE CVE CVE-2012-3466 | recommended: 160 | 2026-07-26T01:47:00+00:00 | Vulnerability · Source |
| CVE-2012-3502 | suse_vex | SUSE CVE CVE-2012-3502 | recommended: 206 | 2026-07-26T01:46:58+00:00 | Vulnerability · Source |
| CVE-2012-3510 | suse_vex | SUSE CVE CVE-2012-3510 | known not affected: 409 | 2026-07-26T01:46:56+00:00 | Vulnerability · Source |
| CVE-2012-3547 | suse_vex | SUSE CVE CVE-2012-3547 | known affected: 22 recommended: 243 | 2026-07-26T01:46:50+00:00 | Vulnerability · Source |
| CVE-2012-3954 | suse_vex | SUSE CVE CVE-2012-3954 | recommended: 199 | 2026-07-26T01:46:46+00:00 | Vulnerability · Source |
| CVE-2012-3955 | suse_vex | SUSE CVE CVE-2012-3955 | known affected: 8 recommended: 195 | 2026-07-26T01:46:44+00:00 | Vulnerability · Source |
| CVE-2012-3959 | suse_vex | SUSE CVE CVE-2012-3959 | known affected: 2 recommended: 201 | 2026-07-26T01:46:40+00:00 | Vulnerability · Source |
| CVE-2012-3967 | suse_vex | SUSE CVE CVE-2012-3967 | known affected: 2 recommended: 205 | 2026-07-26T01:46:38+00:00 | Vulnerability · Source |
| CVE-2012-3968 | suse_vex | SUSE CVE CVE-2012-3968 | known affected: 2 recommended: 201 | 2026-07-26T01:46:36+00:00 | Vulnerability · Source |
| CVE-2012-3969 | suse_vex | SUSE CVE CVE-2012-3969 | known affected: 2 recommended: 205 | 2026-07-26T01:46:34+00:00 | Vulnerability · Source |
| CVE-2012-3972 | suse_vex | SUSE CVE CVE-2012-3972 | known affected: 2 recommended: 205 | 2026-07-26T01:46:32+00:00 | Vulnerability · Source |
| CVE-2012-3985 | suse_vex | SUSE CVE CVE-2012-3985 | known affected: 2 recommended: 154 | 2026-07-26T01:46:22+00:00 | Vulnerability · Source |
| CVE-2012-3988 | suse_vex | SUSE CVE CVE-2012-3988 | known not affected: 39 recommended: 162 | 2026-07-26T01:46:20+00:00 | Vulnerability · Source |
| CVE-2012-4183 | suse_vex | SUSE CVE CVE-2012-4183 | known not affected: 39 recommended: 158 | 2026-07-26T01:46:09+00:00 | Vulnerability · Source |
| CVE-2012-4184 | suse_vex | SUSE CVE CVE-2012-4184 | known not affected: 39 recommended: 158 | 2026-07-26T01:46:07+00:00 | Vulnerability · Source |
| CVE-2012-4194 | suse_vex | SUSE CVE CVE-2012-4194 | known not affected: 39 recommended: 173 | 2026-07-26T01:46:05+00:00 | Vulnerability · Source |
| CVE-2012-4203 | suse_vex | SUSE CVE CVE-2012-4203 | known affected: 3 recommended: 138 | 2026-07-26T01:46:00+00:00 | Vulnerability · Source |
| CVE-2012-4205 | suse_vex | SUSE CVE CVE-2012-4205 | known affected: 3 recommended: 179 | 2026-07-26T01:45:58+00:00 | Vulnerability · Source |
| CVE-2012-4213 | suse_vex | SUSE CVE CVE-2012-4213 | known affected: 3 recommended: 187 | 2026-07-26T01:45:53+00:00 | Vulnerability · Source |
| CVE-2012-4216 | suse_vex | SUSE CVE CVE-2012-4216 | known affected: 3 recommended: 183 | 2026-07-26T01:45:51+00:00 | Vulnerability · Source |
| CVE-2012-4217 | suse_vex | SUSE CVE CVE-2012-4217 | known affected: 3 recommended: 183 | 2026-07-26T01:45:49+00:00 | Vulnerability · Source |
| CVE-2012-4285 | suse_vex | SUSE CVE CVE-2012-4285 | recommended: 159 | 2026-07-26T01:45:44+00:00 | Vulnerability · Source |
| CVE-2012-4289 | suse_vex | SUSE CVE CVE-2012-4289 | recommended: 159 | 2026-07-26T01:45:40+00:00 | Vulnerability · Source |
| CVE-2012-4293 | suse_vex | SUSE CVE CVE-2012-4293 | recommended: 159 | 2026-07-26T01:45:37+00:00 | Vulnerability · Source |
| CVE-2012-4411 | suse_vex | SUSE CVE CVE-2012-4411 | recommended: 250 | 2026-07-26T01:45:32+00:00 | Vulnerability · Source |
| CVE-2012-4425 | suse_vex | SUSE CVE CVE-2012-4425 | recommended: 205 | 2026-07-26T01:45:28+00:00 | Vulnerability · Source |
| CVE-2012-4444 | suse_vex | SUSE CVE CVE-2012-4444 | known not affected: 495 recommended: 44 | 2026-07-26T01:45:26+00:00 | Vulnerability · Source |
| CVE-2012-4508 | suse_vex | SUSE CVE CVE-2012-4508 | known not affected: 493 recommended: 84 | 2026-07-26T01:45:23+00:00 | Vulnerability · Source |
| CVE-2012-4530 | suse_vex | SUSE CVE CVE-2012-4530 | known not affected: 495 recommended: 128 | 2026-07-26T01:45:19+00:00 | Vulnerability · Source |
| CVE-2012-4536 | suse_vex | SUSE CVE CVE-2012-4536 | recommended: 241 | 2026-07-26T01:45:16+00:00 | Vulnerability · Source |
| CVE-2012-4537 | suse_vex | SUSE CVE CVE-2012-4537 | known not affected: 1 recommended: 250 | 2026-07-26T01:45:14+00:00 | Vulnerability · Source |
| CVE-2012-4564 | suse_vex | SUSE CVE CVE-2012-4564 | known affected: 409 known not affected: 55 recommended: 319 | 2026-07-26T01:45:12+00:00 | Vulnerability · Source |
| CVE-2012-5071 | suse_vex | SUSE CVE CVE-2012-5071 | known affected: 1 known not affected: 51 recommended: 171 | 2026-07-26T01:45:08+00:00 | Vulnerability · Source |
| CVE-2012-5085 | suse_vex | SUSE CVE CVE-2012-5085 | known affected: 1 known not affected: 51 recommended: 79 | 2026-07-26T01:45:06+00:00 | Vulnerability · Source |
| CVE-2012-5237 | suse_vex | SUSE CVE CVE-2012-5237 | recommended: 138 | 2026-07-26T01:45:04+00:00 | Vulnerability · Source |
| CVE-2012-5375 | suse_vex | SUSE CVE CVE-2012-5375 | known not affected: 111 | 2026-07-26T01:45:02+00:00 | Vulnerability · Source |
| CVE-2012-5511 | suse_vex | SUSE CVE CVE-2012-5511 | known not affected: 1 recommended: 227 | 2026-07-26T01:45:00+00:00 | Vulnerability · Source |
| CVE-2012-5517 | suse_vex | SUSE CVE CVE-2012-5517 | known not affected: 410 recommended: 144 | 2026-07-26T01:44:57+00:00 | Vulnerability · Source |
| CVE-2012-5525 | suse_vex | SUSE CVE CVE-2012-5525 | known not affected: 1 recommended: 173 | 2026-07-26T01:44:55+00:00 | Vulnerability · Source |
| CVE-2012-5577 | suse_vex | SUSE CVE CVE-2012-5577 | known not affected: 79 | 2026-07-26T01:44:53+00:00 | Vulnerability · Source |
| CVE-2012-5595 | suse_vex | SUSE CVE CVE-2012-5595 | known not affected: 122 recommended: 159 | 2026-07-26T01:44:48+00:00 | Vulnerability · Source |
| CVE-2012-5599 | suse_vex | SUSE CVE CVE-2012-5599 | known not affected: 122 recommended: 159 | 2026-07-26T01:44:46+00:00 | Vulnerability · Source |
| CVE-2012-5601 | suse_vex | SUSE CVE CVE-2012-5601 | recommended: 159 | 2026-07-26T01:44:44+00:00 | Vulnerability · Source |
| CVE-2012-5612 | suse_vex | SUSE CVE CVE-2012-5612 | known not affected: 84 recommended: 252 | 2026-07-26T01:44:40+00:00 | Vulnerability · Source |
| CVE-2012-5688 | suse_vex | SUSE CVE CVE-2012-5688 | known not affected: 485 recommended: 411 | 2026-07-26T01:44:37+00:00 | Vulnerability · Source |
| CVE-2012-5830 | suse_vex | SUSE CVE CVE-2012-5830 | known affected: 1 recommended: 187 | 2026-07-26T01:44:35+00:00 | Vulnerability · Source |
| CVE-2012-5835 | suse_vex | SUSE CVE CVE-2012-5835 | known affected: 3 recommended: 183 | 2026-07-26T01:44:33+00:00 | Vulnerability · Source |