CVE-2020-1726: Files or Directories Accessible to External Parties in github.com/containers/libpod

github.com/containers/libpod Updated 02 Oct 2025

Summary

20/08/2024
No i
Unrated
Not published

CVE-2020-1726: Podman has Files or Directories Accessible to External Parties in github.com/containers/libpod. Affects github.com/containers/libpod versions >= 1.6.0. No fix is published. How to fix ↓

Also tracked for

The same CVE-2020-1726 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Podman is a tool for managing containers and pods, providing a user-friendly interface to interact with container runtimes. It is written in Go and is widely used in the container ecosystem. The vulnerability identified as CVE-2020-1726 affects the github.com/containers/libpod package, which is a core component of Podman.

Vulnerability Detail

The vulnerability in github.com/containers/libpod allows external parties to access files or directories that should not be accessible. This can lead to unauthorized access, data leakage, or potential exploitation of sensitive information. The issue was introduced in version 1.6.0 of the package and was fixed in version 2.0.6 of github.com/containers/libpod/v2.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a workaround, it is advised to restrict access to the vulnerable files or directories by modifying the file permissions or implementing access controls. Additionally, monitoring and auditing file access can help detect any unauthorized activity.

Conclusion

The vulnerability in github.com/containers/libpod exposes files or directories to external parties, potentially leading to unauthorized access or data leakage. Users of Podman are advised to update to version 2.0.6 or later to mitigate this vulnerability. Implementing access controls and monitoring file access can provide additional security measures.

See every vulnerability recorded for github.com/containers/libpod →

Share this vulnerability

FAQ

Podman is a container management tool that provides a command-line interface to manage containers and pods. It is an alternative to Docker and is widely used in the container ecosystem.

github.com/containers/libpod is a Go package that is a core component of Podman. It provides the functionality to interact with container runtimes and manage containers and pods.

The vulnerability allows external parties to access files or directories that should not be accessible. This can lead to unauthorized access, data leakage, or potential exploitation of sensitive information.

The vulnerability was introduced in version 1.6.0 of github.com/containers/libpod and was fixed in version 2.0.6 of github.com/containers/libpod/v2.

To fix the vulnerability, it is recommended to update the affected package to version 2.0.6 or later. It is important to ensure that all dependencies are also updated to their latest secure versions.

Related vulnerabilities

Recent vulnerabilities recorded for github.com/containers/libpod.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback