Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-5928: Buffer Under-read in GNU C Library ungetwc()

Published Apr 20, 2026 · Updated 5 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days11 mentions · peak 2 in a dayToday
CVSS7.5High · v3.1
EPSS0.38%32nd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
GNU Project
IdentifiersCVE-2026-5928CWE-127 · Buffer Under-read

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.

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.

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.

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 ProjectGlibcapplication
FAQ

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.
Activity feed

Recent activity

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

View more in app →
tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.1 : glibc (EulerOS-SA-2026-4636) | Tenable®A wide-character pushback bug in GNU C Library 2.43 and earlier makes ungetwc() use the regular character buffer pointer instead of the wide-stream pointer. This can cause a crash or, under particular character-encoding conditions, a heap buffer under-read and information disclosure. The spurious-match condition does not occur with standard Unicode character sets.Read more ↗tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.0 : glibc (EulerOS-SA-2026-4694) | Tenable®A wide-character pushback implementation bug in glibc can cause a buffer under-read, disclosure of neighboring heap data, or a crash. Information disclosure requires character encodings with overlapping single-byte and multibyte representations; standard Unicode character sets do not permit that case.Read more ↗tenable cloud security pluginsNews · Oct 16, 2026Google: sys-libs/glibc: security update to 19506.505.25 | Tenable®A flaw in GNU C Library's wide-character pushback implementation causes ungetwc() to use the regular character buffer pointer instead of the wide-stream read pointer. This can cause a crash when the regular pointer is NULL, or a buffer under-read potentially disclosing neighboring heap data under particular overlapping single-byte and multibyte encodings. The spurious-match condition does not occur with standard Unicode character sets. The advisory reports exploit availability and recommends updating the Google COS sys-libs/glibc package and related packages to version 19506.505.25 or later.Read more ↗tenable cloud security pluginsNews · Oct 16, 2026Google: sys-libs/glibc: security update to 19216.700.23 | Tenable®A flaw in GNU C Library (glibc) 2.43 and earlier causes the wide-character pushback implementation, _IO_wdefault_pbackfail, to use the regular character buffer pointer instead of the wide-stream read pointer. This can cause a crash when the regular pointer is NULL, or a buffer under-read and possible heap-data disclosure with character encodings containing overlapping single-byte and multibyte representations. The spurious-match condition does not occur with standard Unicode character sets. The plugin reports a CVSS v3 base score of 7.5 and available exploits.Read more ↗
+8 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 activity12Community discussion across Reddit, Mastodon, and other social sources.