Ironic Standalone Operator's controller modifies user-owned resources without consent
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/metal3-io/ironic-standalone-operator 0.8.2, 0.7.3), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/metal3-io/ironic-standalone-operator
- Affected
- <= 0.7.2>= 0.8.0, <= 0.8.1
- Fixed in
- 0.7.3, 0.8.2
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-hfc8-w5f4-3x6m lists affected ranges: Go github.com/metal3-io/ironic-standalone-operator >=0 =0.8.0 <=0.8.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
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
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-hfc8-w5f4-3x6m
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-hfc8-w5f4-3x6m Advisory: Ironic Standalone Operator's controller modifies user-owned resources without consent IDs: GHSA-hfc8-w5f4-3x6m Record: https://patchnext.com/advisories/ghsa-hfc8-w5f4-3x6m (revision 1, source checked 26 Oct 2026, 15:23 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 4.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/metal3-io/ironic-standalone-operator 0.8.2, 0.7.3. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/metal3-io/ironic-standalone-operator: affected <= 0.7.2; >= 0.8.0, <= 0.8.1; fixed in 0.7.3, 0.8.2 ## Suggested inspection (read-only) - Go github.com/metal3-io/ironic-standalone-operator: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/metal3-io/ironic-standalone-operator. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-hfc8-w5f4-3x6m (GitHub-reviewed advisory GHSA-hfc8-w5f4-3x6m lists affected ranges: Go github.com/metal3-io/ironic-standalone-operator >=0 =0.8.0 <=0.8.1) Commands are suggestions: review each one before running it.
Loading voting…