CVE-2022-4123: A flaw was found in Buildah

Routine

LOW 3.3DOWNGRADEMITIGATE

CVE-2022-4123 is a low-severity flaw (CVSS 3.3) affecting podman, fedora. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A flaw was found in Buildah. The local path and the lowest subdirectory may be disclosed due to incorrect absolute path traversal, resulting in an impact to confidentiality.

Why this priority

No elevated risk signals yet

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

Risk facts

CVSS score	3.3 (Low)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.2% (top 84%)
CISA exploited list	No
Weakness	CWE-23, CWE-22
Published	2022-12-08
Last modified	2026-06-17

Publisher (CNA): Red Hat, Inc. · Vendor: fedoraproject · podman project

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

Am I affected?

Timeline

2022-12-08 16:15 UTCPublished CVE record published
2026-06-17 05:20 UTCUpdated Record last modified

podman project podman DOWNGRADE

Affected: 4.1.0 · 4.1.0 rc1 · 4.1.0 rc2 · 4.1.1 · 4.2.0 · 4.2.0 rc1 · 4.2.0 rc2 · 4.2.0 rc3

Fixed in: no fixed release known

Safe to downgrade to: a release before 4.1.0

1. Check installed version

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

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

apt-cache madison podman sudo apt install podman=<VERSION_BEFORE_4.1.0> sudo apt-mark hold podman

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

dnf --showduplicates list podman sudo dnf downgrade podman-<VERSION_BEFORE_4.1.0> sudo dnf versionlock add podman

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.

fedoraproject fedora MITIGATE

Affected: 35 · 36 · 37

Fixed in: no fixed release known

Safe to downgrade to: a release before 35

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-2022-4123?

podman: downgrade or apply the listed mitigation; fedora: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-4123 being exploited?

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

CVE-2022-4123 affects podman, fedora. Severity is low (CVSS 3.3). A flaw was found in Buildah. The local path and the lowest subdirectory may be disclosed due to incorrect absolute path traversal, resulting in an impact to confidentiality.

How urgent is CVE-2022-4123?

Priority 15/100. No elevated risk signals yet.

Software pages

Podman vulnerabilities

Related CVEs

CVE-2024-3056 HIGH 7.7 UPGRADE DOWNGRADE A flaw was found in Podman
CVE-2026-57231 HIGH 7.5 UPGRADE Podman is a tool for managing OCI containers and pods
CVE-2026-55686 MEDIUM 5.3 UPGRADE Podman is a tool for managing OCI containers and pods
CVE-2026-33414 HIGH 7.8 UPGRADE Podman is a tool for managing OCI containers and pods
CVE-2023-0778 MEDIUM 6.8 MITIGATE MITIGATE A Time-of-check Time-of-use (TOCTOU) flaw was found in podman

References

← Back to latest CVEs