Vulnerabilities in pkg:golang/github.com/bitnami-labs/sealed-secrets

PACKAGE
Advisory Identifier: GHSA-465p-v42x-3fmj
Advisory Summary

CVE-2026-22728 is a MODERATE (CVSS 4.9) rotate api allows scope widening vulnerability (CWE-284: Improper Access Control) affecting Sealed Secrets for Kubernetes libraries in the Go ecosystem. The issue involves rotate api allows scope widening from strict/namespace-wide to cluster-wide via untrusted template annotations. Remediation is available by upgrading affected packages to version 0.36.0.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:golang/github.com/bitnami-labs/sealed-secrets

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:golang/github.com/bitnami-labs/sealed-secrets. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-465p-v42x-3fmj CVE-2026-22728 MODERATE Sealed Secrets for Kubernetes: Rotate API Allows Scope Widening from Strict/Namespace-Wide to Cluster-Wide via Untrusted Template Annotations

CVE-2026-22728 at a Glance

CVE Identifier CVE-2026-22728
GHSA Identifier GHSA-465p-v42x-3fmj
Severity MODERATE
CVSS v3.1 Base Score 4.9
CWE Classification CWE-284: Improper Access Control
Affected Product Sealed Secrets for Kubernetes
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 4.9

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required High (PR:H)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-22728

To remediate this vulnerability, upgrade all affected Sealed Secrets for Kubernetes dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/bitnami-labs/sealed-secrets fixed: 0.36.0
Upgrade github.com/bitnami-labs/sealed-secrets to 0.36.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/bitnami-labs/sealed-secrets

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-22728, inspect your project dependencies for Sealed Secrets for Kubernetes:

inspect dependencies for github.com/bitnami-labs/sealed-secrets

Analyze the terminal output to locate any version of Sealed Secrets for Kubernetes in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.36.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-284: Improper Access Control, where the product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. In Sealed Secrets for Kubernetes, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

This report shows a scope-widening issue in the rotate (re-encrypt) flow: the output scope can be derived from untrusted `spec.template.metadata.annotations` on the input sealed secret. If a victim sealed secret is strict- or namespace-scoped, an attacker who can submit it to the rotate endpoint can set `sealedsecrets.bitnami.com/cluster-wide=true` in the template metadata and receive a rotated sealed secret that is cluster-wide, enabling retargeting (`metadata.name`/`metadata.namespace`) and unsealing to recover the victim plaintext. ## Relevant Links (Pinned) - Rotate handler uses `NewSealedSecret(..., secret)` after unsealing: https://github.com/bitnami-labs/sealed-secrets/blob/946bc048f3407117c837da6e4300686522d4c4eb/pkg/controller/controller.go#L560-L606 - Scope derivation reads secret annotations (`SecretScope`): https://github.com/bitnami-labs/sealed-secrets/blob/946bc048f3407117c837da6e4300686522d4c4eb/pkg/apis/sealedsecrets/v1alpha1/sealedsecret_expansion.go#L112-L122 ## Root Cause The rotate flow unseals the input sealed secret to a `Secret`, then reseals using `NewSealedSecret(..., secret)`. Because `SecretScope(secret)` is computed from secret annotations, and unsealing applies `spec.template` metadata onto the unsealed secret, an attacker can influence the scope of the rotated output by mutating template annotations on the rotate input. ## Attack Path 1. Attacker obtains a victim `SealedSecret` object (for example via read access to resources or logs) and can submit it to the controller rotate endpoint. 2. Attacker sets `spec.template.metadata.annotations.sealedsecrets.bitnami.com/cluster-wide=true` (and optionally retargets name/namespace fields). 3. Rotate returns a resealed, cluster-wide sealed secret that is no longer bound to the victim name/namespace. 4. Attacker unseals the rotated output in their chosen namespace/name to recover the victim plaintext. ## Proof of Concept Setup + run: ```bash unzip poc.zip -d poc cd poc make test ``` Canonical output (excerpt): ``` [CALLSITE_HIT]: pkg/apis/sealedsecrets/v1alpha1/sealedsecret_expansion.go:112 SecretScope [PROOF_MARKER]: scope_widened=true rotated_scope=cluster-wide ``` Control output (excerpt): ``` [NC_MARKER]: scope_widened=false strict_scope_preserved=true ``` ## Fix Accepted When Rotate preserves the original sealing scope and does not allow scope widening based on untrusted template metadata; strict or namespace-wide inputs cannot produce cluster-wide outputs. [poc.zip](https://github.com/user-attachments/files/25080027/poc.zip) [PR_DESCRIPTION.md](https://github.com/user-attachments/files/25080028/PR_DESCRIPTION.md) [attack_scenario.md](https://github.com/user-attachments/files/25080029/attack_scenario.md)

CVE-2026-22728 Affected Sealed Secrets for Kubernetes Versions

1 component(s)
Fixed Versions:
0.36.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/bitnami-labs/sealed-secrets
Go
< 0.36.0
0.36.0

References

Frequently Asked Questions

