CVE-2026-82976
Description
A flaw was found in the image-customization-controller used in OpenShift's bare metal provisioning stack. The controller registers an HTTP file server on port 8084 with no authentication. The custom imageFileSystem implementation exposes a browsable HTML directory listing of all registered images at the root path. The only access control on per-host images is the random UUID filename; the directory listing discloses those UUIDs to any caller on the provisioning network. Each served image embeds an Ignition config containing the base64-encoded cluster pull secret, optional IRONIC_RAMDISK_SSH_KEY, proxy settings, and per-host NetworkManager keyfiles. An adjacent network attacker can enumerate all image UUIDs via directory listing, download any image, extract the embedded Ignition config, and recover the cluster pull secret and SSH key.
Evidence
pkg/imagehandler/imagefilesystem.go — root directory is browsable and enumerates all UUID image names
func (f *imageFileSystem) Readdir(n int) ([]fs.FileInfo, error) {
f.mu.Lock()
defer f.mu.Unlock()
result := []fs.FileInfo{}
for _, im := range f.images {
result = append(result, im)
}
return result, nil
}
func (f *imageFileSystem) Open(name string) (http.File, error) {
f.log.Info("Open", "path", name)
if name == "/" {
return f, nil
}
...
cmd/controller/main.go — file server bound on all interfaces without auth or TLS
http.Handle("/", http.FileServer(imageServer.FileSystem()))
go func() {
server := &http.Server{
Addr: imagesBindAddr, // default ":8084"
ReadHeaderTimeout: 5 * time.Second,
}
err := server.ListenAndServe()
pkg/ignition/service_config.go:94-100 — pull secret is embedded in every served image
func (b *ignitionBuilder) authFile() ignition_config_types_32.File {
source := "data:;base64," + strings.TrimSpace(b.ironicAgentPullSecret)
return ignition_config_types_32.File{
Node: ignition_config_types_32.Node{Path: "/etc/authfile.json"},
...
Attack Pattern
Adjacent provisioning-network client → GET / lists UUID image names → download ISO/initramfs → extract embedded Ignition → recover cluster pull secret and SSH key.
Statement
The image-customization-controller is deployed in the openshift-machine-api namespace as part of OpenShift's bare metal IPI provisioning flow. The image server binds on all interfaces at port 8084 with no authentication or TLS. The directory listing is unconditional — any client on the provisioning network can browse and download all served images. The embedded Ignition configs contain the cluster pull secret (registry credentials), optional SSH keys for the IPA ramdisk, proxy settings, and per-host NetworkManager keyfiles. Red Hat rates this as Important because exploitation requires adjacent network access (provisioning network) with no authentication, and the scope of exposed secrets is high — the pull secret grants access to container registries outside the cluster boundary.
Mitigation
There is no way to disable the directory listing or add authentication without a code change. As a workaround, administrators can apply network-level controls to restrict access to port 8084 on the image-customization-controller pod to only the BMC/provisioning network hosts that require it. Use NetworkPolicy or firewall rules to block access from workload pods. Additionally, rotate any pull secrets and SSH keys that may have been exposed if unauthorized access to the provisioning network is suspected.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.1 | N/A | 7.1 |
| Attack Vector | Adjacent Network | N/A | Adjacent Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | Low | N/A | Low |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
cve.org: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Red Hat CVSS v3 Score Explanation
Reconciled from source finding FIND-001 (migration 2026-09-01)
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Files or Directories
Exposing the contents of a directory can lead to an attacker gaining access to source code or providing useful information for the attacker to devise exploits, such as creation times of files or any information that may be encoded in file names. The directory listing may also compromise private or confidential data.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.