Vulnerability in github.com/gittuf/gittuf (CVE-2026-44544)
Summary
Vulnerability in github.com/gittuf/gittuf (CVE-2026-44544). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.14.0 or later.
Original description
The description as published by the source.
gittuf is a platform-agnostic Git security system. Prior to 0.14.0, an attacker with push access to gittuf's Reference State Log (RSL) can roll back the current policy to any previous policy trusted by the current set of root keys. gittuf determines the policy to load by inspecting the RSL. Except for the very first policy (which is automatically trusted given gittuf's TOFU model, or verified against manually specified keys), whenever an RSL entry that points to a new policy is encountered, gittuf validates that this policy is trusted. This is done by checking that the new policy’s root metadata is signed by the required threshold of the current policy's root keys. Because of this, an attacker with push access to the RSL may create a new entry that references an old policy (that is trusted by the most recent policy's set of root keys), thereby rolling back gittuf's policy to the attacker's chosen state. This vulnerability is fixed in 0.14.0.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44544 has been found in github.com/gittuf/gittuf.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/gittuf/gittuf to 0.14.0 or later.
If unsure, ask your IT team or search "github.com/gittuf/gittuf CVE-2026-44544" on the vendor's site.
CVE-2026-44544 (github.com/gittuf/gittuf) — CWE-639
Patched: 0.14.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-639) exists in github.com/gittuf/gittuf.
Check the vendor advisory for the affected versions of github.com/gittuf/gittuf.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.14.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/gittuf/gittuf' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/gittuf/gittuf' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/gittuf/gittufを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/gittuf/gittuf to 0.14.0ステージング環境で 0.14.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-44544 gittuf
- Ubuntu UBUNTU-CVE-2026-44544 gittuf
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com