CVE-2023-32076
MEDIUMDescription
in-toto is a framework to protect supply chain integrity. The in-toto configuration is read from various directories and allows users to configure the behavior of the framework. The files are from directories following the XDG base directory specification. In versions 1.4.0 and prior, among the files read is `.in_totorc` which is a hidden file in the directory in which in-toto is run. If an attacker controls the inputs to a supply chain step, they can mask their activities by also passing in an `.in_totorc` file that includes the necessary exclude patterns and settings. RC files are widely used in other systems and security issues have been discovered in their implementations as well. Maintainers found in their conversations with in-toto adopters that `in_totorc` is not their preferred way to configure in-toto. As none of the options supported in `in_totorc` is unique, and can be set elsewhere using API parameters or CLI arguments, the maintainers decided to drop support for `in_totorc`. in-toto's `user_settings` module has been dropped altogether in commit 3a21d84f40811b7d191fa7bd17265c1f99599afd. Users may also sandbox functionary code as a security measure.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 16% of all known CVEs.
References
Related Vulnerabilities
Other CWE-15 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-39280 | Critical | 9.1 | 34% | - | - |
| CVE-2026-41176 | Critical | 9.8 | 33% | - | Fix |
| CVE-2023-50252 | High | 8.3 | 24% | - | Fix |
| CVE-2024-38666 | Critical | 9.1 | 19% | - | - |
| CVE-2024-51544 | High | 8.2 | 13% | - | Fix |
| CVE-2026-45087 | Critical | 10.0 | 13% | - | - |
Common questions
How do I fix CVE-2023-32076?
Published advisories record a fix for 2 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2023-32076 being actively exploited?
Not that we know of. CVE-2023-32076 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.24% is the estimated probability that it will be exploited in the next 30 days. That is higher than 16% of all scored CVEs.
How severe is CVE-2023-32076?
CVE-2023-32076 has a CVSS v3 base score of 5.5, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2023-32076 affect?
Published advisories record a fix for in-toto (Debian), in-toto (PyPI (Python)). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2023-32076
Markdown
[](https://tridentstack.com/cve/CVE-2023-32076)HTML
<a href="https://tridentstack.com/cve/CVE-2023-32076"><img src="https://tridentstack.com/cve/badge/CVE-2023-32076.svg" alt="CVE-2023-32076"></a>Check your Linux endpoints for this class of vulnerability
TridentStack Control continuously scans Linux endpoints for known vulnerabilities and deploys the fixes from the same console. 200 endpoints free forever, no credit card.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-06-17.