GHSA-PMWQ-PJRM-6P5R

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

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.

GHSA-PMWQ-PJRM-6P5R has a CVSS score of 4.1 (Medium). The vector is requires local access, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.11.0); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is GHSA-PMWQ-PJRM-6P5R? GHSA-PMWQ-PJRM-6P5R is a medium-severity security vulnerability in github.com/in-toto/in-toto-golang (go), affecting versions < 0.11.0. It is fixed in 0.11.0.
2. How severe is GHSA-PMWQ-PJRM-6P5R? GHSA-PMWQ-PJRM-6P5R has a CVSS score of 4.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/in-toto/in-toto-golang are affected by GHSA-PMWQ-PJRM-6P5R? github.com/in-toto/in-toto-golang (go) versions < 0.11.0 is affected.
4. Is there a fix for GHSA-PMWQ-PJRM-6P5R? Yes. GHSA-PMWQ-PJRM-6P5R is fixed in 0.11.0. Upgrade to this version or later.
5. Is GHSA-PMWQ-PJRM-6P5R exploitable, and should I be worried? Whether GHSA-PMWQ-PJRM-6P5R is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-PMWQ-PJRM-6P5R is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-PMWQ-PJRM-6P5R? Upgrade github.com/in-toto/in-toto-golang to 0.11.0 or later.