CVE-2026-7309: Openshift-controller-manager: openshift container platform: information disclosure via environment variable injection

Published Apr 28, 2026
·
Updated

A flaw was found in the OpenShift Container Platform build system. A user with the edit ClusterRole can inject arbitrary environment variables, such as LDPRELOAD or httpproxy, into docker-build containers through the buildconfigs/instantiate API. This incomplete fix for a previous vulnerability allows for information disclosure, specifically impacting the confidentiality of build traffic.

Other sources

An incomplete fix for CVE-2024-45496 was identified in the OpenShift Container Platform build system. The buildconfigs/instantiate API still accepts arbitrary environment variable names (including LDPRELOAD, PATH, BUILDAHRUNTIME, DOCKERCONFIG, httpproxy, httpsproxy) that propagate to the docker-build container, which remains privileged: true.

A user with the stock edit ClusterRole can inject these env vars into any BuildConfig in the namespace. The env var name validation only applies a format regex with no semantic deny-list for dangerous names.

In stock OpenShift, the edit role already grants Secret read access, making proxy interception largely redundant. The practical impact is limited to unsupported minimal role configurations.

Affected: openshift/api build/v1/consts.go Tested on: OCP 4.21.0 CVE-2024-45496 fix applied but env injection into docker-build remains.

Red Hat

Affected Software

2 affected components
Red Hat OpenShift Container Platform=4.21.0
redhat OpenShift Container Platform=4.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    Restrict access to the buildconfigs/instantiate API (used by BuildConfig instantiate) so that only highly trusted users can call it; users with the `edit` ClusterRole can inject arbitrary environment variables (e.g., `LD_PRELOAD`, `http_proxy`) into `docker-build` containers.

Event History

Apr 28, 2026
Data Sourced
via Red Hat·12:14 PM
DescriptionSeverityAffected Software
CVE Published
via MITRE·12:33 PM
Data Sourced
via MITRE·12:33 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:19 PM
DescriptionSeverityWeaknessAffected Software
Sep 20, 58317
Event
via FIRST·05:53 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-7309?

CVE-2026-7309 is classified as a medium severity vulnerability.

2

How do I fix CVE-2026-7309?

To mitigate CVE-2026-7309, limit the ClusterRole permissions for users and avoid granting the 'edit' ClusterRole unnecessarily.

3

What type of vulnerability is CVE-2026-7309?

CVE-2026-7309 is an information disclosure vulnerability due to environment variable injection.

4

Who is affected by CVE-2026-7309?

Users with the 'edit' ClusterRole in the OpenShift Container Platform are affected by CVE-2026-7309.

5

What are the potential impacts of CVE-2026-7309?

CVE-2026-7309 can allow an attacker to inject arbitrary environment variables, potentially leading to unauthorized access or data exposure.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203