CVE-2026-128036 · Package
NO FIX YET · SEE WHAT TO DO
gittuf, a Git security tool, verifies only the root-of-trust signatures on a new policy and not the signatures on its rule files. A user already trusted to push to the repository can craft an invalid policy that verification accepts, which changes the rules for later changes.
first public Oct 19, 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 enforce policy on Git repositories in versions 0.4.0 through 0.16.0. The risk requires a user who is already trusted to push to the repository and who bypasses gittuf policy apply to write the policy reference directly. Teams on other versions, or who do not use gittuf, can skip it.
Not affected if gittuf-not-used, version-outside-range
Who cares git, gittuf, supply-chain
gittuf --version and see whether it falls in 0.4.0 through 0.16.0.In gittuf 0.4.0 through 0.16.0, when a policy update appears within the range of reference state log entries being verified, verification checks only the root of trust signatures of the new policy and not the signatures of its other metadata (rule files). A user trusted to push to the repository who bypasses gittuf policy apply and writes the policy reference and reference state log directly can make an invalid policy apply during verification, weakening or strengthening the rules for later changes. The update is still recorded in the reference state log.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/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.