Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-15789: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in moby BuildKit

0
Medium
VulnerabilityCVE-2026-15789cvecve-2026-15789cwe-22
Published: 07/21/2026 (07/21/2026, 16:10:20 UTC)
Source: CVE Database V5
Vendor/Project: moby
Product: BuildKit

Description

A custom client can produce such an upload request to the BuildKit daemon that files can escape from the BuildKit-controlled state directory. The client needs to have valid permissions to access the BuildKit control API to issue builds, e.g., bypass authentication, etc.

CVSS v4.0

Score 6.9medium

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vuln. Confidentiality
None
Vuln. Integrity
High
Vuln. Availability
High
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/21/2026, 16:57:53 UTC

Technical Analysis

This vulnerability (CWE-22) in moby BuildKit involves improper limitation of a pathname to a restricted directory, allowing a client with valid permissions on the BuildKit control API to upload files that escape the intended BuildKit state directory. The issue arises from insufficient validation of upload request paths, enabling path traversal attacks. Exploitation requires the attacker to have legitimate access to the BuildKit API, such as through bypassing authentication or possessing appropriate privileges. No official remediation or patch information is currently available, and no known exploits in the wild have been reported.

Potential Impact

An attacker with limited privileges to the BuildKit control API can leverage this vulnerability to write files outside the designated BuildKit state directory. This could lead to unauthorized file creation or modification on the host system, potentially impacting system integrity or enabling further attacks depending on the environment and file locations affected.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to the BuildKit control API to trusted users only and monitor for unauthorized API usage. Avoid exposing BuildKit APIs to untrusted networks or users.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Docker
Date Reserved
2026-07-14T19:27:01.532Z
Cvss Version
4.0
State
PUBLISHED
Remediation Level
null

Threat ID: 6a5fa1722a4a8d59896d3414

Added to database: 07/21/2026, 16:42:26 UTC

Last enriched: 07/21/2026, 16:57:53 UTC

Last updated: 07/21/2026, 20:43:27 UTC

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses