All reports
Medium

IPAM controller service account granted unnecessary full access to Secrets

Affected versions

Version ranges need review.

Affected versions
>= 1.12.0, <= 1.12.3
Fixed version
1.12.4
Affected versions
<= 1.11.6
Fixed version
1.11.7
Affected versions
<1.11.7 || >=1.12.0 <1.12.4
Fixed version
1.11.7 · 1.12.4
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-47190

Probability of exploitation in the next 30 days: 0.33%

FIRST EPSS · 2026-11-19

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

Links