Podman has Files or Directories Accessible to External Parties

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.9 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

EPSS

• CVE-2020-1726: 1.77% estimated exploitation activity in the next 30 days; percentile 78.16 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A flaw was discovered in Podman where it incorrectly allows containers when created to overwrite existing files in volumes, even if they are mounted as read-only. When a user runs a malicious container or a container based on a malicious image with an attached volume that is used for the first time, it is possible to trigger the flaw and overwrite files in the volume. This issue was introduced in version 1.6.0.

Published by the source

24 May 2022, 17:08 UTC

Last modified by the source

1 May 2023, 22:27 UTC

Source last checked

26 Oct 2026, 14:58 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-vmhj-p9hw-vgrf

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-1726

Advisory: Podman has Files or Directories Accessible to External Parties
IDs: CVE-2020-1726, GHSA-vmhj-p9hw-vgrf
Record: https://patchnext.com/advisories/cve-2020-1726 (revision 1, source checked 26 Oct 2026, 14:58 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/containers/podman 2.0.6; github.com/containers/podman/v2 2.0.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/containers/podman: affected >= 1.6.0, < 2.0.6; fixed in 2.0.6
- Go github.com/containers/podman/v2: affected < 2.0.6; fixed in 2.0.6

## Suggested inspection (read-only)
- Go github.com/containers/podman: check the installed version with your package manager.
- Go github.com/containers/podman/v2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/containers/podman, github.com/containers/podman/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-vmhj-p9hw-vgrf (GitHub-reviewed advisory GHSA-vmhj-p9hw-vgrf lists affected ranges: Go github.com/containers/podman >=1.6.0 =0 <2.0.6)

Commands are suggestions: review each one before running it.