CVE-2026-121757 json
CP949 decoder may read past input
published 5h ago modified 4h ago also EUVD-2026-128301
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
Converting crafted CP949 input to UTF-8 character encoding and ignoring invalid characters, in the GNU C Library version 2.1 or later may result in the converter reading past the end of the input buffer, causing the calling application to crash.
When the CP949 decoder encounters an invalid input byte sequence like '\xa2\xe8' it ends up advancing the pointer tracking the read buffer position twice. If //IGNORE is set on the destination encoding and this sequence is at the end of the input buffer, the decoder may then end up reading past the bounds of the input buffer. To exploit this, the target iconv function needs to set //IGNORE on the destination of the conversion and the input and encoding needs to be attacker controlled.
Is CVE-2026-121757 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected products
- The GNU C Library glibc
Classification
- Weakness
-
- CWE-126 Buffer Over-read
References
-
sourceware.org
/git/?p=glibc.git;a=blob_plain;f=advisories/GLIBC-SA-2026-0029
vendor-advisory
-
sourceware.org
/bugzilla/show_bug.cgi?id=35016
issue-tracking
Sources
- CVE List CVE-2026-121757
- NVD CVE-2026-121757
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.