CVE Catalog

CVE-2026-5928

HighCVSS 7.5
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.35%

27th percentile - higher than 27% of all known CVEs

Summary

In the GNU C Library version 2.43 and earlier, calling ungetwc on a FILE stream with wide characters encoded in a character set that has overlaps between single-byte and multi-byte encodings may cause an out-of-bounds read before an allocated buffer. A bug in the wide character pushback implementation (_IO_wdefault_pbackfail) causes ungetwc to operate on the regular character buffer instead of the wide-stream read pointer, potentially leading to disclosure of heap data or a program crash.

Risk Assessment

The organization risks unintentional disclosure of sensitive heap data or system crashes if applications use ungetwc on streams with certain character encodings (e.g., Shift-JIS).

Recommendation

Upgrade GNU C Library to version 2.44 or later, which includes the fix. If upgrading is not possible, avoid using ungetwc with character sets that have overlapping single-byte and multi-byte representations.

Other vulnerabilities in GNU C Library

See all
Original NVD description (English source)

Calling the ungetwc function on a FILE stream with wide characters encoded in a character set that has overlaps between its single byte and multi-byte character encodings, in the GNU C Library version 2.43 or earlier, may result in an attempt to read bytes before an allocated buffer, potentially resulting in unintentional disclosure of neighboring data in the heap, or a program crash. A bug in the wide character pushback implementation (_IO_wdefault_pbackfail in libio/wgenops.c) causes ungetwc() to operate on the regular character buffer (fp->_IO_read_ptr) instead of the actual wide-stream read pointer (fp->_wide_data->_IO_read_ptr). The program crash may happen in cases where fp->_IO_read_ptr is not initialized and hence points to NULL. The buffer under-read requires a special situation where the input character encoding is such that there are overlaps between single byte representations and multibyte representations in that encoding, resulting in spurious matches. The spurious match case is not possible in the standard Unicode character sets.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS