| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| binutils-dev | clangml.3.6.0 | n/a | High | CVE-2025-69650 | 3/6/2026 |
| binutils | clangml.3.7.0 | n/a | High | CVE-2025-69650 | 3/6/2026 |
| binutils-dev | clangml.3.5.0 | n/a | High | CVE-2025-69650 | 3/6/2026 |
| binutils | clangml.3.8.0.1 | n/a | High | CVE-2025-69650 | 3/6/2026 |
| sys-devel/binutils | clangml.3.8.0.1 | n/a | High | CVE-2025-69650 | 3/6/2026 |
| binutils | clangml.3.6.0.5 | n/a | High | CVE-2025-69650 | 3/6/2026 |
| binutils-dev | clangml.3.6.0.5 | n/a | High | CVE-2025-69650 | 3/6/2026 |
| sys-devel/binutils | clangml.3.6.0.2 | n/a | High | CVE-2025-69650 | 3/6/2026 |
| binutils-dev | clangml.3.7.0.1 | n/a | High | CVE-2025-69650 | 3/6/2026 |
| sys-devel/binutils | clangml.3.6.0.4 | n/a | High | CVE-2025-69650 | 3/6/2026 |
| sys-devel/binutils | clangml.3.6.0 | n/a | High | CVE-2025-69650 | 3/6/2026 |
| sys-devel/binutils | clangml.3.7.0.1 | n/a | High | CVE-2025-69650 | 3/6/2026 |
| binutils-dev | clangml.3.7.0 | n/a | High | CVE-2025-69650 | 3/6/2026 |
| binutils-dev | clangml.3.7.0.2 | n/a | High | CVE-2025-69650 | 3/6/2026 |
| sys-devel/binutils | clangml.3.5.0 | n/a | High | CVE-2025-69650 | 3/6/2026 |
| sys-devel/binutils | clangml.0.5.2 | n/a | High | CVE-2025-69650 | 3/6/2026 |
| binutils | clangml.3.9.1 | n/a | High | CVE-2025-69650 | 3/6/2026 |
| sys-devel/binutils | clangml.3.7.0.2 | n/a | High | CVE-2025-69650 | 3/6/2026 |
| binutils-dev | clangml.0.5.2 | n/a | High | CVE-2025-69650 | 3/6/2026 |
| sys-devel/binutils | clangml.3.5.0.2 | n/a | High | CVE-2025-69650 | 3/6/2026 |