Vulnerability · Published Oct 30, 2026 · Assigned by glibc

CVE-2026-84243gettext: Directory traversal via the LANGUAGE environment variable

High 7.0

In plain English

A high-severity path traversal in glibc from The GNU C Library. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 23% of all known vulnerabilities).

Severity (CVSS 3.1)7.0High
Exploit odds (30 days)0.3%top 77.5% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

The gettext family of functions in the GNU C Library version 2.0 and later accept LANGUAGE environment variable entries that contain '/' or that are equal to "..", unless the program is setuid or setgid (AT_SECURE). An attacker who can set LANGUAGE in the environment of a program that uses gettext can make it load a message catalog (.mo file) from an arbitrary location in the file system. A crafted .mo file can crash the program through out-of-range offsets, or supply translations whose format directives do not match the arguments passed by the program. That causes undefined behaviour in the printf family of functions and may allow arbitrary code execution with the privileges of the program. The safety of message catalogs relies on them being installed in trusted, read-only locations, and the directory traversal bypasses this. The fix for CVE-2014-0475 rejects ".." path components in locale names passed to setlocale or taken from the LC_ALL, LC_* and LANG environment variables. gettext reads LANGUAGE directly and appends each colon-separated entry to the message catalog directory, so that fix did not cover LANGUAGE. LANGUAGE is only used when the LC_MESSAGES locale is not "C", "C.<encoding>" or "POSIX", so the attacker must also be able to select another installed locale, for example through LANG or LC_ALL. Exploitation also requires that the attacker can place the crafted file in a location readable by the target program, and that the environment crosses a trust boundary without the program running as AT_SECURE. An example is an SSH server that accepts LANGUAGE and LANG from clients through the AcceptEnv directive and restricts an account to a forced command; the attacker may use this to escape the restriction.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12glibcno fix listedDEBIAN-CVE-2026-84243
Debian:13glibcno fix listedDEBIAN-CVE-2026-84243
Debian:14glibcno fix listedDEBIAN-CVE-2026-84243
Ubuntu:22.04:LTSglibcno fix listedUBUNTU-CVE-2026-84243
Ubuntu:24.04:LTSglibcno fix listedUBUNTU-CVE-2026-84243
Ubuntu:26.04:LTSglibcno fix listedUBUNTU-CVE-2026-84243
Ubuntu:26.10glibcno fix listedUBUNTU-CVE-2026-84243

Affected products (as reported)

VendorProductVersions
The GNU C Library glibc 2.0 – before *

Weakness: CWE-22 · Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

References