Vulnerability
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)
No CVSS base score from NVD or GHSA yet. NVD typically scores within 24–72 hours of publication; GHSA usually within a day for OSS-flagged CVEs. Last record update .
For interim severity, fall back on KEV / EXPLOIT signals and the EPSS percentile (lower panel). Re-check this CVE after one cron tick — the score lands automatically when the source publishes.
Low exploitation likelihood — defer if no other signals fire.
No VEX statements published for CVE-2026-47190. Vendors publish VEX (Vulnerability Exploitability eXchange) to assert per-product whether a CVE is actually exploitable in their distribution.
No exploitation, limited impact or prevalence