dbcve.org
Openshift Container PlatformApplication · Redhat

CVE-2025-32990

HIGH · 8.2 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 →
91/100
Remediation priority · Urgent
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-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.

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 · high confidence

Heap buffer overflow (off-by-one) in GnuTLS certtool template parsing logic allows an attacker controlling template file content to write a NULL pointer out-of-bounds, causing memory corruption and potential system crash.

MitigationUpdate GnuTLS to the patched version when released; avoid using untrusted or externally-sourced template files with certtool until patched.

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
None
Integrity
Low
Availability
High

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

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. Verify GnuTLS certtool is installed
    Run 'which certtool' or 'rpm -q gnutls-utils' (RHEL) to locate the certtool binary
    Affected if certtool binary exists on the system
  2. Confirm GnuTLS version
    Run 'certtool --version' or 'gnutls-cli --version' to get the installed GnuTLS version number
    Affected if The installed version falls within Red Hat EL 6.0-10.0 or is any version of GnuTLS (as all versions are affected)
  3. Identify template file usage
    Search for .template files in use, check for 'certtool --template' or '--load-template' arguments in scripts, cron jobs, or configuration files
    Affected if Template files are processed by certtool, enabling the vulnerable parsing code path
  4. Check for certtool crash logs
    Review system logs (/var/log/messages, journalctl, or audit logs) for certtool segfaults, abort signals, or heap-corruption errors
    Affected if Recent crashes or memory corruption indicators appear in certtool process history

A user is affected if GnuTLS certtool is installed AND template file processing is in use, regardless of version since all versions are vulnerable.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update GnuTLS to the patched version when released; avoid using untrusted or externally-sourced template files with certtool until patched.

Recommended fix Moderate confidence

Latest available GnuTLS version in your RHEL repository (see 'dnf info gnutls' or 'yum info gnutls')

  1. Update the GnuTLS package using your system's package manager: 'sudo dnf update gnutls' (RHEL 8/9) or 'sudo yum update gnutls' (RHEL 7)
  2. For RHEL 7, use 'sudo yum update gnutls'
  3. After updating, verify the new GnuTLS version with 'gnutls-cli --version'
  4. Restart any services that use GnuTLS (such as web servers, SSH daemons, or container runtimes) to ensure the updated library is loaded
  5. Test that the certtool utility functions correctly with 'certtool --version'
Caveat Ensure compatibility with applications relying on GnuTLS after update; test critical certificate operations

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32990 — 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-32990 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