dbcve.org
Openshift Container PlatformApplication · Redhat

CVE-2025-32989

MEDIUM · 5.3 CVSS v3.1 Published 2025-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A heap-buffer-overread vulnerability exists in GnuTLS during X.509 certificate parsing when handling the Certificate Transparency Signed Certificate Timestamp (SCT) extension (OID 1.3.6.1.4.1.11129.2.4.2). A malicious certificate with a malformed SCT extension can cause GnuTLS to read beyond allocated buffer boundaries, potentially exposing sensitive memory contents during certificate verification.

MitigationUpdate GnuTLS to the latest patched version that addresses this vulnerability. Ensure certificate verification properly validates SCT extensions and test with certificates containing malformed SCT data.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Openshift Container PlatformApplication
Affected:= 4.0
Enterprise LinuxOperating system
Affected:= 6.0= 7.0= 8.0= 9.0= 10.0
GnutlsApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed GnuTLS version
    Run `gnutls-cli --version` or check the library file version (e.g., `rpm -q gnutls` on RHEL systems, or `dpkg -l libgnutls*` on Debian-based systems)
    Affected if The installed version falls within the affected ranges or is an unpatched version of GnuTLS (all versions are listed as affected)
  2. Verify if applications use GnuTLS for certificate handling
    Check which applications are linked against GnuTLS using `ldd <application_binary>` or review application documentation to confirm it uses GnuTLS for X.509 certificate verification
    Affected if The application uses GnuTLS for TLS/certificate operations and processes X.509 certificates
  3. Determine if certificate verification with SCT extension processing is enabled
    Review application configuration for Certificate Transparency / SCT validation settings. Check if the application processes certificates containing the SCT extension (OID 1.3.6.1.4.1.11129.2.4.2). For custom applications, inspect code or runtime logs for CT/SCT-related features
    Affected if Certificate verification is performed and SCT extensions are processed or parsed during X.509 certificate validation
  4. Check for system exposure to external certificates
    Identify if the system accepts or verifies X.509 certificates from untrusted sources, particularly in scenarios where an attacker could supply a malicious certificate (e.g., TLS connections, client certificate authentication, custom certificate parsing)
    Affected if The system processes certificates from untrusted or potentially malicious sources without additional validation layers
  5. Review Red Hat subsystem versions (for RHEL systems)
    Check OpenShift Container Platform version with `oc version` or RHEL version with `cat /etc/redhat-release`. For RHEL, also verify gnutls-related packages with `rpm -qa | grep gnutls`
    Affected if Running Red Hat Enterprise Linux 6.0, 7.0, 8.0, 9.0, or 10.0, or OpenShift Container Platform 4.0, with GnuTLS handling certificates

You are affected if your system runs any version of GnuTLS that processes X.509 certificates containing SCT extensions (OID 1.3.6.1.4.1.11129.2.4.2) without the patched fix applied.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update GnuTLS to the latest patched version that addresses this vulnerability. Ensure certificate verification properly validates SCT extensions and test with certificates containing malformed SCT data.

Fix this in Openshift Container Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32989 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32989 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data