| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| libboost-dev | clangml.0.5.2 | n/a | Unknown | CVE-2016-9840 | 5/23/2017 |
| boost | clangml.3.6.0 | n/a | Unknown | CVE-2016-9840 | 5/23/2017 |
| boost | clangml.3.6.0.5 | n/a | Unknown | CVE-2016-9840 | 5/23/2017 |
| libboost-dev | clangml.0.5.1 | n/a | Unknown | CVE-2016-9840 | 5/23/2017 |
| libboost-dev | clangml.3.8.0.1 | n/a | Unknown | CVE-2016-9840 | 5/23/2017 |
| dev-libs/boost | clangml.3.7.0.1 | n/a | Unknown | CVE-2016-9840 | 5/23/2017 |
| libboost-dev | clangml.3.6.0 | n/a | Unknown | CVE-2016-9840 | 5/23/2017 |
| boost | clangml.3.5.0.2 | n/a | Unknown | CVE-2016-9840 | 5/23/2017 |
| libboost-dev | clangml.3.6.0.4 | n/a | Unknown | CVE-2016-9840 | 5/23/2017 |
| boost | clangml.0.5.2 | n/a | Unknown | CVE-2016-9840 | 5/23/2017 |
| dev-libs/boost | clangml.3.7.0.2 | n/a | Unknown | CVE-2016-9840 | 5/23/2017 |
| dev-libs/boost | clangml.3.9.1 | n/a | Unknown | CVE-2016-9840 | 5/23/2017 |
| libboost-dev | clangml.3.5.0.1 | n/a | Unknown | CVE-2016-9840 | 5/23/2017 |
| boost | clangml.3.6.0.1 | n/a | Unknown | CVE-2016-9840 | 5/23/2017 |
| libboost-dev | clangml.3.7.0.2 | n/a | Unknown | CVE-2016-9840 | 5/23/2017 |
| dev-libs/boost | clangml.0.5.2 | n/a | Unknown | CVE-2016-9840 | 5/23/2017 |
| dev-libs/boost | clangml.3.6.0.6 | n/a | Unknown | CVE-2016-9840 | 5/23/2017 |
| dev-libs/boost | clangml.0.5.1 | n/a | Unknown | CVE-2016-9840 | 5/23/2017 |
| boost | clangml.3.9.1 | n/a | Unknown | CVE-2016-9840 | 5/23/2017 |
| libboost-dev | clangml.3.6.0.5 | n/a | Unknown | CVE-2016-9840 | 5/23/2017 |