---
id: "CVE-2026-128035"
page: "https://infrastack.ai/live/CVE-2026-128035"
kind: "vulnerability"
aliases: ["CVE-2026-128035"]
title: "gittuf: verification ignores later upstream policy changes, letting blocked changes pass"
severity: "medium"
cvss: 5.5
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["git", "gittuf", "package", "supply-chain"]
not_affected_if: ["default-config"]
published_at: "2026-11-13T16:18:58+00:00"
first_seen_at: "2026-11-13T16:47:33+00:00"
updated_at: "2026-11-13T16:48:57+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-128035", "first_seen_at": "2026-11-13T16:47:33+00:00"}]
exploit_sources: []
---

# gittuf: verification ignores later upstream policy changes, letting blocked changes pass

Link for people: https://infrastack.ai/live/CVE-2026-128035 (this .md is for agents)

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.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed gittuf version with `gittuf version`; versions 0.10.0 through 0.17.0 are affected.
- Check whether the repository uses propagated policy from an upstream controller repository.

## Fix

- Move to a gittuf release later than `0.17.0`; the exact fixed version is unknown from the sources.

## Timeline

- 2026-11-13T16:47:33+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-128035

## Documents

- [advisory] Vendor advisory: github.com https://github.com/gittuf/gittuf/security/advisories/GHSA-pchw-g6rm-gxvh
- [fix] Release notes: github.com https://github.com/gittuf/gittuf/releases/tag/v0.18.0

## 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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_