# CVE-2025-32990: Gnutls: vulnerability in gnutls certtool template parsing

> A heap-buffer-overflow in GnuTLS certtool allows attackers to cause memory corruption and system crashes via malicious template files.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jul 2025
- **Updated:** 1 Sep 2026
- **Also known as:** ALPINE-CVE-2025-32990, AZL-65091, AZL-65100, BELL-CVE-2025-32990, CLSA-2025-1757949650, CLSA-2025-1758022425, CLSA-2025-1758022501, CLSA-2025-1758025991, CLSA-2025-1758816068, CLSA-2025-1759334361, CLSA-2025-1759334959, CLSA-2025-1759335207, DEBIAN-CVE-2025-32990, GHSA-v8v5-8mm8-3j8p, SUSE-SU-2025:02520-1, SUSE-SU-2025:02521-1, UBUNTU-CVE-2025-32990

## What is CVE-2025-32990?

CVE-2025-32990 is a medium-severity memory corruption vulnerability in Gnu Gnutls, published on 10 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A heap-buffer-overflow (off-by-one) flaw was found in the GnuTLS software in the template parsing logic within the certtool utility. When it reads certain settings from a template file, it allows an attacker to cause an out-of-bounds (OOB) NULL pointer write, resulting in memory corruption and a denial-of-service (DoS) that could potentially crash the system.

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2025-32990?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gnutls` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 3.3.27-3.12.1 |
| `gnutls` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 3.4.17-8.20.1 |

Products: Gnu Gnutls, Redhat Enterprise Linux, Redhat Openshift Container Platform.

## How do I fix CVE-2025-32990?

Apply the vendor's patch.

## Is CVE-2025-32990 being exploited?

There is no known exploitation of CVE-2025-32990 in the wild and no public exploit code.

## Other vulnerabilities in Gnu Gnutls

- [CVE-2008-1948](https://insights.sbomify.com/CVE-2008-1948/): Memory corruption in n/a (critical 10.0)
- [CVE-2017-5334](https://insights.sbomify.com/CVE-2017-5334/): Use after free in n/a (critical 9.8)
- [CVE-2017-5336](https://insights.sbomify.com/CVE-2017-5336/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-5337](https://insights.sbomify.com/CVE-2017-5337/): Memory corruption in n/a (critical 9.8)
- [CVE-2008-1949](https://insights.sbomify.com/CVE-2008-1949/): Null dereference in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-32990 and fix it if it is affected.

What it is: CVE-2025-32990 is a medium-severity memory corruption vulnerability in Gnu Gnutls, published on 10 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-32990 in the wild and no public exploit code.

Affected product: Gnu Gnutls. 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-2025-32990/ (Markdown: https://insights.sbomify.com/CVE-2025-32990/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-32990
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-32990
- OSV: https://osv.dev/vulnerability/CVE-2025-32990

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-32990/
Summaries are generated and may contain mistakes; the official description above is the record.