Client or server crash via unchecked allocation failure
Published Jul 24, 2025 · Updated Sep 1, 2026
NULL pointer dereference in libssh before 0.11.3 allows local users to crash an SSH client or server during key exchange. The KEX session-ID calculation fails to stop after a cryptographic memory-allocation error and dereferences the resulting NULL pointer. Low-privilege local access and a specific, high-complexity allocation-failure condition are required; the bounded consequence is process termination and service interruption.
Summary
What happened
NULL pointer dereference in libssh before 0.11.3 allows local users to crash an SSH client or server during key exchange. The KEX session-ID calculation fails to stop after a cryptographic memory-allocation error and dereferences the resulting NULL pointer. Low-privilege local access and a specific, high-complexity allocation-failure condition are required; the bounded consequence is process termination and service interruption.
The record
- CVE
- CVE-2025-8114
- Published
- Jul 24, 2025
- Updated
- Sep 1, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Enterprise Linux 10
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 24, 2025CVE publishedPublication date reported by the CVE source.
- Sep 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo