Skip to content

deps(deps): update module github.com/in-toto/in-toto-golang to v0.11.0 [security] - #324

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/go-github.com-in-toto-in-toto-golang-vulnerability
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/go-github.com-in-toto-in-toto-golang-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
github.com/in-toto/in-toto-golang v0.9.0 → v0.11.0 age confidence

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

GHSA-pmwq-pjrm-6p5r

More information

Details

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.

Severity

  • CVSS Score: 4.1 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

in-toto/in-toto-golang (github.com/in-toto/in-toto-golang)

v0.11.0

Compare Source

What's Changed

Full Changelog: in-toto/in-toto-golang@v0.10.0...v0.11.0

v0.10.0

Compare Source

What's Changed

New Contributors

Full Changelog: in-toto/in-toto-golang@v0.9.0...v0.10.0


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

…0 [security]

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate
renovate Bot requested a review from a team as a code owner October 13, 2026 11:06
@renovate
renovate Bot requested a review from arturshadnik October 13, 2026 11:06
@renovate

renovate Bot commented Oct 13, 2026

Copy link
Copy Markdown
Contributor Author

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 14 additional dependencies were updated
  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.23.10 -> 1.24.0
github.com/spf13/cobra v1.8.1 -> v1.10.2
github.com/stretchr/testify v1.10.0 -> v1.11.1
github.com/go-jose/go-jose/v4 v4.0.4 -> v4.1.4
github.com/google/go-cmp v0.6.0 -> v0.7.0
github.com/secure-systems-lab/go-securesystemslib v0.8.0 -> v0.10.0
github.com/spf13/pflag v1.0.5 -> v1.0.10
golang.org/x/crypto v0.31.0 -> v0.46.0
golang.org/x/mod v0.23.0 -> v0.30.0
golang.org/x/net v0.32.0 -> v0.48.0
golang.org/x/sync v0.11.0 -> v0.19.0
golang.org/x/sys v0.28.0 -> v0.41.0
golang.org/x/term v0.27.0 -> v0.38.0
golang.org/x/text v0.21.0 -> v0.32.0
google.golang.org/protobuf v1.35.2 -> v1.36.11

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants