cve.bz

CVE-2026-15792 mobyproject buildkit: Improper Input Validation

6.0 mediumEPSS 0.2%

Medium (6.0) in mobyproject buildkit. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
A malicious BuildKit client or frontend could craft a request that could lead to BuildKit daemon crashing with a panic.

Severity

CVSS 4.0

6.0 medium
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-07-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-20 Improper Input Validation
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-15792 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-15792?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-15792?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-15792 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
moby BuildKitbefore 0.31.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu26.04:LTS, 26.10, Pro:20.04:LTS and 2 moredocker.io, docker.io-appno fix listedUBUNTU-CVE-2026-15792
UbuntuPro:16.04:LTS, Pro:18.04:LTSdocker.iono fix listedUBUNTU-CVE-2026-15792
Red Hathummingbird:1buildah, buildah-tests2:1.44.0-3.2.hum1RHSA-2026:43122
Red Hathummingbird:1podman, podmansh, podman-tests and 3 more5:6.0.2-2.1.hum1RHSA-2026:44152
Red Hathummingbird:1trivy0:0.72.0-0.1.2.hum1RHSA-2026:46988

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu · Red Hat.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

BuildKit is used by several Red Hat products to build container images. This issue allows a malicious BuildKit frontend or client to cause the BuildKit build process to crash. Exploiting this issue requires the ability to supply a build definition (for example, a Dockerfile specifying a custom #syntax frontend) to a BuildKit-based build; it does not allow remote code execution or exposure of data. The issue is fixed upstream in BuildKit version 0.31.2. Red Hat Hardened Images (Buildah, Podman, and Trivy) has already shipped the fixed version. Other affected Red Hat products are being assessed and will ship the fixed version of BuildKit in upcoming releases.

Red Hat's mitigation

Avoid building container images using BuildKit frontends from untrusted sources. A BuildKit frontend is typically specified using a "# syntax" directive at the top of a Dockerfile, or with the "--frontend" option to the "buildctl build" command. Only use frontend images that come from a trusted source.

ProductPackageStateAdvisory
Logging Subsystem for Red Hat OpenShift 6.2openshift-logging/cluster-logging-rhel9-operator:1789050399Fixed 2026-09-16RHSA-2026:68349
Logging Subsystem for Red Hat OpenShift 6.6openshift-logging/cluster-logging-rhel9-operator:1788439505Fixed 2026-09-10RHSA-2026:66521
OpenShift API for Data Protection 1.5oadp/oadp-mustgather-rhel9:1788859896Fixed 2026-09-09RHSA-2026:66022
Red Hat Hardened Imagesbuildah-main-1.44.0-3.2.hum1Fixed 2026-07-22RHSA-2026:43122
Red Hat Hardened Imagespodman-main-6.0.2-2.1.hum1Fixed 2026-07-23RHSA-2026:44152
Red Hat Hardened Imagestrivy-main-0.72.0-0.1.2.hum1Fixed 2026-07-27RHSA-2026:46988
Red Hat OpenShift AI 3.4rhoai/odh-cli-rhel9:1791509689Fixed 2026-10-19RHSA-2026:84734
Red Hat OpenShift AI 3.4rhoai/odh-must-gather-rhel9:1791351741Fixed 2026-10-19RHSA-2026:84734
Red Hat OpenShift AI 3.4rhoai/odh-pipeline-runtime-datascience-cpu-py312-rhel9:1791829804Fixed 2026-10-19RHSA-2026:84734
Red Hat OpenShift AI 3.4rhoai/odh-pipeline-runtime-minimal-cpu-py312-rhel9:1791829069Fixed 2026-10-19RHSA-2026:84734
Assisted Installer for Red Hat OpenShift Container Platform 2assisted/agent-preinstall-image-builder-rhel9Not affected
Assisted Installer for Red Hat OpenShift Container Platform 2rhai/assisted-installer-controller-rhel9Affected
Compliance Operatorcompliance/openshift-compliance-must-gather-rhel8Affected
Confidential Compute Attestationbuild-of-trustee/trustee-must-gather-rhel9Not affected
Confidential Compute Attestationopenshift-sandboxed-containers/osc-must-gather-rhel9Not affected
Confidential Compute Attestationopenshift-sandboxed-containers/osc-podvm-builder-rhel9Not affected
Kernel Module Management Operator for Red Hat Openshiftkmm/kernel-module-management-must-gather-rhel9Affected
Logical Volume Manager Storagelvms4/lvms-must-gather-rhel8Not affected
Logical Volume Manager Storagelvms4/lvms-must-gather-rhel9Not affected
Migration Toolkit for Applications 8mta/mta-cli-rhel9Not affected
165 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-15792.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON