Analysis and contextual insights are available on OpenCVE Cloud.
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.
No advisories yet.
Fri, 13 Nov 2026 15:30:00 +0000
| 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
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: Akrites
Published:
Updated: 2026-11-13T15:20:35.569Z
Reserved: 2026-11-12T20:36:23.290Z
Link: CVE-2026-128034
No data.
Status : Deferred
Published: 2026-11-13T16:18:58.683
Modified: 2026-11-13T16:18:58.797
Link: CVE-2026-128034
No data.
OpenCVE Enrichment
No data.