Skip to main content

dash EUVDEUVD-2026-88668

| CVE-2026-102474 MEDIUM
Out-of-bounds Write (CWE-787)
2026-09-29 redhat GHSA-fgjp-hq6c-rfv8
4.0
CVSS 3.1 · Vendor: redhat
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain local shell access to dash
  2. Exploit
    Supply crafted \u/\U escape to printf or echo %b
  3. Impact
    Write 1-2 bytes past 4-byte reservation

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires local access to a host where dash is invoked. The attacker supplies a crafted Unicode \u or \U escape that decodes to a 5-6 byte UTF-8 token to the dash printf builtin or to echo %b - reachable non-interactively via 'dash -c' with the escape passed as a positional argument. Exploitation is limited to local users, produces only a bounded 1-2 byte out-of-bounds write with no demonstrated code-execution primitive, and the corruption stays within the caller's own dash process, so it confers no inherent privilege escalation.

Impact

This is a low-severity local memory-safety flaw, not a priority. The provided CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N) computes to roughly 3.3, and the listed 'CVSS Score: 4.0' appears to be a Red Hat CVSS 4.0 base score rather than a 3.1 score - both agree the real-world risk is minor. Attack vector is LOCAL (the attacker must already be able to run dash on the host), there is no confidentiality or availability impact, and the integrity impact is limited to a controlled 1-2 byte out-of-bounds write past a fixed reservation. There is no EPSS score, no CISA KEV listing, and no public exploit code referenced, so exploitation is theoretical. A 1-2 byte overflow is a genuine CWE-787 bug but the description shows no path to code execution or privilege escalation, and dash's printf typically runs at the caller's own privilege - so a local user overflowing memory in their own shell process gains little. Note the CPE lists only Red Hat Enterprise Linux 6, which is unusual since dash is a Debian-family shell and not RHEL 6's default /bin/sh; the affected component is dash itself, so scope should be read as the dash package wherever deployed, not RHEL 6 specifically.

Exploit ScenarioDerived

A local user on a system running dash executes 'dash -c' (or a printf/echo %b command) supplying a crafted multi-byte Unicode \u or \U escape that decodes to a 5-6 byte UTF-8 sequence, exceeding dash's 4-byte reservation and writing 1-2 bytes past it. No public exploit code is referenced, and the corruption is confined to the attacker's own dash process, offering no demonstrated privilege gain.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 29, 2026

An out-of-bounds write in the printf builtin of the dash shell allows a local user to corrupt one or two bytes past a four-byte reservation when a crafted Unicode \u or \U escape expanding to a five- or six-byte token is processed, including via 'dash -c' with the escape passed as a positional argument to printf or 'echo %b'. The flaw affects dash as shipped in Red Hat Enterprise Linux 6 (CPE cpe:2.3:a:red_hat:red_hat_enterprise_linux_6) and is rated CVSS 4.0 (AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N). No public exploit code was identified at time of analysis, and the bounded write stays within the caller's own shell process, so it provides no inherent privilege escalation.

RemediationAI

No vendor-released patch version is specified in the input data, so no fix version can be cited; Red Hat's advisory page (https://access.redhat.com/security/cve/CVE-2026-102474) and Bugzilla 2543004 are the authoritative sources to monitor for an updated dash package on RHEL 6, noting that RHEL 6 is past end of life and may not receive a fix. Until a patched build is available, the practical compensating controls are to avoid passing untrusted input containing \u or \U escapes to dash's printf builtin or to 'echo %b' - for example, sanitize or reject escape sequences in any script or service that invokes dash -c with user-controlled positional arguments, and use a shell whose escape handling is not affected (such as bash or a hardened interpreter) for that specific processing path. The trade-off is that switching shells can change script behavior and portability, and input filtering must be applied consistently because dash is often invoked indirectly as /bin/sh. Given the CVSS 4.0 score, the local-only attack vector, the absence of demonstrated privilege escalation, and the bounded 1-2 byte out-of-bounds write within the caller's own process, remediation can be prioritized accordingly; no network-level blocking or privilege restriction is indicated by the data.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

dash (Debian Almquist shell) is a small POSIX-compliant shell commonly used as /bin/sh where speed and low overhead matter; the vulnerability is in its built-in printf implementation and the related echo %b path, which expand backslash escapes such as \uXXXX and \UXXXXXXXX into UTF-8. According to the description, the code reserves four bytes of buffer space for the converted token, but a crafted escape can decode to a five- or six-byte sequence, so the copy overruns the reservation by one or two bytes. This is a classic CWE-787 out-of-bounds write: an insufficient size calculation (off-by-one class) in the escape-expansion logic. The attack surface is local and requires the user to feed the crafted escape to the builtin, e.g. through 'dash -c "printf ..."' with the escape supplied as a positional argument; no authentication is required per the CVSS vector (PR:N), but the write occurs inside the invoking user's own dash process. The supplied CPE data maps the affected product to Red Hat Enterprise Linux 6 only.

Know when Dash gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (redhat) PRIMARY 4.0 MEDIUM
AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
vuln.today AI 4.0 MEDIUM

Any local user can trigger it with no special privileges or interaction (AV:L, PR:N, UI:N); the bounded 1-2 byte overwrite gives limited integrity impact with no confidentiality or availability effect.

3.1 AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
4.0 AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
SUSE MEDIUM
Red Hat 4.0 MEDIUM

Primary rating from Vendor (redhat).

CVSS VectorVendor: redhat

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

DescriptionCVE.org

A flaw was found in dash. The printf builtin reserves four bytes before converting a Unicode \u or \U escape, but the multi-byte token can need five or six bytes. A local user who can supply such an escape to dash printf or echo %b, including through dash -c and a positional argument, can write one or two bytes past that reservation.

Threat Intelligence Overview

EPSS Score
0.1%
Top 97% exploitable
Prevalence
Ubiquitous
dash is the default /bin/sh on Debian and Ubuntu systems
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact· derived
High
Technical Impact
Partial

Priority Score

20
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +20
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

Affected Products (CPE)CVE.org

cpe:2.3:a:red_hat:red_hat_enterprise_linux_6:*:*:*:*:*:*:*:*

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Module for Development Tools 15 SP7 Affected
SUSE Linux Enterprise Server 15 SP7 Affected
SUSE Linux Enterprise Server for SAP Applications 15 SP7 Affected
SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy