Podman vulnerabilitiesRanked by how likely they are to be used.
Podman is made by Podman Project. We track 14 published vulnerabilities in it, across 155 versions. None of them is on the list of flaws known to be exploited today. If you run Podman, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Podman vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Podman's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Podman flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 4.2%CVE-2022-1227High
A privilege escalation flaw was found in Podman.
- 2.6%CVE-2019-25067High
A vulnerability, which was classified as critical, was found in Podman and Varlink 1.5.1.
- 1.4%CVE-2022-27649High
A flaw was found in Podman, where containers were started incorrectly with non-empty default permissions.
- 1.4%CVE-2020-14370Medium
An information disclosure vulnerability was found in containers/podman in versions before 2.0.5.
- 1.1%CVE-2021-20199Medium
Rootless containers run with Podman, receive all traffic with a source IP address of 127.0.0.1 (including from remote hosts).
- 1.1%CVE-2021-4024Medium
A flaw was found in podman. The `podman machine` function (used to create and manage Podman virtual machine containing a Podman process) spawns a `gvproxy` process on the host system.
- 0.9%CVE-2022-2738High
The version of podman as released for Red Hat Enterprise Linux 7 Extras via RHSA-2022:2190 advisory included an incorrect version of podman missing the fix for CVE-2020-8945, which was previously fixed via RHSA-2020:2117.
- 0.9%CVE-2022-4122Medium
A vulnerability was found in buildah. Incorrect following of symlinks while reading .containerignore and .dockerignore results in information disclosure.
- 0.5%CVE-2024-3056High
A flaw was found in Podman. This issue may allow an attacker to create a specially crafted container that, when configured to share the same IPC with at least one other container, can create a large number of IPC...
- 0.5%CVE-2023-0778Medium
A Time-of-check Time-of-use (TOCTOU) flaw was found in podman.
Running Podman? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
A privilege escalation flaw was found in Podman. This flaw allows an attacker to publish a malicious image to a public registry. Once this image is downloaded by a potential victim, the vulnerability is triggered after a user runs the 'podman top' command. This action gives the attacker access to the host filesystem, leading to information disclosure or denial of service.
- Matched to
- Podman on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 14 published vulnerabilities listed under the name Podman, across 155 versions.
None of Podman's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Podman. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.