# CVE-2026-47190: IPAM controller service account granted unnecessary full access to Secrets

> The IPAM controller service account had excessive permissions to read and modify Secrets, allowing attackers to expose sensitive data if the pod is compromised.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Jun 2026
- **Updated:** 13 Jun 2026
- **Also known as:** GHSA-49pm-43hf-6xfq, GO-2026-5117

## What is CVE-2026-47190?

CVE-2026-47190 is a medium-severity missing authorization vulnerability in metal3-io ip-address-manager, published on 12 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

IPAM is the IP address Manager for Cluster API Provider Metal3. Prior to versions 1.11.7, 1.12.4, and 1.13.0, the IPAM controller's ClusterRole granted full CRUD permissions (create, delete, get, list, patch, update, watch) on core/v1 Secrets. The controller never accesses Secrets during normal operation. If the controller pod were compromised (e.g. via supply chain attack or container escape), an attacker could leverage these excessive permissions to read, modify, or delete Secrets in the namespace, potentially exposing credentials and other sensitive data. This issue has been patched in versions 1.11.7, 1.12.4, and 1.13.0.

Weakness: CWE-250 (Execution with Unnecessary Privileges)

## Which versions are affected by CVE-2026-47190?

5 open source packages ship an affected version, including github.com/metal3-io/ip-address-manager. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/metal3-io/ip-address-manager` | Go | All versions | 1.11.7, 1.12.4 |
| `github.com/metal3-io/ip-address-manager` | Go | All versions | 1.11.7 |
| `github.com/metal3-io/ip-address-manager` | Go | All versions | 1.11.7 |
| `github.com/metal3-io/ip-address-manager` | Go | From 1.12.0 | 1.12.4 |
| `github.com/metal3-io/ip-address-manager` | Go | From 1.12.0 | 1.12.4 |

Products: Metal3 Ip-Address-Manager.

## How do I fix CVE-2026-47190?

Upgrade github.com/metal3-io/ip-address-manager to a fixed version for your release line: 1.11.7 or 1.12.4.

## Is CVE-2026-47190 being exploited?

There is no known exploitation of CVE-2026-47190 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47190 and fix it if it is affected.

What it is: CVE-2026-47190 is a medium-severity missing authorization vulnerability in metal3-io ip-address-manager, published on 12 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47190 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/metal3-io/ip-address-manager (Go): affected all versions; fixed in 1.11.7, 1.12.4
- github.com/metal3-io/ip-address-manager (Go): affected all versions; fixed in 1.11.7
- github.com/metal3-io/ip-address-manager (Go): affected all versions; fixed in 1.11.7
- github.com/metal3-io/ip-address-manager (Go): affected from 1.12.0; fixed in 1.12.4
- github.com/metal3-io/ip-address-manager (Go): affected from 1.12.0; fixed in 1.12.4

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/CVE-2026-47190/ (Markdown: https://insights.sbomify.com/CVE-2026-47190/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47190
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47190
- OSV: https://osv.dev/vulnerability/CVE-2026-47190

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47190/
Summaries are generated and may contain mistakes; the official description above is the record.