Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
High

Double-free in GnuTLS SAN otherName export logic

IdentifiersCVE-2025-32988CWE-415· Double Free

CVE-2025-32988 is a double-free vulnerability in GnuTLS caused by incorrect ownership handling during export of Subject Alternative Name (SAN) entries that contain an otherName value. When processing an otherName whose type-id OID is invalid or malformed, GnuTLS may invoke asn1_delete_structure() on an ASN.1 node that it does not own. The same structure may later be freed again by the parent function or caller, resulting in a double-free condition. The issue is reachable through public GnuTLS APIs and affects the SAN export logic for malformed otherName content.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can crash the consuming application, causing denial of service. Depending on memory allocator behavior and surrounding memory state, the double-free may also lead to memory corruption, which could potentially enable more severe consequences than a simple crash. The provided information specifically confirms denial of service or memory corruption.

Mitigation

If you can’t patch tonight, do this now.

Until patched, reduce exposure by avoiding or rejecting untrusted certificates or inputs that cause processing/export of SAN entries containing otherName values with malformed or invalid type-id OIDs, where operationally feasible. Applications that parse or export certificate SAN data from untrusted sources should isolate that processing and monitor for crashes. These are only partial mitigations; patching is the reliable fix.

Remediation

Patch, then assume compromise.

Apply a vendor fix from GnuTLS or consume an updated package from your operating system or product vendor that includes the correction for CVE-2025-32988. Because the flaw is in ownership handling in SAN otherName export logic, remediation requires updating to a fixed GnuTLS build rather than configuration-only changes.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GNU ProjectGnutlsapplication
Red HatEnterprise Linuxoperating_system
Red HatOpenshift Container Platformapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity6

Community discussion across Reddit, Mastodon, and other social sources.