How severe is CVE-2026-47190?

CVE-2026-47190 has a CVSS score of 4.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2026-47190?

CVE-2026-47190 affects the following packages: github.com/metal3-io/ip-address-manager (Go), github.com/metal3-io/ip-address-manager (Go). Ecosystems affected: Go.

How do I fix CVE-2026-47190?

Update github.com/metal3-io/ip-address-manager to 1.11.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-47190 is resolved across your whole dependency graph.

How do I detect CVE-2026-47190 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/metal3-io/ip-address-manager, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-47190 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-47190 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-47190 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-47190?

CVE-2026-47190 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 35th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-47190?

CVE-2026-47190 is classified as CWE-250 (CWE-250). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-47190 published, and has it been updated?

CVE-2026-47190 was published on June 12, 2026 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

CVE-2026-47190 — ip-address-manager

MEDIUMFix: metal3-io/ip-address-manager#1355

CVE-2026-47190 is a medium-severity (CVSS 4.4) CWE-250 vulnerability in github.com/metal3-io/ip-address-manager. A fix is available for github.com/metal3-io/ip-address-manager — see the affected versions and patch details below.

IPAM controller service account granted unnecessary full access to Secrets

Also known asGHSA-49pm-43hf-6xfqGO-2026-5117

Published

Jun 12, 2026

Updated

Aug 12, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-47190.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs35th percentile — riskier than 35% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-47190 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected

🐹github.com/metal3-io/ip-address-manager🐹github.com/metal3-io/ip-address-manager

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

IPAM is the IP address Manager for Cluster API Provider Metal3. 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.

All users running ip-address-manager versions prior to the patched releases are affected.

Patches

Fixed in:

v1.11.7
v1.12.4
v1.13.0

Users should upgrade to the patched version for their release branch.

Workarounds

Manually remove the Secrets resource entry from the metal3-ipam-controller-manager-role ClusterRole:

# Remove this entire block from the ClusterRole
- apiGroups:
  - ""
  resources:
  - secrets
  verbs:
  - create
  - delete
  - get
  - list
  - patch
  - update
  - watch

Resources

https://github.com/metal3-io/ip-address-manager/pull/1355
https://github.com/metal3-io/ip-address-manager/pull/1356 (backport to release-1.12)
https://github.com/metal3-io/ip-address-manager/pull/1357 (backport to release-1.11)

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/metal3-io/ip-address-manager`	all versions	1.11.7`go get github.com/metal3-io/ip-address-manager@v1.11.7`
🐹Go	`github.com/metal3-io/ip-address-manager`	≥ 1.12.0&&< 1.12.4	1.12.4`go get github.com/metal3-io/ip-address-manager@v1.12.4`

Affected Products

1 product · 4 configurations

Application

ip-address-managermetal3

≥ 1.12.0 && < 1.12.4

1 version

1.13.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/metal3-io/ip-address-manager, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/metal3-io/ip-address-manager to 1.11.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-47190 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact IPAM is the IP address Manager for Cluster API Provider Metal3. 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. All users running ip-address-manager versions prior to the patched