GHSA-pmwq-pjrm-6p5r is a medium-severity (CVSS 4.1) vulnerability in github.com/in-toto/in-toto-golang. A fix is available for github.com/in-toto/in-toto-golang — see the affected versions and patch details below.
in-toto-golang and in-toto-python have inconsistent negation behavior
Real-World Exposure
github.com/in-toto/in-toto-golangReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/in-toto/in-toto-golang | all versions | 0.11.0go get github.com/in-toto/in-toto-golang@v0.11.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/in-toto/in-toto-golang, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/in-toto/in-toto-golang to 0.11.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pmwq-pjrm-6p5r is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-pmwq-pjrm-6p5r can be triaged on real exposure rather than presence alone.
Tailored to GHSA-pmwq-pjrm-6p5r. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-pmwq-pjrm-6p5r in your dependencies?
O3 Security finds GHSA-pmwq-pjrm-6p5r across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.