Heap disclosure via short NTLM challenge
Published Jun 23, 2026 · Updated Jun 23, 2026
Memory disclosure in GNU SASL before 2.2.4 allows remote attackers controlling an NTLM server to read client heap data. _gsasl_ntlm_client_step accepts a short Type-2 challenge, copies it into a malloc-allocated fixed-size structure, and passes the uninitialized tail to libntlm. The leak requires an NTLM client connection to an attacker-controlled server, which receives the uninitialized bytes in the client's response.
Summary
What happened
Memory disclosure in GNU SASL before 2.2.4 allows remote attackers controlling an NTLM server to read client heap data. _gsasl_ntlm_client_step accepts a short Type-2 challenge, copies it into a malloc-allocated fixed-size structure, and passes the uninitialized tail to libntlm. The leak requires an NTLM client connection to an attacker-controlled server, which receives the uninitialized bytes in the client's response.
The record
- CVE
- CVE-2026-56968
- Published
- Jun 23, 2026
- Updated
- Jun 23, 2026
- Vendor
- The GnuPG Project
- Product
- GNU SASL
- Classifications
- CWE-839, CWE-908
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 23, 2026CVE publishedPublication date reported by the CVE source.
- Jun 23, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.2.4
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.
Weakness, pattern, technique
Public exploit references
- Short NTLM Type-2 challenge reproducerproof of concept · demonstrated
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