CVE-2020-1726

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data tampering.

Exploit odds

1.5% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2020-02-11 20:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 03:02 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.5% in the next 30 days (EPSS).
• Severity: 5.9 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2020-02-11 20:15 UTC

Last modified

2026-06-17 03:02 UTC

Exploit probability

1.5% · EPSS, next 30 days

Weakness

CWE-552

Record status

Modified

Affected

• Libpod Project Libpod 1.6.0
• Redhat Openshift Container Platform 4.3
• Redhat Enterprise Linux 8.0

Attack profile CVSS 3.1 · 5.9

Attack vector

Network

Complexity

High

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2020-1726.md and follow it. Check whether this project is affected by CVE-2020-1726. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge