# CVE-2026-128036: gittuf: Invalid intermediate policies trusted when the policy apply workflow is bypassed


- **Severity:** Low 2.3 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-774m-m728-236h, UBUNTU-CVE-2026-128036

## What is CVE-2026-128036?

CVE-2026-128036 is a low-severity vulnerability in gittuf, published on 13 Nov 2026. 

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

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-128036?


## How do I fix CVE-2026-128036?

No fix has been published for CVE-2026-128036 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-128036 being exploited?

There is no known exploitation of CVE-2026-128036 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-128036 and fix it if it is affected.

What it is: CVE-2026-128036 is a low-severity vulnerability in gittuf, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-128036 in the wild and no public exploit code.

Affected product: gittuf. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-128036/ (Markdown: https://insights.sbomify.com/CVE-2026-128036/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-128036
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-128036
- OSV: https://osv.dev/vulnerability/CVE-2026-128036

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-128036/
Summaries are generated and may contain mistakes; the official description above is the record.
