# CVE-2025-32988: Gnutls: vulnerability in gnutls othername san export

> A double-free vulnerability in GnuTLS SAN export logic allows attackers to cause denial of service or potential code execution via malformed otherName entries.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H`)
- **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:** 15 Oct 2026
- **Also known as:** ALPINE-CVE-2025-32988, AZL-65085, AZL-65106, BELL-CVE-2025-32988, CLSA-2025-1756751437, CLSA-2025-1756759707, CLSA-2025-1756760036, DEBIAN-CVE-2025-32988, GHSA-fv5h-vqpf-6fqj, JLSEC-2026-527, UBUNTU-CVE-2025-32988

## What is CVE-2025-32988?

CVE-2025-32988 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 flaw was found in GnuTLS. A double-free vulnerability exists in GnuTLS due to incorrect ownership handling in the export logic of Subject Alternative Name (SAN) entries containing an otherName. If the type-id OID is invalid or malformed, GnuTLS will call asn1_delete_structure() on an ASN.1 node it does not own, leading to a double-free condition when the parent function or caller later attempts to free the same structure.

This vulnerability can be triggered using only public GnuTLS APIs and may result in denial of service or memory corruption, depending on allocator behavior.

Weakness: CWE-415 (Double Free)

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

It affects 3 products.


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

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

Apply the vendor's patch.

## Is CVE-2025-32988 being exploited?

There is no known exploitation of CVE-2025-32988 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-32988 and fix it if it is affected.

What it is: CVE-2025-32988 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-32988 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-32988/ (Markdown: https://insights.sbomify.com/CVE-2025-32988/index.md)
```

## Sources

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

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