Application crash via overlong command file
Published Jan 15, 2026 · Updated Jan 15, 2026
Buffer overflow in Cmder Console Emulator 1.3.18 allows attackers to crash the application when a local user opens a crafted .cmd file. Cmder.exe command-file handling accepts an overlong sequence of repeated characters without enforcing the destination buffer's bounds. A user must open the malicious file; the documented consequence is termination of the console emulator, not code execution or data access.
Summary
What happened
Buffer overflow in Cmder Console Emulator 1.3.18 allows attackers to crash the application when a local user opens a crafted .cmd file. Cmder.exe command-file handling accepts an overlong sequence of repeated characters without enforcing the destination buffer's bounds. A user must open the malicious file; the documented consequence is termination of the console emulator, not code execution or data access.
The record
- CVE
- CVE-2021-47781
- Published
- Jan 15, 2026
- Updated
- Jan 15, 2026
- Vendor
- Cmder
- Product
- Cmder
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 15, 2026CVE publishedPublication date reported by the CVE source.
- Jan 15, 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=1.3.18
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
- Cmder Console Emulator 1.3.18 Cmder.exe Denial of Service PoCproof of concept · unverified
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