Vulnerabilities in pkg:golang/github.com/in-toto/in-toto-golang

PACKAGE
Share
Advisory Summary

GHSA-pmwq-pjrm-6p5r is a MODERATE (CVSS 4.1) in-toto-golang and in-toto-python have inconsistent vulnerability (CWE-168: Improper Handling of Inconsistent Special Elements) affecting Github.com/in toto/in toto golang libraries in the Go ecosystem. The issue involves in-toto-golang and in-toto-python have inconsistent negation behavior. Remediation is available by upgrading affected packages to version 0.11.0.

2 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:golang/github.com/in-toto/in-toto-golang

2 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:golang/github.com/in-toto/in-toto-golang. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-pmwq-pjrm-6p5r - MODERATE in-toto-golang and in-toto-python have inconsistent negation behavior
GHSA-vrxp-mg9f-hwf3 CVE-2021-41087 MODERATE Improperly Implemented path matching for in-toto-golang

GHSA-pmwq-pjrm-6p5r at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-pmwq-pjrm-6p5r
Severity MODERATE
CVSS v3.1 Base Score 4.1
CWE Classification CWE-168: Improper Handling of Inconsistent Special Elements
Affected Product Github.com/in toto/in toto golang
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 4.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N).

Attack Vector Local (AV:L)
Attack Complexity High (AC:H)
Privileges Required High (PR:H)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability None (A:N)

How to Fix GHSA-pmwq-pjrm-6p5r

To remediate this vulnerability, upgrade all affected Github.com/in toto/in toto golang dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/in-toto/in-toto-golang fixed: 0.11.0 
Upgrade github.com/in-toto/in-toto-golang to 0.11.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for github.com/in-toto/in-toto-golang

How to Check if You Are Affected

To determine whether your application is affected by GHSA-pmwq-pjrm-6p5r, inspect your project dependencies for Github.com/in toto/in toto golang:

inspect dependencies for github.com/in-toto/in-toto-golang

Analyze the terminal output to locate any version of Github.com/in toto/in toto golang in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.11.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-168: Improper Handling of Inconsistent Special Elements, where the product does not properly handle input in which an inconsistency exists between two or more special characters or reserved words. In Github.com/in toto/in toto golang, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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.

GHSA-pmwq-pjrm-6p5r Affected Github.com/in toto/in toto golang Versions

1 component(s)
Fixed Versions:
0.11.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/in-toto/in-toto-golang
golang/github.com/in-toto/in-toto-golang
Go
< 0.11.0
0.11.0

References

GitHub Advisory / Wiki ADVISORY
https://github.com/in-toto/in-toto-golang/security/advisories/GHSA-pmwq-pjrm-6p5r
Github.com/in toto/in toto golang Source Repository REPOSITORY
https://github.com/in-toto/in-toto-golang/pull/462
Security Fix Commit FIX COMMIT
https://github.com/in-toto/in-toto-golang/commit/36d782ffb2ca3adbffcdce1fd971c23319dd4469
Github.com/in toto/in toto golang Source Repository REPOSITORY
https://github.com/in-toto/in-toto-golang

Frequently Asked Questions

What is GHSA-pmwq-pjrm-6p5r?
GHSA-pmwq-pjrm-6p5r is a security vulnerability in Github.com/in toto/in toto golang involving in-toto-golang and in-toto-python have inconsistent negation behavior under CWE-168: Improper Handling of Inconsistent Special Elements.
Which Github.com/in toto/in toto golang versions are affected?
Affected versions include releases prior to 0.11.0 across affected packages: github.com/in-toto/in-toto-golang.
What version fixes GHSA-pmwq-pjrm-6p5r?
Upgrading to 0.11.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/in-toto/in-toto-golang affected?
Yes, github.com/in-toto/in-toto-golang is affected in releases prior to 0.11.0. Upgrade your dependency to 0.11.0 or later.
What is the CVSS score of GHSA-pmwq-pjrm-6p5r?
GHSA-pmwq-pjrm-6p5r has a CVSS v3.1 base score of 4.1 (MODERATE) with vector string CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N.
What CWE is associated with GHSA-pmwq-pjrm-6p5r?
GHSA-pmwq-pjrm-6p5r is classified under CWE-168: Improper Handling of Inconsistent Special Elements (The product does not properly handle input in which an inconsistency exists between two or more special characters or reserved words.).
How can I check Go dependencies for GHSA-pmwq-pjrm-6p5r?
Run the dependency tree command: 'inspect dependencies for github.com/in-toto/in-toto-golang'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-pmwq-pjrm-6p5r",
  "modified" : "2026-05-08T22:24:19Z",
  "published" : "2026-05-08T22:24:19Z",
  "aliases" : [ ],
  "summary" : "in-toto-golang and in-toto-python have inconsistent negation behavior",
  "details" : "### 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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/in-toto/in-toto-golang"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.11.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/in-toto/in-toto-golang/security/advisories/GHSA-pmwq-pjrm-6p5r"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/in-toto/in-toto-golang/pull/462"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/in-toto/in-toto-golang/commit/36d782ffb2ca3adbffcdce1fd971c23319dd4469"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/in-toto/in-toto-golang"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-168" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-08T22:24:19Z",
    "nvd_published_at" : null
  }
}