# CVE-2021-46195: Denial of service in n/a > Attackers can cause a Denial of Service in GCC v12.0 by triggering uncontrolled recursion in the Rust demangler, consuming excessive CPU and memory. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 14 Jan 2022 - **Updated:** 14 Oct 2026 - **Also known as:** ALSA-2022:8415, CLSA-2026-1780063601, DEBIAN-CVE-2021-46195, GHSA-gr6j-4vhj-c665, RHSA-2022:8415, UBUNTU-CVE-2021-46195 ## What is CVE-2021-46195? CVE-2021-46195 is a medium-severity denial of service vulnerability in n/a, published on 14 Jan 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description GCC v12.0 was discovered to contain an uncontrolled recursion via the component libiberty/rust-demangle.c. This vulnerability allows attackers to cause a Denial of Service (DoS) by consuming excessive CPU and memory resources. Weakness: CWE-674 (Uncontrolled Recursion) ## Which versions are affected by CVE-2021-46195? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `mingw32-cpp` | AlmaLinux:9 | All versions | 12.0.1-11.2.el9 | | `mingw32-gcc` | AlmaLinux:9 | All versions | 12.0.1-11.2.el9 | | `mingw32-gcc-c++` | AlmaLinux:9 | All versions | 12.0.1-11.2.el9 | | `mingw32-libgcc` | AlmaLinux:9 | All versions | 12.0.1-11.2.el9 | | `mingw64-cpp` | AlmaLinux:9 | All versions | 12.0.1-11.2.el9 | | `mingw64-gcc` | AlmaLinux:9 | All versions | 12.0.1-11.2.el9 | | `mingw64-gcc-c++` | AlmaLinux:9 | All versions | 12.0.1-11.2.el9 | | `mingw64-libgcc` | AlmaLinux:9 | All versions | 12.0.1-11.2.el9 | | `mingw-gcc` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `mingw-gcc-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `mingw-gcc-debugsource` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `mingw32-cpp` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `mingw32-cpp-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `mingw32-gcc` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `mingw32-gcc-c++` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `mingw32-gcc-c++-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `mingw32-gcc-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `mingw32-gcc-gfortran-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `mingw32-gcc-objc++-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `mingw32-gcc-objc-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `mingw32-libgcc` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `mingw64-cpp` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `mingw64-cpp-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `mingw64-gcc` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `mingw64-gcc-c++` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `mingw64-gcc-c++-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `mingw64-gcc-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `mingw64-gcc-gfortran-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `mingw64-gcc-objc++-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `mingw64-gcc-objc-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `mingw64-libgcc` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `ucrt64-cpp-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `ucrt64-gcc-c++-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `ucrt64-gcc-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `ucrt64-gcc-gfortran-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `ucrt64-gcc-objc++-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | | `ucrt64-gcc-objc-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:12.0.1-11.2.el9 | Products: Gnu Gcc. ## How do I fix CVE-2021-46195? Upgrade to a fixed version. ## Is CVE-2021-46195 being exploited? There is no known exploitation of CVE-2021-46195 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2018-12886](https://insights.sbomify.com/CVE-2018-12886/): Security feature bypass in n/a (high 8.1) - [CVE-2002-2439](https://insights.sbomify.com/CVE-2002-2439/): Integer overflow in the new[] operator in gcc before 4.8.0 allows attackers to have unspecified impacts. (high 7.8) - [CVE-2019-15847](https://insights.sbomify.com/CVE-2019-15847/): Weak cryptography in n/a (high 7.5) - [CVE-2008-1367](https://insights.sbomify.com/CVE-2008-1367/): Memory corruption in n/a (high 7.5) - [CVE-2008-1685](https://insights.sbomify.com/CVE-2008-1685/): Integer overflow in n/a (medium 6.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2021-46195 and fix it if it is affected. What it is: CVE-2021-46195 is a medium-severity denial of service vulnerability in n/a, published on 14 Jan 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2021-46195 in the wild and no public exploit code. Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2021-46195/ (Markdown: https://insights.sbomify.com/CVE-2021-46195/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2021-46195 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-46195 - OSV: https://osv.dev/vulnerability/CVE-2021-46195 --- From sbomify Insights: https://insights.sbomify.com/CVE-2021-46195/ Summaries are generated and may contain mistakes; the official description above is the record.