In gittuf 0.4.0 through 0.16.0, when a policy update appears within the range of reference state log entries being
Affects gittufSource GCVE Database
Not known to be exploited · CVSS 2.3 Low.
Data as of 18 Nov 2026, 16:08 UTC
Thin evidence
One scorer or none| CNA (Akrites) | CVSS 3.1 | 2.3 |
|---|
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10gittufpkg:deb/ubuntu/gittuf?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu Pro 26.04 LTSgittufpkg:deb/ubuntu/gittuf?arch=source&distro=esm-apps/resoluteOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a fix is available, restrict push access to trusted users only and monitor for any unauthorized direct modifications to the policy reference and reference state log. Avoid bypassing the gittuf policy apply mechanism.
Description
In gittuf versions 0.4.0 through 0.16.0, a vulnerability exists in the verification process of policy updates. When a policy update appears within the range of reference state log entries being verified, only the root of trust signatures of the new policy are checked, not the signatures of its other metadata such as rule files. This allows a user with push privileges who bypasses the gittuf policy apply mechanism and writes the policy reference and reference state log directly to cause an invalid policy application during verification, potentially weakening or strengthening rules for subsequent changes. The update is still recorded in the reference state log.