Skip to main content
Mallory
MediumVulnerability

CVE-2026-56391: Out-of-bounds read in GNU coreutils uniq multibyte character handling

Published Jul 24, 2026 · Updated 11 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days6 mentions · peak 4 in a dayToday
CVSS4.6Medium · v4
EPSS0.13%3rd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
GNU Project
IdentifiersCVE-2026-56391CWE-125 · Out-of-bounds Read

CVE-2026-56391 is an out-of-bounds read vulnerability affecting GNU coreutils versions 9.5 through 9.11 in the uniq utility. When processing crafted multibyte input with the -w (--check-chars) option, find_field() repeatedly processes a fixed pointer instead of advancing through the input. This produces an inflated character byte-length calculation that is subsequently passed to memcmp(), causing reads beyond the allocated buffer. Exploitation can crash the process and potentially expose adjacent heap memory.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A local attacker can potentially cause denial of service by crashing uniq and may obtain sensitive information from adjacent heap memory. Applications or scripts invoking the affected utility on attacker-controlled input and arguments may also be disrupted. Integrity compromise, arbitrary code execution, and privilege escalation are not established.

Mitigation

If you can’t patch tonight, do this now.

Until patched, avoid using uniq with -w (--check-chars) on untrusted multibyte input, and prevent untrusted users from controlling arguments supplied to uniq by applications or scripts. Restrict untrusted local access where feasible. No vendor-approved workaround is specified.

Remediation

Patch, then assume compromise.

Apply upstream commit d64e35a8a4c0e4608321433e0d84d917e4e36371 or install a vendor package incorporating the fix. Fixed packages include coreutils 9.5-8.el10_2.1 for RHEL 10; gnu-coreutils 9.7-3ubuntu2.1 for Ubuntu 26.04 LTS; coreutils 9.6-160000.3.1 for SLES 16.0, SLES for SAP applications 16.0, and openSUSE Leap 16.0; coreutils 9.6-160100.3.1 for SLES and SLES for SAP applications 16.1; and coreutils 9.11-5.1 for openSUSE Tumbleweed. Install applicable subsequent vendor updates and update associated installed subpackages. Rebuild or redeploy affected containers with patched packages. VMware Tanzu RabbitMQ fixes are included in releases 3.13.21, 4.1.17, 4.2.12, and 4.3.7 for their respective release branches.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GNU ProjectCoreutilsapplication
FAQ

Frequently asked questions

Is CVE-2026-56391 exploited in the wild?
As of Nov 7, 2026, Mallory has no reports of CVE-2026-56391 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-56391?
As of Nov 7, 2026, Mallory has found no public exploit for CVE-2026-56391.
Is there a patch for CVE-2026-56391?
Apply upstream commit d64e35a8a4c0e4608321433e0d84d917e4e36371 or install a vendor package incorporating the fix. Fixed packages include coreutils 9.5-8.el10_2.1 for RHEL 10; gnu-coreutils 9.7-3ubuntu2.1 for Ubuntu 26.04 LTS; coreutils 9.6-160000.3.1 for SLES 16.0, SLES for SAP applications 16.0, and openSUSE Leap 16.0; coreutils 9.6-160100.3.1 for SLES and SLES for SAP applications 16.1; and coreutils 9.11-5.1 for openSUSE Tumbleweed.
What products are affected by CVE-2026-56391?
GNU Project Coreutils.
How severe is CVE-2026-56391?
CVE-2026-56391 has a CVSS v4 score of 4.6 (Medium) and an EPSS score of 0.13% (3rd percentile) as of Nov 7, 2026.
Activity feed

Recent activity

18 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
tenable nessus pluginsNews · Oct 23, 2026openSUSE 16: coreutils / coreutils-lang / coreutils-single / c... | Tenable®An out-of-bounds read in the coreutils uniq utility when processing multibyte input can cause denial of service and information disclosure. The advisory identifies affected coreutils packages on openSUSE 16 and provides a security update. Nessus detects affected versions using package version information rather than testing exploitation.Read more ↗tenable nessus pluginsNews · Oct 23, 2026SUSE SLES16: coreutils / coreutils-doc / coreutils-lang / core... | Tenable®An out-of-bounds read in the coreutils uniq utility when processing multibyte input can cause denial of service and information disclosure. The advisory identifies affected packages on SUSE SLES16 and SLES_SAP16. The CVSS v3 base score is 6.1 (Medium). Nessus detects affected package versions rather than testing exploitation.Read more ↗tenable nessus pluginsNews · Oct 13, 2026Ubuntu 22.04 LTS / 24.04 LTS / 26.04 LTS : GNU Core Utilities ... | Tenable®An out-of-bounds read in GNU Core Utilities uniq, triggered by crafted multibyte input with the -w option, could allow a local attacker to cause denial of service or disclose sensitive information. Within this advisory, only Ubuntu 26.04 LTS is affected. Nessus detects affected versions rather than testing exploitation.Read more ↗tenable nessus pluginsNews · Sep 17, 2026AlmaLinux 10 : coreutils (ALSA-2026:67886) | Tenable®A vulnerability addressed by AlmaLinux security advisory ALSA-2026-67886 for AlmaLinux 10 coreutils packages. The supplied CVSS data rates it as a local, low-complexity issue requiring user interaction, with no privileges required.Read more ↗
+7 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.