Skip to main content
CVE-2026-121757VulnerabilityPublished

Converting crafted CP949 input to UTF-8 character encoding and ignoring invalid characters, in the GNU C Library

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-121757· Medium 5.9

Not known to be exploited · CVSS 5.9 Medium : upgrade to 0 when convenient.

Data as of 18 Nov 2026, 02:39 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (glibc)CVSS 3.15.9
Patch
Available – fixed in 0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade glibc to 0.

Affected software

ProductAffectedFixed in
The GNU C LibraryglibcAffected
  • >=2.1 <0
Fixed in
  • 0
Red Hatredhat/glibcpkg:rpm/redhat/glibcOther threatsAffected
  • >=2.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should avoid using the //IGNORE flag on destination encoding when converting CP949 input with iconv until a fix is released.

Description

A vulnerability in the GNU C Library (glibc) version 2.1 or later involves converting crafted CP949 input to UTF-8 with the //IGNORE flag set. This can cause the iconv converter to read past the end of the input buffer, leading to a crash of the calling application. The issue arises when an invalid CP949 byte sequence causes the decoder to advance the read pointer incorrectly at the buffer's end.

References

Community reviews

Loading reviews…