What is CVE-2026-22728?
CVE-2026-22728 is a security vulnerability in Sealed Secrets for Kubernetes involving Rotate API Allows Scope Widening from Strict/Namespace-Wide to Cluster-Wide via Untrusted Template Annotations under CWE-284: Improper Access Control.
Which Sealed Secrets for Kubernetes versions are affected?
Affected versions include releases prior to 0.36.0 across affected packages: github.com/bitnami-labs/sealed-secrets.
What version fixes CVE-2026-22728?
Upgrading to 0.36.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/bitnami-labs/sealed-secrets affected?
Yes, github.com/bitnami-labs/sealed-secrets is affected in releases prior to 0.36.0. Upgrade your dependency to 0.36.0 or later.
What is the CVSS score of CVE-2026-22728?
CVE-2026-22728 has a CVSS v3.1 base score of 4.9 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-22728?
CVE-2026-22728 is classified under CWE-284: Improper Access Control (The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.).
How can I check Go dependencies for CVE-2026-22728?
Run the dependency tree command: 'inspect dependencies for github.com/bitnami-labs/sealed-secrets'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-465p-v42x-3fmj",
  "modified" : "2026-02-26T22:49:14Z",
  "published" : "2026-02-26T22:49:14Z",
  "aliases" : [ "CVE-2026-22728" ],
  "summary" : "Sealed Secrets for Kubernetes: Rotate API Allows Scope Widening from Strict/Namespace-Wide to Cluster-Wide via Untrusted Template Annotations",
  "details" : "This report shows a scope-widening issue in the rotate (re-encrypt) flow: the output scope can be derived from untrusted `spec.template.metadata.annotations` on the input sealed secret.\n\nIf a victim sealed secret is strict- or namespace-scoped, an attacker who can submit it to the rotate endpoint can set `sealedsecrets.bitnami.com/cluster-wide=true` in the template metadata and receive a rotated sealed secret that is cluster-wide, enabling retargeting (`metadata.name`/`metadata.namespace`) and unsealing to recover the victim plaintext.\n\n## Relevant Links (Pinned)\n\n- Rotate handler uses `NewSealedSecret(..., secret)` after unsealing: https://github.com/bitnami-labs/sealed-secrets/blob/946bc048f3407117c837da6e4300686522d4c4eb/pkg/controller/controller.go#L560-L606\n- Scope derivation reads secret annotations (`SecretScope`): https://github.com/bitnami-labs/sealed-secrets/blob/946bc048f3407117c837da6e4300686522d4c4eb/pkg/apis/sealedsecrets/v1alpha1/sealedsecret_expansion.go#L112-L122\n\n## Root Cause\n\nThe rotate flow unseals the input sealed secret to a `Secret`, then reseals using `NewSealedSecret(..., secret)`.\n\nBecause `SecretScope(secret)` is computed from secret annotations, and unsealing applies `spec.template` metadata onto the unsealed secret, an attacker can influence the scope of the rotated output by mutating template annotations on the rotate input.\n\n## Attack Path\n\n1. Attacker obtains a victim `SealedSecret` object (for example via read access to resources or logs) and can submit it to the controller rotate endpoint.\n2. Attacker sets `spec.template.metadata.annotations.sealedsecrets.bitnami.com/cluster-wide=true` (and optionally retargets name/namespace fields).\n3. Rotate returns a resealed, cluster-wide sealed secret that is no longer bound to the victim name/namespace.\n4. Attacker unseals the rotated output in their chosen namespace/name to recover the victim plaintext.\n\n## Proof of Concept\n\nSetup + run:\n\n```bash\nunzip poc.zip -d poc\ncd poc\nmake test\n```\n\nCanonical output (excerpt):\n\n```\n[CALLSITE_HIT]: pkg/apis/sealedsecrets/v1alpha1/sealedsecret_expansion.go:112 SecretScope\n[PROOF_MARKER]: scope_widened=true rotated_scope=cluster-wide\n```\n\nControl output (excerpt):\n\n```\n[NC_MARKER]: scope_widened=false strict_scope_preserved=true\n```\n\n## Fix Accepted When\n\nRotate preserves the original sealing scope and does not allow scope widening based on untrusted template metadata; strict or namespace-wide inputs cannot produce cluster-wide outputs.\n\n[poc.zip](https://github.com/user-attachments/files/25080027/poc.zip)\n[PR_DESCRIPTION.md](https://github.com/user-attachments/files/25080028/PR_DESCRIPTION.md)\n[attack_scenario.md](https://github.com/user-attachments/files/25080029/attack_scenario.md)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/bitnami-labs/sealed-secrets"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.36.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/bitnami-labs/sealed-secrets/security/advisories/GHSA-465p-v42x-3fmj"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-22728"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/bitnami-labs/sealed-secrets/commit/d57ee4a8357d250e602b995399b525496ab688c1"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/bitnami-labs/sealed-secrets"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/bitnami-labs/sealed-secrets/releases/tag/v0.36.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-284" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-26T22:49:14Z",
    "nvd_published_at" : "2026-02-26T02:16:20Z"
  }
}