Hardened ImagesApplication · Redhat
CVE-2026-1584
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 · uneditedA flaw was found in gnutls. A remote, unauthenticated attacker can exploit this vulnerability by sending a specially crafted ClientHello message with an invalid Pre-Shared Key (PSK) binder value during the TLS handshake. This can lead to a NULL pointer dereference, causing the server to crash and resulting in a remote Denial of Service (DoS) condition.
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 confidenceA NULL pointer dereference vulnerability exists in GnuTLS when processing a TLS handshake with a Pre-Shared Key (PSK) extension containing an invalid binder value. An attacker can send a specially crafted ClientHello message that triggers this condition, causing the server to crash and result in a denial of service.
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
Hardened ImagesApplication
all versionsall versionsCVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify GnuTLS installationRun 'gnutls-cli --version' or 'rpm -q gnutls' (Red Hat) to confirm GnuTLS is present on the systemAffected if GnuTLS is installed - all versions are affected per the advisory
-
Check if TLS-PSK cipher suites are enabledRun 'gnutls-cli -l | grep -i psk' or review server TLS configuration files for enabled cipher suites containing 'PSK'Affected if Any PSK cipher suite (e.g., TLS_PSK_WITH_AES_128_CBC_SHA256) is listed as enabled
-
Verify PSK binding in TLS configurationInspect server configuration files (e.g., nginx/apache config, custom TLS configs) for lines containing 'psk' or 'pre_shared_key' directivesAffected if The server is configured to accept or require TLS-PSK connections
-
Test for PSK handshake exposureUse a TLS client tool (gnutls-cli or openssl s_client) with a PSK cipher suite flag to attempt connection: 'gnutls-cli -_priority +PSK example.com' or check server logs for PSK handshake attemptsAffected if The server responds to or accepts PSK-based TLS handshake attempts
The environment is affected if GnuTLS is installed and TLS-PSK cipher suites are enabled or configured on any service, since all versions of GnuTLS are vulnerable to NULL pointer dereference when processing invalid PSK binder values.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the vendor-supplied patch or update GnuTLS to the latest version that addresses this vulnerability. If immediate patching is not possible, consider filtering or rate-limiting TLS handshake attempts at the network perimeter to reduce attack surface.
Fix this in Hardened Images
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1584 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1584 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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