cve.bz

CVE-2026-102474 Out-of-bounds Write

4.0 mediumEPSS 0.1%

Medium (4.0). EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

4.0 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-09-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-787 Out-of-bounds Write
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-102474 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-102474?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-102474?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-102474 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14dashno fix listedDEBIAN-CVE-2026-102474
Ubuntu14.04:LTS, 16.04:LTS, 18.04:LTS and 5 moredashno fix listedUBUNTU-CVE-2026-102474
openSUSETumbleweeddash0.5.13.5-1.1openSUSE-SU-2026:11980-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate severity because exploitation requires local access and the ability to pass crafted Unicode escape sequences directly into the shell's built-in formatting utilities. In Red Hat Enterprise Linux, dash is not deployed as the default system shell (/bin/sh is linked to bash), restricting exposure primarily to environments where dash is deliberately installed and executed on untrusted input. Consequently, the flaw presents a limited blast radius consisting of out-of-bounds heap memory corruption without direct privilege escalation under standard operating conditions.

Red Hat's mitigation

No practical runtime mitigation is available in the shipped build. Do not pass untrusted data into dash printf/echo %b or into dash -c as a positional argument. The fix is to raise the CHECKSTRSPACE reservation at both printf call sites to 8. The later unaligned-access memcpy change in conv_escape does not enlarge that reservation and does not fix this issue.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 6dashOut of support scope

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-102474.

References

Check your stackJSON