How severe is CVE-2024-7387?

CVE-2024-7387 has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2024-7387?

CVE-2024-7387 affects the following packages: github.com/openshift/builder (Go). Ecosystems affected: Go.

How do I fix CVE-2024-7387?

The records we use list no patched version of github.com/openshift/builder for CVE-2024-7387. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2024-7387 in my Go dependencies?

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

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

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2024-7387 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-7387 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-2024-7387?

CVE-2024-7387 has an EPSS (Exploit Prediction Scoring System) score of 2.3%, placing it in the 84th 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-2024-7387?

CVE-2024-7387 is classified as CWE-250 (CWE-250). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-7387 published, and has it been updated?

CVE-2024-7387 was published on September 16, 2024 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

CRITICAL severity

CVE-2024-7387 — builder

CRITICALFix: openshift/builder@0b62633

CVE-2024-7387 is a critical-severity (CVSS 9.1) CWE-250 vulnerability in github.com/openshift/builder. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Openshift/builder: path traversal allows command injection in privileged buildcontainer using docker build strategy

Also known asGHSA-qqv8-ph7f-h3f7GO-2024-3129

Published

Sep 16, 2024

Updated

Oct 28, 2026

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-7387.

EPSS Exploitation Probability

via FIRST.org ↗

2.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐹github.com/openshift/builder

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

A flaw was found in openshift/builder. This vulnerability allows command injection via path traversal, where a malicious user can execute arbitrary commands on the OpenShift node running the builder container. When using the “Docker” strategy, executable files inside the privileged build container can be overridden using the spec.source.secrets.secret.destinationDir attribute of the BuildConfig definition. An attacker running code in a privileged container could escalate their permissions on the node running the container.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/openshift/builder`	all versions	No fix

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/openshift/builder, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of github.com/openshift/builder for CVE-2024-7387. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

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 HatImportant

In all versions of OpenShift, the "Custom" build strategy gives developers permission to run arbitrary commands in a privileged container. This is disabled by default, and documentation explicitly warns that this should only be enabled for highly trusted users (eg: cluster admins). We therefore do not consider this…

Workaround published by Red Hat

Cluster admins can follow the instructions in "Securing Builds by Strategy" to block use of the "Docker" build strategy on a cluster, or restrict the use to a set of highly trusted users, until the cluster is able to be upgraded. https://docs.openshift.com/container-platform/4.16/cicd/builds/securing-builds-by-strategy.html

Source: Red Hat security advisory for CVE-2024-7387 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat OpenShift Container Platform 4.12	`openshift4/ose-docker-builder:v4.12.0-202409121032.p1.g609473f.assembly.stream.el8`	RHSA-2024:6705
Red Hat OpenShift Container Platform 4.13	`openshift4/ose-docker-builder:v4.13.0-202409120505.p1.g2c7e99d.assembly.stream.el8`	RHSA-2024:6691
Red Hat OpenShift Container Platform 4.14	`openshift4/ose-docker-builder:v4.14.0-202409111409.p1.g52565ca.assembly.stream.el8`	RHSA-2024:6689
Red Hat OpenShift Container Platform 4.15	`openshift4/ose-docker-builder:v4.15.0-202409101936.p1.ge7749a3.assembly.stream.el8`	RHSA-2024:6685
Red Hat OpenShift Container Platform 4.16	`openshift4/ose-docker-builder-rhel9:v4.16.0-202409101737.p1.gfee4b58.assembly.stream.el9`	RHSA-2024:6687
Red Hat OpenShift Container Platform 4.17	`openshift4/ose-docker-builder-rhel9:v4.17.0-202409122005.p1.gcfcf3bd.assembly.stream.el9`	RHSA-2024:3718
Red Hat OpenShift Container Platform 4.18	`openshift4/aws-kms-encryption-provider-rhel9:v4.18.0-202501230001.p0.g088dcaf.assembly.stream.el9`	RHSA-2024:6122

Frequently Asked Questions

A flaw was found in openshift/builder. This vulnerability allows command injection via path traversal, where a malicious user can execute arbitrary commands on the OpenShift node running the builder container. When using the “Docker” strategy, executable files inside the privileged build container can be overridden using the `spec.source.secrets.secret.destinationDir` attribute of the `BuildConfig` definition. An attacker running code in a privileged container could escalate their permissions on the node running the container.

O3 Security · Impact-Aware SCA

Is CVE-2024-7387 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works