# CVE-2020-1726: GO-2023-1544 - Podman has Files or Directories Accessible to External Parties in github.com/containers/libpod

Source: https://junglewise.ai/threats/cve-2020-1726-podman-has-files-or-directories-accessible-to-external-parties  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2024-08-20  
License: CC BY 4.0 with a link back

CVE-2020-1726 · Severity: low · CVSS 3.1 · Published 2024-08-20

Podman has Files or Directories Accessible to External Parties in github.com/containers/libpod

Technologies: [github.com/containers/libpod (Go)](https://junglewise.ai/threats/technologies/github-com-containers-libpod), [github.com/containers/podman (Go)](https://junglewise.ai/threats/technologies/github-com-containers-podman), [github.com/containers/podman/v2 (Go)](https://junglewise.ai/threats/technologies/github-com-containers-podman-v2). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2020-1726 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2020-1726 being exploited in the wild.

**How severe is CVE-2020-1726?** Low severity, with a CVSS score of 3.1, published 20 August 2024.

**Which products and versions are affected?** github.com/containers/libpod (Go) SEMVER:introduced=1.6.0; github.com/containers/libpod/v2 (Go) SEMVER:introduced=0,fixed=2.0.6; github.com/containers/podman (Go) SEMVER:introduced=1.6.0,fixed=2.0.6; github.com/containers/podman/v2 (Go) SEMVER:introduced=0,fixed=2.0.6.

**Is there a fix for CVE-2020-1726?** Yes. github.com/containers/libpod/v2 (Go): upgrade to 2.0.6 or later; github.com/containers/podman (Go): upgrade to 2.0.6 or later; github.com/containers/podman/v2 (Go): upgrade to 2.0.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2020-1726?** Check whether you run github.com/containers/libpod (Go), github.com/containers/libpod/v2 (Go), github.com/containers/podman (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/containers/libpod/v2 (Go): upgrade to 2.0.6 or later

  ```sh
  go get github.com/containers/libpod/v2@v2.0.6
  ```

- github.com/containers/podman (Go): upgrade to 2.0.6 or later

  ```sh
  go get github.com/containers/podman@v2.0.6
  ```

- github.com/containers/podman/v2 (Go): upgrade to 2.0.6 or later

  ```sh
  go get github.com/containers/podman/v2@v2.0.6
  ```


## Affected products

- github.com/containers/libpod (Go) SEMVER:introduced=1.6.0
- github.com/containers/libpod/v2 (Go) SEMVER:introduced=0,fixed=2.0.6
- github.com/containers/podman (Go) SEMVER:introduced=1.6.0,fixed=2.0.6
- github.com/containers/podman/v2 (Go) SEMVER:introduced=0,fixed=2.0.6

## Identifiers

- CVE-2020-1726
- GHSA-vmhj-p9hw-vgrf
- GO-2023-1544

## Related threats

- [Podman sandbox bypass via checkpoint image annotation](https://junglewise.ai/threats/cve-2026-94603-podman-the-podman-run-command-can-be-instructed-to-disable-almost)
- [Podman quadlet install incomplete file truncation](https://junglewise.ai/threats/cve-2026-19730-podman-quadlet-install-incomplete-file-truncation)
- [Podman host environment variable leak via malformed container image](https://junglewise.ai/threats/cve-2026-57231-podman-host-environment-variable-leak-via-malformed-container)
- [Podman symlink traversal in WORKDIR path resolution](https://junglewise.ai/threats/cve-2026-55686-podman-symlink-traversal-in-workdir-path-resolution)
- [Podman command injection in HyperV machine backend](https://junglewise.ai/threats/cve-2026-33414-podman-command-injection-in-hyperv-machine-backend)