CVE-2020-1726: A flaw was discovered in Podman where it incorrectly allows containers when created to overwrite existing file

This month

MEDIUM 5.9REMOTEWATCHLISTDOWNGRADEDOWNGRADEMITIGATE

CVE-2020-1726 is a medium-severity flaw (CVSS 5.9) affecting libpod, openshift container platform, enterprise linux. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Remotely exploitable, no login, no user action
On your watchlist

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	5.9 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	1.8% (top 22%)
CISA exploited list	No
Weakness	CWE-552
Published	2020-02-11
Last modified	2026-06-17

Publisher (CNA): Red Hat, Inc. · Vendor: libpod project · redhat

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

Am I affected?

Timeline

2020-02-11 20:15 UTCPublished CVE record published
2026-06-17 03:02 UTCUpdated Record last modified

libpod project libpod DOWNGRADE

Affected: 1.6.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.6.0

1. Check installed version

apt-cache policy libpod || rpm -q libpod || libpod --version

2. No fixed release: DOWNGRADE to a release before 1.6.0 (Debian / Ubuntu)

apt-cache madison libpod sudo apt install libpod=<VERSION_BEFORE_1.6.0> sudo apt-mark hold libpod

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list libpod sudo dnf downgrade libpod-<VERSION_BEFORE_1.6.0> sudo dnf versionlock add libpod

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

redhat openshift container platform DOWNGRADE

Affected: 4.3

Fixed in: no fixed release known

Safe to downgrade to: a release before 4.3

1. Check installed version

apt-cache policy openshift-container-platform || rpm -q openshift-container-platform || openshift-container-platform --version

2. No fixed release: DOWNGRADE to a release before 4.3 (Debian / Ubuntu)

apt-cache madison openshift-container-platform sudo apt install openshift-container-platform=<VERSION_BEFORE_4.3> sudo apt-mark hold openshift-container-platform

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list openshift-container-platform sudo dnf downgrade openshift-container-platform-<VERSION_BEFORE_4.3> sudo dnf versionlock add openshift-container-platform

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

redhat enterprise linux MITIGATE

Affected: 8.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 8.0

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

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-2020-1726?

libpod: downgrade or apply the listed mitigation; openshift container platform: downgrade or apply the listed mitigation; enterprise linux: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2020-1726 being exploited?

CVE-2020-1726 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-2020-1726 affect?

CVE-2020-1726 affects libpod, openshift container platform, enterprise linux. Severity is medium (CVSS 5.9). 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 im

How urgent is CVE-2020-1726?

Priority 50/100. Remotely exploitable, no login, no user action; On your watchlist

Software pages

Red Hat OpenShift vulnerabilities · Podman vulnerabilities

Related CVEs

CVE-2019-18466 MEDIUM 5.5 UPGRADE An issue was discovered in Podman in libpod before 1.6.0
CVE-2019-10214 MEDIUM 5.9 MITIGATE MITIGATE The containers/image library used by the container tools Podman, Buildah, and Skopeo in Red Hat Enterprise Lin
CVE-2019-10152 HIGH 7.2 UPGRADE MITIGATE A path traversal vulnerability has been discovered in podman before version 1.4.0 in the way it handles symlin
CVE-2018-10856 MEDIUM 5.3 UPGRADE It has been discovered that podman before version 0.6.1 does not drop capabilities when executing a container

References

← Back to latest CVEs