CVE-2026-128035 · Package
NO FIX YET · SEE WHAT TO DO
gittuf verification applies only the propagated policy in effect at the start of checking, and skips later policy updates recorded in the reference state log. As a result, changes that later global rules such as threshold requirements or force-push blocks should reject can pass verification.
first public Nov 12, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams that use gittuf to verify Git repositories whose policy is propagated from an upstream controller repository. Repositories without propagated policy from a controller are not described as affected.
Not affected if default-config
Who cares git, gittuf, supply-chain
gittuf version; versions 0.10.0 through 0.17.0 are affected.0.17.0; the exact fixed version is unknown from the sources.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.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.