Local editor crash via crafted directory name
Published Apr 22, 2026 · Updated Apr 22, 2026
Format string injection in nano allows local users to crash the editor by opening a crafted directory name containing printf specifiers. The statusline() error path passes the directory name as a formatting template rather than inert text, so specifiers consume unintended arguments and trigger a segmentation fault. Exploitation requires a local user to create the directory and a nano session to display the associated error; the observed consequence is termination of that nano process.
Summary
What happened
Format string injection in nano allows local users to crash the editor by opening a crafted directory name containing printf specifiers. The statusline() error path passes the directory name as a formatting template rather than inert text, so specifiers consume unintended arguments and trigger a segmentation fault. Exploitation requires a local user to create the directory and a nano session to display the associated error; the observed consequence is termination of that nano process.
The record
- CVE
- CVE-2026-6843
- Published
- Apr 22, 2026
- Updated
- Apr 22, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Enterprise Linux 6
- Classifications
- CWE-134, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 22, 2026CVE publishedPublication date reported by the CVE source.
- Apr 22, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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