Skip to content

← Public intelligence

Go package

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

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 4.4GoPublished

    IPAM controller service account granted unnecessary full access to Secrets

    CVE-2026-47190 · GHSA-49pm-43hf-6xfq

    Affected
    • Go github.com/metal3-io/ip-address-manager <= 1.11.6; >= 1.12.0, <= 1.12.3
    Fixed in
    1.12.41.11.7· Vendor fix available
    Issue
    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: Resources - https://github.com/metal3-io/ip-address-manager/pull/1355 - https://github.com/metal3-io/ip-address-manager/pull/1356 (backport to…

    Recommended action: Upgrade to 1.12.4 or 1.11.7 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →