gittuf: File protection rules bypassed for filenames with special characters

MITRE NVD CVE.ORG JSON API

Summary

CVECVE-2026-128034
StatePUBLISHED
AssignerAkrites
Source PriorityCVE Program / NVD first with legacy fallback
Published2026-11-13 16:18:58 UTC
Updated2026-11-13 16:18:58 UTC
DescriptionIn 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.

Risk And Classification

Primary CVSS: v3.1 5.5 MEDIUM from 7fefd608-56a6-419f-a002-fd8543c0710a

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Problem Types: CWE-863 | CWE-863 CWE-863 Incorrect Authorization

VersionSourceTypeScoreSeverityVector
3.17fefd608-56a6-419f-a002-fd8543c0710aSecondary5.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
3.1CNACVSS5.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

CVSS v3.1 Breakdown

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Vendor Declared Affected Products

SourceVendorProductVersionPlatforms
CNA Gittuf Gittuf affected 0.18.0 semver Not specified

References

ReferenceSourceLinkTags
github.com/gittuf/gittuf/security/advisories/GHSA-hxqr-h35w-2898 7fefd608-56a6-419f-a002-fd8543c0710a github.com
github.com/gittuf/gittuf/releases/tag/v0.18.0 7fefd608-56a6-419f-a002-fd8543c0710a github.com
CVE Program record CVE.ORG www.cve.org canonical
NVD vulnerability detail NVD nvd.nist.gov canonical, analysis

Vendor Comments And Credit

Discovery Credit

CNA: Pratham Hegde (en)

CNA: Bhuvan Somisetty (en)

Additional Advisory Data

Solutions

CNA: 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.

© CVE.report 2026

Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. It is the responsibility of user to evaluate the accuracy, completeness or usefulness of any information, opinion, advice or other content. EACH USER WILL BE SOLELY RESPONSIBLE FOR ANY consequences of his or her direct or indirect use of this web site. ALL WARRANTIES OF ANY KIND ARE EXPRESSLY DISCLAIMED. This site will NOT BE LIABLE FOR ANY DIRECT, INDIRECT or any other kind of loss.

CVE, CWE, and OVAL are registred trademarks of The MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. This site includes MITRE data granted under the following license.

Free CVE JSON API cve.report/api

CVE.report and Source URL Uptime Status status.cve.report