In gittuf 0.10.0 through 0.17.0, the verification workflow does not load policy updates that are propagated from an upstream (controller) repository and recorded in the reference state log after the first entry being verified. Only the propagated policy in effect at the start of verification is applied, so later controller changes to global rules, such as threshold requirements and force-push blocks, are ignored and changes that these rules should block pass verification.
Project Subscriptions
No data.
Advisories
No advisories yet.
Fixes
Solution
Upgrade to gittuf 0.18.0 or later, then run gittuf verify-ref over the full history of each protected reference. Policy propagation has been moved back into gittuf's developer mode.
Workaround
No workaround given by the vendor.
References
History
Fri, 13 Nov 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In gittuf 0.10.0 through 0.17.0, the verification workflow does not load policy updates that are propagated from an upstream (controller) repository and recorded in the reference state log after the first entry being verified. Only the propagated policy in effect at the start of verification is applied, so later controller changes to global rules, such as threshold requirements and force-push blocks, are ignored and changes that these rules should block pass verification. | |
| Title | gittuf: Propagated controller policies not loaded during verification | |
| Weaknesses | CWE-863 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: Akrites
Published:
Updated: 2026-11-13T15:20:36.628Z
Reserved: 2026-11-12T20:36:23.291Z
Link: CVE-2026-128035
No data.
No data.
No data.
OpenCVE Enrichment
No data.
Weaknesses