---
id: "CVE-2026-128034"
page: "https://infrastack.ai/live/CVE-2026-128034"
kind: "vulnerability"
aliases: ["CVE-2026-128034"]
title: "gittuf: file protection rules skip files with special-character names"
severity: "medium"
cvss: 5.5
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["git", "gittuf", "package", "supply-chain"]
not_affected_if: ["ascii-filenames-only", "no-file-protection-rules", "no-gittuf"]
published_at: "2026-11-13T16:18:58+00:00"
first_seen_at: "2026-11-13T16:47:33+00:00"
updated_at: "2026-11-13T16:48:56+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-128034", "first_seen_at": "2026-11-13T16:47:33+00:00"}]
exploit_sources: []
---

# gittuf: file protection rules skip files with special-character names

Link for people: https://infrastack.ai/live/CVE-2026-128034 (this .md is for agents)

gittuf, a Git security tool, checks file protection rules against the quoted pathnames Git prints for names with non-ASCII or special characters instead of the real paths. An unauthorized user can change a protected file whose name contains such characters and still pass verification.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed gittuf version with `gittuf version`; versions before `0.18.0` are affected.
- Review whether your repository uses gittuf file protection rules (file: patterns) and has files with non-ASCII or special characters in their names.

## Fix

- gittuf: move to `0.18.0` or later

## Timeline

- 2026-11-13T16:47:33+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-128034

## Documents

- [advisory] Vendor advisory: github.com https://github.com/gittuf/gittuf/security/advisories/GHSA-hxqr-h35w-2898
- [fix] Release notes: github.com https://github.com/gittuf/gittuf/releases/tag/v0.18.0

## From the sources

In gittuf before 0.18.0, verification of file protection rules uses the quoted, escaped pathnames that Git prints by default for files with special characters (for example non-ASCII characters) instead of the raw paths. Such paths do not match patterns like file:internal/*, so the files are treated as unprotected, and a user who is not authorized by a file protection rule can change a protected file whose name contains special characters and still pass verification.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_