CVE-2021-41087: in-toto-golang is a go implementation of the in-toto framework to protect software supply chain integrity

Q: How do I fix CVE-2021-41087?

in-toto-golang: upgrade to 0.3.0. Exact commands for each OS are on this page.

Q: Is CVE-2021-41087 being exploited?

CVE-2021-41087 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2021-41087 affect?

CVE-2021-41087 affects in-toto-golang. Severity is medium (CVSS 5.6). in-toto-golang is a go implementation of the in-toto framework to protect software supply chain integrity. In affected versions authenticated attackers posing as functionaries (i.e., within a trusted set of users for a layout) are able to c

Q: How urgent is CVE-2021-41087?

Priority 29/100. No elevated risk signals yet.

Routine

MEDIUM 5.6UPGRADE

CVE-2021-41087 is a medium-severity flaw (CVSS 5.6) affecting in-toto-golang. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

in-toto-golang is a go implementation of the in-toto framework to protect software supply chain integrity. In affected versions 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 se

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.6 (Medium)
Attack vector	Local
Attack complexity	High
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.4% (top 63%)
CISA exploited list	No
Weakness	CWE-345, CWE-22
Published	2021-09-21
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: in-toto

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2021-09-21 21:15 UTCPublished CVE record published
2026-06-17 04:07 UTCUpdated Record last modified

in-toto in-toto-golang UPGRADE

Affected: < 0.3.0

Fixed in: 0.3.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy in-toto-golang || rpm -q in-toto-golang || in-toto-golang --version

2. UPGRADE to 0.3.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade in-toto-golang

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade in-toto-golang

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2021-41087?

in-toto-golang: upgrade to 0.3.0. Exact commands for each OS are on this page.

Is CVE-2021-41087 being exploited?

CVE-2021-41087 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2021-41087 affect?

CVE-2021-41087 affects in-toto-golang. Severity is medium (CVSS 5.6). in-toto-golang is a go implementation of the in-toto framework to protect software supply chain integrity. In affected versions authenticated attackers posing as functionaries (i.e., within a trusted set of users for a layout) are able to c

How urgent is CVE-2021-41087?

Priority 29/100. No elevated risk signals yet.

Software pages

Go (Golang) vulnerabilities

References

← Back to latest CVEs