CVE and update status of the FreeBSD ports tree3,864 unaddressed CVEs in 671 portsAll times are CET
CVE details

CVE-2026-56391

GNU coreutils uniq is vulnerable to an out‑of‑bounds read due to incorrect handling of multibyte input when the -w (--check-chars) option is used. The find_field() function miscalculates the byte length of characters by repeatedly processing a fixed pointer instead of advancing through the input, resulting in an inflated length value. This incorrect length is later used in a memcmp operation, causing reads beyond the allocated buffer when processing crafted multibyte input. When running GNU coreutils uniq with attacker-provided arguments, this behavior leads to a crash and potential adjacent heap memory exposure. This issue has been fixed in the commit d64e35a8a4c0e4608321433e0d84d917e4e36371.

Score
4.6 medium
Published
2026-07-24
Links
NVD · cve.org

Matched ports (1)

PortPackageVersionStatusMaintainer
sysutils/coreutilscoreutils9.9unaddressedjharris@widomaker.com

Template for a VuXML entry

Range taken from the CVE record, check it before committing. make newentry in security/vuxml creates the vid.

  <vuln vid="FIXME (make newentry)">
    <topic>FIXME -- FIXME</topic>
    <affects>
      <package>
	<name>coreutils</name>
	<range><lt>FIXME</lt></range>
      </package>
    </affects>
    <description>
      <body xmlns="http://www.w3.org/1999/xhtml">
	<p>GNU coreutils uniq is vulnerable to an out‑of‑bounds read due to
	incorrect handling of multibyte input when the -w (--check-chars)
	option is used. The find_field() function miscalculates the byte
	length of characters by repeatedly processing a fixed pointer instead
	of advancing through the input, resulting in an inflated length value.
	
This incorrect length is later used in a memcmp operation, causing
	reads beyond the allocated buffer when processing crafted multibyte
	input.

When running GNU coreutils uniq with attacker-provided
	arguments, this behavior leads to a crash and potential adjacent heap
	memory exposure.


This issue has been fixed in the commit
	d64e35a8a4c0e4608321433e0d84d917e4e36371.</p>
      </body>
    </description>
    <references>
      <cvename>CVE-2026-56391</cvename>
      <url>https://nvd.nist.gov/vuln/detail/CVE-2026-56391</url>
    </references>
    <dates>
      <discovery>2026-07-24</discovery>
      <entry>2026-10-26</entry>
    </dates>
  </vuln>