cve.bz

CVE-2026-113408 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in Git

3.3 lowEPSS 0.3%

Low (3.3) in git git. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
Path traversal in Git allows writing to arbitrary file via cloning and committing to bad repository

Severity

CVSS 3.1

3.3 low
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 17th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
GitLab (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-113408 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-113408?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-113408?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-113408 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.

Badge for a README or a site

CVE-2026-113408

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-113408](https://cve.bz/cve/badge/CVE-2026-113408.svg)](https://cve.bz/cve/CVE-2026-113408)

HTML:

<a href="https://cve.bz/cve/CVE-2026-113408"><img src="https://cve.bz/cve/badge/CVE-2026-113408.svg" alt="CVE-2026-113408"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Git2.50.1
Git2.51.2
Git2.52.0
Git2.53.0
Git2.54.0
Git2.55.0
Git2.56.0

Fix and patched versions

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14gitno fix listedDEBIAN-CVE-2026-113408
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 4 moregitno fix listedUBUNTU-CVE-2026-113408
Alpinev3.23git2.52.1-r0ALPINE-CVE-2026-113408
Alpinev3.24git2.54.1-r0ALPINE-CVE-2026-113408
Alpaquitastreamgit2.56.1-r0BELL-CVE-2026-113408

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; the Alpine secdb, CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpine · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate severity because successful exploitation requires connecting to a malicious or compromised remote repository. In typical Red Hat deployments, Git client interactions are restricted to trusted upstream repositories and internal source control servers. While an attacker-controlled remote server could manipulate unborn branch advertisements to trigger unintended client-side file writes with the default files backend, this issue does not permit remote code execution or privilege 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 Enterprise Linux 10gitFix deferred
Red Hat Enterprise Linux 6gitFix deferred
Red Hat Enterprise Linux 7gitFix deferred
Red Hat Enterprise Linux 8gitFix deferred
Red Hat Enterprise Linux 9gitFix deferred
Red Hat Hardened ImagesgitAffected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9Fix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Fix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Fix deferred
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Fix deferred
Red Hat OpenShift Dev Spacesdevspaces/code-rhel9Fix deferred
Red Hat OpenShift Dev Spacesdevspaces/pluginregistry-rhel9Fix deferred
Red Hat Satellite 6rubygem-gitFix deferred

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-113408.

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

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.

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON