CVE-2026-47680

The source-controller is a Kubernetes operator, specialised in artifacts acquisition from external sources such as Git, OCI, Helm repositories and S3-compatible buckets. In versions 0.0.17 through 1.8.4, an actor with the ability to influence the contents of a bucket referenced by a `Bucket` resource can cause source-controller to write fetched object data to paths outside the per-reconciliation working directory. The corruption surface is bounded by source-controller's own and downstream Flux controllers' digest verification: source-controller verifies stored artifact digests during reconciliation and rebuilds on divergence; consumers (kustomize-controller, helm-controller) verify the digest of fetched artifacts and reject mismatches. These checks prevent a manipulated artifact from reaching the cluster, but an attacker can still write files anywhere the source-controller pod has permission to write. Separately, a user with permission to create or update `GitRepository` resources can cause source-controller to test for the existence of paths outside the cloned repository. Because the result is exposed via the resource's status, this allows limited enumeration of file paths on the controller pod. This surface exists only on source-controller v1.6.0 and later, where the sparse-checkout feature was introduced. This vulnerability was fixed in source-controller v1.8.5. There is no in-product workaround. Users should upgrade to a patched version. As a defense-in-depth measure for the GitRepository sparse-checkout surface, a `ValidatingAdmissionPolicy` (or a third-party policy engine such as Kyverno or OPA Gatekeeper) can be deployed to reject `GitRepository` resources whose `.spec.sparseCheckout` entries contain `..` or absolute path segments.

• CWE-23

• https://github.com/fluxcd/source-controller/commit/759bd6c451e7cc4327b38f42c8b671980165cb0e
• https://github.com/fluxcd/source-controller/pull/2054
• https://github.com/fluxcd/source-controller/security/advisories/GHSA-jjrm-hr5f-673x

Published

Sep 8, 2026

Last Modified

Sep 9, 2026

Status

Received

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-47672epa4all-client is the Java Client for epa4all / ePA 3.0 in t…6.5
• CVE-2026-47673Hono is a Web application framework that provides support fo…6.5
• CVE-2026-47674Hono is a Web application framework that provides support fo…5.3
• CVE-2026-47675Hono is a Web application framework that provides support fo…5.3
• CVE-2026-47676Hono is a Web application framework that provides support fo…5.3
• CVE-2026-47679GLPI is a free asset and IT management software package. Fro…8.5
• CVE-2026-47682CVAT is an open source interactive video and image annotatio…7.1
• CVE-2026-47683vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.…8.7
• CVE-2026-47684Sync-in Server is a secure, open-source platform for file st…7.7
• CVE-2026-47685FOG is a free open-source cloning/imaging/rescue suite/inven…8.7
• CVE-2026-47686vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.…9.9
• CVE-2026-47687FOG is a free open-source cloning/imaging/rescue suite/inven…8.7