CVE-2026-121758: 
Wolfi Analyse et atténuation de la vulnérabilité

Aperçu

CVE-2026-121758 is a buffer over-read vulnerability in the GNU C Library (glibc) ISO-2022-CN-EXT character encoding decoder that can cause application crashes when processing crafted input. It affects glibc versions 2.2 through 2.44 and was published on November 17, 2026. The flaw occurs when converting malformed ISO-2022-CN-EXT input to UTF-8, causing the decoder to read past the end of the input buffer. It carries a CVSS v3.1 base score of 5.9 (Medium) (GitHub Advisory).

Détails techniques

The root cause is a buffer over-read (CWE-126) in glibc's ISO-2022-CN-EXT decoder. When the decoder encounters an invalid input byte sequence such as \x0e, it incorrectly advances the read buffer pointer twice instead of once. If this malformed sequence is positioned at the end of the input buffer, the decoder reads past the buffer boundary, triggering a crash in the calling application. Exploitation requires that both the input data and the character encoding be attacker-controlled, making this a network-exploitable but high-complexity attack (GitHub Advisory, GNU Bugzilla).

Impact

Successful exploitation results in a denial of service (DoS) by crashing any application that uses glibc's character encoding conversion routines to process attacker-supplied ISO-2022-CN-EXT encoded data. There is no impact on confidentiality or data integrity — the vulnerability is limited to availability. Given glibc's ubiquity across Linux-based systems, a wide range of applications performing automatic character encoding conversion could be affected if they accept untrusted input (GitHub Advisory).

Exploitabilité

There is no known public proof-of-concept exploit and no evidence of in-the-wild exploitation as of the time of disclosure (GitHub Advisory). The EPSS score is 0.0, reflecting a very low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation requires high attack complexity, as the attacker must control both the input content and the encoding type used by the target application.

Étapes d’exploitation

  1. Identify a target application: Find a network-accessible application that uses glibc's iconv or similar character encoding conversion functions and accepts user-controlled input with a user-controlled or inferred encoding (e.g., a web application, email server, or text processing service running on a Linux system with glibc 2.2–2.44).
  2. Craft malicious input: Construct an ISO-2022-CN-EXT encoded payload that includes an invalid byte sequence such as \x0e positioned at the very end of the input buffer, so that the double pointer advancement causes an out-of-bounds read.
  3. Deliver the payload: Submit the crafted input to the target application via the relevant network interface (e.g., HTTP request body, email message, file upload), ensuring the encoding is interpreted as ISO-2022-CN-EXT by the application.
  4. Trigger the crash: The glibc ISO-2022-CN-EXT decoder processes the malformed sequence, advances the read pointer past the buffer boundary, and causes the calling application to crash, resulting in a denial of service (GitHub Advisory, GNU Bugzilla).

Indicateurs de compromis

  • Logs: Application crash logs or core dumps referencing glibc's iconv or character encoding conversion routines; segmentation fault signals (SIGSEGV) in system logs (/var/log/syslog, journalctl) associated with applications performing encoding conversion.
  • Process: Unexpected application crashes or restarts in services that handle text encoding conversion, particularly those accepting external input in ISO-2022-CN-EXT encoding.
  • Network: Repeated requests to a service containing ISO-2022-CN-EXT encoded data with unusual or malformed byte sequences (e.g., \x0e at buffer boundaries), especially if followed by service unavailability.

Atténuation et solutions de contournement

Update glibc to a version patched beyond 2.44, as all versions from 2.2 through 2.44 are affected. The patch is tracked under glibc security advisory GLIBC-SA-2026-00230 (glibc Advisory). As a workaround, restrict or validate sources of untrusted ISO-2022-CN-EXT encoded input in applications that perform automatic character encoding conversion, and consider implementing input sanitization to reject or re-encode unexpected character encoding data from untrusted sources (GitHub Advisory).

Ressources supplémentaires

État de correction de la distribution Linux

Corrigez la disponibilité entre les grandes distributions Linux et leurs versions.

Debian

Affecté

bookworm

glibc

Affecté

sid

glibc

Affecté

trixie

glibc

Affecté

Ubuntu

Inconnu

bionic (esm-infra)

glibc

Inconnu

devel

glibc

Inconnu

focal (esm-infra)

glibc

Inconnu

jammy

glibc

Inconnu

noble

glibc

Inconnu

resolute

glibc

Inconnu

trusty (esm-infra-legacy)

eglibc

Inconnu

xenial (esm-infra-legacy)

glibc

Inconnu

Source: Ce rapport a été généré à l’aide de l’IA

Connexe Wolfi Vulnérabilités :

CVE ID

Gravité

Partition

Technologies

Nom du composant

Exploit CISA KEV

A corrigé

Date de publication

CVE-2026-114938HIGH8.1
  • Amazon Corretto JDK logoAmazon Corretto JDK
  • java-21-openjdk-static-libs-fastdebug
NonOuiNov 17, 2026
CVE-2026-128089HIGH7.5
  • Python logoPython
  • dnspython
NonOuiNov 13, 2026
CVE-2026-129852MEDIUM6.9
  • Wolfi logoWolfi
  • seaweedfs
NonOuiNov 16, 2026
CVE-2026-129851MEDIUM6.9
  • Wolfi logoWolfi
  • seaweedfs
NonOuiNov 16, 2026
CVE-2026-121758MEDIUM5.9
  • Wolfi logoWolfi
  • glibc
NonNonNov 17, 2026

Évaluation gratuite des vulnérabilités

Évaluez votre posture de sécurité cloud

Évaluez vos pratiques de sécurité cloud dans 9 domaines de sécurité afin d’évaluer votre niveau de risque et d’identifier les lacunes dans vos défenses.

Évaluation de la demande

Ressources Wiz supplémentaires

Obtenez une démo personnalisée

Prêt(e) à voir Wiz en action ?

"La meilleure expérience utilisateur que j’ai jamais vue, offre une visibilité totale sur les workloads cloud."
David EstlickRSSI
"Wiz fournit une interface unique pour voir ce qui se passe dans nos environnements cloud."
Adam FletcherChef du service de sécurité
"Nous savons que si Wiz identifie quelque chose comme critique, c’est qu’il l’est réellement."
Greg PoniatowskiResponsable de la gestion des menaces et des vulnérabilités