in-toto-golang and in-toto-python have inconsistent negation behavior

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.1 · CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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…

Published by the source

8 May 2026, 22:24 UTC

Last modified by the source

8 May 2026, 22:24 UTC

Source last checked

26 Oct 2026, 15:20 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-pmwq-pjrm-6p5r

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-pmwq-pjrm-6p5r

Advisory: in-toto-golang and in-toto-python have inconsistent negation behavior
IDs: GHSA-pmwq-pjrm-6p5r
Record: https://patchnext.com/advisories/ghsa-pmwq-pjrm-6p5r (revision 1, source checked 26 Oct 2026, 15:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/in-toto/in-toto-golang 0.11.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/in-toto/in-toto-golang: affected < 0.11.0; fixed in 0.11.0

## Suggested inspection (read-only)
- Go github.com/in-toto/in-toto-golang: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/in-toto/in-toto-golang.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-pmwq-pjrm-6p5r (GitHub-reviewed advisory GHSA-pmwq-pjrm-6p5r lists affected ranges: Go github.com/in-toto/in-toto-golang >=0 <0.11.0)

Commands are suggestions: review each one before running it.