{"answers":{"affected":"3 open source packages ship an affected version, including github.com/in-toto/in-toto-golang.","exploited":"There is no known exploitation of GHSA-pmwq-pjrm-6p5r in the wild and no public exploit code.","fix":"Upgrade github.com/in-toto/in-toto-golang to 0.11.0 or later.","what":"GHSA-pmwq-pjrm-6p5r is a vulnerability in github.com/in-toto/in-toto-golang, published on 8 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-pmwq-pjrm-6p5r and fix it if it is affected.\n\nWhat it is: GHSA-pmwq-pjrm-6p5r is a vulnerability in github.com/in-toto/in-toto-golang, published on 8 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-pmwq-pjrm-6p5r in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/in-toto/in-toto-golang (Go): affected all versions; fixed in 0.11.0\n- github.com/in-toto/in-toto-golang (Go): affected all versions; fixed in 0.11.0\n- github.com/in-toto/in-toto-golang (Go): affected all versions; fixed in 0.11.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-pmwq-pjrm-6p5r/ (Markdown: https://insights.sbomify.com/GHSA-pmwq-pjrm-6p5r/index.md)","id":"GHSA-pmwq-pjrm-6p5r","markdown":"https://insights.sbomify.com/GHSA-pmwq-pjrm-6p5r/index.md","name":"GHSA-pmwq-pjrm-6p5r","record":{"aliases":["GO-2026-5547"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Go supply chain library","requires_auth":"none","summary":"Inconsistent glob negation syntax between Go and Python in-toto libraries allows bypassing artifact verification rules in mixed-implementation pipelines.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nin-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.\n\nThis 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.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nin-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.","ecosystems":["Go"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"in-toto-golang and in-toto-python have inconsistent negation behavior","id":"GHSA-pmwq-pjrm-6p5r","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Go","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"Go","fixed":["0.11.0"],"introduced":["0"],"last_affected":[],"package":"github.com/in-toto/in-toto-golang","purl":null,"source":"GHSA-pmwq-pjrm-6p5r"},{"ecosystem":"Go","fixed":["0.11.0"],"introduced":["0"],"last_affected":[],"package":"github.com/in-toto/in-toto-golang","purl":"pkg:golang/github.com/in-toto/in-toto-golang","source":"GHSA-pmwq-pjrm-6p5r"},{"ecosystem":"Go","fixed":["0.11.0"],"introduced":["0"],"last_affected":[],"package":"github.com/in-toto/in-toto-golang","purl":"pkg:golang/github.com/in-toto/in-toto-golang","source":"GO-2026-5547"}],"products":null,"published":"2026-05-08","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Inconsistent glob negation syntax between Go and Python in-toto libraries allows bypassing artifact verification rules in mixed-implementation pipelines.","url":"https://insights.sbomify.com/GHSA-pmwq-pjrm-6p5r/"}