CVE-2026-47680

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 74% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

June 5, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Sep 8, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit.
github_commit

commit 759bd6c451e7 (fluxcd/source-controller)

Fix landed in fluxcd/source-controller commit 759bd6c451e7 — awaiting tagged release

https://github.com/fluxcd/source-controller/commit/759bd6c451e7cc4327b38f42c8b671980165cb0e
github_pr

Improve path handling in source reconcilers

Fix merged in fluxcd/source-controller PR #2054 on 2026-05-19 — awaiting tagged release

https://github.com/fluxcd/source-controller/pull/2054
github Patch Available🟡 PoC Available

Improper path handling allows traversal · Advisory · fluxcd/source-controller · GitHub

https://github.com/fluxcd/source-controller/security/advisories/GHSA-jjrm-hr5f-673x

Vendor Advisories for CVE-2026-47680(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/fluxcd/source-controller—1.8.5—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 12× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-16 14:08 UTCEPSS rescore
  3. 2026-09-16 05:15 UTCEPSS rescore
  4. 2026-09-14 05:01 UTCEG score recompute
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-10 09:34 UTCEPSS rescore
  8. 2026-09-09 13:40 UTCEG score recompute
  9. 2026-09-09 13:05 UTCEG score recompute
  10. 2026-09-08 23:21 UTCEG score recompute
  11. 2026-09-08 23:13 UTCEG score recompute▲ 5.30
  12. 2026-09-08 23:13 UTCMITRE cvelistV5CVSS v3 → 5.3 · CVSS v4 → 5.3
  13. 2026-08-01 11:11 UTCEG score recompute
  14. 2026-07-26 21:53 UTCEG score recompute
  15. 2026-07-23 03:17 UTCEG score recompute
  16. 2026-06-14 23:18 UTCEPSS rescore
  17. 2026-06-13 23:00 UTCEPSS rescore
  18. 2026-06-12 23:12 UTCEPSS rescore
  19. 2026-06-05 16:57 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-47680?
CVE-2026-47680 is a medium vulnerability published on June 5, 2026. 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…
When was CVE-2026-47680 disclosed?
CVE-2026-47680 was first published in the National Vulnerability Database on June 5, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47680 actively exploited?
CVE-2026-47680 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.0% of all scored CVEs.
What is the CVSS score of CVE-2026-47680?
CVE-2026-47680 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-47680?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47680, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47680

Explore →

Is Your Infrastructure Affected by CVE-2026-47680?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs