CVE-2026-77117
MEDIUMDescription
Converting crafted SHIFT_JISX0213 input to UCS-4 or the internal wide character encoding, for example with iconv, in the GNU C Library version 2.3 to 2.44 may result in the converter making no progress, causing the calling application to hang. Some SHIFT_JISX0213 sequences decode to two code points. If the output buffer has room for only the first one, the converter stores the second in the conversion state and returns E2BIG, but it never clears that pending character after emitting it on the next call. The converter then keeps emitting the pending character without consuming further input, so an application that retries the conversion loops forever. The input must be attacker controlled and the application must convert it with an output buffer small enough to split the two code points. Only the SHIFT_JISX0213 character set is affected, which is not commonly used. The related defect in the EUC_JISX0213 converter is tracked separately as CVE-2026-80489.
How to fix
This vulnerability affects an unusually large number of packages. The highest-confidence fixes are shown above; the full list is longer. Check the referenced advisories for complete coverage.
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H/E:U
Exploit Intelligence
Low risk: more likely to be exploited than 33% of all known CVEs.
References
Related Vulnerabilities
Other CWE-835 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2020-13935 | High | 7.5 | 87% | - | Fix |
| CVE-2014-0050 | High | 7.5 | 83% | - | Fix |
| CVE-2020-36227 | High | 7.5 | 77% | - | Fix |
| CVE-2022-0778 | High | 7.5 | 73% | - | Fix |
| CVE-2024-20353 | High | 8.6 | 71% | KEV | - |
| CVE-2019-14241 | High | 7.5 | 70% | - | - |
Common questions
How do I fix CVE-2026-77117?
Published advisories record a fix for 453 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2026-77117 being actively exploited?
Not that we know of. CVE-2026-77117 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.41% is the estimated probability that it will be exploited in the next 30 days. That is higher than 33% of all scored CVEs.
How severe is CVE-2026-77117?
CVE-2026-77117 has a CVSS v3 base score of 5.9, rated moderate. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-77117 affect?
Published advisories record a fix for glibc (Debian), glibc (Red Hat / RHEL), glibc (Rocky), glibc-all-langpacks (Red Hat / RHEL), and 449 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-77117
Markdown
[](https://tridentstack.com/cve/CVE-2026-77117)HTML
<a href="https://tridentstack.com/cve/CVE-2026-77117"><img src="https://tridentstack.com/cve/badge/CVE-2026-77117.svg" alt="CVE-2026-77117"></a>Check your Linux endpoints for this class of vulnerability
TridentStack Control continuously scans Linux endpoints for known vulnerabilities and deploys the fixes from the same console. 200 endpoints free forever, no credit card.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-18.