CVE-2026-5928: Buffer Under-read in GNU C Library ungetwc()
- Vendor
- GNU Project
CVE-2026-5928 is a wide-character pushback vulnerability in GNU C Library (glibc) versions 2.43 and earlier. The _IO_wdefault_pbackfail implementation used by ungetwc() incorrectly operates on the regular character-buffer read pointer, fp->_IO_read_ptr, instead of the wide-stream read pointer, fp->_wide_data->_IO_read_ptr. With character encodings whose single-byte and multibyte representations overlap, spurious matches can cause reads before an allocated buffer, potentially disclosing neighboring heap data. The incorrect pointer access can also crash an application when the regular character-buffer read pointer is NULL. Standard Unicode character sets do not permit the spurious-match condition required for the buffer under-read.
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.
Affected applications may disclose adjacent heap data through an out-of-bounds read or terminate because of an invalid read or NULL pointer dereference, causing denial of service. Actual disclosure depends on whether the application exposes the incorrectly read data. Arbitrary code execution and integrity compromise are not established.
Mitigation
If you can’t patch tonight, do this now.
Until patched, avoid the affected ungetwc() wide-character pushback code path where feasible. Using standard Unicode character sets instead of encodings with overlapping single-byte and multibyte representations prevents the described spurious-match buffer under-read condition, but does not establish protection against the separate NULL-pointer crash condition.
Remediation
Patch, then assume compromise.
Install the operating-system or product vendor's glibc security update addressing CVE-2026-5928, including backported fixes where applicable. The implementation must use the wide-stream read pointer in _IO_wdefault_pbackfail. Identified fixed package releases include Echo glibc 2.41-12+deb13u2+e4 or later and Google Container-Optimized OS glibc-related updates 19216.700.23 or 19506.505.25 or later for their respective release branches. For EulerOS, apply the applicable glibc security advisory updates.
Exploits
No public exploits tracked yet. Mallory keeps watching.
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.
Frequently asked questions
- Is CVE-2026-5928 exploited in the wild?
- As of Nov 12, 2026, Mallory has no reports of CVE-2026-5928 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-5928?
- Yes. As of Nov 12, 2026, Mallory has reports of a public exploit for CVE-2026-5928.
- Is there a patch for CVE-2026-5928?
- Install the operating-system or product vendor's glibc security update addressing CVE-2026-5928, including backported fixes where applicable. The implementation must use the wide-stream read pointer in _IO_wdefault_pbackfail.
- What products are affected by CVE-2026-5928?
- GNU Project Glibc.
- How severe is CVE-2026-5928?
- CVE-2026-5928 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.38% (32nd percentile) as of Nov 12, 2026.
Recent activity
35 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.