Client crash via stale Kerberos context handle
Published Mar 30, 2026 · Updated Mar 30, 2026
Double free in FreeRDP before 3.24.2 allows remote attackers to crash Kerberos-enabled RDP clients after failed NLA authentication. The Kerberos SSPI failure path frees its context but leaves PCtxtHandle pointing to released memory, so a later teardown frees the same context again. Exploitation requires a WITH_KRB5 build, a configured Kerberos realm, and a failed authentication after an earlier successful context call; the reported consequence is a client crash.
Summary
What happened
Double free in FreeRDP before 3.24.2 allows remote attackers to crash Kerberos-enabled RDP clients after failed NLA authentication. The Kerberos SSPI failure path frees its context but leaves PCtxtHandle pointing to released memory, so a later teardown frees the same context again. Exploitation requires a WITH_KRB5 build, a configured Kerberos realm, and a failed authentication after an earlier successful context call; the reported consequence is a client crash.
The record
- CVE
- CVE-2026-33995
- Published
- Mar 30, 2026
- Updated
- Mar 30, 2026
- Vendor
- FreeRDP
- Product
- FreeRDP
- Classifications
- CWE-415, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 30, 2026CVE publishedPublication date reported by the CVE source.
- Mar 30, 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=< 3.24.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
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