Bookmarks

    Nothing saved yet. Use the bookmark on any article. Bookmarks are kept on this device only: they stay private and work without an account.

    Settings

    Appearance

    Reading mode

    Font size

    Content width

    Line spacing

    Keyboard shortcuts

    /
    Search
    j k
    Next / previous story
    ← →
    Previous / next section (columns)
    b
    Bookmarks
    s
    Settings
    r
    Columns / scroll
    t
    Light / dark

    Saved in this browser only.

    Ping2Prompt
    Subscribe to the Weekly Brief Sign in
    Rows of blue shipping-container-style blocks bearing the white Kubernetes ship's-wheel logo, receding into the distance.
    Photo by Growtika on Unsplash

    AWS Private CA Connector for Kubernetes 1.12.0 fixes cross-namespace certificate issuance

    Automated source check

    Kubernetes

    Two authorization flaws fixed in aws-privateca-issuer 1.12.0

    aws-privateca-issuer 1.12.0 fixes two authorization flaws in the AWS Private CA Connector for Kubernetes, both in how credentials are handled for namespace-scoped issuers. Each scores 5.1 (CVSS 4.0, medium).

    Cross-namespace certificates through stored credentials

    CVE-2026-130622 affects the connector's credential loading logic. A user who can create namespace-scoped issuers might get certificates, including subordinate CA certificates, signed by another namespace's AWS Private CA. The attacker points an issuer at a credentials Secret in the other namespace, and the connector uses the AWS credentials stored there. The attack runs over the network and needs only low privileges: an authenticated user with permission to create such issuers.

    Issuers without credentials borrow the controller's identity

    CVE-2026-130623 covers issuers that supply no credentials, or set only a role. Those issuers fall back to the controller's own AWS identity. A user who can create namespace-scoped issuers might then obtain certificates, including subordinate CA certificates, from any private CA and certificate template that identity can reach, or that any role it can assume can reach.

    Versions before 1.12.0 are affected

    Both CVEs affect aws-privateca-issuer before 1.12.0. You are exposed if you run it and let users create namespace-scoped issuers. The exploitation status is unknown: the sources do not say whether either flaw is being exploited.

    Update to 1.12.0 after fixing issuers and secrets

    Update to aws-privateca-issuer 1.12.0, or to the EKS add-on v1.12.0-eksbuild.1 if you use the add-on. Adjust your configuration before you upgrade.

    • Secrets (CVE-2026-130622): copy any credentials Secret a namespace-scoped issuer is meant to use into that issuer's namespace, then set the issuer's secretRef.namespace to match.
    • Controller identity (CVE-2026-130623): update any namespace-scoped issuer that relies on the controller's identity so it uses its own credentials.

    The sources give no disclosure or patch dates.

    Product Affected Fixed
    aws-privateca-issuer (AWS Private CA Connector for Kubernetes) before 1.12.0 1.12.0 (EKS add-on v1.12.0-eksbuild.1)

    Sources

    Image: Photo by Growtika on Unsplash


    This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].

    Continue

    Share on Bluesky · Mastodon · Email ·

    Discussion