Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

Improperly Implemented path matching for in-toto-golangGHSA-vrxp-mg9f-hwf3

MEDIUMFix: in-toto/in-toto-golang@f2c57d1

GHSA-vrxp-mg9f-hwf3 is a medium-severity (CVSS 5.6) CWE-345 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.

Also known asCVE-2021-41087GO-2022-0936
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs35th percentile — riskier than 35% of all scored CVEsHighest risk
0.00%0.31%0.62%0.93%0.3%0.4%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-vrxp-mg9f-hwf3 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected
🐹github.com/in-toto/in-toto-golang

Real-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

Authenticated attackers posing as functionaries (i.e., within a trusted set of users for a layout) are able to create attestations that may bypass DISALLOW rules in the same layout. An attacker with access to trusted private keys, may issue an attestation that contains a disallowed artifact by including path traversal semantics (e.g., foo vs dir/../foo).

Patches

The problem has been fixed in version 0.3.0.

Workarounds

Exploiting this vulnerability is dependent on the specific policy applied.

For more information

If you have any questions or comments about this advisory:

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/in-toto/in-toto-golangall versions0.3.0go get github.com/in-toto/in-toto-golang@v0.3.0

Affected Products

1 product · 1 configurations
Application
in-toto-golangin-toto
< 0.3.0
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    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.

  2. Fix

    Update github.com/in-toto/in-toto-golang to 0.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vrxp-mg9f-hwf3 is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

### Impact Authenticated attackers posing as functionaries (i.e., within a trusted set of users for a layout) are able to create attestations that may bypass DISALLOW rules in the same layout. An attacker with access to trusted private keys, may issue an attestation that contains a disallowed artifact by including path traversal semantics (e.g., foo vs dir/../foo). ### Patches The problem has been fixed in version 0.3.0. ### Workarounds Exploiting this vulnerability is dependent on the specific policy applied. ### For more information If you have any questions or comments about this advisor
O3 Security · Impact-Aware SCA

Is GHSA-vrxp-mg9f-hwf3 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Improperly Implemented path matching for in-toto-golang