Vulnerability Database · Rocky Linux · Package report

buildah: vulnerability history, versions and safety

buildah is a package in the Rocky Linux ecosystem. Vulert records 21 vulnerabilities for it across 14 affected ranges, from Apr 2020 to Nov 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
21 vulnerabilities recorded U21
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 28 Nov 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on buildah i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 28 Nov 2025. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 21 vulnerabilities on record across 5 years, 1 in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 21 over 5 years · 1 in the last year i
  • Latest disclosure 28 Nov 2025 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
up to 1:1.24.7-1.module+el8.9.0+1797+b9a484c9 (exclusive) 1
up to 1:1.24.6-7.module+el8.9.0+1445+07728297 (exclusive) 4
up to 1:1.24.5-2.module+el8.7.0+1077+0e4f03d4 (exclusive) 1
up to 1:1.24.2-4.module+el8.6.0+785+d1251653 (exclusive) 1
up to 0:1.22.3-2.module+el8.5.0+710+4c471e88 (exclusive) 1
up to 0:1.19.9-6.module+el8.7.0+1076+9b1c11c1 (exclusive) 1
up to 0:1.19.9-3.module+el8.6.0+783+10209741 (exclusive) 2
up to 0:1.19.9-1.module+el8.5.0+709+440d5e7e (exclusive) 1
up to 0:1.19.7-2.module+el8.4.0+556+40122d08 (exclusive) 1
up to 0:1.19.7-1.module+el8.4.0+558+7340b765 (exclusive) 2
up to 0:1.11.6-10.module+el8.5.0+770+e2f49861 (exclusive) 1
up to 0:1.11.6-9.module+el8.5.0+708+6758137d (exclusive) 1
up to 0:1.11.6-8.module+el8.4.0+559+c02fa3b2 (exclusive) 3
up to 0:1.5-8.gite94b4f9.module+el8.5.0+681+c9a1951f (exclusive) 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2021 9
  • 2022 6
  • 2023 1
  • 2024 1
  • 2025 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 21 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for buildah

The 5 most severe of 21 vulnerabilities recorded for this package

Search all 21 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Security Vulnerability in Container Tools: Moderate Update Required 9.8 critical 1:1.24.6-7.module+el8.9.0+1445+07728297 28 Nov 2025
Important: container-tools:rhel8 security update 8.8 high 0:1.11.6-8.module+el8.4.0+559+c02fa3b2 28 Apr 2020
Critical Security Flaw in Container Tools: runc File Descriptor Leak and DoS Vulnerabilities 8.6 high 1:1.24.6-7.module+el8.9.0+1445+07728297 07 May 2025
Important: container-tools:rhel8 security, bug fix, and enhancement update 8.0 high 1:1.24.2-4.module+el8.6.0+785+d1251653 10 May 2022
Important: container-tools:3.0 security update 8.0 high 0:1.19.9-3.module+el8.6.0+783+10209741 10 May 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 →

Questions

About buildah

Is buildah safe to use?

Vulert records 21 vulnerabilities for buildah in Rocky Linux: 0 critical, 0 high, 0 medium and 0 low, plus 21 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does buildah have?

21 vulnerabilities are recorded for buildah in the Rocky Linux ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 21 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new buildah vulnerabilities disclosed?

1 vulnerability was recorded for buildah in the last 12 months, and the oldest entry in this database dates to 28 Apr 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of buildah are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor buildah for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the buildah version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.