Process crash via null smartcard reader-state cleanup
Published Aug 1, 2026 · Updated Aug 1, 2026
Null pointer dereference in FreeRDP before 3.29.0 allows remote attackers to crash a client or proxy through malformed smartcard requests. The parsers set a nonzero cReaders before truncated rgReaderStates decoding fails, and free_reader_states_a/w then indexes the null array. A client must enable smartcard redirection and connect to a malicious RDP server, or a proxy must enable smartcard interception; impact is process termination only.
Summary
What happened
Null pointer dereference in FreeRDP before 3.29.0 allows remote attackers to crash a client or proxy through malformed smartcard requests. The parsers set a nonzero cReaders before truncated rgReaderStates decoding fails, and free_reader_states_a/w then indexes the null array. A client must enable smartcard redirection and connect to a malicious RDP server, or a proxy must enable smartcard interception; impact is process termination only.
The record
- CVE
- CVE-2026-67304
- Published
- Aug 1, 2026
- Updated
- Aug 1, 2026
- Vendor
- FreeRDP
- Product
- FreeRDP
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 1, 2026CVE publishedPublication date reported by the CVE source.
- Aug 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.29.0
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
- GHSA smartcard reader-state Docker reproductionproof 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