IPAM controller service account granted unnecessary full access to Secrets

### 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: ```yaml # 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)

Source published

29 May 2026 18:24:45 UTC

Source modified

25 Jun 2026 18:56:38 UTC

Observed here

24 Oct 2026 13:19:41 UTC

Source terms

GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · GitHub Advisory Database · CC-BY-4.0. Source text is retained; field grouping and change labels are provided by ChangeIntel.

CVSS_V3 · CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N

Publisher rating · MODERATE