| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| gcc-g++ | libbinaryen.115.0.0 | n/a | Unknown | CVE-2022-27943 | 3/26/2022 |
| gcc-g++ | libbinaryen.102.0.2 | n/a | Unknown | CVE-2022-27943 | 3/26/2022 |
| gcc-g++ | libbinaryen.110.0.0 | n/a | Unknown | CVE-2022-27943 | 3/26/2022 |
| gcc-g++ | libbinaryen.119.0.0 | n/a | Unknown | CVE-2022-27943 | 3/26/2022 |
| gcc-g++ | libbinaryen.111.0.0 | n/a | Unknown | CVE-2022-27943 | 3/26/2022 |
| gcc-g++ | libbinaryen.113.0.0 | n/a | Unknown | CVE-2022-27943 | 3/26/2022 |
| gcc-g++ | libbinaryen.107.0.1 | n/a | Unknown | CVE-2022-27943 | 3/26/2022 |
| gcc-g++ | libbinaryen.106.0.0 | n/a | Unknown | CVE-2022-27943 | 3/26/2022 |
| gcc-g++ | libbinaryen.109.0.1 | n/a | Unknown | CVE-2022-27943 | 3/26/2022 |
| gcc-g++ | libbinaryen.108.0.0 | n/a | Unknown | CVE-2022-27943 | 3/26/2022 |
| gcc-g++ | libbinaryen.102.0.4 | n/a | Unknown | CVE-2022-27943 | 3/26/2022 |
| gcc-g++ | libbinaryen.116.0.0 | n/a | Unknown | CVE-2022-27943 | 3/26/2022 |
| gcc-g++ | libbinaryen.105.0.0 | n/a | Unknown | CVE-2022-27943 | 3/26/2022 |
| gcc-g++ | libbinaryen.118.0.0 | n/a | Unknown | CVE-2022-27943 | 3/26/2022 |
| gcc-g++ | libbinaryen.104.0.0 | n/a | Unknown | CVE-2022-27943 | 3/26/2022 |
| gcc-g++ | libbinaryen.120.0.0 | n/a | Unknown | CVE-2022-27943 | 3/26/2022 |
| gcc-g++ | libbinaryen.117.0.0 | n/a | Unknown | CVE-2022-27943 | 3/26/2022 |
| gcc-g++ | libbinaryen.111.1.0 | n/a | Unknown | CVE-2022-27943 | 3/26/2022 |
| gcc-g++ | libbinaryen.103.0.1 | n/a | Unknown | CVE-2021-46195 | 1/14/2022 |
| gcc-g++ | libbinaryen.115.0.0 | n/a | Unknown | CVE-2021-46195 | 1/14/2022 |