How severe is CVE-2026-33748?

No CVSS score has been assigned to CVE-2026-33748 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-33748?

CVE-2026-33748 affects the following packages: github.com/moby/buildkit (Go). Ecosystems affected: Go.

How do I fix CVE-2026-33748?

Update github.com/moby/buildkit to 0.28.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-33748 is resolved across your whole dependency graph.

How do I detect CVE-2026-33748 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/moby/buildkit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-33748 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2026-33748 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-33748 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-33748?

CVE-2026-33748 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 42th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-33748?

CVE-2026-33748 is classified as Path Traversal (CWE-22), CWE-59 (CWE-59). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-33748 published, and has it been updated?

CVE-2026-33748 was published on March 27, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2026-33748 — buildkit

CVE-2026-33748 is a Path Traversal vulnerability in github.com/moby/buildkit. A fix is available for github.com/moby/buildkit — see the affected versions and patch details below.

BuildKit Git URL subdir component can cause access to restricted files

Also known asGHSA-4vrq-3vrq-g6ggGO-2026-4859

Published

Mar 27, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-33748.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs42th percentile — riskier than 42% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/moby/buildkit

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. Prior to version 0.28.1, insufficient validation of Git URL fragment subdir components may allow access to files outside the checked-out Git repository root. Possible access is limited to files on the same mounted filesystem. The issue has been fixed in version v0.28.1 The issue affects only builds that use Git URLs with a subpath component. As a workaround, avoid building Dockerfiles from untrusted sources or using the subdir component from an untrusted Git repository where the subdir component could point to a symlink.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/moby/buildkit`	all versions	0.28.1`go get github.com/moby/buildkit@v0.28.1`

Affected Products

1 product · 1 configurations

Application

buildkitmobyproject

< 0.28.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/moby/buildkit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/moby/buildkit to 0.28.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-33748 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for CVE-2026-33748 (CC BY 4.0)

Product	Fixed in	Advisory
multicluster engine for Kubernetes 2.10	`multicluster-engine/must-gather-rhel9:1784849867`	RHSA-2026:46885
multicluster engine for Kubernetes 2.10	`multicluster-engine/must-gather-rhel9:1784849867`	RHSA-2026:47388
multicluster engine for Kubernetes 2.8	`multicluster-engine/must-gather-rhel9:1782158798`	RHSA-2026:30650
OpenShift API for Data Protection 1.3	`oadp/oadp-mustgather-rhel9:1785177359`	RHSA-2026:51033
OpenShift API for Data Protection 1.4	`oadp/oadp-mustgather-rhel9:1779770049`	RHSA-2026:29854
OpenShift API for Data Protection 1.5	`oadp/oadp-mustgather-rhel9:1779770057`	RHSA-2026:26568
Red Hat Openshift Data Foundation 4.20	`odf4/cephcsi-rhel9:1786627460`	RHSA-2026:57013
Red Hat Openshift Data Foundation 4.22	`odf4/cephcsi-rhel9:1782932114`	RHSA-2026:37387