CVE-2026-47190: metal3-io ip-address-manager · Execution with Unnecessary Privileges
Affects metal3-io ip-address-managerSource CVE Database V5
Not known to be exploited · CVSS 4.4 Medium · fixed in 1.13.0 : update metal3-io ip-address-manager when convenient.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.13.0, 1.12.4, 1.11.7
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade ip-address-manager and metal3-io/ip-address-manager to 1.13.0, 1.12.4 or 1.11.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| metal3-ioip-address-manager | Affected
| Fixed in
|
| metal3-ioip-address-manager | Affected
| Fixed in
|
| metal3-ioip-address-manager | Affected
| Fixed in
|
GitHubmetal3-io/ip-address-managerpkg:github/metal3-io/ip-address-managerOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability has been patched in metal3-io ip-address-manager versions 1.11.7, 1.12.4, and 1.13.0. Users should upgrade to one of these versions or later to eliminate the excessive permissions. No other mitigation guidance is provided or required.
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.
References
- github.com/metal3-io/ip-address-manager/security/advisories/GHSA-49pm-43hf-6xfq (opens in a new tab)
- github.com/metal3-io/ip-address-manager/pull/1355 (opens in a new tab)
- github.com/metal3-io/ip-address-manager/pull/1356 (opens in a new tab)
- github.com/metal3-io/ip-address-manager/pull/1357 (opens in a new tab)