GHSA-pmwq-pjrm-6p5r json
in-toto-golang and in-toto-python have inconsistent negation behavior
published 6mo ago modified 2mo ago also GO-2026-5547
- cvss
- 4.1
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
### Impact _What kind of vulnerability is it? Who is impacted?_
in-toto-golang and in-toto-python both support glob patterns in artifact rules to indicate the artifacts that a rule applies to. Both support negations in character classes to indicate what should *not* be matched, but they used different operators to indicate the negation. in-toto-python uses `!` while in-toto-golang used `^`. A layout authored with the expectations of one implementation can therefore exhibit different behavior in the other implementation.
This impacts users in a specific set of circumstances where two different implementations are used to verify the same layout + attestation bundle at different stages of the same pipeline. As a rule of thumb, we advise using a single implementation across all aspects of a pipeline, from layout creation to pipeline execution and verification to prevent this class of bugs.
### Patches _Has the problem been patched? What versions should users upgrade to?_
in-toto-golang has been updated to use `!` instead of `^` to indicate negation. See https://github.com/in-toto/in-toto-golang/pull/462. This is part of v0.11.0.
Patch / fix
- go github.com/in-toto/in-toto-golang 0.11.0
- github.com/in-toto/in-toto-golang@36d782f commit
- github.com/in-toto/in-toto-golang#462 pull request
Is GHSA-pmwq-pjrm-6p5r in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 4.1 | CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/in-toto/in-toto-golang | <0.11.0 |
0.11.0 |
Classification
- Weakness
-
- CWE-168 Improper Handling of Inconsistent Special Elements
References
Sources
- GitHub Advisory GHSA-pmwq-pjrm-6p5r
- OSV GO-2026-5547
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.