CVE-2026-6843
Redhat Enterprise Linux 10.0 … 9.0
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:HSummary
CVE-2026-6843 is a medium-severity Use of Externally-Controlled Format String (CWE-134) vulnerability in Redhat Enterprise Linux. Its CVSS base score is 5.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 1th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-2 (Flaw Remediation) and CM-7 (Least Functionality) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-24708
Vulnerability Data
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…
more
fault (SEGV). This results in a Denial of Service (DoS) for the `nano` application.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Format string vuln in nano directly enables local application crash via crafted input (directory name), matching Application or System Exploitation for DoS.
Likely ATT&CK TechniquesAI
Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly requires applying patches or updates to remediate the format-string flaw in nano before a local user can trigger the SEGV via a crafted directory name.
Verifies integrity of the nano binary and its runtime behavior, blocking or alerting on execution of the vulnerable version that mishandles directory-name input.
Disables or restricts nano (least functionality) on systems where the vulnerable statusline() code cannot be immediately replaced, eliminating the attack surface for this DoS.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect format-string vulnerabilities before release.
Secure SDLC mandates input validation and safe API usage that can prevent externally-controlled format strings.
Application security requirements can specify safe formatting functions and ban uncontrolled format strings.
Secure architecture principles discourage dangerous string-handling patterns that lead to format-string issues.
Secure coding standards directly forbid the use of untrusted format strings and prescribe safe alternatives.