Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2022-1227: A privilege escalation flaw was found in Podman

64
This week
HIGH 8.8WATCHLISTUPGRADEUPGRADEDOWNGRADE

CVE-2022-1227 is a high-severity flaw (CVSS 8.8) affecting podman, psgo, developer tools. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • High severity
  • EPSS top 9%: very likely to be exploited
  • Public exploit reference
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score8.8 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionRequired
EPSS exploit chance4.2% (top 9%)
CISA exploited listNo
WeaknessCWE-281, CWE-269
Published2022-04-29
Last modified2026-06-17
Publisher (CNA): Red Hat, Inc. · Vendor: podman project · psgo project · redhat

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

podman project podman UPGRADE
Affected: < 4.0.0
Fixed in: 4.0.0
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy podman || rpm -q podman || podman --version
2. UPGRADE to 4.0.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade podman
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade podman
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
psgo project psgo UPGRADE
Affected: < 1.7.2
Fixed in: 1.7.2
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy psgo || rpm -q psgo || psgo --version
2. UPGRADE to 1.7.2 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade psgo
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade psgo
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
redhat developer tools DOWNGRADE
Affected: 1.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.0
1. Check installed version
apt-cache policy developer-tools || rpm -q developer-tools || developer-tools --version
2. No fixed release: DOWNGRADE to a release before 1.0 (Debian / Ubuntu)
apt-cache madison developer-tools sudo apt install developer-tools=<VERSION_BEFORE_1.0> sudo apt-mark hold developer-tools
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list developer-tools sudo dnf downgrade developer-tools-<VERSION_BEFORE_1.0> sudo dnf versionlock add developer-tools
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 server update services for sap solutions DOWNGRADE
Affected: 8.6
Fixed in: no fixed release known
Safe to downgrade to: a release before 8.6
1. Check installed version
apt-cache policy enterprise-linux-server-update-services-for-sap-solutions || rpm -q enterprise-linux-server-update-services-for-sap-solutions || enterprise-linux-server-update-services-for-sap-solutions --version
2. No fixed release: DOWNGRADE to a release before 8.6 (Debian / Ubuntu)
apt-cache madison enterprise-linux-server-update-services-for-sap-solutions sudo apt install enterprise-linux-server-update-services-for-sap-solutions=<VERSION_BEFORE_8.6> sudo apt-mark hold enterprise-linux-server-update-services-for-sap-solutions
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list enterprise-linux-server-update-services-for-sap-solutions sudo dnf downgrade enterprise-linux-server-update-services-for-sap-solutions-<VERSION_BEFORE_8.6> sudo dnf versionlock add enterprise-linux-server-update-services-for-sap-solutions
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.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 4.0
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.0 (Debian / Ubuntu)
apt-cache madison openshift-container-platform sudo apt install openshift-container-platform=<VERSION_BEFORE_4.0> 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.0> 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 quay DOWNGRADE
Affected: 3.0.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 3.0.0
1. Check installed version
apt-cache policy quay || rpm -q quay || quay --version
2. No fixed release: DOWNGRADE to a release before 3.0.0 (Debian / Ubuntu)
apt-cache madison quay sudo apt install quay=<VERSION_BEFORE_3.0.0> sudo apt-mark hold quay
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list quay sudo dnf downgrade quay-<VERSION_BEFORE_3.0.0> sudo dnf versionlock add quay
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.
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-2022-1227?

podman: upgrade to 4.0.0; psgo: upgrade to 1.7.2; developer tools: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-1227 being exploited?

CVE-2022-1227 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-2022-1227 affect?

CVE-2022-1227 affects podman, psgo, developer tools. Severity is high (CVSS 8.8). 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 'podm

How urgent is CVE-2022-1227?

Priority 64/100. High severity; EPSS top 9%: very likely to be exploited; Public exploit reference; On your watchlist

Software pages

SAP vulnerabilities · Red Hat OpenShift vulnerabilities · Podman vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.