Tool crash via unchecked terminfo substring copy
Published Mar 19, 2026 · Updated Mar 19, 2026
Stack-based buffer overflow in GNU ncurses infocmp before 6.5-20251213 allows local users to crash the tool via crafted terminfo data. In analyze_string(), strlen(cp) determines a strncpy length into the 4,096-byte stack buffer buf2 without checking that the substring fits. A victim must run infocmp in initialization-analysis mode against the crafted entry; ordinary invocations do not reach the affected path.
Summary
What happened
Stack-based buffer overflow in GNU ncurses infocmp before 6.5-20251213 allows local users to crash the tool via crafted terminfo data. In analyze_string(), strlen(cp) determines a strncpy length into the 4,096-byte stack buffer buf2 without checking that the substring fits. A victim must run infocmp in initialization-analysis mode against the crafted entry; ordinary invocations do not reach the affected path.
The record
- CVE
- CVE-2025-69720
- Published
- Mar 19, 2026
- Updated
- Mar 19, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-121, CWE-120, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 19, 2026CVE publishedPublication date reported by the CVE source.
- Mar 19, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Crafted terminfo entry proof of conceptproof 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