CVE-2025-32989: Gnutls: vulnerability in gnutls sct extension parsing
A heap-buffer-overread vulnerability was found in GnuTLS in how it handles the Certificate Transparency (CT) Signed Certificate Timestamp (SCT) extension during X.509 certificate parsing. This flaw allows a malicious user to create a certificate containing a malformed SCT extension (OID 1.3.6.1.4.1.11129.2.4.2) that contains sensitive data. This issue leads to the exposure of confidential information when GnuTLS verifies certificates from certain websites when the certificate (SCT) is not checked correctly.
Security readout for executives and security teams
Plain-English summary
GnuTLS may read beyond allocated memory when checking a certificate containing a malformed Certificate Transparency timestamp extension. An attacker-controlled certificate could expose a limited amount of confidential process memory. The supplied assessment indicates no integrity or availability impact.
Executive priority
Treat as a routine but time-bound security update. Prioritize exposed services and software that validates certificates from untrusted endpoints. The stated impact is limited information disclosure, and the bundle provides no evidence of active exploitation, so emergency response is not currently justified.
Technical view
CVE-2025-32989 is a remotely triggerable heap-buffer over-read in GnuTLS X.509 parsing of the SCT extension identified by OID 1.3.6.1.4.1.11129.2.4.2. CVSS 3.1 scores it 5.3: low-complexity, unauthenticated, and requiring no user interaction, with low confidentiality impact only.
Likely exposure
Exposure exists where applications use affected GnuTLS packages to verify attacker-influenced X.509 certificates. The bundle identifies affected Red Hat products, including specified RHEL 9 and 10 packages, OpenShift 4, Ceph Storage 7, and several containers. RHEL 8 is marked unaffected; RHEL 6 and 7 status is unknown.
Exploitation context
The supplied bundle does not identify active exploitation, and the CVE is not listed as KEV. Exploitation requires presenting a certificate with a malformed SCT extension to software that parses it through vulnerable GnuTLS code. No conclusion about public proof-of-concept availability can be drawn from the bundle.
Researcher notes
The bundle attributes CWE-295, although the described primitive is a heap-buffer over-read during SCT parsing. Exact upstream vulnerable and fixed version boundaries are not provided. The generic libgnutls record is also ambiguous, while Red Hat product statuses are more specific; validate against the applicable vendor advisory rather than extrapolating across distributions.
Mitigation direction
Inventory applications, hosts, and containers using GnuTLS for X.509 certificate verification.
Match installed package versions and product streams against the applicable Red Hat advisory.
Apply vendor-provided security updates from the relevant Red Hat errata.
Check current vendor guidance for products or versions whose status remains unknown.
Prioritize internet-facing certificate-verification paths and rebuild affected container images.
Validation and detection
Record installed GnuTLS package versions and their originating repositories or container layers.
Confirm each asset's product stream appears as affected, unaffected, or unknown in vendor guidance.
Verify updated packages match the applicable Red Hat security advisory.
Restart or redeploy dependent processes so they load the updated library.
Use approved regression tests to confirm certificate verification still functions after remediation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-295: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-295 · source CWE mapping
Improper Certificate Validation
Improper Certificate Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.