Skip to main content
Menu
CVEs

CVE

The GNU C Library glibc buffer over-read in ISO-2022-CN-EXT decoder

CVE-2026-121758EUVD-2026-128306

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

5.9MediumCNA
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Not reported
Published
Last modified
Reference
Last checked
48/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

The GNU C Library (glibc) has a flaw in its ISO-2022-CN-EXT decoder, which converts text to UTF-8. Crafted input can make the converter read past the end of its input buffer, which can crash the application that calls it. The attack can be launched remotely, without logging in, provided the attacker controls the input and the encoding.

Written by a model from the sources below. Verify against them.

Original description

Converting crafted ISO-2022-CN-EXT input to UTF-8 character encoding, in the GNU C Library version 2.2 through 2.44 may result in the converter reading past the end of the input buffer, causing the calling application to crash.

When the ISO-2022-CN-EXT decoder encounters an invalid input byte sequence like '\x0e' it ends up advancing the pointer tracking the read buffer position twice. If 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 input and encoding needs to be attacker controlled.

cve.now Index

48Pcve.now Index 48 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach20/20Affects glibc (software on nearly every server, desktop or phone)
  • Severity5.9/10CVSS 5.9
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 93 if added to CISA KEV
  • Would score about 88 if CISA's SSVC rates exploitation active
  • Would score about 53 if advisories confirm default setups are exposed

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-121758 (ISO-2022-CN-EXT decoder may read past input), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-121758 (entry last updated 2026-11-17):
Affected:
- The GNU C Library glibc: from 2.2, through 2.44
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-121758 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-121758 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://sourceware.org/git/?p=glibc.git;a=blob_plain;f=advisories/GLIBC-SA-2026-00230
- https://sourceware.org/bugzilla/show_bug.cgi?id=34774
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-121758
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-121758"}.

Timeline

  1. CVE published1 day
  2. First seen by cve.now

Affected versions

  • The GNU C Library glibc

    From 2.2 · through 2.44

Evidence 4

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Write-ups · 1

Establishes: Technical detail and context.

  1. Report

Other links · 1

  1. Advisory

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-121758

Is CVE-2026-121758 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-121758?

glibc: from 2.2 through 2.44.Source: cve.now feed data

More CVEs