CVE-2026-128034

gittuf: File protection rules bypassed for filenames with special characters

Published Nov 13, 2026 CVSS 3.1 · 5.5 Medium EPSS n/a KEV · Not listed
Description
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.

Remediation

Vendor Solution

Upgrade to gittuf 0.18.0 or later, which asks Git for raw paths. Then re-run verification (gittuf verify-ref) for each protected reference: a reference that passed verification before the upgrade but fails after it contains a change that should have been blocked.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Description 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.
Title gittuf: File protection rules bypassed for filenames with special characters
Weaknesses CWE-863
References
Metrics cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N'}

Subscriptions

No data.

Weaknesses

Sources

Status
PUBLISHED
Assigner
Akrites
Published
Updated
Nov 13, 2026, 3:20 PM
Reserved
Nov 12, 2026, 8:36 PM
Status
Deferred
Published
Nov 13, 2026, 4:18 PM
Modified
Nov 13, 2026, 4:18 PM