Skip to content
Fencer Intel
medium 4.3

GHSA-hfc8-w5f4-3x6m json

Ironic Standalone Operator's controller modifies user-owned resources without consent

published 5mo ago modified 4mo ago also GO-2026-5425

cvss
4.3
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

## Impact

The Ironic Standalone Operator (IRSO) is the operator to maintain an Ironic deployment for Metal3. IRSO controller automatically adds its environment label to user-provided Secrets and ConfigMaps without the resource owner's consent. A high-privilege controller modifying user-owned resources constitutes an unauthorized integrity violation. Deployments running IrSO v0.7.0 through v0.8.1 that reference user-provided Secrets or ConfigMaps (TLS certificates, BMC CA, trusted CA) are affected.

## Patches

Fixed in v0.9.0, v0.8.2, v0.7.3.

## Workarounds

Manually add the environment label (ironic-standalone-operator.metal3.io/environment) to all user-provided Secrets and ConfigMaps before they are referenced in the Ironic resource. This prevents the controller from modifying them.

## Resources

- https://github.com/metal3-io/ironic-standalone-operator/pull/619 - https://github.com/metal3-io/ironic-standalone-operator/pull/664 - https://github.com/metal3-io/ironic-standalone-operator/pull/665

Patch / fix

  • go github.com/metal3-io/ironic-standalone-operator 0.7.3, 0.8.2

Is GHSA-hfc8-w5f4-3x6m in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
GitHub 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
go github.com/metal3-io/ironic-standalone-operator
<0.7.3
>=0.8.0, <0.8.2
0.7.3
0.8.2

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.