VulnerabilityPublished 3 Nov 2026

CVE-2026-82976: Red Hat OpenShift Container Platform 4 · Exposure of Information Through Directory Listing

Affects Red Hat OpenShift Container Platform 4Source CVE Database V5

Compare

Not known to be exploited · CVSS 7.1 High.

Data as of 3 Nov 2026, 18:59 UTC

CVSS 3.1 base score

7.1High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (redhat)	CVSS 3.1	7.1

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Red Hat OpenShift Container Platform 4openshift4/ose-image-customization-controller-rhel8	Affected–	Fixed in–
Red Hat OpenShift Container Platform 4openshift4/ose-image-customization-controller-rhel9	Affected–	Fixed in–
Red Hat OpenShift Container Platform 5openshift5/ose-image-customization-controller-rhel9	Affected–	Fixed in–

AI-suggested

There is currently no code-level fix or way to disable directory listing or add authentication without code changes. Administrators should apply network-level controls to restrict access to port 8084 on the image-customization-controller pod to only trusted BMC/provisioning network hosts. Use Kubernetes NetworkPolicy or firewall rules to block access from workload pods and untrusted clients. If unauthorized access to the provisioning network is suspected, rotate all cluster pull secrets and SSH keys embedded in the images. Monitor vendor advisories for any forthcoming official patches.

Description

CVE-2026-82976 is a vulnerability in the image-customization-controller of Red Hat OpenShift Container Platform 4's bare metal provisioning stack. The controller runs an unauthenticated HTTP file server on port 8084 that exposes a browsable directory listing of all registered image UUIDs. These images embed Ignition configs containing sensitive data such as the base64-encoded cluster pull secret, optional SSH keys, proxy settings, and network keyfiles. An attacker on the adjacent provisioning network can enumerate image UUIDs, download images, extract secrets, and gain access to container registries and SSH keys.

Impact

An attacker with access to the provisioning network can enumerate all image UUIDs via directory listing, download any image, and extract embedded Ignition configs containing the cluster pull secret and SSH keys. This exposure allows unauthorized access to container registries outside the cluster boundary and potential SSH access to provisioning hosts. The vulnerability compromises confidentiality of critical cluster secrets, but does not affect integrity or availability directly. Exploitation requires no privileges or user interaction but requires adjacent network access.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2026, 18:59 UTC

Technical details

References

Community reviews

Related threats