CVE-2026-128036

Description

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.

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

• 2.3CVSS 3.1, Lowfrom the CNA (Akrites)CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N

What to do

• Upgrade to gittuf 0.17.0 or later, then run gittuf verify-ref over the full history of each protected reference. If an intermediate policy is invalid, verification stops with an error; review the reference state log and repository audit logs to find out whether a user with write access tampered with the policy.CNA solution statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

Timeline

1. 13 Nov 2026 Published

Weakness

• CWE-863

References

• github.com
• github.com