# GHSA-hfc8-w5f4-3x6m: Ironic Standalone Operator's controller modifies user-owned resources without consent

> The Ironic Standalone Operator controller modifies user-owned Secrets and ConfigMaps without consent, violating resource integrity.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 May 2026
- **Also known as:** GO-2026-5425

## What is GHSA-hfc8-w5f4-3x6m?

GHSA-hfc8-w5f4-3x6m is a missing authorization vulnerability in github.com/metal3-io/ironic-standalone-operator, published on 29 May 2026. 

### Official description

## 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

## Which versions are affected by GHSA-hfc8-w5f4-3x6m?

5 open source packages ship an affected version, including github.com/metal3-io/ironic-standalone-operator.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/metal3-io/ironic-standalone-operator` | Go | All versions | 0.7.3, 0.8.2 |
| `github.com/metal3-io/ironic-standalone-operator` | Go | All versions | 0.7.3 |
| `github.com/metal3-io/ironic-standalone-operator` | Go | All versions | 0.7.3 |
| `github.com/metal3-io/ironic-standalone-operator` | Go | From 0.8.0 | 0.8.2 |
| `github.com/metal3-io/ironic-standalone-operator` | Go | From 0.8.0 | 0.8.2 |

## How do I fix GHSA-hfc8-w5f4-3x6m?

Upgrade github.com/metal3-io/ironic-standalone-operator to a fixed version for your release line: 0.7.3 or 0.8.2.

## Is GHSA-hfc8-w5f4-3x6m being exploited?

There is no known exploitation of GHSA-hfc8-w5f4-3x6m in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-hfc8-w5f4-3x6m and fix it if it is affected.

What it is: GHSA-hfc8-w5f4-3x6m is a missing authorization vulnerability in github.com/metal3-io/ironic-standalone-operator, published on 29 May 2026. 
Exploitation: There is no known exploitation of GHSA-hfc8-w5f4-3x6m in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/metal3-io/ironic-standalone-operator (Go): affected all versions; fixed in 0.7.3, 0.8.2
- github.com/metal3-io/ironic-standalone-operator (Go): affected all versions; fixed in 0.7.3
- github.com/metal3-io/ironic-standalone-operator (Go): affected all versions; fixed in 0.7.3
- github.com/metal3-io/ironic-standalone-operator (Go): affected from 0.8.0; fixed in 0.8.2
- github.com/metal3-io/ironic-standalone-operator (Go): affected from 0.8.0; fixed in 0.8.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-hfc8-w5f4-3x6m/ (Markdown: https://insights.sbomify.com/GHSA-hfc8-w5f4-3x6m/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-hfc8-w5f4-3x6m

---
From sbomify Insights: https://insights.sbomify.com/GHSA-hfc8-w5f4-3x6m/
Summaries are generated and may contain mistakes; the official description above is the record.