Is this vulnerability remotely exploitable?

It can be, depending on how BuildKit is exposed. If an attacker can remotely supply or influence Git URLs or the repositories used for builds, they may trigger the issue over a network interface that starts builds on their behalf.

What level of access does an attacker need to exploit this?

The attacker typically must control or significantly influence either the Git repository content (including symlinks and directory structure) or the Git URL parameters (notably the subdir component) that BuildKit uses as build context.

What is the safest general fix pattern for developers and operators?

From an implementation perspective, ensure that after resolving any subdir path and following symlinks, the resulting canonical path is validated to remain within the repository checkout root. Operationally, isolate build contexts on dedicated mounts and avoid colocating sensitive files with untrusted build workspaces.

Severity:

HIGH RISK

(7.5)

Path Traversal via Git Subdir Symlink (CWE-22) in BuildKit Git Source Handling

CVE-2026-33748

Published:

Mar 27, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-74;CWE-89

HIGH RISK

HIGH

(7.3)

SQL Injection via Unsanitized ID Parameter (CWE-89) in Pharmacy Sales and Inventory System /ajax.php

Database Compromise and Data Integrity Loss

April 27, 2026

CWE-863

HIGH RISK

HIGH

(8.5)

Incorrect Authorization (CWE-863) in OpenClaw chat.send Session Management

Privilege Escalation and Unauthorized Session Control

April 27, 2026

Vulnerability Type

Category:

Path Traversal / Directory Traversal

CWE:

CWE-22;CWE-59

Impact:

Unauthorized File System Access / Information Disclosure

Severity:

HIGH RISK

(7.5)

CVSS Version:

3.1

Vulnerability Type

Category:

Path Traversal / Directory Traversal

CWE:

CWE-22;CWE-59

Impact:

Unauthorized File System Access / Information Disclosure

Severity:

HIGH RISK

(7.5)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Path Traversal via Git Subdir Symlink (CWE-22) in BuildKit Git Source Handling

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(7.3)

SQL Injection via Unsanitized ID Parameter (CWE-89) in Pharmacy Sales and Inventory System /ajax.php

HIGH RISK

HIGH

(8.5)

Incorrect Authorization (CWE-863) in OpenClaw chat.send Session Management

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare