CVE-2026-6843: Nano: nano: format string vulnerability leads to denial of service
A flaw was found in nano. A local user could exploit a format string vulnerability in the `statusline()` function. By creating a directory with a name containing `printf` specifiers, the application attempts to display this name, leading to a segmentation fault (SEGV). This results in a Denial of Service (DoS) for the `nano` application.
Security readout for executives and security teams
Plain-English summary
A local actor can cause the nano text editor to crash when it displays a specially named directory. The documented impact is interruption of nano, not data theft, privilege escalation, or system-wide compromise. Exploitation requires local filesystem influence and user interaction.
Executive priority
Treat as a routine, moderate-priority availability issue. Prioritize shared administrative systems and environments where untrusted local users can influence paths used by operators. Emergency response is not supported by the supplied evidence, but vendor updates should be tracked and deployed.
Technical view
CVE-2026-6843 is a CWE-134 format-string flaw in nano’s statusline() function. A directory name containing printf-style specifiers can be interpreted while displayed, causing a segmentation fault. CVSS 3.1 is 5.5: local access, low complexity, no privileges, user interaction, and high availability impact only.
Likely exposure
The bundle identifies nano packages across Red Hat Enterprise Linux 6 through 10 and related RHEL CoreOS packages in OpenShift Container Platform 4 as affected. Exact vulnerable and fixed package versions are not provided, so presence of these products alone cannot confirm exploitable package status.
Exploitation context
CISA KEV status is false, and the supplied sources do not report active exploitation. A plausible scenario requires someone to create a specially named directory locally and another user to make nano display that path. Evidence supports application denial of service only.
Researcher notes
The sources establish the vulnerable function, trigger class, segmentation-fault outcome, and affected Red Hat product families. They do not provide precise version boundaries, patch identifiers, or evidence of code execution. Assessment should remain limited to local, interaction-dependent nano denial of service unless further vendor evidence emerges.
Mitigation direction
Check Red Hat guidance for affected and fixed nano package versions.
Apply vendor-provided updates when available and operationally approved.
Limit untrusted users’ ability to create directories in shared working locations.
Avoid using nano with attacker-controlled paths until vendor remediation is confirmed.
Validation and detection
Inventory installed nano packages across RHEL 6 through 10 systems.
Check OpenShift 4 nodes and images for the listed RHEL CoreOS packages.
Compare installed package versions with current Red Hat advisories.
Review system logs for unexplained nano segmentation faults.
Confirm updated packages through normal configuration and vulnerability-management tooling.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-134: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-134 · source CWE mapping
Use of Externally-Controlled Format String
Use of Externally-Controlled Format String represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.