# Insecure permissions on build temporary rootfs in Singularity

Advisory record · `GHSA-jv9c-w74q-6762`

- **Identifiers:** `GHSA-jv9c-w74q-6762` · `CVE-2020-25040`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-668](https://cwe.mitre.org/data/definitions/668.html) · [CWE-732](https://cwe.mitre.org/data/definitions/732.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 24 May 2021
- **Updated:** 8 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 24 May 2021, 16:56 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/sylabs/singularity` (Go): affected `<3.6.3`; fixed in `3.6.3`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Singularity (github.com/sylabs/singularity) versions before 3.6.3 create build temporary directories with insecure permissions. A user with local access to the system can read the image contents during a build and, if the image contains world-writable files or directories, inject content that may lead to arbitrary code execution during the build or when the container runs. Upgrade to Singularity 3.6.3, which fixes the issue. Setting TMPDIR to a location accessible only to the user reduces exposure, but the source says this is hard to enforce.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.8 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.020, the 81st percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:05 UTC: First seen by agentprime
- 31 Oct 2026, 15:05 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jv9c-w74q-6762)

## Sources

- [GitHub Advisory Database: GHSA-jv9c-w74q-6762](https://github.com/advisories/GHSA-jv9c-w74q-6762)
- [OSV: GHSA-jv9c-w74q-6762](https://osv.dev/vulnerability/GHSA-jv9c-w74q-6762)
- <https://github.com/hpcng/singularity/security/advisories/GHSA-jv9c-w74q-6762>
- <https://nvd.nist.gov/vuln/detail/CVE-2020-25040>
- <https://medium.com/sylabs>
- <http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00070.html>
- <http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00088.html>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-jv9c-w74q-6762>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jv9c-w74q-6762/>. Everything for agents: <https://agentprime.io/llms.txt>.
