gittuf: Policy rules bypassed in the presence of global rules
Summary
| CVE | CVE-2026-128037 |
|---|---|
| State | PUBLISHED |
| Assigner | Akrites |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-11-13 16:18:59 UTC |
| Updated | 2026-11-13 16:18:59 UTC |
| Description | In gittuf 0.10.0 through 0.15.0, when a minimum threshold global rule and a policy rule protect the same namespace, verification gives the global rule's check over all trusted users in the policy precedence over the policy rule's own authorized users. A user listed in the policy file but not authorized by the policy rule, or fewer users than the rule's threshold, can make changes to the protected namespace that pass verification. |
Risk And Classification
Primary CVSS: v3.1 6.5 MEDIUM from 7fefd608-56a6-419f-a002-fd8543c0710a
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Problem Types: CWE-863 | CWE-863 CWE-863 Incorrect Authorization
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | 7fefd608-56a6-419f-a002-fd8543c0710a | Secondary | 6.5 | MEDIUM | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
| 3.1 | CNA | CVSS | 6.5 | MEDIUM | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
NoneIntegrity
HighAvailability
NoneCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Vendor Declared Affected Products
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| github.com/gittuf/gittuf/releases/tag/v0.16.0 | 7fefd608-56a6-419f-a002-fd8543c0710a | github.com | |
| github.com/gittuf/gittuf/security/advisories/GHSA-qc8j-pcph-6q9x | 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: Arpit Jain (en)
Additional Advisory Data
Solutions
CNA: Upgrade to gittuf 0.16.0 or later, which checks policy rules and global rules independently. Then re-run verification on the repository to make sure the vulnerability was not exploited.
There are currently no legacy QID mappings associated with this CVE.