cve.bz

CVE-2026-84243 the gnu c library glibc: Path traversal

7.0 highEPSS 0.3%

High (7.0) in the gnu c library glibc. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.0 high
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.3% (unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 23rd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-84243 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-84243?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-84243?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-84243 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
The GNU C Library glibc2.0 and later

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14glibcno fix listedDEBIAN-CVE-2026-84243
Ubuntu22.04:LTSglibc2.35-0ubuntu3.18UBUNTU-CVE-2026-84243 USN-9065-1
Ubuntu24.04:LTSglibc2.39-0ubuntu8.12UBUNTU-CVE-2026-84243 USN-9065-1
Ubuntu26.04:LTSglibc2.43-2ubuntu2.7UBUNTU-CVE-2026-84243 USN-9065-1
Ubuntu26.10glibc2.44-1ubuntu2.1UBUNTU-CVE-2026-84243 USN-9065-1
UbuntuPro:14.04:LTSeglibcno fix listedUBUNTU-CVE-2026-84243
UbuntuPro:16.04:LTS, Pro:18.04:LTS, Pro:20.04:LTSglibcno fix listedUBUNTU-CVE-2026-84243
Red Hathummingbird:1glibc, libnsl, nss_db and 226 more0:2.43-9.3.hum1RHSA-2026:96401
SUSELinux Enterprise Server 16.1, Linux Enterprise Server for SAP applications 16.1glibc2.40-160100.4.1SUSE-SU-2026:24741-1
openSUSELeap 16.1glibc, glibc-cross-s390x-src, glibc-cross-aarch64-src and 2 more2.40-160100.4.1openSUSE-SU-2026:22346-1
openSUSETumbleweedglibc2.44-4.1openSUSE-SU-2026:12539-1
Azure Linux3gettextno fix listedAZL-112735
Azure Linux3glibcno fix listedAZL-112354
Alpaquita25glibc2.39.0-r19BELL-CVE-2026-84243
Alpaquitastreamglibc2.43.0-r14BELL-CVE-2026-84243
BellSoft Hardened Containers25glibc2.39.0-r19BELL-CVE-2026-84243
BellSoft Hardened Containersstreamglibc2.43.0-r14BELL-CVE-2026-84243

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE · Alpaquita · BellSoft Hardened Containers.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate impact because privilege boundaries protected by AT_SECURE, such as setuid and setgid binaries, are inherently not affected. Exploitation requires multiple specific preconditions, including the ability to write a crafted message file to the system and control environment variables across a non-setuid trust boundary (such as through SSH forced command configurations accepting client locales). Under standard Red Hat Enterprise Linux configurations, users able to set their own process environment already run with identical privileges to those of the executed binary, significantly limiting scenarios for unauthorized escalation.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Hardened Imagesglibc-main-2.43-9.3.hum1Fixed 2026-11-09RHSA-2026:96401
Red Hat Enterprise Linux 10glibcAffected
Red Hat Enterprise Linux 6compat-glibcOut of support scope
Red Hat Enterprise Linux 6glibcOut of support scope
Red Hat Enterprise Linux 7compat-glibcAffected
Red Hat Enterprise Linux 7glibcAffected
Red Hat Enterprise Linux 8glibcAffected
Red Hat Enterprise Linux 9glibcAffected
Red Hat Hardened ImagesfilesystemNot affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-ai-gateway-operator-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-core-bff-rhel9Under investigation
Red Hat OpenShift AI (RHOAI)rhoai/odh-dashboard-operator-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-dashboard-rhel9Under investigation
Red Hat OpenShift AI (RHOAI)rhoai/odh-data-science-pipelines-operator-controller-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-kf-notebook-controller-rhel9Under investigation
Red Hat OpenShift AI (RHOAI)rhoai/odh-kserve-controller-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-kserve-llmisvc-controller-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-kserve-module-operator-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-kuberay-operator-controller-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-kube-rbac-proxy-rhel9Not affected
24 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-84243.

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON